As I couldn't end the completed sprint on time, I was forced to start the next sprint retroactively for a past date there by starting it 2 days after the scheduled date. When I ran the velocity chart, I saw that although our delivered velocity was decent, our committed velocity was terrible. Can I attribute this to the delay in starting the sprint? If yes -
1. How do i know how much velocity I'm committing in such cases where there is a delay in the sprint?
2. My stakeholders have questioned this & I'd like to genuinely point out to them the root cause.
When to use CSV importer When managing your processes in Jira, there are many occasions where you need to create a lot of tasks. Creating them one by one will cost you a lot of time and effort and i...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event