Kanban: Successful Evolutionary Change for Your Technology Business
Giv mig besked når bogen er tilgængelig
Vurdering
Føj til hylde
Har allerede læst
Rapportér en fejl i denne bog
Del
Facebook
Twitter
Kopier link
Denne bog er ikke tilgængelig i streaming pt. men du kan uploade din egen epub- eller fb2-fil og læse den sammen med dine andre bøger på Bookmate. Hvordan overfører jeg en bog?
Card walls common in agile software development are not kanban systems.
Alex Polorotovhar citeretfor 3 år siden
But I knew that these processes were derived from the same principles and that because team members understood those basic principles, they were therefore capable of adapting when reassigned from one team to another.
Alex Polorotovhar citeretfor 3 år siden
simple act of limiting work-in-progress with kanban encourages higher quality and greater performance.
Alex Polorotovhar citeretfor 3 år siden
doing this we can achieve a sustainable pace of development so that all individuals can achieve a work versus personal life balance.
Alex Polorotovhar citeretfor 3 år siden
should become evident in subsequent chapters, we use a kanban system to limit a team’s work-in-progress to a set capacity and to balance the demand on the team against the throughput of their delivered work.
Alex Polorotovhar citeretfor 3 år siden
However, if there is no explicit limit to work-in-progress and no signaling to pull new work through the system, it is not a kanban system. This is more fully explained in chapter 7.
Sergeyhar citeretfor 11 år siden
Balancing demand against throughput implies that we will set the rate at which we accept new requirements into our software development pipe to correspond with the rate at which we can deliver working code.
Sergeyhar citeretfor 11 år siden
Balance Demand against Throughput Prioritize Attack Sources of Variability to Improve Predictability
Sergeyhar citeretfor 11 år siden
The six steps in the recipe are Focus on Quality Reduce Work-in-Progress Deliver Often
Sergeyhar citeretfor 11 år siden
Measure and Manage Flow Make Process Policies Explicit Use Models[1] to Recognize Improvement Opportunities