Common pitfalls in engineering teams and how to avoid them
summary
Seven recurring failure modes get mapped to the seven deadly sins and paired with concrete fixes: use a sequencer column, a red bin for unworkable tickets and a suspending flag so blocked work is visible; enforce one‑piece flow, timeboxing and MoSCoW prioritization; measure with the DORA four metrics; adopt Gradle tools like gradle profiler, catalogs and convention plugins to cut dependency and build drift; automate tedious Jira tasks with a GPT and run PDCA cycles for continuous improvement. Instagram pivot serves as a real success from listening to users.
AI-written summary · about
chapters (9)
- 0:00Engineering team pitfalls
- 3:39Overengineering and I know better
- 13:40Feature overload and backlog chaos
- 25:42Trends and unstable tech stacks
- 32:28Envy of other teams
- 36:45Excessive processes and meetings
- 39:58Code review conflicts
- 46:09Delaying decisions and improvements
- 47:57Continuous improvement
related talks
22m7 Deadly Traps of SRE
47m7 Sins of Scaling and Other Agile Anti Patterns
48mThe 10 vicious circles at work: detecting and breaking them up
44mEnhancing the Performance of Engineering Teams
32mPanel discussion: The journey to building effective engineering teams
13mTen Ways to Doom Your DevSecOps
22mLeading software teams with context (visibility)
43mTen DevSecOps Culture Failures