This question is in reference to Atlassian Documentation: Settings estimates with story points
When you are creating a plan, and you want to manage a mixed portfolio (Scrum/Kanban), Story Points is not available as an option for estimation purposes; the only options available are Days or Hours.
Story points are inherently focused on scheduling and planning on a team basis, and we use teams not only for Scrum but for Kanban as well, and we would like to manage them keeping this estimation strategy for our mixed approach.
What should I do if I want to estimate that mixed portfolio (Scrum/Kanban) using story points?
Thank you in advance for your inputs.
One option I've seen several users apply is to set the plan to story points, and configure also the Kanban teams as "Scrum" in Portfolio, with a 1 week iteration length. Then based on the Kanban teams' throughput estimate a "velocity" for how many points are achieved in a week and use this for longer term planning.
For a rough roadmap, it does not matter that much if the Kanban team's forecast is on a weekly cadence, or day-to-day as long as the rough capacity and throughput is right.
Why is this the answer instead of someone saying the feature should be built into all Agile boards? Story points are just another mechanism for estimation, so there is no reason why the estimates on tickets couldn't be used for prediction purposes. I'm going to very disappointed if this continues to be the way Atlassian addresses product demands.
An extension to the solution proposed by @Martin Suntinger is to create both a Scrum and Kanban board for the same project. Then you can manage issues through both approaches.
A couple of configuration changes I would recommend though are as follows.
By doing the above you will be able to quickly see the Story Points and use it for understanding the workload at any point in time. However, this will not on its own allow you to report or plan with Story Points it will just give you visibility during the actual day-day activity.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs