On maintenance, killing projects, and what it says on the tin


Happy 5W-1h Sunday.

Here’s your dose of What? Who? Where? When? Why? How?, a curation of articles, podcasts and videos that piqued my curiosity this week.


WHAT does it say on the tin?

In 1935, Alan Turing came up with a theory for software which led to the study of its creation. Growth in the field moved the industry to evolve, with Margaret Hamilton coining the term ‘software engineering’. Even in the 1990s, IT system quality was still an adventure. Who knew when or where the system was going to break?

Does it do what it says on the tin? | Joe Newbert (Text at Newbert’s Blog)

WHO am I talking change with?

How do you introduce change management in conversations? And how does your audience shape the discussion? Building buy-in and support for change management requires pivoting the conversation away from yourself and toward your specific audience, clearly relating the benefits to what matters to them.

How to Introduce Change Management by Audience | Tim Creasy (Text at Prosci)

WHERE do Agile coaches make an impact?

Several years ago at a monthly meetup, we asked coaches what evidence they could share about the impact of coaching.  I think I actually asked, “When the budget cuts come, what defence have you got against being first out the door?” The Agile and Lean coaches didn’t really have a solid answer to hand.

Is there any evidence that Agile coaches make things better? | Craig Brown (Text at Better Projects)

WHEN should we call the project quits?

Fail fast, the adage goes, and move on to the next big idea. Most innovation managers know that few of their initiatives will succeed, so they keep multiple projects running at the same time and create processes for quickly separating winners from losers.

Research: How to Get Better at Killing Bad Projects | Ronald Klingebiel (Text at Harvard Business Review)

WHY should I consider a business analysis maintenance role?

If you are offered a role as a software business analyst (BA) to look after software/products/projects in maintenance mode, don’t freak out. Why would you freak out? Because someone would tell you that the best thing to be is a BA for a project which is about to start or is in motion.

What is a Maintenance Business Analyst Role? | Pushkar Anand (Text at Modern Analyst)

HOW should I go about requirements elicitation?

The work of a business analyst is not possible without having proper and complete information and a clear picture of requirements within an organisation. Obtained information and requirements lay a foundation for determining a solution that enables value to the organisation. 

Introduction & Guidance To Elicitation And Collaboration | Jerry Nicolas (Text at Business Analyst Mentor)

And, as always, please give feedback on Twitter. Whose piece above stood out for you? What would you like more or less of? Other ideas? Please let me know. Just send a tweet to @joenewbert and put #5W1H at the end so I can find it.

Keep growing.


P.S. How are you setting yourself apart?