By Nick Butler
Choose our next topic – Vintage image created by Dragana_Gordic – Freepik.com
We were tossing up what to write about next on the blog and thought, why not ask the people who read it? So we presented a list of topics we’ve been thinking of covering and asked people to let us know which one you’d like us to tackle next.
It was a close run thing but the winner, with 33% of the votes, was: 5. Prioritising user stories
So here is your review of Prioritisation tools and tips for Agile projects.
It’s generally asking for trouble to have more than one Product Owner on an Agile project, but sometimes it just can’t be avoided. This case study would look at what we’ve learned about how to work when it’s the only option available.
We’ve found a number of ways you can run a successful project even when the product owner and the team are in different towns (or even countries).
A key part of our just-in-time planning is the mid-sprint meeting to groom or refine the backlog so it’s ready for the next sprint. You’ll learn what you want to get out of your product backlog refinement meeting, and the best way go about it.
Retrospectives are regular meetings where the team reflects on and reviews its practices, adjusting them accordingly. Here at Boost we see them as a powerful tool for continuous improvement and are always looking for new ways to get more out of them. We’ll cover the underlying principles and some of our favourite approaches.
In Agile projects, prioritisation isn’t something you do once and lock in for ever. As you learn more about what your users need, you often have to adjust your ideas about which user stories will deliver the most value, most quickly. We’ll look at when and how you can set these priorities.
There are all sorts of ways you can estimate the amount of effort needed to complete a user story. It’s an important skill that can help create a shared understanding of each piece of work. We’ll look at the pros and and cons of some of our favourites.
What criteria need to be met before a story is complete and can be accepted by the Product Owner as done. Acceptance criteria are a way of adding enough detail to a story that the people working on it will know when they’ve hit the mark. Learn who comes up with acceptance criteria and how to go about it.
