Tips for part-time project managers
summary
Practical rules and tools: choose a unit and translate for estimates (clarify whether estimate means cost time or commitment), force an early decision between time-bound vs scope-bound with concrete consequences (open enrollment requires ruthless scope cuts; a security bug requires full scope), and run a lightweight critical path exercise so the visible bottleneck (e.g. five days reduced to four by adding a third engineer) guides staffing and highlights hidden dependencies like QA.
AI-written summary · about
related talks
39mManaging Complexity: Best Practices for Software Development Project Manager
39mProject Management for Engineers
58mProject Management for Engineers
17mHow to drive pace in your team
46mEstimates and complexity: a tale in 42 and a half minutes
42mEstimates: Is There a Silver Bullet?
45mHow to not shoot yourself in the foot with estimation
47mCreating efficient, accurate, software estimations