Development Management checklists (15)-agile development framework scrum content

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future.

This article mainly aims to check your understanding and usage of scrum,
Through this article, you can check
1. Are the roles in your scrum project qualified,
2. Are there any issues with the meetings required by scrum and whether the meeting process is correct?
3. Is the project output correct.

I. Scrum functions: 
1. Product owner 
(1) define all product functions
(2) determine the product release content and date
(3) responsible for product Input and Output
(4) Prioritize the features to be developed based on market changes
(5) Reasonably adjust product functions and Iteration Sequence
(6) Identify or reject iteration delivery

2. Scrum master 
(1) direct management of projects
(2) lead the team to complete scrum practices and reflect its value
(3) eliminate the difficulties encountered by the Team
(4) ensure that the team is competent for its work and maintain efficient productivity
(5) the close cooperation of teams enables individual teams to have the ability to work in many aspects.
(6) Protecting the team from external influences without any reason

3. Team 
(1) 5-9 members in the classic team
(2) team members are all versatile:
(3) programmers, testers, user experience design, etc.
(4) All team members work full-time
(5) special functions (for example, database administrators)
(6) self-organizing and management by the Team
(7) Team relationship should be fixed in an iteration, and personal functions can be adjusted at the Beginning of the New iteration.

Ii. Scrum Process

(Click the following options to go to The Link)
1,Full MEETING
2,Evaluation Meeting
3,Sprint plan meeting 1
4,Sprint Planning Meeting 2
5,Scrum daily meeting
6,Sprint review meeting
7,Sprint review meeting

Iii. Scrum output:
1,Product backlog
2,Requirement
3,List of tasks to be completed in the project
4,Ideally, every task to be completed will produce value to customers and users.
5,The product owner will sort the priority of this list
6,Priority sorting before each iteration starts needs to be corrected again
7,Iterative backlog
8,Burnout Diagram

Product burning drawing example

4. ScrumFeatures
1. Simple Development Process
2. Products for iterative and incremental development and development systems with rapid demand changes
3. Control the process from conflicting interests and needs to chaos
4. Improve communication and optimize cooperation
5. detect obstacles in product development and production and remove them
6. Summary of the design process
7. maximize productivity
8. Each participant can be proud and proud to make the best possible contribution.

Different from traditional development models:
The most notable feature is: Response to frequent changes in demand
5. Applicable scenarios:
1. heavyweight leads to complicated development processes
2. Duties-oriented and task-oriented jobs lead to poor process connection and difficult project progress control
3. The project cycle in the above two cases is too long.

Vi. Scrum principles
1. Goal-driven, Unified Software Delivery goals: organize teams
2. The SCRUM team makes assessment plans, even design, development, and testing.
3. Basic Project Development attributes: Cycle + quality (if the number of bugs is B and the cycle is T, reduce T * B as much as possible)

Keywords:
Sprint: one of several small iteration cycles in the project
Backlog: list of requirements sorted by business value (each item is user story) ---- PM (PO) is responsible for output
Sprint backlog: the backlog obtained after the sprint analysis, discussion, and estimation
Issue: topic

Other activities
Double check: Cross-check whether project products meet requirements (such as analysis documents and core code)
Checklist: summarizes lessons learned and serves as a check item for subsequent projects (scrum master, scrum Team)
Tech show: Technical Communication (must be short-term and high-frequency) (scrum Team)
Goalkeeper: Creates quiet conditions for the team and increases the focus on the project. (scrum Team)
Unit Testing: tests give priority to code quality assurance (scrum Team)
Peer programming (PP): improves design and code quality, shares personnel experience and strengthens cooperation (scrum Team)
Task card: increases the objectivity of Task Evaluation (scrum master, scrum team

<Development Management checklists> by dylove98 @ Development Management checklists