ContextWhy me?A man without government for 327 days!
One month ago in PolandA man without government for 291 days!
the ResultsAgile made problems visibleFight for resources / priorityDisruptions made planning hard > expectations not metBig variety of workSpecialistsNot giving good customer service
Need for ChangeFocus was too narrow suboptimizing input WE output THEM THEM
Kanban adoption1 pilot productHow do we start? “Draw the workflow!”
Kanban adoption1 st attempt
Kanban adoption2 nd attempt
Kanban adoptionInitial workflow
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