Agile Experiences
2 likes185 views
The document discusses Diego Pacheco's experiences with various agile frameworks and practices over his career, including Scrum, Lean, Kanban, and DevOps. He outlines some of the challenges faced with early software factories and waterfall approaches, as well as issues implementing Scrum. The presentation then covers experiences and lessons learned from adopting XP engineering practices, Lean, Kanban for change management, and building the right organizational culture to support agile. Pacheco also discusses DevOps experiences in overcoming barriers between development and operations teams. The presentation concludes by considering where agile practices are headed next.
Agile Experiences
- 2. @diego_pacheco ❏ Cat's Father ❏ Principal Software Architect ❏ Agile Coach ❏ SOA/Microservices Expert ❏ DevOps Practitioner ❏ Speaker ❏ Author diegopacheco http://diego-pacheco.blogspot.com.br/ https://goo.gl/eEqvzl About me...
- 3. Agenda ❏ What agile means for us ❏ Some “Agile” Experiences ❏ SW Factories age ❏ Scrum ❏ Lean ❏ Kanban ❏ DevOps ❏ Engineering Culture ❏ Where are we going Next ❏ Agile ORG ❏ Lean Startup ❏ Holacracy ❏ Questions & Feedbacks
- 4. What is agile anyway?
- 5. Discipline
- 6. Principles
- 9. CMMI, RUP, Factory Experiences ❏ Software Factory: MPS.BR and CMMI level 2 ❏ Issues ❏ Process Focus => No Continuous Improvement ❏ Very High LEAD time ❏ Waterfall => Low feedback system ❏ Mgmt and Developers was not happy ❏ Lack of customer collaboration => Focus on Negotiation ❏ Software Quality(Tests & Refactoring) was always the first thing to be dropped ❏ Just “Functional(QA)” tests - no unit tests ❏ Focus on process rather than CUSTOMER and TECH.
- 10. Scrum issues ❏ Issues: ❏ It's hard to work with Dates ❏ Lack of POs that make calls - POs proxy problem ❏ Scrum does not work well with dependencies ❏ Daily meeting lost the value pretty quickly - focus on status ❏ Prioritization issues: Dev Stories VS Ops Tickets(ITIL) ❏ Teams often lack of proper DoD and Acceptance Criteria
- 11. XP ❏ Tech Savvy ❏ Basy Steps ❏ How we do things? Matters! ❏ Engineering Practices ❏ Spikes ❏ Refactoring ❏ Tests are important ❏ Dimensional Quality =>
- 12. Lean
- 13. Kanban Change MGMT approach
- 15. Kanban Practices
- 16. Building the Right culture
- 21. DevOps Issues ❏ 2 Contracts - 2 Mgmt schools - 2 priorities. 1 big wall! ❏ Tickets X Post its: Speed VS Stability ❏ Ops does not want learn how to CODE ❏ Dev does not want worry about STABILITY ❏ UX creates the waterfall(new Analyst) ❏ Bi-MODAL does not work for everyone ❏ Hard to change Culture ❏ Companies are not agile ❏ Sabotage ❏ Dependency kills innovation ❏ Hard to change structures
- 26. Self-Service
- 27. Software as a change agent! Software Scales way better than Process.
- 29. Whats Next?