ZenTao ManualBook Info
1 Introduction
1.1 About ZenTao
1.2 Introduction PPT
1.3 Technical Support
1.4 Follow Us
2 How to Install ZenTao
2.1 Choose the best installation
2.2 ZenTao Cloud
2.3 One-click Installation for Windows
2.4 One-click Installation for Linux
2.5 Installation with Lampp
2.6 Source Code Installation (for all Systems)
2.7 Set up Virtualbox for ZenTao
2.8 Softaculous service
3 Upgrade ZenTao
3.1 Upgrade ZenTao
3.2 Upgrade by source code (for all systems)
3.3 Upgrade for one-click installation for Windows (xampp)
3.4 Upgrade for one-click installation package for Linux
4 Users and Groups
4.1 Organization Structure
4.2 Add a User
4.3 Batch Manage Users
4.4 Groups and Privileges
5 Simple Application
5.1 Project and Task Management
5.2 Bug Management
5.3 Product Management
5.4 Individual Task 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 Stories
6.9 Story Breakdown
6.10 Report a Bug
6.11 Manage Contacts
6.12 Customization
7 Advanced Application
7.1 Workflow
7.1.1 ZenTao Workflow
7.2 Personal management
7.2.1 My Todo
7.2.2 My Task, Story and Bug
7.2.3 My Profile
7.3 For 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 Story Status
7.3.6 Notes for Writing a Story
7.3.7 Product Modules
7.3.8 Release Plan
7.3.9 Create a Release
7.3.10 Roadmap
7.3.11 Manage Documents
7.3.12 Product Planning Meetings
7.3.13 Daily Scrum, Review and Retrospective Meetings
7.3.14 Story Reports
7.4 For Project Manager
7.4.1 Create a Project
7.4.2 Set up a Team
7.4.3 Confirm Stories
7.4.4 Story 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 For Development Team
7.5.1 Project planning meeting and task breakdown
7.5.2 Claim tasks and update
7.5.3 Kanban and Tree Diagram
7.5.4 Create a Build
7.5.5 Test Task
7.5.6 Resolve a Bug
7.5.7 Manage Documents
7.5.8 Confirm Bugs
7.6 For QA Team
7.6.1 Bug Management
7.6.2 Report a Bug
7.6.3 Confim and Close a Bug
7.6.4 Activate a Bug
7.6.5 Locate a Bug
7.6.6 Test Cases
7.6.7 Create and Review Test Cases
7.6.8 Manage Test Tasks
7.6.9 Test Suites, Public Case Libs and Reports
7.6.10 Manage Test Tasks
7.6.11 Execute Cases and Report Bugs
7.6.12 Reports
8 Configuration
8.1 Maintain ZenTao
8.1.1 Initialize scripts
8.1.2 Back up ZenTao
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 Configure Static Access
8.2.5 Delete "zentao" from the address
8.2.6 Integrate ZenTao with SVN
8.2.7 Integrate ZenTao with Git
8.2.8 Integrate webhook
9 Custom Development
9.1 ZenTao customization
9.2 ZenTao Directory
9.3 Locate and Change Files
9.4 ZenTao 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 Web Editor
9.11 Packaging Standards of ZenTao 1.1
10 Other Relevant Issues
10.1 About third-party code
10.2 How to Help ZenTao
10.3 ZenTao Business Service
10.4 Acknowledgement

Agile and Scrum

2015-09-10 16:21:23
Last edited by Renee on 2018-01-08 10:13:46

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 of Scrum.

1. Agile

Waterfall is the well-known method of software project management, and its basic process is story -> development -> QA. 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 development and finally put up the concept of Agile. There are various Agile development, and Scrum is a relatively popular one.

2. Scrum

2.1 Scrum Roles

Scrum roles include Product Owner, Scrum master and 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 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. 

This is the basic process of Scrum and we will continue to elaborate it further in relevant chapters.

    Write a Comment
    Comment will be posted once reviewed.