It's that dreaded time again. You've gathered for the sprint commitment meeting and already have a fairly good idea of what the team will be willing to commit. Your velocity is 100 story points per sprint, and over the last three sprints they achieved +/-10% against that target. You're hoping for a 95 point commitment as there is a big meeting this week that will pull the team off task.
Only you know that the product owner is going to hope for a 108 story point commitment. She's aiming to get two more stories done this sprint, one with eight points and the other with five points.
And she'll come with all the right reasons why end-users will want the added improvements sooner. Your team has CI/CD in place but
follows a release management standard of 3-sprints for a major release.
Continuous deployment wouldn't work for this organization as every release requires some manual testing that can't easily be automated, documentation for SOC-2 compliance, and end-user training that can't be performed more frequently.
