How does Quality fit in CALMS?
summary
Defines quality as value to some person and a quality strategy as a system of achievable goals delivering user and business outcomes; maps that onto CALMS by making culture mean quality is everyone’s responsibility, automation mean scripting repetitive checks so teams stop breaking builds and deliver faster, lean mean seeing cross-team dependencies so one bottleneck doesn’t ruin system quality, measurement mean stop counting only bugs and measure what people actually want, and sharing mean include product and marketing knowledge in feedback loops.
AI-written summary · about
related talks
15mDefining Quality
06m“Quality-conscious Software Delivery”
28mGet a grip on your quality by using Quality Views
28mInstilling the built-in quality mindset into a dev team
49mIs your Quality on the Road to Nowhere?
41mQuality Transformation
28mQuality as an attitude – From Testing to Quality Engineering to…what?
08m“Quality Acceleration: delivering quality software at speed”