Sprint best practices

- [Instructor] Occasionally a Scrum team…will execute a sprint…at the earliest stages of a project…that just focuses on planning…and does not produce a working product increment.…This is known as sprint zero.…I do not recommend this as a best practice.…The Scrum cycle can start with just a product vision…and a team.…While there is nothing wrong…with having a large planning component…in early sprints,…each sprint should combine planning…with pieces of functionality…that deliver business value.…

The purpose of Scrum is to maximize business value…for each product iteration.…Hardening sprints are designated…for stabilizing products by fixing quality…and performance issues.…The problem with this approach…is that it encourages teams…to produce unstable products…at the end of sprints…that do not provide expected business value…and reduce transparency about a team's progress status.…For example, it may look like a team is progressing more…than it actually has…because a product increment was released…with known issues that will have to be fixed…