1 Download and Upgrade to 15.0+ Series
2 New Features of ZenTao 15 Series
3 Interface Changes of 15 Series
4 Update to the Latest Version
5 Quick Start of 15 Series
6. Basic Application of Version 15
6.1 Beginner
6.2 Add Integrally
6.3 API Library
7. Base On The Roles
7.1. Admin
7.1.1 Edit Departments and Team Members
7.1.2 Edit Users
7.1.3 Edit Privilege
7.2. Program Leader
7.2.1 Create a Program
7.2.2 Link to Products
7.2.3 Create a Project
7.2.4 Manage Staffs
7.2.5 Add a Program Stakeholder
7.3. Product Owner
7.3.1 Create a Product
7.3.2 Edit Modules
7.3.3 Product Multi-branch/Platform Management
7.3.4 Edit Plans
7.3.5 Edit Stories
7.3.6 Review a Story
7.3.7 Create a Release
7.3.8 Tracking Progress
7.4. Project Manager
7.4.1 Edit Projects and Execution
7.4.2 Edit Teams
7.4.3 Link to Stories
7.4.4 Split Tasks
7.4.5 Tracking Progress
7.4.6 Waterfall Project
7.4.7 Kanban Project
7.5. Development Team
7.5.1 Apply for Tasks and Bugs
7.5.2 Update Status
7.5.3 Complete Tasks and Bugs
7.5.4 Submit Codes
7.5.5 The General Kanban, Story Kanban, Bug Kanban, and Task Kanban
7.6. Test Team
7.6.1 Edit Users' Case
7.6.2 Execute Users' Case
7.6.3 Submit a Bug
7.6.4 Test and Close a Bug
8. DevOps Features
8.1 Git/SVN Repository Management and Viewing Code
8.2. Integrate GitLab
8.2.1 Integrate GitLab, Bind Users, Link to Issues and Create a Build
8.2.2 Integrate GitLab and Submit the Merge Requests
8.2.3 GitLab Privilege in ZenTao
8.3 Integrate Jenkins and Create a Build
8.4 Integrate SonarQube
9 General Kanban
10. Backstage Settings of Version 15
10.1 Desktop
10.2 Model
10.3 Custom
10.4. Message
10.4.1 Mail
10.4.2 Webhook
10.4.3 Browser
10.4.4 Settings
10.5 Extension
10.6 Secondary Development
10.7 System
10.8 Import Jira Data
10.9 Registration Menu and Privilege
11. Privileges Management and Access Control of Version 15
11.1 Privileges Management and Access Control for Programs
11.2 Privileges Management and Access Control for Products
11.3 Privileges Management and Access Control for Projects
11.4 Privileges Management and Access Control for Executions
11.5 Access Control and Data Relationships for Projects and Executions

Waterfall Project

2022-03-10 11:11:42
Jing
344
Last edited by WANG JING on 2022-03-10 11:14:45
Share links
Summary : From ZenTao 16.0.beta1, a new waterfall management model has been added. The functions of the Waterfall Project are introduced in this article.

From ZenTao 16.0.beta1, a new waterfall management model has been added.

Project management provides a new tool and a new method, users can choose a management model according to their actual needs, and enhance the flexibility of project management, which enhances the flexibility of project management.

The functions of the Waterfall Project are introduced as follows.

1. Create a Waterfall Project

Click the "Create" button, and on the "Select Management Type" page.

Click Waterfall (Waterfall Project Management) to jump to the Create Waterfall Project page.

The page for creating a waterfall project is basically the same as the page for creating a Scrum project. Fill in the information and click Save.

Different from the Scrum projects,after the waterfall project is created successfully, it will directly jump to the setup phase page.

On the setting stage page, you can set the workload ratio of each stage, the start and end time, access control, milestone phase or not, phase leader, etc.

After setting up a stage, you can view it in the project stage.

It can be searched and viewed by All, Incomplete, Not Started, In Progress, Suspended, and Closed tags.

Click on the stage name to jump to the stage's task list page. Click the "More" button, the drop-down list can view other stages under the waterfall project.

The functions of the waterfall project and the phase to which it belongs are basically the same as the Scrum project and the iteration/sprint to which it belongs, so will not be repeated here.

2. The Process of Waterfall Projects

ZenTao's waterfall project model divides the software life-cycle into six basic phases: Requirements, Design, Development,Testing, Release, and Review.

Scrum projects have a completely different life cycle, consisting of one or more executions, each of which is relatively independent of the other, independently developing requirements and solving some bugs.

A waterfall project is a fixed set of stages, and each stage is closely related. If the previous stage does not end, the next stage will not start.

  • Requirement Stage: 
    The main purpose is to organize, analyze user requirements, review requirements, and clarify the list of requirements. Tasks of transaction type can be created to manage the requirements sorting and review.
  • Design Stage: 
    The main purpose is to write summary design, detailed design, database design, and interface design documents for the defined requirements, and to review the design documents. Associated requirements, create design-type tasks and transaction type tasks for management.
  • Development Stage:
    It is almost the same as the iteration/sprint of Scrum project, that is, associate the identified requirements for development. Associate requirements, create development type tasks to manage, and view development progress based on burn-down charts, task boards, and various views.
  • Testing Stage:
    Test the requirements that have been developed during the development phase. Associate requirements, write test cases, and perform test case reviews. Create test-type tasks, transaction-type tasks to manage. Create a version and submit a test order, associate the test order with the test case, and execute the test order's case to complete the test.
  • Release Stage: 
    Release testing is performed for the version that has passed testing. Create transaction-type tasks and test-type tasks for management. After passing the test for the release version, you can perform "Project - Release" to complete the release of the entire project.
  • Review Stage: 
    Requirements start from sorting, to writing design documents, development, testing, and the final release. The summary review stage provides a conclusive review for the previous five stages, draw the experience and problems, to provide a reference for the subsequent project.

3. Design function of waterfall project

In the secondary navigation menu of Waterfall projects and Scrum projects, only the design function is currently unique to the Waterfall project.

Let's detail the use of the design function.

Design includes summary design, detailed design, database design, and interface design.

You can search through the All, Summary Design, Detailed Design, Database Design, and Interface Design tags, or you can search and view according to conditions.

The use of summary design, detailed design, database design, and interface design is basically the same. So we will take the summary design as an example and give you a detailed explanation.

Other designs can directly refer to the summary design.

3.1 Create Summary Design

Click the "Create" button on the right of the summary design to create and batch create designs.

Create a Design page, you can select relevant requirements and design types.

Only requirements associated with the project are listed in the Linked Story drop-down list. You can fill in the detailed information of the summary design document in the Description, or upload the written summary design document as an attachment.

Successfully created summary design can be viewed in the list.

3.2 Summary Design Operations

The summary design can be assigned, changed, associated commit, and deleted.

3.2.1 Assignment and deletion of Summary designs

Assigning a design brief can be done by clicking on the AssignedTo. The assignee can go to view and make changes to the design document.

Click Delete, and in the pop-up prompt, click OK to delete the summary design, and click Cancel to not delete it.

3.2.2 Change of Summary Design

Once the summary design has been created successfully, it needs to be modified only through the modification operation.

3.2.3 Associated Submission of Summary Design

A design document can be associated with a commit of the repository. To implement this function, you need to create a repository of the product associated with the waterfall project in the DevOps function module.

After the creation is successful, you can see the repository information under Project--Code.

View the code submission information associated with the design by clicking on the View Commits button on the right side of the Summary Design list page.

You can also submit an associated design by clicking the associated submit button.

On the associated commits page, you can filter the repository and commit time, check the submission, and click Save.

A design can be associated with one or more commits.

Successfully associated submissions can be viewed in the related commits of the design, and you can also remove commits on this page.

4. Custom Stage Types and Stage Lists

4.1 Custom Stage Type

Our default stage types are Requirements, Design, Development, Test, Release, Review, and Others.

You can go to the "Admin" - "Waterfall" to customize the stage type according to the actual work needs. You can modify the original stage type, or delete the original stage type and add the stage type you actually require.

The default stage types are:

4.2 Custom Stage List

Similarly, our default phase types are: Requirements, Design, Development, Test, Release, and Review.

The current default stage type has the same name as the stage type, with the difference that the workload ratio is listed in the stage list.

It should be noted that in the maintenance stage of a waterfall project, the total workload of all phases is 100%. Therefore, in the background maintenance phase, the workload ratio of each phase needs to be fully considered.

All can be customized according to work needs.

To add a stage, click the "Create" or "Batch Create" to enter the Add Stage page.

After the addition is successful, you can view it in the stage list.

Write a Comment
Comment will be posted after it is reviewed.