1 / 44

When Agile goes bad...

When Agile goes bad. How to stay calm and move forward. Sebastien Lambla. Founder of . Helping people achieve greatness. seb@serialseb.com - @ serialseb – http://serialseb.blogspot.com. A company becomes agile as a whole. The organization. Watch out for. High turnover

kamana
Download Presentation

When Agile goes bad...

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. When Agile goes bad... How to stay calm and move forward

  2. Sebastien Lambla Founder of Helping people achieve greatness seb@serialseb.com - @serialseb – http://serialseb.blogspot.com

  3. A company becomes agile as a whole The organization

  4. Watch out for... • High turnover • High documentation environment

  5. Dealing with the sceptics Managers & ctos

  6. “Engineers are not agile! And they build planes! And they fly!” Boeing and Airbus are Lean companies.

  7. “We have a culture of working hard” Measure and show what happens with long hours

  8. “Agile proponents are socialists. We want superstars!” Heroes != Talent

  9. “In waterfall, I have a full one-year ahead plan. I need that for my budget” The budgets have always been estimates. That’s not changing...

  10. “Agile is just an excuse for cowboys development” Business-focus and releases, and a structured approach to development

  11. Choosing a project

  12. “You can’t do agile for fixed price projects” Usually followed by...

  13. “Scope, resources and release dates are fixed!” Are they?

  14. Building your project team

  15. Accountability

  16. The Developers

  17. Don’t impose a methodology. Build a trust relationship.

  18. Heroes Detect and address early

  19. The business, the stakeholders, the sponsors, their proxies, etc. The customer

  20. The proxy: “I can’t make that call, need to discuss it” Proxy without authority is an impediment

  21. Manager managing something The Scrum Master

  22. “I’m your boss” Don’t manage people, manage issues. Leadership over control.

  23. “We need to take what will work for our organization and blend it with its current practices” You should, but you can’t. Not at the beginning anyway.

  24. Agile is like cooking • Learn the recipeThe Checklist step • Grab other people’s recipes • Blend “The final stage—if you ever get there—is a level of fluency and intuitiveness where you can't say what you're doing, but you kind of borrow and blend” - Cockburn

  25. Workshop Iteration 0

  26. The workshop

  27. Time, estimates, cards, points, poker game etc. The Planning

  28. “just write it”

  29. The Scrum Master writes and distribute tasks Iterative waterfall != agile

  30. Development The iteration

  31. “We’re stopping the SCRUM temporarily because we know exactly what needs to be done” Except when you don’t.

  32. “We can’t do CI, it doesn’t work with our source-control repository” Change the tools, not the practices

  33. “It’s done, except for a bit of data integration” Done != Done Done

  34. The Daily standup

  35. People sit down

  36. People have conversations

  37. “Can I talk now?”

  38. Building from experience The Retrospective

  39. “It’s John’s fault.” The team succeeds or fails as a unit.

  40. “What do you mean we write less than perfect code?” Charge interest to your technical debt!

  41. The release party

  42. “The stakeholders are not coming...” Ask the hard questions

More Related