Helping Your Whole Team Own Software Quality
summary
Paylocity builds a quality maturity model with seven attributes and three levels (minimum/standard/excellent), asks teams to write team-specific quality strategies, runs monthly advocate check‑ins and quarterly self‑assessments, and dashboards metrics (rollbacks, uptime, response time, security issues, deployment frequency). Results after a year: 65% teams hit 100% minimum, 18% hit standard, some teams cut deploy cadence from monthly to per‑sprint, developers adopt Cypress, create test harnesses and maintain acceptance tests.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:19From "Accelerate" by Nicole Forsgren, Jez Humble, Gene Kim
- 3:05From "Clean Code", by Robert C. Martin
- 7:43Results After the First Year of Adoption
- 9:26What's Next
- 10:34The 7 Attributes of Quality at Paylocity
- 12:00Levels of Behavior
- 12:46Example Behaviors: Valuable
- 13:52Example Behaviors: Functional
- 14:27Example Behaviors: Reliable
- 14:54Example Behaviors: Performant
- 15:42Example Behaviors: Secure
- 16:13Example Behaviors: Usable
- 16:39Example Behaviors: Maintainable
- 17:48Types of Questions to Be Answered in the Quality Strategy
- 18:57Sample Team Strategy 3
- 21:57Ideas for Developer Involvement
- 24:55Developer Success Stories
- 32:02Success Metrics
- 32:28Metrics Not to Use
- 34:22Communication Strategies
related talks
36mHow Good Is Your Software Product? (Evolving "Quality"Throughout The SDLC)
06m“Quality-conscious Software Delivery”
01h 02mThe Pursuit of Quality
24mThe 3-pillar, balanced quality model of Proactive QA, Detective QA and Reactive QA
46mFull Court Quality: Lacing Up for Speed, Stability & Style
28mGet a grip on your quality by using Quality Views
46mProject Culture and Team Responsibility for Quality
46mQuality Engineering for DevOps Teams