The agile development of scrum is relatively strict with the process control. Each stage has a complete set of processes and strict time control. The main development process of our project team is as follows:
The picture is taken from the book scrum-Checklists-Chinese. I modified the content in Chinese. Next I will split the entire process one by one,
- Full meeting: mobilize the development team to announce the establishment of the project team on a formal occasion. Describe the project vision and define the development process to the team members. And the technologies that will be used in the prediction, so that the team members can have a preparation time. The meeting will be completed in about two hours.
- Product story list: completed by the product owner. After the full meeting, our team received three days of free trial. During this period, the product owner will organize the requirements into a list of stories. A story is similar to a common use case, but the text description only stays at the business level and never involves technical terms. We mainly use Excel documents. Our documents mainly include the story ID, story name, how to demonstrate, importance level, and the fields of the module.
- Sprint Development (Sprint). So far, all preparations have been completed and the Sprint has started. Regarding the setting of each sprint time, our project team chose two weeks as a sprint cycle.
- Sprint plan meeting: There are two parts in the Sprint plan meeting. In our project development, we found that we can basically deal with all the projects in about two hours, so we can just do a plan meeting. First, we will ask the product owner to describe each product story and directly communicate with developers in this process. Then, evaluate the time required for the product story based on the Importance level, and select the product story to be implemented in this sprint. Next, developers split the tasks that can be completed on a daily basis. The direct product of the Sprint plan meeting is the sprint task list.
- Sprint task list: as a product of the Sprint plan meeting, the sprint task list will play a guiding role in the next two weeks. It is divided into three columns: undeveloped, under development, and not under development, plus a sprint burnout chart.
- Sprint and daily meeting: the two-week development will start after the scheduled meeting, during which the daily meeting will start at every day, taking 5 to 10 minutes. The popular daily standing meeting was not implemented in our project team. Our project team is not talking too much in meetings, so it is unnecessary to stand up to prevent such behavior. After the daily meeting, each person updates his/her task table. I also need to update the burned-out chart every day.
- New Function Demonstration: the demonstration is completed by the product owner of the organization, and the product owner evaluates the new function module.
- Sprint Review Meeting: the Development Team reviews the successes and failures of this sprint and summarizes them so that they can do better in the next sprint.
We plan to complete our cms1.0 version after four sprints.
