Scrum elements Reading Notes

I. Common Project development modes: Agile iteration and waterfall

 

1. agile Iteration

 

Sprint features: product and team members PK stories, stories are divided into tasks by team members, self-commitment, regular incremental continuous delivery of business value, early delivery, frequency delivery, a typical Iteration Method

 

2. waterfall Mode

 

Waterfall Model features: linear (non-linear people and Development), not embracing changes (sequential), planning and execution

Original blog address: http://blog.csdn.net/paulery2012/article/details/40581043 (reproduced please note)

 

Ii. About scrum

 

1. Three major meetings: Sprint Planning Meeting (2-4hour), scrum day meeting (5-10mins), sprint Review Meeting (1-2hour)

 

2. role:

 

A typical scrum team consists of 5-9 members, with the product owner, master, and team members.

 

Product owner: Write stories and accept tests, and define the story priority based on the business value.

 

MASTER: a constantly changing role, non-hierarchical. At the beginning, I acted as a coach to organize the team, act as an echo board, and finally promote the team to make decisions. Mainly focusing on the process and progress, is the bulldozer of scrum (obstacle cleaning machine ). (Coach-echo board-push self-management)

 

Team members: self-organized task estimation. The measurement unit can be time or task point. A user story needs to be delivered to complete a job rather than a personal job.

 

3. Period

 

Sprint Planning Meeting: Select deliverables (user stories) and split stories into tasks (more than half a day will be split)

 

Scrum day: Let's share what I did before the last day, what I will do before the next day, and finally let's talk about development barriers. (Todo, doing, done)

 

Story time: the sprint list trimming time (based on the visualization tool and the story that will verify the adjustment progress until the end of the sprint can be delivered smoothly)

 

Sprint Review: Ultra-high transparency, that is, results should be presented even if not completed

 

Review: discuss your experiences and make improvements in the next cycle (you can use the visualization tools: story cards, burned-out charts, etc.). Thanks to other team members for their help, continuous inspection and adaptation.

 

4. Tools

 

Sprint list: subdivided entries

 

Task Board: workload (continuous adjustment, to do, doing, done)

 

Burning diagram: the trajectory of remaining work changing over time (can be used to observe and test whether team members can deliver stories on time)

 

5. Exceptions

 

Consensus: the Basic Agreement between the management and the team is not changed during the sprint.

 

If the change is required due to external factors, the product manager can apply for termination of exceptions. Hold review and summary meetings for inspection and adaptation

 

Start the sprint of the next cycle.

 

Iii. Summary

 

Key words about iterative development: self-management, self-commitment and incremental development, burnout diagram and task version control delivery risks,

 

Requirements remain unchanged during the iteration cycle, review and review are continuously tested and adapted

Scrum elements Reading Notes