Herding Cats Standardizing Engineering Processes
summary
Teams standardize Jira workflows, screens and fields, add automation rules that sync story-to-epic status and roll up into a unified dashboard, and create a status-reporting mechanism and partner-management flow to limit leaks. Pilots show 67% faster status reporting and 63% fewer fields on screens, making issue creation simpler and dashboards reliable. Work includes proto-personas, iterative pilots, GitHub→Jira integrations for some projects, and documented maintenance expectations because automation and standards require ongoing upkeep.
AI-written summary · about
chapters (17)
- 0:00Standardizing engineering processes
- 1:25Why standardization matters
- 4:37Why people resist being told what to do
- 6:05Proto Personas for workflows
- 8:55Collaboration vs team workflows
- 11:39Best practices for standards
- 14:29Avoiding complex standards
- 16:13Unified backlog and fields
- 17:41Automation reduces overhead
- 19:03Unified dashboards for visibility
- 20:07Standardizing status reports
- 21:52Partner management for security
- 23:16Measuring productivity impact
- 24:41Standardized Jira fields
- 26:09Next steps for teams
- 27:33Closing remarks
- 27:54Q&A: Extending to external contributors
related talks
16mFrom Herding Cats to Efficiency That Slaps
40mThe Joys of Managing Engineering Teams
06mSi ta përdorim JIRA për të planifikuar projektet tona
44mEnhancing the Performance of Engineering Teams
09m"The Joys of Managing Engineering Teams"
43mCase study: Managing a complex engineering project
23mManaging diverse engineers for high-impact deliveries
38mBreaking Down Silos Between Platform and Product Teams