#CAPACITY PLANNING CALCULATOR PROFESSIONAL#

Teams that use velocity for planning typically base velocity ion the empirical observation of previously completed sprints. And, focus factor is not in the Scrum Guide at all. Likewise, capacity is mentioned only twice in the Scrum Guide. It is one of those things left to the team to decide what works best for them. Let me know and I'll try and provide as much info as possible.Р”Р‡irst of all, velocity is not a term used in the Scrum Guide. What are the views of Capacity planning vs Velocity planning? I've taken a Sprint Retro action to review this. The issue was more apparent during our 2week Sprints. We always seem to fall short especially given there is no true mechanism in JIRA to report this. There are growing concerns that we're not 'successful' in the amount of points we estimate at the start in comparison to the completed points at the end of the sprint. Our focus factor of 60% has been kept at 60% so where previously a dev was given 6 points to complete during a 2 week Sprint, the dev is now allocated 9points over the 3weeks. We have recently moved from 2 week Sprint cycles to 3 week Sprint cycles so that we enough breathing space to complete the governance for the production environment, resolve any bugs/issues within the additional time and tackle technical debt. This is currently done on a capacity basis working on a focus factor of 60%. Our stakeholders actively like to understand the output of story points in advance of a Sprint. We've adopted Agile/Scrum methodologies for some time now and are currently on our 53rd Sprint. I'm currently the Scrum Master of a 10 developer strong team.

#CAPACITY PLANNING CALCULATOR PROFESSIONAL#

Search Professional Scrum Certificate Holders.Professional Scrum with User Experience.Professional Agile Leadership - Evidence-Based Management.

Capacity planning calculator