In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-03-28 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/03 Report--
Scrum is an agile development method for developing innovative products and services. We first take a look at the agile development process and characteristics, and focus on the roles, activities and artifacts of the Scrum framework. Then we introduce the team to use the requirements management, defect management, iteration management and other application functions in TAPD to help the team effectively practice Scrum agile development.
What is agile development?
What Agile Development advocates is to develop and implement product functions incrementally according to a certain priority through several short iteration cycles (also known as sprint sprint, the range is generally 1 week-1 month), and get a runnable product incremental function package for each iteration.
Agile development first needs to establish a priority product list, which is composed of product requirements, functional optimization or functional defects, and the items with high priority are first included in the iterative plan for implementation. these items are decomposed and refined before they are included in the iterative plan to meet the granularity implemented by the development team.
The lower the priority of the items in the lower row, this part of the requirements will not be put on the development implementation schedule for the time being, and the current stage can be roughly described, and there is no need to elaborate in order to deal with possible changes.
At the beginning of each iteration, a certain number of inventory items are selected from the product list as the goal tasks to be completed in this iteration, which are usually discussed and decided by all stakeholders, and the number depends on the situation of the development team. Try to match the development rhythm of the development team.
In the iterative process, the development team communicates the progress and problems faced by the standing meeting every day. During this period, the development team generally no longer accepts new product items or other development tasks, and special circumstances can accept the replacement of tasks.
At the end of each iteration, the team reviews work items such as realized product functions, and optimizes current work and development methods based on feedback. In the process, the product list needs to be continuously maintained and combed, such as inserting new requirements, updating existing product functional descriptions, or removing unwanted work items, and reprioritizing them. At the end of each iteration, start planning for the next iteration and restart the process.
Scrum framework
Scrum is one of the agile development approaches, and three roles are defined in its framework:
Product owner: responsible for finalizing what to develop and in what order to develop. He is mainly responsible for the maintenance of the product list.
ScrumMaster: help team members understand and accept the values and principles of Scrum, guide and assist in the implementation and optimization of the Scrum framework within the organization
Development team: includes traditional software development roles such as architects, developers, testers, etc. The development team as a whole is responsible for building working software products
The following figure illustrates the roles, activities, and artifacts in the Scrum framework:
The product owner establishes the product vision and forms the product list by combing.
At the beginning of the sprint (iteration), delineate the development work involved in this sprint through the sprint planning meeting, that is, the sprint list. The sprint list needs to be confirmed by the development team
After receiving the sprint list, the development team starts the sprint execution activity and makes planned checks and adjustments by standing every day during the sprint.
At the end of the sprint execution, produce a deliverable product increment
At the end of the sprint, the built product is reviewed and the implementation process is reviewed and optimized through sprint review and sprint review.
Practice of Scrum Development with TAPD
The applications on TAPD mainly include requirements management, defect management, iterative management, story wall, wiki and reports and so on. Using these TAPD application functions, we can easily and effectively practice the agile development process of Scrum.
1. Product list
The items of the product list in the Scrum framework mainly come from the management content in the requirements and defects in TAPD, and each sprint list is selected and assigned from these two parts of work, where:
The requirements list mainly records the functional requirements, technical research, and non-functional requirements of the product. It is classified and managed through requirements classification, and the coarse-grained requirements can be decomposed and refined by the way of sub-requirements. The priority setting is used to sort the requirements items. In addition, you can customize the view to filter the requirements items of the specified range. The main interface is as follows:
Defect management mainly records the realized product function bug, etc. By defining the input template of the defect, defining the record content of the defect, including the problem description, troubleshooting process, solution, etc., you can also define the defect list of the specified conditions for view filtering. The interface is as follows:
two。 Sprint planning and execution
In TAPD, the planning and execution of the sprint is realized through iterative management, the goal of this iteration is defined when the iteration is created, and the high priority items from the list of requirements and defects are assigned to the sprint plan, and each task item is implemented to the specific person in the development team. In the process of execution, the status of each requirement task follows the → realized / rejected process change in the planned → implementation, and the status of each defective task follows the new → receiving and processing → has resolved → has verified that the → has been closed to change the process, by updating and tracking the status of each task to achieve sprint plan tracking and control.
In addition, TAPD provides a sprint plan in the form of a story wall, including a status story wall and a resource story wall. Through the resource story wall, you can understand the task status and progress of everyone in the development team. Every day, you can explain the responsible work and difficult problems according to the display content of this story wall.
3. Sprint review and knowledge precipitation
At the end of the sprint, through the sprint review and review of the current sprint results and process feedback and collation, the use of Wiki application to record the content of sprint review and related technical knowledge. All members of the project team can access and update, and support full-text search, which is very convenient to use keyword queries. Through the review of the sprint, the development team confirms the output results; through the review of the sprint, finds out the shortcomings of the implementation process and optimizes it; through the precipitation of business and technical knowledge, accelerate the flow of relevant knowledge among team members.
Summary
The Scrum framework does not define the standardization process and does not guarantee that the team will be able to produce a customer-satisfied product within a specified period of time after following its steps step by step. On the contrary, each team must constantly explore and improve according to its own situation in order to establish a unique and effective practice based on the Scrum agile framework and form its own Scrum version.
Author: Li Hao
Review of previous periods
Jiawei attended the GOPS global operation and maintenance conference: in the peak era of operation and maintenance, the research and operation center may be the only choice.
Error message: network connection problem? Try netstat monitoring network connection!
How to manage and define cloudy?
How does DevOps achieve efficiency improvement?
Tencent PaaS Influxdb node migration
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 237
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.