- Even if the team is using tasks, WIP limits should primarily be applied to PBI and not tasks. Limiting tasks may be useful, but doesn't replace limiting WIP at PBI level.
- Flow of Value / Learnings = Flow of PBI and not the tasks
Scraps from various sources and my own writings on Generative AI, AGI, Digital, Disruption, Agile, Scrum, Kanban, Scaled Agile, XP, TDD, FDD, DevOps, Design Thinking, etc.
Page Hits
Thursday, September 27, 2018
What item of WIP are you limiting in a Scrum with Kanban?
Monday, September 24, 2018
Friday, September 21, 2018
Tuesday, September 18, 2018
Friday, September 14, 2018
Coaching Levels...
Not intending to sound hierarchical, agile coaching targets several layers of the management / teams.
1. Executive Coach -- CXO's
2. Enterprise Coach -- Directors
3. Agile Coach -- Senior Managers / General Managers
4. Scrum Master -- Team coach
1. Executive Coach -- CXO's
2. Enterprise Coach -- Directors
3. Agile Coach -- Senior Managers / General Managers
4. Scrum Master -- Team coach
Wednesday, September 05, 2018
Subscribe to:
Comments (Atom)
If we already have automation, what's the need for Agents?
“Automation” and “agent” sound similar — but they solve very different classes of problems. Automation = Fixed Instruction → Fixed Outcome ...
- 
Requirements Analysis -- Business requirements document or business requirements specification System Design -- Systems requireme...
 
 


 
