View
964
Download
1
Category
Tags:
Preview:
Citation preview
http://www.flickr.com/photos/code_martial/4145914957/
Government Stereotypes
Low personal motivation
Context
Agile coaching efforts• Planning• Communication• Process visualization• Continuous improvement• Stakeholder management• Self-organization
the ResultsAgile made problems visibleFight for resources / priorityDisruptions made planning hard >
expectations not metBig variety of workSpecialistsNot giving good customer service
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 detail
Business 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:
READY Analysis DESIGN VALI PROD2 1
As a user I want to fill in a new reservation
As a user I want to send my reservation...
As a user I want to receive ane-mail confirmation ...
2TEST
21
TOO Low Level for
Stakeholders
TOO Low Level too
early
Not all applicable
DEV2
OKOKTOO Low Level
Improving1st Retrospective (cont’d)
• Walking the board took longer than daily standup
• Big difference in size of work items • Need for progress visualization
“A politician needs the ability to foretell what is going to happentomorrow, next week, next month, and next year.
And to have the ability afterwards to explain why it didn't happen.”
W. Churchill
Discoveries2nd Retrospective (cont’d)
• Limitations of the physical task board• Bigger teams ~ distributed• More administration ~ measuring• Progress visualization
Discoveries2nd Retrospective (cont’d)
• WIP limits + pull made things happen• People idle causes action!
WIP limits enable more cross-functional collaboration
Discoveries2nd Retrospective (cont’d)
• Still fight for resources / priorities
Why? Step out, watch from customer viewpoint
1 project asks to put stuff in queue & prioritize
What about non-project related work?
Confusing for stakeholders
The FutureFull Kanban flow? With cadance?
Product Development + Product Maintenance & Extension
Faster & smaller deployment
Recommended