The simple idea of Kanban: work-in-progress (WIP) must be limited
WIP ceiling and pull Production
1. Scrum and KanbanScrum: Organization splitting, work splitting, development time splitting, optimization of release plans, Process Optimization dashboard: process visualization, restriction of WIP, measurement of production cycle
2. Relationship between scrum and KanbanScrum and Kanban are both process tools. Scrum and Kanban only give some clear constraints and guidance. For example, scrum constraints are fixed duration iterations and cross-functional teams, the constraint of Kanban is to have a visible kanban, and the size of the queue must be constrained.
Agile methods are also called Lightweight methods.
3. Scrum defines rolesScrum defines three roles: Po, team, and SM. The dashboard does not specify any roles.
4. Scrum specifies a fixed duration iteration.Scrum iterations mix three types of activities: planning, process improvement, and release.
5. Scrum limits WIP by iteration, and dashboard limits WIP by flow status
6.
Scrum and Kanban are both empirical and require introspection/feedback/adjustment
7.
Scrum rejects changes during Iteration
The principle of Kanban is "one piece out, one piece in". The response time is equal to the processing time of the task at hand.
The average response practice of scrum is equal to half of the sprint Length
8.
Task ScaleThe SCRUM team only undertakes the tasks that can be completed in one iteration. If the tasks are too large to be split, the dashboard does not clearly define the task scale and must be completed in a certain period of time.
9. Scrum specifies estimation and productivity, and Kanban does not specify EstimationSome teams skip estimation, split each task close to the same size, and count the number of features completed each week. Some teams package tasks into MMF (minimum marketable features) to measure the production cycle of each MMF, establish SLA (Service Quality commitment)
10. How to Use backlog for cross-product teamsThe product backlog can be viewed as a team backlog. Multiple products can be distinguished through the swimming channels.
------------------------------------- Scrum and dashboard. After reading this book, it is clearer than before (I think)
1. scrum focuses more on the team's organization and job splitting (implementation), and Kanban focuses more on the visualization (Presentation) of the job flow. dashboard makes the team work more transparent, and more meticulous work requires scrum to implement the implementation (three sessions, various roles, estimation, sprint) 3. both of them are process tools. Like the design model, they are previous experiences. to apply them to the team, you need to extract the best of them and find a method suitable for the team. 4. the team usually uses scrum and Kanban in combination.
Several keywords in the book,
WIP: work-in-progress, work-in-process, WIP must be restricted. This is one of the main concepts of Kanban. Swimming: it first appeared in UML and was also called partition Lane, in addition to vertically defining columns by status, you can also use horizontal swimming channels to differentiate them. For example, you can differentiate multiple products in a team using the T-shirt method: used for estimation, small/medium/large, qualitative and non-quantitative
From Weizhi note (wiz)
Kanban and scrum Reading Notes
