Developing a Scrum Project
The following topics describe the development process of Scrum projects:
- Requirement Breakdown and Multi-Role Collaboration
- Continuous Iterative Delivery for Closed-Loop Feedback
- Development Example
Requirement Breakdown and Multi-Role Collaboration
In Scrum projects, requirements can be broken down in the four-layer hierarchy: .
Continuous Iterative Delivery for Closed-Loop Feedback
Scrum is an incremental, iterative, and agile software development method. It enables continuous delivery through repetitive sprints, which are cycles of closed-loop software development from user requirements planning to user feedback collection.
Sprint planning meetings, daily Scrum meetings, sprint retrospective meetings, and sprint review meetings are key to simple but efficient project management.
Development Example
The following figure shows the basic process of a Scrum project. This process can be repeated for continuous planning and delivery in each sprint.
|
Step |
Description |
|---|---|
|
Create Scrum project |
For details, see Creating a Scrum Project.
NOTE:
You can invite other users to join a Scrum project after it is created. For details, see Managing Members. |
|
Plan requirements |
Plan requirements using mind maps or Gantt charts based on the project breakdown needs. For details, see Mind Maps and Gantt Chart. |
|
Create work items |
Create work items after the requirements are planned. For details, see Creating a Work Item (Epic/Feature/Story/Task or Bug). |
|
Manage sprints |
Plan and manage sprints. For details, see Managing Sprints. |
|
(Optional) Customize workflows |
Customize the workflows as required. For details, see Customizing Workflows. |
|
Review sprints |
Review the sprints for improvements. For details, see Organizing Sprint Retrospective Meetings. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
