Information Product Roadmap

Ralph Hughes [[ken??? ]] in his book [[????]] discusses the use of a roadmap during the [[initiaiton phase]] to allow the stakeholders to prioritise the development in the upcoming sprint interations.

We have found this concept is great and we use the following Information Product Roadmap template as a way of visualising the results:

[[info Lego block roadmap]]

There are two key sections in this diagram:

1. The top section shows the the Information product prioritised to be delivered and when.
2. The bottom section shows a number of high level capabilities that will be delivered during the sprint iteration.  Importantly it shows the visualisations that will be delivered at the end of the iteration.

S0me key points about this roadmap diagram:

• Each Lego tower represents a sprint integration
• The towers are stacked to show that we are iteratively building out the environment and will get reuse of the deliverables from the previous iteration in future iterations
• An Information Product may take multiple interations to be delivered fully, so we colour code each Informati0n Product lego piece differently to show when a Information Product spans multiple sprint interations.

There are a number of benefits to using this diagram.

== visability

It provides a very visible view of when an Information Product is planned to be delivered.

This provides a powerful ??

It also allows the development team to be able to constantly look ahead and decide if they can do anything within the current sprint iterations that will make their lives easier in the future sprint iterations.

[[put not a wall somewhere, would be surprised how often you start pointing at it]]

== Change, change and more change

Priority for the Information Products will often change and will change often.

• This may happen because a new business priority emerged that requires a change in the order the Information Products should be developed
• It may be due to a Information product that was previously high priority no longer being needed, due to a change in business process or an alternative solution having been found
• During the current sprint iteration additional requirements may have been identified for the Information Product currently under development and this may required the use of an additional sprint iteration to deliver
• Additional a don unexpected complexity may have been identified in the current sprint that requires the Onformation Product development to extend into the next sprint iteration

This roadmap provides a great visual marker to enable a discussion to be had about the impact of these changes.  Once agreed the roadmap can be updated and made visible to all the stakeholders so they can see what has been agreed.

The roadmap diagram is

== Visualising success

[[show what has been delivered over time]]
== mapping to waterfall reporting process
[[map milestones to waterfall reports]]

== Technical Sprint

[[put a block in every 4 sprints]]

== Prioritisation process
== Information Product Size

[[no info product can more than 3 sprints]][[toio big, to unweidly]][[other parts of the business will get dissatisfied as they have to wait to long]]