Scrum related concepts

1. agile
Agility
2. Backlog
One job
3. Build
It refers to a runable software version that has been compiled and built.
4. burndown chart
This graphic tool is used to display the amount of work that has not been completed. Generally, the time is used as the horizontal axis, and the work to be completed in this iteration is used as the vertical axis.
5. Code Review
Code Review, usually completed by non-code writers.
6. Daily scrum MEETING
Daily scrum meeting. Every 15-minute daily meeting, every member of the team should answer the following three questions: What have I done since the last meeting? What will I do before the next meeting? Is there anything that hinders my work?
7. In progress
In progress
8. product backlog
Product feature line list, which is maintained and defined by the product owner.
9. product backlog item
In the product feature list, each item is a unit of work, and its size must be limited to the number of items that the team can complete in one iteration. A work unit can be divided into multiple tasks.
10. Product owner
The product owner is responsible for determining the priority of each entry in the backlog and solving all requirements.
11. Scrum
Scrum once came from British rugby and compared the software development team to rugby. Scrum is one of the popular agile development methods.
12. Scrum master
The person responsible for managing the daily scrum process serves as a bridge between the product owner and the team. They should promote cooperation between the two parties, resolve obstacles and problems for the team members, and ensure the smooth operation of their work. The SCRUM master is equivalent to a project manager or supervisor in a traditional software development project.
13. Sprint
A sprint represents an iteration of scrum. The cycle is usually 30 days, during which additional requirements cannot be added to the team to ensure that the expected results are obtained at the end of the iteration.
14. Sprint planning meeting
The spint plan meeting will be held at the beginning of an iteration. The Team and the product owner will discuss the objectives of this iteration and decide what work should be done in this iteration.
15. Sprint review meeting
The Sprint review meeting is held at the end of an iteration. Generally, the team displays the functions completed by this iteration in the form of a demo.
16. Sprint impact spective MEETING
The Sprint review meeting will be held after the sprint Review Meeting. The Team and the scrum master will discuss which aspects of the iteration are better and which areas need improvement so that the team can continue to grow.
17. Stakeholders
Stakeholders are a type of people who have little impact on project success or failure. They participate in product requirements and actively provide feedback.
18. Task
Task
19. Team
The number of different functional scrum teams is limited to 3 ~ 10. roles may include developers, architects, testers, and UI designers. As a self-organizing team, the team members decide how to better meet user needs, and take appropriate responsibilities.
20. User story
User stories (scenarios) briefly describe a function of the system from the user's perspective.
21. Wiki
Wikipedia is an open and shared online document editing system. Anyone can edit and modify documents in this system. The earliest application is the online open encyclopedia, it is widely used in various document systems.