Project Management Workflows
summary
Practical production playbook: uses Notion instead of Jira/Confluence for a single tasks+docs database with personal Kanban boards and a docs playground inbox; Slack for comms and FigJam for whiteboarding; projects include Dinox (NFT PC strategy) and Brustory (released on iOS/Android). Claims: limit sprints to the top ~10% of tasks (task essentialization), run daily flexible standups, reserve Tuesdays and Thursdays as call-free days to protect deep work, and use iterative “first complete iteration” checkpoints plus PARA-style personal organization to keep teams of ~5–9 focused and aligned.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 3:15Project lifecycle and team setup
- 6:45Sprint planning
- 8:50Aligning priorities
- 10:36Notion workflow
- 14:54Slack tips
- 16:37Call-free days
- 18:44Team member competence
- 21:14Iterative development
- 23:43Personal productivity
- 29:41Documenting decisions
- 32:07Team morale
- 34:34Empathy and professionalism
- 37:06Closing remarks
- 37:47Q&A: Empathy vs emotions
- 40:14Q&A: Planning vs production
- 42:20Q&A: Call-free days impact
- 44:48Q&A: Team size and tools
related talks
46mManaging The Process
52mGame Production: Helping your team succeed
49mBaking Boards: Tweak the Recipe for Agile Development
50mFrom Good to Great: Elevating your Production
45mPortofolio Kanban, The Art of Being Loosely Coupled and Highly Aligned
49mFrom Artist to Producer — The Strategic Path to Impact
36mDEVELOPER ORIENTED PROJECT MANAGEMENT
48mLess Process, more Guidance with a Team Playbook