Two Methods
Although agile born only 20 years, but it has helped many companies succeeded, during which there have been various agile methodology and ideology, this article, we try to discuss a problem: prepare for the implementation of agile teams how to choose between Scrum and Kanban are two methods? (Special note: Some would say that Kanban is actually mind-set, not the methodology, here we do not want to fall into the concept of the fight, they just want to explain the applicable scenarios, so the following method will call them, without distinction deliberately) .
Both Scrum and Kanban are as consistent with lean thinking and quick thinking results inevitably there are some similarities between them:
-
Both limit the number of development work
-
Both are driven by the improved transparency of the process
-
Both advocate mention timely delivery and stable value
-
Both are based on self-organizing type of team
-
Both require the Work Breakdown
-
Both are continuously optimized based on empirical data
Let's look at some of the differences between the two:
The following examples demonstrate how to combine Scrum and Kanban these two methods is reflected in Worktile Agile in.
Scrum
In the standard Scrum process definition, there are two key products: Product Backlog and Sprint Backlog, as well as four key conference: planning meeting, daily legislature, review meetings and review meetings.
In Worktile Agile products, we divided the Product Backlog demand and defects, which needs to use part of Epic-Feature-User Story three systems to represent.
-
Epic: Epic, represents the larger properties, the development cycle is generally from January to March, for product planning roadmap
-
Feature: characteristics, represents a relatively small number of properties, the development cycle is generally 1-3 weeks for product release planning
-
User Story: user story represents the minimum user scenarios, the development cycle is generally 1-3 days for iteration planning.
Figure 1 Worktile Agile Requirements Management
Will be held at the beginning of each iteration planning meetings, will participate in full, the most important thing of this meeting is to determine the Sprint Backlog, the Product Owner in accordance with the priority introduction Product Backlog, then the team decide whether a particular entry into the current iteration.
Figure 2 Worktile Agile iterative planning
Time iteration, there will be a day for 10-15 minutes of stand-ups, each member of the team in front Worktile iterative tasks plate presentation is based on a working day doing things, and the problems encountered.
FIG 3 Worktile Agile iterative task board
Held a review meeting at the end of the iteration, each person based product demonstrations themselves in this iteration of the complete results, team members can make some suggestions in the review meeting for the completion of. After the review meeting, the team members will be held with the iteration retrospective, the retrospective Scrum is an iterative practice last part is the most important part, the entire iterative review will form a closed loop iteration. Review issues raised at the meeting recording through an iterative review panel.
Figure 4 Worktile Agile iterative review panel
Scrum in practice, most of the team will ignore version management, iteration is for activity behavior Scrum team, and version management for the product, which is the definition of the concept of a batch for version management and delivery schedule risk management, clear in one version of the final deliverables, Worktile Agile you can create a version and it is associated with the iteration, or simply setting a user story / defects belong to a version
Figure 5 Worktile Agile in version management
Kanban
For a team approach to managing the use of Kanban whether success depends on the use of Kanban can bring the following improvements for your team:
-
Help teams visualize the flow of the entire value chain
-
Help teams identify the value of liquidity risk points
-
Help the team measure the value of various waste flows and to eliminate them
Based on these considerations, Kanban type Worktile Agile project in currently supports the following capabilities:
-
Able to clearly define the process WIP
-
It can be clearly defined in the article limits WIP Limit
-
Clearly defined DoD
-
Support multi-lane divided
Figure 6 Worktile Agile Kanban in the project
In the same project in the Worktile Agile, Kanban support to create multiple, different definitions for your convenience more different billboards, or team roles based on business scenarios, and can be personalized for the needs of each configuration kanban.
Figure 7 according to individual needs of your team Kanban
Local conditions
Finished the basics of Scrum and Kanban, as well as the support for the Worktile Agile Scrum and Kanban, we take a look at the actual landing team, how the actual situation to choose between the two.
- If your team is product-oriented, it is recommended to use Scrum; if it is research-oriented, such as performance optimization, code optimization, uncertainty is very large, it is recommended to use Kanban.
- Group size is moderate, about 5-9 people, and there are cross-functional team members, recommended to use Scrum; the contrary, if your team size is relatively small, only about 2-5 people, it is recommended to use Kanban, relatively high efficiency.
- Product or project delivery is calculated according to a certain period, such as every two weeks or every month requires a new version, it is recommended to use Scrum; if the product or project delivery is not calculated in cycles, but in accordance with a specific event as a symbol, such as a 10 percent performance increase released a new version, it is recommended to use Kanban.
Of course, these are only a little from experience, it depends on the specific situation of the team, according to local conditions to promote the real floor in agile teams, rather than a mere formality.
Author: Worktile CTO Terry
Worktile official website: worktile.com
Article first appeared in " Worktile official blog ", please indicate the source.