"Time Management for Developers"
summary
Argues a concrete workflow: collect-organize-sync-anticipate — capture every task outside code, put true tasks into a task list, and time-block selected items on a daily grid (she demos a tablet/paper quarter-hour grid). Uses Kanban for flow, short standups only to synchronize, and split day into quarters so inbox/sand slots absorb interruptions. Shrinks surprises by tracking real time and estimating with developers, keeps reserve 10% agile time, never plans five full days, and reports that tracking reveals procrastination and improves future estimates.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 3:19Perception of time and priorities
- 8:05Big rocks and task prioritization
- 11:38Visualizing time and cycles
- 16:05Social acceleration and synchronization
- 19:43Synchronization tools and meetings
- 24:00Task collection and management tools
- 30:24Organizing and tracking tasks
- 33:41Anticipation and planning
- 38:27Handling emergencies and priorities
- 40:20Tracking time and estimation
- 44:25Q&A on time management challenges
related talks
42mLife-Hacking and Personal Time Management for the Rest of Us
47mUnleashing Your Super-dev-powers
11mSS & BR: Productivity for ordinary developers
55mZen-Driven Development - Protect Your Sanity
42mA Day in The Life of a Developer Bo$$
46mFrom Dallas to Happy Days: tips for positively hacking your life
47mEveryday Agile for One: Recipes that make development for one … Fun
34mHow to effectively communicate to Developers/PMs - A guide for developers and project managers