- Product Backlog
- User Story Workshop
- What is BV for this project?
- Priority Poker –> BV points
- Planning Pokers –> Story points
Then we have to talk about some other things, and see where we go. For example, often we find that the skill sets involved need to change (as we now see the product or project differently).
Then we have to do Release Plan Refactoring every sprint, until the number are decent.
As I have said elsewhere, the real value in doing this is NOT the ‘crappy’ estimates that the team arrives at after the initial release planning. It is that everyone is now ‘on the same page’ about what the elephant is. At least a whole lot more than we ever had before. And I find that tremendously valuable.
Note: If they do really bad or no release planning, I think it ups the chances a lot that the stories are not small enough. This means that lots of stories just can’t get to done, done in the sprint. So, good release planning is linked to having good sprints! Now, this problem (stories too big) can be fixed later, but god, all hell is breaking loose then.