"Breakthrough products don’t come from thinking small. They don’t come from the fear of losing ground, either. They come from thinking big and responding to change better than everyone else. "
-Janna Bastow, Co-Founder of Mind the Product and ProdPad.
An agile product roadmap revolves around desired goals and outcomes, instead of features or timelines.With an agile roadmap, you can communicate both your big picture narrative—that pie-in-the-sky vision—and the series of steps you anticipate will help you
meet that vision over time. The steps matter, but they also don’t.
Technology will change, new and unexpected markets will open up, business will boom or suddenly drop, and all of these changes will affect what you’re able to build both in the short- and long-term. You can’t exactly know what you’re going to build ahead of time, but you can plan for how you’re going to respond to change in order to keep on track with your innovative vision.
- Stage 1, the product owner identifies the product vision. The product vision is a definition of what your product is, how it will support your company or organization’s strategy, and who will use the product. On longer projects, revisit the product vision atleast once a year.
- Stage 2, the product owner creates a product roadmap. The product roadmap is a high-level view of the product requirements,with a loose time frame for when you will develop those requirements. Identifying product requirements and then prioritizing and roughly estimating the effort for those requirements are a large part of creating your product roadmap. On longer projects, revisethe product roadmap at least twice a year.
- Stage 3, the product owner creates a release plan. The release plan identifies a high-level timetable for the release of working software. An agile project will have many releases, with the highest-priority features launching first. A typical release includes three-to-five sprints. Create a release plan at the beginning of each release.
- Stage 4, the product owner, the master, and the development team plan sprints, also called iterations, and start creating the product within those sprints. Sprint planning sessions take place at the start of each sprint, where the scrum team determines what requirements will be in the upcoming iteration.
- Stage 5, during each sprint, the development team has daily meetings. In the daily meeting, you spend no more than 15 minutes and discuss what you completed yesterday, what you will work on today, and any roadblocks you have.
- Stage 6, the team holds a sprint review. In the sprint review, at the end of every sprint, you demonstrate the working product created during the sprint to the product stakeholders.
- Stage 7, the team holds a sprint retrospective. The sprint retrospective is a meeting where the team discusses how the sprint went and plans for improvements in the next sprint. Like the sprint review, you have a sprint retrospective at the end of every sprint.
In brief,An agile road-map helps you communicate your priorities in clear “what problems are we trying to solve?” terms for everyone you work with.You don’t need to know exactly what you’re working on ahead of time. It’s fine to have a fuzzy idea of what’s way out in the future and prioritize what’s coming up now.
According to the 2018 State of Agile Report, 75% of respondents adopted an agile approach within the last year, with the aim of accelerating software delivery. The results? Over 60% cited that Agile improved their time to market, project visibility, team productivity and management of changing priorities.
No comments:
Post a Comment