Kanban and scrum : making the most of both /

Saved in:
Bibliographic Details
Main Author: Kniberg, Henrik
Format: Book
Language: English
Published: United States of America : C4Media, ©2010.
Series: InfoQ Enterprise Software Development series
Subjects:
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

MARC

LEADER 00000nam a2200000 a 4500
001 000096060
003 CO-BoSNA
005 20260109094540.0
008 180516s2010^^^^xxk^^^^gr^^^^^000^0^eng^d
020 |a 9780557138326 
040 |a CO-BoSNA  |b spa 
082 0 4 |a 005.12  |b K691k  |2 23 
100 1 |a Kniberg, Henrik 
245 1 0 |a Kanban and scrum :  |b making the most of both /  |c Henrik Kniberg & Matthias Skarin. 
260 |a United States of America :  |b C4Media,  |c ©2010. 
300 |a xi, 104 páginas ;  |c 23 cm. 
490 0 |a InfoQ Enterprise Software Development series 
505 0 |a 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 
650 1 7 |a Scrum (Programa para computador)  |2 Armarc 
650 2 7 |a Control de la producción  |2 Armarc 
650 2 7 |a Ingeniería de software  |2 Armarc 
952 |0 0  |1 0  |4 5  |6 005_120000000000000_K691K  |7 0  |8 GENER  |9 452362  |a 68541  |b 68541  |d 2018-05-16  |i 68359  |l 0  |o 005.12 K691k  |p 689541000057  |r 2026-01-09 09:45:40  |t Ej. 1  |w 2026-01-09  |y BOOK  |z Calle 22 No. 9-82, San Gil 
952 |0 0  |1 0  |4 5  |6 005_120000000000000_K691K  |7 0  |8 GENER  |9 452363  |a 68541  |b 68541  |d 2018-05-16  |i 68359  |l 0  |o 005.12 K691k  |p 689541000058  |r 2026-01-09 09:45:40  |t Ej. 2  |w 2026-01-09  |y BOOK  |z Calle 22 No. 9-82, San Gil 
999 |c 99992  |d 99992 
942 |6 005_120000000000000__K691K