Timeline for Why does our Sprint Planning not align with our original Release Plan?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 18, 2013 at 12:14 | comment | added | Doug B | In hindsight it might have been better to have said "We are 75% confident we can hit date X, and are 95% confident we can hit date Y", or something to that effect. At the end of the day you can avoid a lot of problems if you under-promise and over-deliver rather than the other way around. | |
| Jul 18, 2013 at 10:47 | comment | added | ramu | The team had estimated the stories during the release planning meeting at the begining of the project based on their best understanding at that point of time.The team had to do that because product management had to commit to the client on when the sofware will be shipped.As a Project Manager gave an end date to product management with 75% confidence level. In Sprint meetings with more information the team estimation of story points is bloated up because the stories were split into multiple stories and story points shooted up for each story which resulted in pushing the end date | |
| Jul 17, 2013 at 15:00 | history | answered | Doug B | CC BY-SA 3.0 |