Skip to main content

Project Inception: The Forgettable Mnemonic



This blog is designed to help me to remember the thing that I'd created a mnemonic about, so I didn't forget. I did forget it, immediately after presenting on the topic. So, writing it down should help.

So, when you want to kick off your project in an expedient but sensible manner try my charming mnemonic, IWOOWI (pronounced I-WOO-WI):


Iterate, Man! 
If your engineering iterations are two weeks then limit your project inception to that period too. There is an excellent chance that more thinking than this will only ever beget more and more thinking at this point.



Who Feels What About Which or Whom and Why? 
I know, this is awkward as you'll need to ask about feelings. Let me put it this way, how many rational decisions were made on your last project? Humans are inherently irrational, place no expectations of sensible decisions on your stakeholders. Discovering how they feel about a feature/deadline/other stakeholder is more useful information than what they know. As it will be what they think they know.


Obvious? 
The software development world does so many things which don't have an obvious reason why they should be done. Not every reason is obvious. Being non-obvious is sign. When the bus is about to run us over it is obvious that we should take evasive action. If your project/product has no obvious reason for existence, ask the question.



Optionality 
In the beginning you will meet those who wish to confirm, finalise and nail down each and every aspect of your project. It is a tempting thought. Until the entropy of time gets involved. Resist these nail-downers and approach your project kick off with a view to increase your options, not narrow them.
Why is this so hard? - If your project kick off is unforgiving, then what you shouldn't do is doggedly push on with your plan to get under way, you should ask the question of why this is so. Perhaps some of the previous parts of this mnemonic are in play, most likely your stakeholder engagement is not what it might be or the critically important project that you are about to embark on is not, well, all that important.



If stuff built > 0 && {insert kick off document name} !signed off 
This test provides an examination of how effective your current process really is. If the kick off document that you have slaved over is still awaiting a rubber stamp 10 weeks into the project, I think you know how keen your stakeholders are on both your project and the way you've handled the kick off phase.

This mnemonic summarises (for me) the key to an effective project inception, setting the tone and direction of the humans involved. Technology and process plays a part but I believe (and experience tells me) that your humans having a similar vision at the same time is crucial for successful delivery.

Comments

Popular posts from this blog

Testers Guide to Myths of Unit Testing

One area that testers might be able to enhance their contributions to software development teams is how we perceive and contribute to unit testing. I believe testers busting their own illusions about this aspect of building something good would bring us much closer to developers, and help us realise what other layers of testing can cover most effectively.

Also, I want to do a talk about it, so I figured I would test the premise, see if potential audiences were into it. I put this on Twitter:
Working on a talk about what testers might believe about unit #testing & how we interact with developers creating unit tests. Any challenges/additions for my list below? #development#agilepic.twitter.com/4oT5HE4qs3 — Ash Winter (@northern_tester) December 19, 201730 replies with ideas tends to indicate that people might be into it. 
The ListI thought, as my final blog of 2017, I would provide a super useful list of the myths and legends we as testers might believe about unit testing:
That developer…

Why do Testers become Scrum Masters?

It was late and I was stuck on a train, so I pondered on the question of why do testers often (in my experience) become Scrum Masters. Its a very dear question to me, as its been a big part of my career journey In fact, I've been there and back again. Tester to supposed-to-be-testing-but-being-a-Scrum-Master to Scrum Master, back to Tester and very happy thank you.

I encapsulated my reasoning in the following:
Long train delay, decided to think about a thing. :) Why do testers (in my world anyway) often become Scrum Masters? #testing#agile#scrumpic.twitter.com/FGGXFiBGz1 — Ash Winter (@northern_tester) February 13, 2018The tweet got a lot of traction, and generated a couple of interesting threads which made me think.
Great list. Personally I think that as a scrum master I can add even more towards the goal of quality. — Christian Kram (@chr_kram) February 13, 2018 Perhaps part of the reason for the transition is a growing appreciation of where quality has its roots? If testing i…

Wheel of Testing Part 3 - Applications

I've only had to quit two jobs to finally find the time to finish this blog series. Winning at life. If you need reminders (like I did) check out Part 1 and Part 2 before reading on...

After the first two blogs regarding the Wheel of Testing, I was delighted to receive a few requests for the wheel itself, which got me thinking about applications of it, beyond what its original intent was, which I've explored in detail in part 1 of this series of intermittent blogs. Most models need a little air time to show their value, in software development we crank out models all the time, but I'm not sure how many get used. I am inspired by models such as the "Heuristic Test Strategy Model" by James Marcus Bach, as I have used it and seen the benefits it has brought for my clients, particularly the ability to ask questions. So, I wanted to create a model which has a number of use cases, both real and imagined:

Helping to unlocking a career in testing which may be stuck

It is no…