Timeline for What is bad to have sprint review before finishing sprint?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 14, 2022 at 12:20 | comment | added | Thomas Owens♦ | @BestAboutMe I'd also say that you shouldn't have any tasks done between the review and the end of the Sprint. Read my last paragraph. The team should plan their work around achieving their Sprint Goal and getting the work done before Sprint Review. The time between Sprint Review and Sprint Planning should focus on refinement (particularly with an eye toward Product Backlog changes made in Sprint Review), skill building and training (to become a more cross-functional team), or even be time off to rest or do things outside of work (to help maintain a sustainable pace). | |
| May 14, 2022 at 12:17 | comment | added | Thomas Owens♦ | @BestAboutMe The timeboxes that I name are right out of the Scrum Guide. The Guide does say that "the event is usually shorter" for shorter Sprints, but that doesn't change the maximum timebox. In my experience, teams usually aim for proportional length events - a 2-week Sprint would have a 2-hour Sprint Review, 1.5-hour Sprint Retrospective, and a 4-hour Sprint Planning. Either your team is very, very efficient and effective at completing the events or you're probably missing the intention of the events and not hitting the objectives. | |
| May 14, 2022 at 7:15 | comment | added | BestAboutMe | As we have 3 developers, 2 weeks a sprint so the review is maximum 30 minutes, retrospectives are 1 hour and sprint plannings are also 1 hour! You mean 8h is for a PI planning I guess. How to call this tasks that are not done during the review but will be done tomorrow morning before the end of the sprint ? Should we show them to stakeholders ? | |
| May 13, 2022 at 12:28 | history | edited | Thomas Owens♦ | CC BY-SA 4.0 |
added 542 characters in body
|
| May 13, 2022 at 10:01 | history | answered | Thomas Owens♦ | CC BY-SA 4.0 |