Case study: Managing a complex engineering project
summary
Atlassian Micros rebuilds platform to support cloud data residency across new AWS regions, splitting load across accounts to avoid rate limits and coordinating 10–15 teams; project runs six months, uses an Atlas project ticket per initiative linked to Jira and GitHub, a dependency mapper and velocity charts, and enforces weekly Friday updates and a half‑day kickoff workshop. Outcome: delivery two weeks early, team happiness ~95% and management happiness 100%, with incremental epics, roles‑and‑responsibilities playbooks, and pairing to avoid scope creep.
AI-written summary · about
chapters (15)
- 0:00Leadership in engineering projects
- 2:45Delivery over technology choices
- 4:53Atlassian data residency case study
- 8:47Recognizing project complexity
- 12:23Accountable engineering teams
- 17:46Stakeholder communication
- 22:04Roles and responsibilities
- 24:10Agile delivery units
- 28:50Preventing scope creep
- 33:29Velocity charts for performance
- 34:10Data-driven decisions
- 37:23Estimation guides delivery
- 38:26Healthy collaborative teams
- 40:58Celebrating delivery and health
- 42:02Key takeaways
related talks
52mToo many cooks! Supporting augmented teams without getting salty
23mManaging diverse engineers for high-impact deliveries
38mBreaking Down Silos Between Platform and Product Teams
40mThe Joys of Managing Engineering Teams
35mBuilding and Growing an Agile Team
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
31mBuilding an Enduring Culture of Engineering Excellence
43mScaling Yourself for Managing Distributed Teams...