Agile projects require continuous analysis

Too many agile projects fail to analyse the problem they are trying to solve because they feel analysis takes too long. All too often the decision to introduce IT is taken by well-meaning senior managers who fail to see the need for analysis or understand the problem they are trying to solve with IT.  Once the problem has been assigned to the IT department analysis can be side-lined in favour of development work and technical solution. If you give the problem to IT to solve, then they are going to look to IT to solve it!

Continue reading “Agile projects require continuous analysis”

Sliding Doors – A Tale of Two Agile Teams

Movie poster for Sliding Doors

In the 1998 movie, Sliding Doors, Gwytheth Paltrow experiences two very different storylines in parallel because of one small difference. In one version, she leaves work early, catches the tube and arrives home to find her boyfriend in bed with another women; in the alternative version, she is slightly delayed, just misses the tube, and doesn’t catch him. The movie plays both versions side by side, switching scene by scene between them.

This blog is based on a real life project, where we were asked to help automate some manual business processes. As we began exploring the problem space, it turned out that another team had also been asked to do the same, but were taking a different approach from us. While we were thinking about business and user goals, they had decomposed the problem functionally.

This story describes how these two approaches differ, particularly with the outcome, tries to explain why goal decomposition is better, yet despite this, is still relatively rare to see.

Continue reading “Sliding Doors – A Tale of Two Agile Teams”

Story Mapping – Getting the best of both worlds!

Jeff Patten’s User Story Mapping is great technique that many teams use early in the development of a solution. His book describes the process in detail, and I highly recommend it. There is also a simplified explanation in the ‘Modelling Stories and Scenarios‘ chapter of Agile and Business Analysis.

User Story Mapping solves some of the problems that Agile teams face when trying to balance the desire of the stakeholders to know details about the whole project against the needs of the Agile team to focus on the short term, high certainty requirements, and avoid big-up-front design.

The approach allows the team to expose the whole project scope in a way that is quick to do, produces enough detail (but not too much) and allows the work to be prioritised.

Stakeholders can indulge themselves in the art of the possible, exposing a breadth of capability for the solution that may far exceed the resources of the team to deliver. This is only OK if it doesn’t consume a lot of effort, or set unrealistic expectations, so it is important to manage that aspect. However, by being able to see the whole solution, stakeholders are better able to prioritise shorter term goals, and direct the team’s focus on what they want first.

Coupling User Story Mapping with a strong focus on Goals and Goal Decomposition allows teams to focus on the right things. Since User Story Mapping can allow teams to functionally decompose the problem, it is really important to ensure that the slices of user value relate to goals rather than functions. For an example the difference this can make in practise, read about A Tale of Two Agile Teams.