transforming chaos to clarity - acm 6.15
TRANSCRIPT
![Page 1: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/1.jpg)
Transforming Chaos to ClarityMaking Your Software Development Hum
Ron Lichty, Software Engineering [email protected]
![Page 2: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/2.jpg)
Ron Lichty, Managing Software People & Teams
SOFTWEST
© Ron Lichty 2
![Page 3: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/3.jpg)
* http://InformIT.com/managing <-----35% off coupon code: MANTLELICHTY
http://ManagingTheUnmanageable.net <-----tools, excerpts, more rules of thumb
*
![Page 4: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/4.jpg)
Poll: Software Development in Disarray?
• Who has seen chaos in a product group?
• Who has seen chaos in your current group?
• Who feels like development is running rough?
• Who is suffering from organizational knots?
• Anyone’s development organization running so smoothly it doesn’t need tuning?
![Page 5: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/5.jpg)
Define Success
• What are you trying to accomplish
• How do you know you're not
• How will you know when you get there
• Assess what’s working
• Assess the issues and the symptoms– Every organization is unique
![Page 6: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/6.jpg)
Issues and Symptoms• Turnover• Productivity• Handoffs• Process glitches, Bottlenecks• Quality• Single points of failure• Communication breakdowns• Unfeasible sales• Heroes vs Teamwork• Sources of disruption and interruption
![Page 7: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/7.jpg)
No One Can Fix Everything
![Page 8: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/8.jpg)
No One Can Fix Everything
• Life is simpler when you plow around the stump.
![Page 9: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/9.jpg)
Chaos Isn’t All Bad
![Page 10: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/10.jpg)
Chaos Isn’t All Bad
• Innovation often emerges from “chaos”– Brainstorming– Thinking outside the box
• Don’t eliminate useful chaos
• Just look for the pings and the misfires– Let’s make our product engines hum
• regardless of where creativity and pivots take us
![Page 11: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/11.jpg)
Patterns of Impediments
![Page 12: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/12.jpg)
Categories of Impediments
• Process
• Culture
• Communication
• Planning
• Rigor
![Page 13: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/13.jpg)
Requirements: Bridge the Gap
• GIGO• Programmers:
– who has received an exceptional set of rqmts?– what was the programming experience like? – how did it differ from the usual?
• How good are your requirements?– How unambiguous?
• Do your requirements change?• Are they ever complete?
![Page 14: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/14.jpg)
Requirements: Solutions
• Communication• Team-building• Agile
![Page 15: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/15.jpg)
15
Blank space.
The Study of Product Team Performance, 2014
![Page 16: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/16.jpg)
Requirements:Fix Interdepartmental Communication
16
Blank space.
The Good News
10%of product teams function as a seamless team.
The Bad News
90%of product teams don’t.
How would you rate your product team’s cross-functional collaboration, trust and communication?
![Page 17: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/17.jpg)
Requirements:Fix Interdepartmental Communication
• Build trust relationships
• Product Mgmt & Engineering: collaboration
• Establish processes for your partners to fit
• Communicate, communicate, communicate
• Never succumb to “them vs. us”• Avoid the “blame game”
![Page 18: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/18.jpg)
Requirements: Solutions
• Agile– Teamwork: developers, testers, product managers
• Co-located, with a focus on team interaction
– A single Product Owner– Just enough requirements
• The entire project at a high level• Prioritized by business value• Details “just in time”
– Requirements very stable during sprints• Change occurs in the sprint boundaries
![Page 19: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/19.jpg)
Agile: The Challenges
• Doing Agile• Being Agile
![Page 20: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/20.jpg)
Doing Agile: Practices
• Common Definition of Done• Timeboxing Standups (and every meeting)• Standups: three questions• Retrospectives• Rapid Relative Sizing• Estimating = ƒ(Size, Velocity, Stable teams)• Sizing, Estimating ≠ Committing• Shippable software every iteration
![Page 21: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/21.jpg)
Being Agile
• It’s the values and the principles• Half done is not done• Standups: How are we doing against our plan?• Being empowered and self-organizing• Being a learning organization• Delivering highest customer value every
sprint• Building trust and respect with each other
![Page 22: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/22.jpg)
Focus• Macro level
• “When everything is a priority, nothing is a priority.” --Sheila Brady, Apple
• Limit task switching
• Micro level• Avoid “multitasking”• Limit interruptions
![Page 23: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/23.jpg)
Task Switching
Source: Mike Cohn, citing Steven C.Wheelwright and Kim B.Clark (1993), Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency and Quality, 1993
![Page 24: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/24.jpg)
Task Switching
Source: Rob Maher, “Increasing Team Productivity: A project focus creates waste and leaves value on the table”, Scrum.org Whitepapers
taking communications overload into account
Rob Maher, surmising that email, texts, IRC, chat, smartphones together represent a second “task”Source: Mike Cohn, citing Steven C.Wheelwright and Kim B.Clark (1993), Revolutionizing Product Development: Quantum Leaps in Speed, Efficiency and Quality, 1993
![Page 25: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/25.jpg)
--Larry Maccherone, The Impact of Agile Quantified, Rally, 2013
![Page 26: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/26.jpg)
Focus• Macro level
• “When everything is a priority, nothing is a priority.” --Sheila Brady, Apple
• Limit task switching
• Micro level• Avoid “multitasking”• Limit interruptions
It’s not that we don't have enough time. We have too much to do. -- Chet Hendrickson
![Page 27: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/27.jpg)
Smart Project Planning
• Show demonstrable progress frequently
• Get the risky stuff done first– the UI should always be high on the risk list
• Deliver the highest customer value first
• Be first / be ready to integrate / be early
• Don’t over-engineer
![Page 28: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/28.jpg)
Pay Down Technical Debt!
• What’s “technical debt”?• Result: interest accrues• Solutions?
– Pay down debt– Prioritize– Refactor– Write tests– Embrace Test Driven Development (TDD)
![Page 29: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/29.jpg)
Optimize Process
• Just about any process is better than no process – Mark Ginnebaugh– The exception: process for process’ sake
• I’m a fan of – “Just-Enough Process”– Agile– baby steps
![Page 30: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/30.jpg)
Improve Onboarding
![Page 31: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/31.jpg)
Improve Onboarding
• Effective Team Onboarding:– 1 of 5 factors
• 67% likelihood high level team performance
![Page 32: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/32.jpg)
32
Only 4% of organizations indicate they have a best practice onboarding product team members
Improve Onboarding
![Page 33: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/33.jpg)
The Bottom Line
• Chaos is common
• It’s really a series of challenges
• It’s a series of improvement milestones
• Each of them can be transformed– Likely each new hum will reveal the next ping
• Like peeling an onion or climbing a mountain
![Page 34: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/34.jpg)
In the beginning, everyone will talk about scope, and budget, and schedule, but in the end, nobody really cares about any of those things.
The only thing they care about is this: People will love your software, or they won’t.
So that’s the only criterion to which you should truly manage.
—Joseph Kleinschmidt
![Page 35: Transforming chaos to clarity - acm 6.15](https://reader034.vdocuments.net/reader034/viewer/2022051618/55c4de64bb61eba07e8b466e/html5/thumbnails/35.jpg)
Ron Lichty Consulting • Mentoring, coaching, interim VP Engineering, acting CTO:
– http://ronlichty.com, [email protected]
• The book: Managing the Unmanageable: Rules, Tools & Insights for Managing Software People & Teams– http://ManagingTheUnmanageable.net <-----tools, excerpts, more rules
of thumb
– http://InformIT.com/managing <---35% off coupon code: MANTLELICHTY
• The annual study: The Study of Product Team Performance – http://ronlichty.com/study.html <----- the studies are free
downloads
• Training:Zero to Agile in Three DaysThe Agile ManagerManaging Software People and Teams© Ron Lichty 35