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
Monday, May 13, 2019
Approach to teams
Whole Team Approach
Whole team approach means everybody in the team is responsible for quality and success of the product. It is unlike the previously held view that quality can be a outside in thing (inspected and fixed - software testing), and can be injected. Quality is in-built into the product, and it is the team as a whole responsible for it. Success likewise cannot be driven by a project manager or another outside (of the team) role. It is for the team to organize, collaborate and succeed. 
Approach to Teams - another way to look at it
- Team Formation
- Training
- Overview
- PO Training
- SM / Team Training
- Gamification
- Estimation
- XP Practices (Pair / Mob Programming, Refactoring, TDD, etc.)
- Skill Gap Analysis
- Develop T, M Skills
- Trainings - internal external as required
- Inspect & Adapt
Friday, May 10, 2019
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...

 
 




 
