Improving1st Retrospective• WIP limits well respected –+ visualization of issues• Missing visualization of detailed tasks• Missing a planning meeting
Improving1st Retrospective (cont’d)• Needed different level of feature detailBusiness request:“Customers have to be able to fill in a reservation, send it to the planning department and get a confirmation email with pdf attachment”
Agile team would split this into:1. As a user I want to fill in a new reservation...2. As a user I want to send my reservation...3. As a user I want to receive an e-mail confirmation with my reservation in pdf attachment so that I ...
Suppose we used user stories in the flow: As a user I As a user I As a user I want want to fill want to send to receive an in a new my e-mail reservation reservation... confirmation ... TOO Low TOO Low TOO Not all Level for Level too OK OK Low applicableStakeholders early Level READY Analysis DESIGN DEV TEST VALI PROD 2 2 1 2 2 1
Improving1st Retrospective (cont’d)• Walking the board took longer than daily standup• Big difference in size of work items• Need for progress visualization