Dev up 2017 - Half Day Workshop: Getting your agile team unstuck
•
0 gostou•219 visualizações
Whether you've been working on an agile team for 6 months, or 6 years, the same obstacles tend to arise to trip us up over and over. Maybe your retrospectives feel more like a death march and no one is participating any more, or your daily stand-ups have bloated into 25 team member status meetings, or you have a QA team that feels buried by your fast-paced development team. These situations are unfortunately very common, and they lower team morale, lead to abandoned transformation initiatives, and ultimately your product and customers suffer because of it. But there's a better way! As an agile coach and consultant, I help software organizations stop the bleeding, mature their process, and develop into high functioning agile teams. And to be clear, I've made mistakes as well! I'd like to share with the audience my own experiences, including strategies that succeeded and failed in hopes of leading them down the path to getting their own teams "unstuck". I'll also give attendees an opportunity to share their own challenges, so that we can leverage those strategies to give them ideas for blasting through their own roadblocks. Learning points: Recognizing when your process, product, or people have gone off the rails by identifying "smells" Review some tools and strategies that teams can leverage when they need a cognitive reset to get them back on track How to apply tools and strategies in your own unique environments.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Semelhante a Dev up 2017 - Half Day Workshop: Getting your agile team unstuck
Semelhante a Dev up 2017 - Half Day Workshop: Getting your agile team unstuck (20)
Mais de Angela Dugan
Mais de Angela Dugan (20)
Último
Último (20)
Dev up 2017 - Half Day Workshop: Getting your agile team unstuck
- 1. Angela Dugan Principal Consultant and Agile Coach Angela@PolarisSolutions.com
- 2. Talk about the common challenges faced by agile teams we’ve worked with Share some of the tells we’ve noticed of when things have “gone off the rails” Review some ways to brush off the dirt and get back in there Practice a few of our favorite techniques Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 3. Your team is GOING to get stuck on its agile journey MANY times OUR GOAL IS TO HELP YOU IDENTIFY WHERE THE BODIES ARE BURIED Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 8. Angela Dugan Principal Consultant, Agile Coach, TFS Specialist Angela@PolarisSolutions.com TFSWhisperer.com @OakParkGirl
- 9. George Evjen Senior Consultant, Agile Coach George.Evjen@PolarisSolutions.com @gevjen http://www.coachandbeer.com/
- 16. Agile is based on immutable, underlying, and proven Lean principles. Agile Overview
- 17. Agile software development describes a set of principles for software development under which requirements and solutions evolve through the collaborative effort of self-organizing cross- functional teams. Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 18. Product Backlog Working Software Sprint (1-4 Weeks) Plan Mtg Review Mtg Refinement Daily Scrum Retrospective Refinement Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 21. Angela@PolarisSolutions.com Twitter: @OakParkGirl So why does every agile team eventually go off the rails?
- 22. VersionOne - 11th Annual State of Agile Report
- 24. commitment discipline meaningful collaboration adaptive planning experimentation permission to fail continuous improvement Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 25. TRUST AND TRANSPARENCY Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 26. No wonder agile is so freaking hard! Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 27. Agile is SIMPLE Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 29. Agile is not EASY Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 31. Agile is ~50% process Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 33. 1. Poor expectations management 2. Quality is lacking 3. Communication breakdown 4. Lack of ownership / accountability Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 34. #1 POOR EXPECTATIONS MANAGEMENT Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 37. 1. TALK TO EACH OTHER, FOR REAL 2. Create safe spaces for sharing status, issues, feedback 3. No assumptions based development / testing / deployment 4. Review progress with the PO/Stakeholders as early and often as possible Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 38. Product Backlog Working Software Sprint (1-4 Weeks) Plan Mtg Review Mtg Refinement Daily Scrum Retrospective Refinement Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 39. #2 QUALITY IS LACKING Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 41. QUALITY SMELLS
- 42. 1. Ask clarity questions early in the process 2. Document decisions made in-flight 3. Review outcomes often, so that divergences are caught early 4. Examine the process to determine why quality wasn’t delivered Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 43. Product Backlog Working Software Sprint (1-4 Weeks) Plan Mtg Review Mtg Refinement Daily Scrum Retrospective Refinement Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 44. #3 COMMUNICATION BREAKDOWN Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 47. 1. Remove artificial boundaries between people 2. Encourage the team to get to know one another 3. Listen to what your team mates are saying and NOT saying 4. Accept mistakes as readily as successes (maybe more!) Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 48. Product Backlog Working Software Sprint (1-4 Weeks) Plan Mtg Review Mtg Refinement Daily Scrum Retrospective Refinement Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 49. #4 LACK OF OWNERSHIP / ACCOUNTABILITY Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 51. OWNERSHIP SMELLS
- 52. 1. Make sure everyone on the team feels empowered to solve problems 2. Implement a fist of five approach to validating team commitments BEFORE committing 3. Take ownership of the big picture and pitch in, don’t just focus on “your part” of the solution 4. Reward team success, not individual success* Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 53. Product Backlog Working Software Sprint (1-4 Weeks) Plan Mtg Review Mtg Refinement Daily Scrum Retrospective Refinement Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 55. What is 1 thing you’re excited about taking away from this conference? Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 57. OPEN LINES OF COMMUNICATION Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 59. SHAKE THINGS UP Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 61. ASK FOR HELP Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 63. CREATE SHARED UNDERSTANDING Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 64. AGILE ESTIMATION Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 65. Estimating how long it takes to build software is HARD It is an educated guess but… Building and testing software is an art AND a science The entire software team needs to participate Diversity of opinion is KEY to agile estimation!
- 66. Estimates are affected by complexity, volume, uncertainty Estimates are affected by experience, or inexperience We do generally know when things are bigger or smaller when compared to other things, with confidence. Methods of Agile Estimation: Planning Poker, T-Shirt Sizes, Story Points
- 67. Quickly jot down answers to the following: How long does it take to get from this training room to the front lobby/entry? How long does it take you to walk to the vendor area? How long does it take you to walk to your car? How long does it take you to walk to the airport? Assume all trips start from this room!
- 68. A “number” associated with each User Story/Product Backlog Item Unitless Relative estimation between user stories IN AGGREGATE: considered highly accurate
- 69. 1, 2, 3, 5, 8, 13, 20, 40, 100, (infinity), (coffee cup) Smaller numbers are closer together Larger numbers are further away
- 70. Giraffe Gorilla Chicken Horse Crocodile Hyena Elephant
- 71. What could affect the accuracy of your estimates? What are some reasons that your estimates could vary wildly between team members? Which estimates might vary the most? How could you minimize that variance?
- 72. LEAN COFFEE Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 74. Participants drive the agenda Pick a theme Gather and vote on topics to cover Drive topics through a Kanban process Participation is optional Typically a small investment (1 – 2 hours per week) Strategy
- 75. Where is it? Right here When is it? Right now What to bring? We’ve got you covered on craft supplies! What is it about? This particular session is focused on Agile adoption related topics, including team dynamics, process frameworks, etc.
- 76. Fail Forward: https://www.admittingfailure.org/ Lean Coffee: http://leancoffee.org/ Drive: The Suprising Truth about What Motivates People: https://www.amazon.com/Drive-Surprising-Truth-About- Motivates/dp/1594484805 Coaching Agile Teams: https://www.amazon.com/Coaching-Agile- Teams-ScrumMasters-Addison-Wesley/dp/0321637704/ Angela@PolarisSolutions.com Twitter: @OakParkGirl
- 77. Get the slides: http://www.slideshare.net/angelabinkowski Twitter: @TeamPolaris Polaris Events - http://www.polarissolutions.com/events Polaris Solutions website - http://www.polarissolutions.com/ Angela@PolarisSolutions.com Twitter: @OakParkGirl