1. Introduction
1.1 About ZenTao
1.2 Introduction PDF
1.3 Technical Support
1.4 Follow Us
2. Installation
2.1 Choose the Right Installation
2.2 ZenTao Cloud
2.3 One-click Installation for Windows
2.4 One-click Installation for Linux
2.5 Lampp Installation in Linux
2.6 Source Code Installation (for all systems)
2.7 Source Code Installation for macOS
2.8 XAMPP-VM Installation for macOS
2.9 XAMPP Installation for macOS
2.10 Install ZenTao in Docker
2.11 Install httpd, Mariadb, PHP 7.2 in Cent OS 8
2.12 Softaculous Service
2.13 Install Ioncube
3. Update
3.1 Update ZenTao
3.2 Update Via Source Code (For All Systems)
3.3 Update for One-Click Installation for Windows (xampp)
3.4 Update for One-Click Installation for Linux
4. Users and Groups
4.1 Company Structure
4.2 Add a User
4.3 Manage Users in batches
4.4 Groups and Privileges
5. Quick Start
5.1 Project and Task Management
5.2 Bug Tracking
5.3 Product Management
5.4 Todo Management
6. Basic Application
6.1 Basic Workflow
6.2 Agile and Scrum
6.3 ZenTao and Scrum
6.4 ZenTao Tutorial for Rookies
6.5 Create a Product
6.6 Create a Story
6.7 Create a Project
6.8 Confirm a Story
6.9 Decompose Stories into Tasks
6.10 Report a Bug
6.11 Manage Contacts
6.12 Customization
6.13 Import Excel, CSV Files
6.14 Document Management
6.15 Work Mode
6.16 Points
6.17 Required Field
6.18 Privileges
6.19 Annual Work Summary
7. Advanced Application
7.1. Workflow
7.1.1 ZenTao Workflow
7.2. Individual management
7.2.1 My Todo
7.2.2 My Task, Story and Bug
7.2.3 My Profile
7.3. Product Owner
7.3.1 Manage a Product
7.3.2 Manage a Product Line
7.3.3 Create and Review a Story
7.3.4 Change and Review a Story
7.3.5 Status and Phase
7.3.6 Story Writing
7.3.7 Product Module
7.3.8 Release Plan
7.3.9 Create a Release
7.3.10 Roadmap
7.3.11 Documents
7.3.12 Planning Meetings
7.3.13 Daily Scrum, Review and Retrospective Meetings
7.3.14 Story Reports
7.4. Scrum Master
7.4.1 Create a Sprint
7.4.2 Set a Team
7.4.3 Confirm a Story
7.4.4 Task Breakdown
7.4.5 Daily Standup Meetings
7.4.6 Check Project Progress via Burndown Chart
7.4.7 Check Project Progress via Lists
7.4.8 Review and Retrospective Meetings
7.4.9 Basic reports on tasks
7.5. Development Team
7.5.1 Project planning meeting and task breakdown
7.5.2 Claim tasks and update efforts
7.5.3 Kanban and Tree Diagram
7.5.4 Build
7.5.5 Test Request
7.5.6 Resolve a Bug
7.5.7 Documents
7.5.8 Confirm Bugs
7.6. Test Team
7.6.1 Bug Tracking
7.6.2 Report a Bug
7.6.3 Verify and Close a Bug
7.6.4 Activate a Bug
7.6.5 Find a Bug
7.6.6 Test Case
7.6.7 Create and Review Test Cases
7.6.8 Test Suites, Public Case Libs and Reports
7.6.9 Manage Test Requests
7.6.10 Run Cases and Report Bugs
7.6.11 Reports
8. Configuration
8.1. Maintain ZenTao
8.1.1 Initialize scripts
8.1.2 Data Backup
8.1.3 Recover the Deleted
8.1.4 Update Burndown Charts
8.1.5 ZenTao Remote Host
8.2. Deploy ZenTao
8.2.1 Guest Login
8.2.2 Email Notification
8.2.3 Set Super Admin
8.2.4 Static Access
8.2.5 Remove "zentao" from URL
8.2.6 Integrate SVN
8.2.7 Integrate Git
8.2.8 Integrate Webhook
8.2.9 Integrate Xuan.im
8.2.10 Integrate Zdoo
8.2.11 Integrate Third-Party Apps
8.2.12 Password-Free Login
8.2.13 Translation Add-on
8.2.14 Integrate Jenkins
8.2.15 Extension
8.2.16 Fix Weak Password
9. Customization
9.1 Introduction
9.2 Directory
9.3 Find Codes
9.4 Database Structure
9.5 Common Modules
9.6 Add Features to Menu
9.7 Set Privileges to Modules
9.8 Examples: modify language prompt
9.9 Examples: set priority when creating bugs
9.10 Extension Editor
9.11 Feature Limitation
9.12 ZenTao Packaging Standards 1.1
10. Misc
10.1 About Third-Party Code
10.2 Support ZenTao
10.3 ZenTao Service
10.4 Acknowledgement

Agile and Scrum

2015-09-10 16:21:23
Last edited by Taotao on 2021-03-08 10:27:53
Share links

Because the design philosophy of ZenTao is based on Scrum,  it will help you learn and use ZenTao better, if you could understand the basic concepts in Scrum.

1. Agile

Waterfall is the well-known method of software project management, and its basic process is story -> development -> test. It is assumed that the final result is right, if each phase is done correctly. There are successful cases with Waterfall, such as Microsoft. But, in general, it has a relatively high failure rate. Software pioneers have made a series of researches, thinkings, and summaries about the problems found in the Waterfall methodology and finally put up the concept of Agile. There are various methods of Agile development, and Scrum is a relatively popular one.

2. Scrum

2.1 Scrum Roles

Scrum roles include the Product Owner, the Scrum Master, and the Development team. 

  • Product Owner is responsible for collecting user stories, defining their commercial values, prioritizing them and making release plans. They are fully responsible for the product.
  • Scrum masters are in charge of holding various meetings, coordinating projects and serving the Development team.
  • Development team is a group of people with different skills. They complete each sprint and deliver products through close cooperations.

2.2 Sprint

Being different from the waterfall development, the product development in Scrum is decomposed into a number of sprints. Usually, a sprint is 1~4 weeks and done by 5~9 team members. User stories to accomplish is fixed in each sprint. Each sprint will bring a certain delivery.

2.3 Basic process of Scrum

The basic workflow of Scrum is shown as above.

  • Product owners collect user stories and create the product backlog as shown at the left of the image above.
  • Release Planning Meeting: product owners explain user stories, estimate and prioritize them. The output of release planning meeting is to make a story list of each sprint and to record sprint backlog.
  • Sprint Planning Meeting: project teams do task breakdown for each story. The breakdown standard is that all the tasks must be finished and each task is assigned to a specific person with an estimation of man-hours.
  • Daily Scrum Meeting: Scrum masters hold a daily stand-up meeting, and the team members report what they did yesterday and what they will do today, and what their problems are.
  • Review Meeting: when a sprint is over, all members involved will get together to have a review meeting. The team will show the deliverables of the Sprint. All the feedbacks should be recorded and compiled to create new stories.  
  • Retrospective Meeting: project teams summarize the sprint, identify the deficiency and make plans in next sprint for continuous improvement. 

See also

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