Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

of

How to Reboot Your Agile Team Agile 2017 Slide 1 How to Reboot Your Agile Team Agile 2017 Slide 2 How to Reboot Your Agile Team Agile 2017 Slide 3 How to Reboot Your Agile Team Agile 2017 Slide 4 How to Reboot Your Agile Team Agile 2017 Slide 5 How to Reboot Your Agile Team Agile 2017 Slide 6 How to Reboot Your Agile Team Agile 2017 Slide 7 How to Reboot Your Agile Team Agile 2017 Slide 8 How to Reboot Your Agile Team Agile 2017 Slide 9 How to Reboot Your Agile Team Agile 2017 Slide 10 How to Reboot Your Agile Team Agile 2017 Slide 11 How to Reboot Your Agile Team Agile 2017 Slide 12 How to Reboot Your Agile Team Agile 2017 Slide 13 How to Reboot Your Agile Team Agile 2017 Slide 14 How to Reboot Your Agile Team Agile 2017 Slide 15 How to Reboot Your Agile Team Agile 2017 Slide 16 How to Reboot Your Agile Team Agile 2017 Slide 17 How to Reboot Your Agile Team Agile 2017 Slide 18 How to Reboot Your Agile Team Agile 2017 Slide 19 How to Reboot Your Agile Team Agile 2017 Slide 20 How to Reboot Your Agile Team Agile 2017 Slide 21 How to Reboot Your Agile Team Agile 2017 Slide 22 How to Reboot Your Agile Team Agile 2017 Slide 23 How to Reboot Your Agile Team Agile 2017 Slide 24 How to Reboot Your Agile Team Agile 2017 Slide 25 How to Reboot Your Agile Team Agile 2017 Slide 26 How to Reboot Your Agile Team Agile 2017 Slide 27 How to Reboot Your Agile Team Agile 2017 Slide 28 How to Reboot Your Agile Team Agile 2017 Slide 29 How to Reboot Your Agile Team Agile 2017 Slide 30 How to Reboot Your Agile Team Agile 2017 Slide 31 How to Reboot Your Agile Team Agile 2017 Slide 32 How to Reboot Your Agile Team Agile 2017 Slide 33 How to Reboot Your Agile Team Agile 2017 Slide 34 How to Reboot Your Agile Team Agile 2017 Slide 35 How to Reboot Your Agile Team Agile 2017 Slide 36 How to Reboot Your Agile Team Agile 2017 Slide 37 How to Reboot Your Agile Team Agile 2017 Slide 38 How to Reboot Your Agile Team Agile 2017 Slide 39 How to Reboot Your Agile Team Agile 2017 Slide 40 How to Reboot Your Agile Team Agile 2017 Slide 41 How to Reboot Your Agile Team Agile 2017 Slide 42 How to Reboot Your Agile Team Agile 2017 Slide 43 How to Reboot Your Agile Team Agile 2017 Slide 44 How to Reboot Your Agile Team Agile 2017 Slide 45 How to Reboot Your Agile Team Agile 2017 Slide 46 How to Reboot Your Agile Team Agile 2017 Slide 47 How to Reboot Your Agile Team Agile 2017 Slide 48 How to Reboot Your Agile Team Agile 2017 Slide 49 How to Reboot Your Agile Team Agile 2017 Slide 50 How to Reboot Your Agile Team Agile 2017 Slide 51 How to Reboot Your Agile Team Agile 2017 Slide 52 How to Reboot Your Agile Team Agile 2017 Slide 53 How to Reboot Your Agile Team Agile 2017 Slide 54 How to Reboot Your Agile Team Agile 2017 Slide 55 How to Reboot Your Agile Team Agile 2017 Slide 56 How to Reboot Your Agile Team Agile 2017 Slide 57 How to Reboot Your Agile Team Agile 2017 Slide 58 How to Reboot Your Agile Team Agile 2017 Slide 59 How to Reboot Your Agile Team Agile 2017 Slide 60 How to Reboot Your Agile Team Agile 2017 Slide 61 How to Reboot Your Agile Team Agile 2017 Slide 62 How to Reboot Your Agile Team Agile 2017 Slide 63 How to Reboot Your Agile Team Agile 2017 Slide 64 How to Reboot Your Agile Team Agile 2017 Slide 65 How to Reboot Your Agile Team Agile 2017 Slide 66 How to Reboot Your Agile Team Agile 2017 Slide 67 How to Reboot Your Agile Team Agile 2017 Slide 68 How to Reboot Your Agile Team Agile 2017 Slide 69 How to Reboot Your Agile Team Agile 2017 Slide 70 How to Reboot Your Agile Team Agile 2017 Slide 71 How to Reboot Your Agile Team Agile 2017 Slide 72 How to Reboot Your Agile Team Agile 2017 Slide 73 How to Reboot Your Agile Team Agile 2017 Slide 74 How to Reboot Your Agile Team Agile 2017 Slide 75 How to Reboot Your Agile Team Agile 2017 Slide 76 How to Reboot Your Agile Team Agile 2017 Slide 77 How to Reboot Your Agile Team Agile 2017 Slide 78 How to Reboot Your Agile Team Agile 2017 Slide 79 How to Reboot Your Agile Team Agile 2017 Slide 80 How to Reboot Your Agile Team Agile 2017 Slide 81 How to Reboot Your Agile Team Agile 2017 Slide 82 How to Reboot Your Agile Team Agile 2017 Slide 83
Upcoming SlideShare
What to Upload to SlideShare
Next

2 Likes

Share

How to Reboot Your Agile Team Agile 2017

Conference Presentation at Agile 2017 by Maurizio Mancini of Exempio (exempio.com) and Martin LaPointe of AgileKlix.

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

How to Reboot Your Agile Team Agile 2017

  1. 1. How to Reboot Your Agile Team MARTIN LAPOINTE • AGILEKLIX • ML@AGILEKLIX.COM MAURIZIO MANCINI • EXEMPIO • MAURIZIO.MANCINI@EXEMPIO.COM
  2. 2. I’m Martin, an Agile Coach with many years of working with Agile teams and Agile transformation. Over the years, I have had the opportunity to work in places with a high potential for experimentation. I was able to develop a deep understanding of what it means to be part of an Agile team. Today, I want to share with you my many years of experience rebooting Agile teams in Canada and Europe. In my personal life, I’m a triathlete and owner of an Agile family. Martin Lapointe
  3. 3. • A leader in the quality and process industries with a sixth sense for Agile, quality, and business process. • I have been refining my Agile approach for more than 10 years. • My passion is to deliver quality software and to see how Agile can help teams deliver quality software! Maurizio Mancini Agile 2014 – Agile: One Size does not fit all! Walmart Labs California 2014 – Quality and Process Atlassian Summit 2014 – From Incremental & Iterative to Agile: What is the right process for your team? Quest 2015 – Building a QA Team that Matters Cutter Summit 2015 – Agile Testing – What’s that all about? Atlassian Summit 2015 – How to Build in Quality from Day 1 using Lean QA and Agile Testing Agile Tour Montreal 2016 – Le guide de réparation de l’équipe Agile : La recette secrète ! Agile Tour Ottawa 2016 – How to Reboot Your Agile Team! Glogal Scum Gathering San Diego 2017 – How to Reboot Your Agile Team!
  4. 4. Today’s presentation • The Edge Change & Comfort Model • Organizational change • Simplicity and Agile • Your Reboot Context • The Essential Ingredients • Change and Emotions • Rebooting the Agile Team • The 5th Agile Value
  5. 5. The Edge Change and Comfort Model by M&M Sprint 5 Sprint 4 The Edge Change & Comfort Model by M&M Sprint 3 Sprint 1 Sprint 2
  6. 6. Organizational Change
  7. 7. Whether organizations like it or not, change will happen… There’s a gap between the pace of change in the world and the pace that an organization is changing
  8. 8. Adapt and change, otherwise organizations will not survive… Organizations have to be ready for change
  9. 9. Creative Destruction • Comes from the world of economics • It is the art of renewing an organization from within
  10. 10. Organizational Change “Can you help me Spin Up some Agile teams? ”
  11. 11. It takes time to build an organization with mature Agile teams ... It doesn’t happen overnight !
  12. 12. La semplicità è la più grande sofisticatezza. LEONARDO DA VINCI “ ”Simplicity is the ultimate sophistication. “ ”
  13. 13. Simplicity is the key to an Italian recipe A true Italian recipe uses 5 and 6 good quality ingredients
  14. 14. It’s just not the same… Just because you have the recipe, doesn’t mean that it will taste good! It’s just not the same! As much as we try to make mom’s recipe…
  15. 15. Simplicity and Agile stories of Agile failures Not “the recipe” secret of Agile minimal quality ingredients
  16. 16. Your Reboot Context
  17. 17. Your Reboot Context Time for you to assess your current state. 10 Minute Exercise In a few words, describe the situation of your team. Include information on interdependencies, relationships between team members, product vision, physical work spaces and team dynamics. Examples: • Improve team communication on a daily basis • Increase requirements understanding with better user stories • Knock down the wall that exists between Dev and QA in the team • Move to a built-in quality process with code review techniques Example: Team has no autonomy Example: No real Product Owner Example: Sprint length is variable Example: Team doesn't take the time to do test automation Example: People don’t like the wall but nobody is doing anything about it.
  18. 18. 6 Essentiel Ingredients
  19. 19. Sprint 5 Sprint 4 The Edge Change & Comfort Model by M&M Sprint 3 Sprint 1 Sprint 2 Foundation The Edge Change and Comfort Model by M&M
  20. 20. Leadership We believe that leadership is required at all levels of an organization. Leadership Executive Coaching Team Coaching
  21. 21. Management Style Management 3.0 promotes the same principles that we need to start the transformation of an Agile team … Management 3.0 Leadership - Management Style It is the future of management, which is all about doing the right thing for your team, involving everyone in improving the system and fostering employee engagement. Jurgen Appello
  22. 22. Change should be enabled from the top but it needs to take root and flourish from the bottom! Change
  23. 23. But why is The Vision essential? The Vision In Agile, a vision is crucial because of the speed that Agile is executed at… • Deliverables are frequent • Business needs change quickly • You need a Vision of what the team needs to achieve and why, in order to help maintain the team's focus. Leadership – Management Style - Vision
  24. 24. • Management Participation • Motivated team members • People that take responsibility • Promote a culture of change Engagement Develop engagement at all levels of the organization… With Agile we don’t have time to be a tourist! Leadership – Management Style - Vision – Engagement
  25. 25. Building in Quality! Quality Leadership – Management Style - Vision - Engagement - Quality • Quality is built into the recipe • Quality must be understood at all stages of the process • Quality is a key ingredient for building a good cadence Quality is one of the core principles of Agile/Scrum!
  26. 26. If your quality assurance is offset, this is not Building in Quality!! Dev QA Dev & QA Building In Quality Leadership – Management Style - Vision - Engagement - Quality One of the most common frAgile patterns! Quality
  27. 27. A good Agile Coach knows how to blend all of the previous ingredients to achieve success. The Agile Coach will know the right amount of each ingredient to make the Agile team successful! The Agile Coach And finally the Chef… Leadership – Management Style - Vision - Engagement - Quality - Coaching
  28. 28. Almost ready to reboot… • Engaged Management and developed the Leadership • Communicated the Vision • Developed Engagement and a Quality strategy • We have an amazing Agile Coach
  29. 29. The Edge Change and Comfort Model by M&M Sprint 5 Sprint 4 The Edge Change & Comfort Model by M&M Sprint 3 Sprint 1 Sprint 2 ENGAGEMENT COACHING LeadershipVision Management Style Quality
  30. 30. Let’s not forget we are dealing with humans…
  31. 31. ? The Edge Change and Comfort Model by M&M
  32. 32. Vision Emotions Leadership Engagement Quality Agile Coach Change is Hard Companies that want their workers to contribute with their heads and hearts, have to accept that emotions are essential to the new management style. Management Style
  33. 33. The success of your Agile transformation will depend on being aware that emotions are part of the change process
  34. 34. Emotions  Positive emotions makes us feel good and brings us to a happy emotional state.  Negative emotions saps our energy and kill our effectiveness. In a negative emotional state, you don’t feel like doing anything.
  35. 35. Working with people is about managing feelings. The issue is not whether employees have “negative” emotions, but rather how to manage them.
  36. 36. The Edge Change and Comfort Model by M&M How do we assess where we are today?
  37. 37. Let’s listen…
  38. 38. We re ready to reboot… Every Reboot is different • Every team has different needs • Need to determine the ingredients in context • Identify what impediments to work on • And define the objectives for the journey
  39. 39. The survey focuses on 5 main dimensions. The results will help us define the objectives and define the type of Reboot needed. The 5 Dimensions are: 1. Agile Health 2. Product Ownership 3. Roles & Skills 4. Team & Processes 5. Technology & Delivery Survey the team to define a roadmap
  40. 40. Product Ownership What is the Vision? Are User Stories actionable? Strategy: 1. Create an Agile Charter for the Product. 2. Train “Business people” on creating effective User Stories. 3. Build a Product Backlog that ties objectives to User Stories. Sample Reboot Type #1 Roles & Skills Do you have the Scrum roles for your Agile team? Strategy: 1. Train the team to understand the new dynamic. 2. Find and formalize the Scrum roles. 3. Strong supervision. 0 1 2 3 4 5 Agile Basics Health Product Ownership Roles & SkillsTeam & Processes Technology & Delivery Agile Dimensions Evaluation
  41. 41. Team & Processes Do you have a stable team? Are you working with fixed iterations? Strategy: 1. Build a Scrum with 7+- 2 people. 2. Design the Sprints and ceremonies. 3. Implement boards to manage the flow. Sample Reboot Type #2 Technology & Delivery What kind Quality process do you have? How’s your continuous integration & delivery? Strategy: 1. Remove dependencies on specialties. 2. Transform from Inspection process into build-in automation quality. 3. Introduce TDD (Test Driven Development). 0 1 2 3 4 5 Agile Basics Health Product Ownership Roles & SkillsTeam & Processes Technology & Delivery Agile Dimensions Evaluation
  42. 42. Rebooting the Agile Team by Martin & Maurizio
  43. 43. Why reboot an Agile team? Is your team "Wagile”, very FrAgile or TrAgile? • Your backlog contains thousands of tickets? Mostly tasks boards of 15 columns? • Project managers fill the role of Scrum Masters? • The team size is more than 20 persons? • Your QA team is 2 sprints behind the dev team? • Daily stand-up is a daily status reports? • The Sprint planning takes 2 days and Sprints are never stable? • …
  44. 44. Reboot Your Team in 5 Sprints Sprint 1: Run in the rain Sprint 2: Thunderstruck Sprint 3: Start the M&M pain machine Sprint 4: Open-up and look at the sun Sprint 5: Removing the training wheels
  45. 45. Sprint 1: Run in the rain
  46. 46. Sprint 1: The group has seen better days • Deliveries are now difficult • Lots of frustration in the team
  47. 47. Sprint 1: Understand the team's current reality • Coaches time to listen • Not the time for changes • Insights from group members
  48. 48. • What is causing problems • Diagnose what is happening in the team Sprint 1: Understand why it’s always raining 0 1 2 3 4 5 Agile Basics Health Product Ownership Roles & PeopleTeam & Processes Technology & Delivery Agile Dimensions Evaluation
  49. 49. • Create an iterative change roadmap • Understand the destination • Communicate = Trust in the upcoming change Sprint 1: Define the path to the sun
  50. 50. Sprint 2: Thunderstruck • Courage!
  51. 51. Sprint 2: Break the status quo
  52. 52. • Organize team activities • Generate passion and motivation • Create change agents • Find creative people Sprint 2: Motivate people in the change
  53. 53. Sprint 2: Creative-Destruction • New Backlog • Definition of Done • Visual Scrum Board
  54. 54. Sprint 3: Start the M&M pain machine
  55. 55. Sprint 3: Live the pain with the team • Crossing the desert • Favor communication • Manage emotions
  56. 56. Sprint 3: Fail, fail fast • Quit the superman syndrome • Strengths & weaknesses • Failing the demo
  57. 57. We need to: • Guide the Product Owner in planning the rollout of the product • Mentor the Scrum Master on implementing lessons learned • Support the Team Members to better collaboration • Visualize the « Work in progress » with the team Sprint 3: Manage frustration
  58. 58. Be watchful: • Over-engineering the processes • Temptation for Command & Control • Being dogmatic • “As a Product Owner, I want…” Sprint 3: Break the frAgile temptations
  59. 59. Sprint 4: Open-up and look at the sun
  60. 60. Sprint 4: Crossing the edge The team metamorphosis • Delivering working products • Building in Quality • New collaboration & responsibility
  61. 61. Sprint 4: Make it visible • Release planning • Story mapping • Refinement sessions • Dynamic sprint planning
  62. 62. Sprint 4: Collaborate and share • Share knowledge with colleagues • Promote transparency • Enjoy success
  63. 63. Sprint 5: Removing the training wheels
  64. 64. • Agile Masters promoting Agile values Sprint 5: The performing Agile team
  65. 65. Sprint 5: Deploy the FUN ! • Flow & speed • Unbelievable happiness • New self-organized team
  66. 66. • Client gets regular deliverables • Users can provide useful feedback • Team can adjust the product on demand Sprint 5: Please our customer
  67. 67. Sprint 5: Grow the Agile mindset in the organization • Implement Meta-Scrum • Product Owner collaboration • Managing at the feature level
  68. 68. M&M Reboot Canvas
  69. 69. Strategic Canvas for the Reboot of an Agile Team
  70. 70. Strategic Canvas for the Reboot of an Agile Team
  71. 71. Key Takeaways
  72. 72. Start with the essential ingredients: Leadership, Management Style, The Vision, Engagement, Quality and an awesome Agile Coach. Or define your own. Remember that emotions are an inevitable part of any change process. Key Takeaways
  73. 73. Change is hard, but work WITH people to create Change Agents. By using a modern Management Style. Key Takeaways
  74. 74. Use a survey to assess where your team is today so that you can build a roadmap and have a strategy how to get the team where they want to be. Key Takeaways
  75. 75. Commit to deliver small pieces of products! Stay with the basics! But let’s not forget Simplicity… Deliver what makes sense, even if it is a sprint of just one Story! Deliver working quality software generating value for the end-user and your company.
  76. 76. The 5th Agile Value
  77. 77. Have fun at work beyond following the recipe!
  78. 78. Thank You! MARTIN LAPOINTE • AGILEKLIX • ML@AGILEKLIX.COM MAURIZIO MANCINI • EXEMPIO • MAURIZIO.MANCINI@EXEMPIO.COM
  79. 79. Reference Books
  • olayinkasteve2

    May. 3, 2021
  • powerirs

    Sep. 11, 2017

Conference Presentation at Agile 2017 by Maurizio Mancini of Exempio (exempio.com) and Martin LaPointe of AgileKlix.

Views

Total views

1,545

On Slideshare

0

From embeds

0

Number of embeds

898

Actions

Downloads

11

Shares

0

Comments

0

Likes

2

×