| Notas Contenido: |
- Comparison
- What is Scrum and Kanban anyway?
- How do Scrum and Kanban relate to each other?
- Scrum prescribes roles
- Scrum prescribes timeboxed iteration
- Kaban limits WIP per worflow state, Scrum limits WIP per iteration
- Both are empirical
- Scrum resists change within an iteration
- Scrum board is reset between each iteration
- Scrum prescribes cross-functional teams
- Scrum backlog items must fit in a sprint
- Scrum prescribes estimation and velocity
- Both allow working on multiple products simultaneously
- Both are lean and Agile
- Minos differences
- Scrum board vs Kanban board - a less trivial example
- Case study
- The nature of technicaloperations
- Why on earth change?
- Where do we star?
- Getting going
- Starting up the teams
- Addressing stakeholders
- Constructing the first board
- Setting the first work in progress (WIP) limit
- Honoring the work in progress (WIP) limit
- Which tasks get on the board?
- How to estimate?
- So how did we work, really?
- Finding a planning concept that worked
- What to measure?
- How things started to change
- General lessons learned
|