<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>Kanban and scrum</title>
    <subTitle>making the most of both</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>Kniberg, Henrik</namePart>
    <role>
      <roleTerm authority="marcrelator" type="text">creator</roleTerm>
    </role>
  </name>
  <typeOfResource>text</typeOfResource>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">xxk</placeTerm>
    </place>
    <place>
      <placeTerm type="text">United States of America</placeTerm>
    </place>
    <publisher>C4Media</publisher>
    <dateIssued>©2010</dateIssued>
    <dateIssued encoding="marc">2010</dateIssued>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <extent>xi, 104 páginas ; 23 cm.</extent>
  </physicalDescription>
  <tableOfContents>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</tableOfContents>
  <targetAudience authority="marctarget">general</targetAudience>
  <note type="statement of responsibility">Henrik Kniberg &amp; Matthias Skarin.</note>
  <subject authority="Armarc">
    <topic>Scrum (Programa para computador)</topic>
  </subject>
  <subject authority="Armarc">
    <topic>Control de la producción</topic>
  </subject>
  <subject authority="Armarc">
    <topic>Ingeniería de software</topic>
  </subject>
  <classification authority="ddc" edition="23">005.12 K691k</classification>
  <relatedItem type="series">
    <titleInfo>
      <title>InfoQ Enterprise Software Development series</title>
    </titleInfo>
  </relatedItem>
  <identifier type="isbn">9780557138326</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">CO-BoSNA</recordContentSource>
    <recordCreationDate encoding="marc">180516</recordCreationDate>
    <recordChangeDate encoding="iso8601">20260706161835.0</recordChangeDate>
    <recordIdentifier source="CO-BoSNA">000096060</recordIdentifier>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">spa</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
