Thanks for your feedback Priya. Personally, I like to create a release burndown using simple tools like paper and pen or an electronic spreadsheet, preferably together with the development team. The latter helps with developing a realistic forecast. Hope this helps!

Hi Barak,

Thank you for sharing your feedback and question. As you are developing a new product, I suggest that you first create an initial product strategy as part of your product discovery work and validate it, for example by conducting more user interviews or carrying out direct observation. Second, derive a product roadmap form your strategy and ensure that it is actionable. Finally, use the roadmap to stock the initial product backlog. I wouldn’t worry too much about creating a product portfolio roadmap, unless the new product extends an existing portfolio and needs to be aligned with the other portfolio members.

Hope this helps!

1. What kind of data should I suppose to write there?
2. Do I need to write only the features that I want to develop?
3. I am building a new digital product from scratch and now I am in the phase of customers and users interviews – it takes time 🙂 do I need to add this to my roadmap? I am little bit confused.

I am new in the product management world , I am coming from a software development so I don’t know how to do strategy and roadmap.

Hope you understand my issues 🙂 Thanks

Hi Kanny,

A release plan like the Release Burndown Chart takes into account three factors: the outstanding work in the product backlog (which is to be done to reach the release goal), the development team’s progress (velocity), and the rate of change in the product backlog (items being added or removed; items being re-estimated). I find it helpful to review the progress at the end of a sprint and update the Release Burndown Chart, as I describe in my book Agile Product Management with Scrum.

Hope this helps!

Thanks for sharing your question Ronny. It’s been a long time since I’ve sone some work with CMMI, and I am probably not the best person to answer your question. You can, however, happily have a fixed date and budget on an agile project if you are flexible on the scope. Assuming that the development team composition stays constant throughout the project and that you don’t require any upfront work item / task allocation, there might not be a contradiction between the CMMI requirements and an agile way of working. Hope this helps!

Hi Blake,

Thanks for sharing your question. If you have three products, then I would use a separate product roadmap for each product–unless the products are closely related and from portfolio, think of Microsoft Office, for example. In the latter case, you might find it helpful to create a portfolio roadmap that shows the products together in a single plan. I would also recommend aligning the teams with the products so that each team works on one product. This facilitates teamwork and continuous improvement. Hope this helps!