PRODUCT ROADMAPS - Set Direction for Success

Seema Sonkiya
Product Owner
iZenBridge Consultancy Private Limited

Most of the time creating a roadmap is painful work for product owners. Our stakeholders want clarity on what features product will deliver and at what dates? There is less focus on what is customer need and what is a vision of the product?
This workshop will engage each participant and they will work together to understand how to focus on outcomes rather output in developing a product roadmap and how to set a clear direction.


Outline/Structure of the Talk

- Set the stage - An introduction of the product roadmap and let participants know what is crucial in developing product roadmap. It would be an interactive discussion
- A case would be given to participants to engage and explore product vision. Now there could be many ways to achieve a product vision. We have a habit to directly jump on a solution to a customer problem and start focusing on features. This workshop will assist how a participant can engage customers and other stakeholders to get product vision and customer themes.

Here is the detailed insight of the session:

I will put product requirements as a customer, and the workshop teams will discuss and come up with a:
-Key customer problems
- Business objectives related to key customer problems
- Components of a Roadmap
- Challenges of keeping Product Roadmap up to date with:
changing Business Situations & Objectives,
external Pressures,
and with special requests
- How to respond to the evolving situations in revising Roadmap

1. In teams, different roles will be identified, few will belong to the product team, and others will take part as different stakeholders. Product Team will gather inputs from stakeholders.
2. Different Case Studies will be given to different teams
3. I will be around to observe and to provide clarification whenever needed.

  1. Once I see that product Roadmap is about to finish by groups, I will put the situation of changed Business Goals and will request them to update Product Roadmap. Here I will give an idea, where and how Product Roadmap components needs have to be changed. I will invite a small discussion about the impact of changes to product roadmap and the release plan.

One of the representatives will be invited to share how they come up with vision, key customer problems, product roadmap, and finally roadmap. Also, how they responded and reflected changed Business Situations in the Product Roadmap.

In closing, I will summarize to communicate how a roadmap can get customers excited about product direction.
Here is the tentative time breakup:
- Initial Discussion to understand audience and give them an idea to go ahead with case study: 15 MInutes
- Team Formation and Case Study Discussion with stakeholders and Roadmap Development: 15 Minutes
- Teams Presentation: 10 Minutes
- Summary of Product Vision and Roadmap Including final Q&A : 5 Minutes

Learning Outcome

- Does Product Roadmap equal to release plan or project plan?
- What are the critical components of a Roadmap?
- Do customer needs equal to features?
- Is there any template to create product roadmap?

- How to respond to changing business situations for the Product Roadmap

Target Audience

product managers, product owners, Development team members, Business Doers, transformation consultants

schedule Submitted 1 year ago

Public Feedback

    • Nitin Mittal

      Nitin Mittal - A mindset Transformation journey - How are we changing behavior on the ground

      45 Mins

      Mindset and Culture change is at the core of agile and DevOps adoption. While we all know it’s importance, there is no single approach or process to make this change happen.

      We have embarked on a mindset transformation Journey at our workplace.

      In my session I will cover pragmatic approach of bringing in mindset and culture change. An approach which we are adopting in our workplace and seeing the change resulting in multifold benefits. You will learn Echo system of Mindset, Culture and Behaviors and leave the session with multiple ideas and an insights on how to make cultural and mindset shift in your organization.

    • Ranjith Tharayil

      Ranjith Tharayil / Jeffson Dsouza / Mahesh Varadharajan - Dojo Delivery Agility : The Art of Crafting High Performing Teams

      45 Mins

      Micro Abstract: A single demo is worth a 100 meetings

      Dojo Delivery Agility is an abstract (non prescriptive ) Agile product development framework built to augment the Dojo way of working across teams. Built on the concept of hyper sprints, Dojo Delivery Agility enables teams to build “E-shaped” skills to unlock the next level of productivity and predictability. Dojo Delivery Agility as a process framework is crafted on the fundamentals of SCRUM, XP, and Agile Dojo.

      Agile Dojo is well known coaching strategy but this talk is about our experiences with respect to our experiments with Dojo as a product development framework across different domains. Our experiences include mostly learning from failures and successes and hence the session would be driven by case studies. We will also be discussing our studies on teams that adopted Dojo as a way of working which showcased substantial improvement in predictability, productivity, and technical agility. We will also touch upon how Dojo acted as a constructive constrain to triggers change for good. Last but not the least we will also discuss our SENSI program which helped us scale our Dojo Delivery Agility capability of practitioners

    • Satya Jyoti Yellapantula

      Satya Jyoti Yellapantula - Product Backlog Refinement - The UnSung "Hero"

      45 Mins

      When we speak of Scrum framework, the 3-3-5 structure is imbibed in our memories. The 3 roles, 3 Artifacts and 5 events are known to all. When we talk of processes, learnings, improvements, most of the teams confine themselves within the limits of 3-3-5. How many of us realize Product Backlog Refinement lays the foundation of the Release/Sprint planning. Do teams really give the right importance to PBR, or do they feel it distracts them from the their current sprint work? How can PBR be more effective and help teams plan better, be more predictable, help in being more productive, and encourage the teams to take calculated risks when needed - these are few of the things we would discuss during the session.

      We conducted with more than 40+ Scrum Masters across the globe in one of the organizations I was associated with, to collect the challenges w.r.t PBR. During this session, we will discuss those practical challenges, and tried and tested recommendations.

    • Ranjith Tharayil

      Ranjith Tharayil / Mahesh Varadharajan - SHE QC ideation, a story grooming technique

      45 Mins

      SHE QC is an effective technique to structure your never-ending grooming meetings. The SHE QC style of grooming is an effective style for complex stories especially when we need different viewpoints to be considered. One can use the technique to structure their 3 Amigo discussion to elaborate and define scenarios. It is a highly structured & time-boxed grooming technique used by advanced engineering teams to learn, define what needs to develop and remove any second-degree ignorance - “I don’t know I don’t know something”. The technique enables teams to groom stories in a more continuous manner and ideal for teams operating in a hyper sprint mode.