The Hard life of Agile Coach Project in a ruin
•Download as PPT, PDF•
0 likes•3,076 views
Slides from my presentation at New Trends in Project Management 2017
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Similar to The Hard life of Agile Coach Project in a ruin
Similar to The Hard life of Agile Coach Project in a ruin (20)
More from Jakub Drzazga
More from Jakub Drzazga (9)
Recently uploaded
Recently uploaded (20)
The Hard life of Agile Coach Project in a ruin
- 1. The Hard life of Agile Coach – Project in a ruin
- 2. Goals
- 5. Agenda • Who is an Agile Coach? • Problems • SOLUTION
- 7. Who is an Agile Coach? • Problem solver • Levels up • Accomplishes high level quests • Is useful
- 8. Quest
- 10. Great success! • April 15th - season starts • Mobile & Web • Delighted customer
- 12. Disaster • Web part - Complete rubbish • No business value • Customer in a depression
- 14. Political map • Stakeholders • My employer – mobile part • Subcontractor – web part: • Management • Team • Serbia – new web team
- 15. Analysis • What is the problem ? • Root causes • What is success ? • All points of view
- 17. 1. Team • Subjectivization • Micro management • Motivation == „Work harder!” • Work beyond strength – 2 months
- 21. 3. Product (Ownership) • Zero business value • Poor quality • No priorities • Very High WIP • Contract negotiation over customer collaboration
- 23. Transparency
- 24. 4. Where are we ? • No Product Backlog • JIRA – Complete mess Waterfall: • "The project is 85% completed " • No working software
- 25. 4. Where will we be ? • No forecasts • Unknown regression • Commitment based on what?
- 27. 5. Inspect & Adapt • „We have no time for this” • Problems sweeped under the carpet • Blamestorming • No feedback from customers
- 29. SOLUTION • PM - out • Team stays • GOAL: BETA for friendly users
- 30. Risks • Customer cancens cooperation • The team hates us • Gigantic regression
- 32. Strategy • Customer engaged • Customer feels secure • Quickly delivered value • Ispect & Adapt
- 34. Absolute honesty • "I say how it is" • "I don’t know how it is" • The pressure of the board
- 36. Process • No iterations • Daily, Retro • Full transparency • Demo each two days
- 37. Process • Measure of success ? Working Software
- 38. Team • "Are you tired?"
- 41. Product Backlog • All knowledge we have Low hanging fruits: • Business values / Effort
- 43. Empower the team • Clear goal • Let's create a process • What is missing ? • Self-organization • Estymation != Commitment
- 45. Calm the board • Sense of security ! • Plan • What are your doubts ? • Quick win
- 47. DEMO • „First time in a year we see results!"
- 49. Together • Let's join the teams • One goal for everybody
Editor's Notes
- Project in a ruin People do not understand what Agile is Employees are frustrated
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- 65034586
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- To show how big is a task Helps PO prioritize tasks in Product Backlog PO can calculate velocity and have time horizon Team knows if something can be taken to a Sprint It is not good idea to calculate velocity for a single team member!
- The customer closes the co-operation The team hates us Giant regression
- Customer feel secure Quickly delivered value