Managing Complexity: Best Practices for Software Development Project Manager

on YouTube ↗39m

" summary

Covers concrete practices: use MoSCoW prioritization so “want” items stay visible and estimated; publish a GitLab board with client access and daily ticket comments to avoid status emails; adopt a sprint-based fixed-profit pricing or time-and-materials-with-ceiling model instead of opaque fixed-price; keep a four-column risk register (risk, consequence, likelihood, action) and a backup/recovery plan; run automated tests, static analysis and preprod releases; track holidays, vacation and integration dependencies; celebrate wins (anonymous kudos) to preserve morale.

AI-written summary · about

" chapters (13)

1. 0:00Introduction to project management
2. 2:17Defining project scope clearly
3. 7:14Setting realistic deadlines
4. 10:51Managing project budget effectively
5. 14:38Agile contract models explained
6. 17:53Handling stakeholder expectations
7. 23:00Process for managing change requests
8. 24:03Improving team communication
9. 27:40Fostering team morale
10. 28:46Ensuring software quality standards
11. 30:55Addressing technical complexity
12. 31:15Project risk management plan
13. 34:53Q&A and celebrating success

" related talks

• 08mTips for part-time project managersJohn Ong · LeadDev Berlin 2022
• 36mDEVELOPER ORIENTED PROJECT MANAGEMENTRobert Pankowecki · wroc_love.rb 2014
• 51mCommon pitfalls in engineering teams and how to avoid themRenaud Mathieu · TechLead Conference 2025: AI in Orgs
• 09mSoftware engineering practices to improve managementNicky Thompson · LeadDev Berlin 2019
• 58mProject Management for EngineersMichelle Brenner · Copenhagen Developers Festival 2023
• 29mBeyond Herding Cats: Lessons for Project Management in a Small AgencyTori Lewis · MidCamp 2019
• 49mBaking Boards: Tweak the Recipe for Agile DevelopmentValerie Andrianova · Build Stuff 2017
• 18mDesign Patterns For Efficient DevOps ProcessesRebecca Fitzhugh, Byron Schaller · DevOpsDays Seattle 2018