Agile Development (v)-Framework scrum content

This article is primarily designed to test your understanding and use of scrum,
Through this article you can test
1. Are the roles in your scrum project qualified,
2. Is there a legacy of the meetings required on scrum, and whether the meeting process is correct
3, the output of the project is correct.
One, the SCRUM function:
1. Product Owner
(1), define all product functions
(2), determine the content of the product release and date
(3), responsible for the input and output of products
(4) Prioritize the functions that need to be developed according to market changes
(5), reasonable adjustment of product function and iteration sequence
(6), agree or reject the delivery of the iteration
2. Scrum Master
(1), direct management of the project
(2), lead the team to complete the practice of scrum and reflect its value
(3), to eliminate the difficulties encountered by the team
(4) To ensure that the team is competent for its work and to maintain efficient productivity
(5), so that the team work closely together, so that the team has a multi-functional capacity
(6), protect the team from external unwarranted influence
3. Team
(1), the classic team has 5-9 people
(2), the team members are all-rounder:
(3), programmers, testers, user experience design, and so on.
(4), team members are full-time workers
(5), special functions can be excepted (for example, database administrator)
(6), Team self-organization and management
(7), a team relationship should be fixed in one iteration, and individual functions can be adjusted at the beginning of a new iteration
Ii. The process of SCRUM

(Click the option below to enter the link)
1.Full-fledged meeting
2.Evaluation meeting
3.Sprint Planning Session 1
4.Sprint Planning Session 2
5.Scrum Daily meeting
6.Sprint Review Meeting
7.Sprint Review Meeting
iii. Scrum output:
1.Product Backlog
2.Demand
3.List of jobs to be completed in the project
4.Ideally, every work to be done will generate value for customers and users.
5.The product owner will prioritize this list
6.The prioritization of priorities before the start of each iteration needs to be revised again
7.Iteration Backlog
8.Burndown Chart
Examples of product Burndown drawings
Iv. SCRUMCharacteristics
      1. Simple development process
      2. Rapid changes in demand for iterative, incremental development of product development systems
      3. Control of processes that are confused by conflicts of interest and demand
      4. Improve communication and optimize cooperation
      5. Detect obstacles in product development and production process and remove obstacles
      6. Summary of the design process
      7. Maximizing productivity
      8. To give each participant the best possible level and to be proud and proud of its contribution
Unlike the traditional development model:
The most notable feature is the response to frequent demand changes
Five, the application scenario:
      1. Heavy-weight results in a complex development process
      2. Job-oriented, task-oriented roles lead to poor process cohesion and difficult project schedule control
      3. The project cycle that results from the above 2 cases is too long
vi. principles of Scrum
      1. Organization of teams under target-driven, unified software delivery goals
      The 2.Scrum team's assessment plans are even designed, developed, tested
      3. Project Basic Development properties: Cycle + quality (if the number of bugs is B, the period is T, then reduce t*b as much as possible)
Keywords:
Sprint: One of several small iteration cycles in a project
Backlog: List of requirements sorted by business value (per user story)----PM (PO) is responsible for output
Sprint Backlog:sprint After a memory analysis, discussion, estimate of the BackLog
Issue: Issues
Remaining activities
Double Check: Cross-check whether the artifact is meeting the requirements (such as analyzing the document, core code, etc.)
Checklist: Lessons learned, checklists for follow-up projects (Scrum master,scrum Team)
Tech Show: Technical exchanges (must be short-time and high-frequency) (Scrum Team)
Goalkeeper: Create quiet conditions for the team and increase focus on the project. (Scrum Team)
Unit Testing: Test first guarantees code quality (Scrum Team)
Pair programming (PP): Improve design and code quality, staff experience sharing and enhanced collaboration (Scrum Team)
Task Solitaire: Increasing objectivity of task evaluation (Scrum Master,scrum Team

Agile Development (v)-Framework scrum content