Michael Tweed at StaffPlus London 2023
summary
Case study of deploying a static analysis system across distributed teams: the team disables all checks then enables one (code coverage) to avoid trust shocks, builds pull-request integrations and internal dashboards and tribe-level reports, and treats opt-outs as signals to improve docs not punish squads. Directors start competing on weekly headlines; platform engineers discover low coverage and fix legacy modules. Outcome is measurable: one or two headline metrics (iOS and Android coverage) show steady upward growth and the effort proves sustainable.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:24Code quality problem
- 2:51Building buy-in
- 4:35Scaling influence with static analysis
- 6:18Reducing friction with trust
- 7:22Communicating progress
- 8:47Outcomes and consequences
- 9:48Personal growth
- 10:51Lessons learned
related talks
18mAgile leadership and technical mastery, a harmonious alliance
11mWorking with sharp tools - A case study of Continuous deployment
50mCase Study: 10 Steps to Agile Development without Compromising Enterprise Security
46mWhen Software Becomes Everyone's Job
06m"Small Changes for Big Wins"
11mWorking with sharp tools - A case study of Continuous deployment
21mScaled Agile DevOps
43mCode quality as an engine of your IT business