What is 3-5-3 Structure in Scrum?
Scrum is one of popular agile methodologies. It is a framework to manage projects, which provides specific procedures, specifications and principles to achieve the project goal.
The quick way to understand Scrum is to understand the 3-5-3 structure.
Simply put, the structure is
- 3 roles: Product Owner, Scrum Master and the Team.
- 5 events: Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
- 3 artifacts: Product Backlog, Sprint Backlog and Increment.
If you want to know more about Scrum, you should read
- The Scrum Guide
- Daily Scrum, Review and Retrospective Meetings
- Scrum Poker: A Scrum Estimating Tool
- Kanban and Kanban tools
3-5-3 Structure in ZenTao
Based on the philosophy of Scrum, ZenTao integrates bug management, test case management, CI and document management, and it completely covers the entire life cycle of software development. In ZenTao, the concepts of product, project and test are clearly defined. Product team, developing team and testing team coordinate and check with each other while they function differently. The three teams interact with each other through stories, tasks and bugs, and eventually deliver the product with quality.
- Product Backlog
The product owner's or product manager's backlog is the master list of work that needs to be completed. This is a complex list of functions, specifications, updates, and fixes that serves as the sprint backlog's input. It is, in essence, the team's "To Do" list. The Inventory Owner regularly revisits, re-prioritizes, and maintains the product backlog.
The Sprint Backlog is a list of products, user stories, or bug fixes chosen by the development team for inclusion in the current sprint cycle. Before each sprint, the team decides which things from the product backlog to focus on during the sprint planning meeting (which we'll go through later in the article). A sprint backlog can be adaptable and evolve during the sprint.
The available end-product of a sprint is an increment (or Sprint Goal). It all depends on your team's definition of "Over" and how you interpret your sprint goals. Some teams, for example, chose to release something to their customers at the end of each sprint. As a result, their concept of "finished" would be "shipped."
- Increment (or Sprint Goal)