Bonus2 - Agile Project Planning & Delivery

Apuntes

Illustrating Iterative Build Analyzing Release Planning ▪ Release in the traditional approach is fixed in terms of scope, and usually in time too, but could be shifted if necessary. ▪ In the Agile approach, you fix the Release, but you're not fully sure yet about what will be released, as needs and complexity can change. Over time, the better teams can predict, the clearer your Release will be, but still it can change based on requirements. ▪ The Value-Driven approach puts the focus on the Customer success. ▪ The Plan-Driven approach puts the focus on the Project success. ▪ Starting to plan a Release, several pieces of information are needed. The Sprint length has to be clear to schedule potential Releases. ▪ Furthermore, the Initial Backlog has to be built up, on which the teams can then perform a first high level estimation and prediction to get a first view on what could be delivered in which time frame. o Therefore, the Scrum Team needs a first understanding of their velocity (speed). o The Product Owner needs to decide what the minimal viable product is supposed to be in order to be released. o At the beginning, this is all a bit vague and only estimated, but it will become mo...