Cornel Fatulescu - Envisaged Collaboration Framework - CodeCamp 25 oct 2014
1 like765 views
This document describes the process of adopting Agile practices at a large international company with over 10,000 employees. It outlines the initial challenges, including a lack of clear vision or leadership over multiple management changes. An Agile coach was brought in to help transition the team to Scrum. The summary describes the coach's step-by-step process, which included establishing buy-in and shared understanding, defining roles and processes, and gradually handing over responsibility to empower the team as the changes were anchored into the culture.
Cornel Fatulescu - Envisaged Collaboration Framework - CodeCamp 25 oct 2014
- 1. AGILE ADOPTIONfrom the trenches Cornel FATULESCU agile coach
- 2. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Case study •Big International Group >10k employees •Top management changed severaltimes in 2 years •Building their IT Solution for 61 countries •Already a team in place of more than 10 people •Willing to work in Scrum •Project started for 2 years and nothing was released
- 3. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready It is always about change
- 4. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Leading change 1.Sense of Urgency 2.Guiding coalition 3.Vision & Strategy 4.Communicate the change vision 5.Empower Broad-Based Action 6.Generate short-term wins 7.Consolidate Gains & Make more change 8.Anchor new approaches in the culture John Cotter
- 5. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Preparations •I’ve been an observer at 2 events •Meeting –something regarding the Enterprise Architecture •Sprint Review, Retrospective, Planning •Made a proposal for a SMART step
- 6. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Preparations •As an Agile Consultant, I will help the Business Team to better prepare the next Sprint Planning, so that the team will focus on activities the event was really meant for. •Deadline: before the next sprint planning •Budget: 5 days
- 7. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Acceptance criteria: Very good Giventhe next Sprint Planning, Whenthe length of the 1st topic “What can be done during the sprint?”<1h andROTI>2 andPMand MDwill evaluate the effects of the consulting mission Thenthe result is “Very good!” andthe client will pay the rest of 60% of the order.
- 8. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Acceptance criteria: Good Giventhe next Sprint Planning, Whenthe length of the 1st topic “What can be done during the sprint?”is between 1hand 2h andROTI>2 andPMand MDwill evaluate the effects of the consulting mission Thenthe result is “Good!” andand the clientwill pay the rest of 60% of the order.
- 9. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Acceptance criteria: Mission failure Giventhe next Sprint Planning, Whenthe length of the 1st topic “What can be done during the sprint?”>=2h andPMand MDwill evaluate the effects of the consulting mission Thenthe result is “Not good!” andthe client will not have to pay the rest of 60% of the order.
- 10. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Leading change 1.Sense of Urgency 2.Guiding coalition 3.Vision & Strategy 4.Communicate the change vision 5.Empower Broad-Based Action 6.Generate short-term wins 7.Consolidate Gains & Make more change 8.Anchor new approaches in the culture John Cotter
- 11. First Step •I’ve listened •Small and quick improvements •Mediated events & conflict management •Passed the 1st evaluation (Mission finished)
- 12. Business Team Developers Sprint Backlog Sprint Planning 3.5 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 0.5 hours Developers Definition of Done Business Lead What I found? Managing Director (hierarchically responsible) Program Manager (budget responsible) Software Architect Enterprise Architect Managing Director (More technical) 2 Product Owners 1 Business Analyst Pruduct Backlog Fired Scrum Master
- 14. Leading change Vizualize Smell Change
- 15. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Leading change 1.Sense of Urgency 2.Guiding coalition 3.Vision & Strategy 4.Communicate the change vision 5.Empower Broad-Based Action 6.Generate short-term wins 7.Consolidate Gains & Make more change 8.Anchor new approaches in the culture
- 16. Second step •Communicate the change vision •Conflict management •Continued helpping the business team •Started to work a little with development team •Establish the collaboration framework
- 17. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Development Team Product Team Sprint Backlog Sprint Backlog Increment Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Developers Business Team (Area Product Owners) Business Team Business Team Business Team Developers Refinement Refinement Definition of Done Definition of Ready
- 18. Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Business Team Refinement Definition of Ready Business Team (Area Product Owners) Product Backlog
- 19. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Definition of Ready Functionality has the following attributes: •Summary •Description in User Story format •Acceptance criteria •Associated screens •Testing Data when needed
- 20. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Business team: Product Suggestions flow Chief Product Owner List of Suggestions (or Large User Stories) TODO In Progress Peer Review Ready for inspection during Sprint Review Area Product Owners
- 21. Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Development Team Product Team Sprint Backlog Sprint Backlog Increment Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Developers Business Team Business Team Business Team Developers Refinement Refinement Definition of Done Definition of Ready Business Team (Area Product Owners) Product Backlog
- 22. Chief Product Owner Development Team Sprint Backlog Increment Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Developers Business Team Business Team Developers Refinement Definition of Done Product Backlog
- 23. Product Backlog Chief Product Owner Development Team Sprint Backlog Increment Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Developers Product Team Product Team Developers Refinement Definition of Done Definition of Done for a User Story Each functionality is considered Done when: •All development tasks are done •All code is checked-in •All unit tests are checked-in •All unit tests pass •All code and test code is reviewed(Peer review) •All Jenkins jobs pass •All acceptance criteria pass •All functional tests are: •Executed & pass •Something missing?
- 24. Product Backlog Chief Product Owner Development Team Sprint Backlog Increment Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Developers Product Team Product Team Developers Refinement Definition of Done Definition of Done for a Sprint Each sprint is considered Done when: •All storiesand their associated tasksare done (The Sprint has a goal. During the Sprint Planning the Product Owner should indicate which stories are critical in order toachieve that Goal andconsider the Sprint Accepted or Refused) •All orphan tasks are done: •manual deploy, •End-to-end test cases, •non-functional tests pass, •etc. •Code coverage is at least 80%
- 25. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Development Team: User Stories flow Area Product Owners List of User Stories Considered Ready TODO Work In Progress APO Feedback Done Development team
- 26. Increment Chief Product Owner Area 1 Product Backlog Area 2 Product Backlog Area 3 Product Backlog In the future? Joint Retrospective 1.5 hours Development Team 1 (Feature Team ) Scrum Master Development Team 2 (Feature Team ) Development Team 3 (Feature Team ) Area 1 Product Owner Area 2 Product Owner Area 3 Product Owner Product Backlog
- 27. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready And there is more... Area Product Owners To be accepted Integration Testing ... Ready to Release Development team ... In Acceptance
- 28. Software tools VS simple tools
- 29. CPO got fired! Business team was confused
- 30. Product Backlog Chief Product Owner Sprint Planning 2 hours Sprint 2 weeks Sprint Review 2 hours Sprint Retrospective 1.5 hours Product Team Sprint Backlog Product Team Product Team Refinement Definition of Ready Leading change 1.Sense of Urgency 2.Guiding coalition 3.Vision & Strategy 4.Communicate the change vision 5.Empower Broad-Based Action 6.Generate short-term wins 7.Consolidate Gains & Make more change 8.Anchor new approaches in the culture
- 31. Third step •Step out of the project •Give the lead to another Pentalog Institute coach specialized in building strong teams •Make regular reviews (ones or twice per month)