It’s hard to believe agile has now been around for more than 15 years. With its introduction, teams started seeing increased output and thus a higher number of releases. With the increased number of releases came the need and implementation of Continuous Integration (CI), Continuous Delivery (CD), and eventually what we’re calling DevOps. While DevOps has increased the speed with which organizations deliver software (both through culture change and new tools) there continues to be a disconnect between development and delivery. The reason for this is often times software teams work on story ABC, however, delivery teams deliver build 1.2.3. […]
Rejoice product owners – the days of dual entry for your roadmaps are gone! No longer will you need to remember to update the roadmap when the ‘real’ plan changes. No longer will you be called out in meetings when your roadmap is out of date. No longer will stakeholders silently wonder if what they are seeing is current and you erode confidence. We’ve heard about the pains you’ve shared with us and have responded.
I’m working with a customer who needed to put their “as-is” product use cases into VersionOne Lifecycle. After looking at several options, we decided to use a combination of planning levels, portfolio items, and user stories to create the customer’s complete product use case repository.
How does your organization decide what features to work on for the next release? Do you let the clients vote and then order the portfolio by those results? Does the loudest sales person get their items prioritized to the top of the list? Or is it more of a “gut feel” by the product owner?
Planning out a set of work across multiple teams during Release Planning or Program Increment (PI) Planning can raise many questions which don’t always have straight forward answers: How much work can the group take on? Should we include a buffer? How should the work be divided among the teams? How do we get everyone on the same page? Will we be able to recognize the necessary adjustments when reality begins? Terminology Evolves, The Practice Holds Firm Release Planning is an age-old agile practice of defining the work for an upcoming release. Over time as organizations have become more agile, […]