Everyday Agile for One: Recipes that make development for one … Fun
summary
Practical recipes for solo development: use a visual backlog (screenshots show Trello/Azure DevOps boards), treat Kanban as a pull system with WIP=1, and timebox work into 25-minute Pomodoro slots to get measurable estimates (example sprint logs 35 of 51 hours tracked). Downscale Scrum: keep a prioritized backlog, short daily check-ins and sprint commitments; use high/low planning poker, automated tests and static reviews, occasional external code reviews, and a start/stop/continue retrospective.
AI-written summary · about
chapters (9)
- 0:00Intro
- 6:08Agile Manifesto
- 11:48Kanban
- 15:49Scrum
- 18:07Prioritization
- 20:14Pomodoro Technique
- 26:10Working with your stakeholders
- 32:40Software quality
- 39:23Retrospective
related talks
51m"Time Management for Developers"
47mMy unusual toolbox as a scrum master and Agile coach
47mUnleashing Your Super-dev-powers
33mHow to Enhance the Skills of Experienced Developers
10mCommon pitfalls of junior developers
50mThe Effective Developer - Work Smarter, Not Harder
01h 03mThe Effective Developer - Work Smarter, Not Harder.
48mThe Effective Software Architect - Work Smarter, not Harder