As a PM, TA may be proficient in five major process groups and ten major managements, and can promote management projects, advance projects, and communicate needs in an orderly manner. However, in today's rapid development, if the TA doesn't know Scrum, it will be a little out. It is a pity that Xiaoman is the latter. In order not to be completely photographed to death on the beach, Xiaoman started to learn Dafa and spent a while to get the entry-level book "scrum and XP in the smoke of gunpowder-How do we implement scrum". This article mainly focuses on what Xiaoman has learned and thought in this book, mainly including some related concepts, technical skills and related experience.
-
Related concepts
(1) About Scrum; about sprint; about backlog;
Scrum is a framework for developing and maintaining complex products. It is an incremental and iterative development process. In this framework, the entire development process consists of several short iteration cycles. A short iteration cycle is called a Sprint. The recommended length of each Sprint is 2 to 4 weeks (Internet product development can use a 1-week Sprint). In Scrum, the product backlog is used to manage product requirements. The product backlog is a list of requirements sorted by business value, and the form of list items is usually a user story. The Scrum team always first develops requirements that are of higher value to customers. In the Sprint, the Scrum team selects the highest priority requirements from the product Backlog for development. The selected requirements are discussed, analyzed and estimated at the Sprint planning meeting to get the corresponding task list, which we call the Sprint backlog. At the end of each iteration, the Scrum team will deliver potentially deliverable product increments. Scrum originated in software development projects, but it is suitable for any complex or innovative projects. [1]
(2) What is XP? What is the relationship between Scrum and XP?
XP refers to Extreme Programming. Like scrum, it is also a practice of agile development process. There is very little mention of XP in this book. Readers who want to understand Extreme Programming can refer to [2]. As far as the current research is concerned, XP, as a kind of agile development practice, has died down in the scrum battle[3], and according to the author’s research on the recruitment responsibilities of many project managers, some of the responsibilities will have "capable of agile development "Experience" is similar to the word, some of which will directly refer to scrum, but "XP Extreme Programming" related content is rare.
2. Important elements of Scrum;
(1) Scrum team role arrangement
The product owner (Product Owner) is the only person responsible for managing the product to-do list. The primary goal is to clearly define the team's goals. In the current jargon, "product managers in agile state do the right thing."
The Scrum Master is a service leader in the team. The primary goal is to ensure that Scrum is understood and implemented. In the current jargon, "The project manager in an agile state is responsible for doing things right and making every story point in Scrum follow Execute in the right direction".
Development team, do not explain. In this book, the team size of 3~8 people is considered to be the most appropriate, and it should be adjusted according to the actual situation of different teams (technical level, running time, etc.) (In this book, consider incorporating test engineers into the development team).
(2) The three artifacts of Scrum
The Product Backlog is actually a list of product requirements. It is a sorted list that contains all the things required by the product. It is also the only source of changes in product requirements. The product owner is responsible for the content of the product to-do list. , Availability and priority.
The Sprint Backlog (SprintBacklog) is a set of product to-do list items selected for the current Sprint, plus a plan for delivering product increments and achieving Sprint goals, which is a collection of planning goals for the current sprint.
Product Increment (Increment), the increment is the sum of all product to-do list items completed in a Sprint, and the sum of the value of the increments generated by all previous Sprints.
(3) Scrum event
Sprint (Sprint itself is an event, including the following 4 events, the specific content can refer to the corresponding chapters in the book), a Sprint refers to a 1-week-4-week iteration, it is a time box. Once the length of the Sprint is determined, it remains unchanged. Sprint output is "completed", usable, and potentially releaseable product increments. Sprint has the same cycle throughout the development process.
-
Sprint Planning Meeting (Sprint Planning Meeting)
-
Daily Scrum Meeting (Daily Scrum Meeting)
-
Sprint Review Meeting (Sprint Review Meeting)
-
Sprint Retrospective Meeting
3. The framework of this book
4. Two feelings after reading the book
(1) The content is comprehensive, simple but not simple
Covers everything from basic definitions, daily operations, complex situations and precautions;
(2) Focus on actual combat and break away from dogmatism
There is no boring theory of long-form discussion, using actual sprint, actual sprintlog, actual Kanban, and actual operation to describe the practice of scrum. As a leader with multiple roles, the author also shows his management talent in the article. There are usually several solutions for reference.
5. Excerpts from this book
- In fact, Agile is not stated, it is done.
-
Add a story to the backlog, but they cannot say how important the story is. This is the exclusive right of the product owner. They also cannot add time estimates, which is the exclusive right of the development team.
-
We finally concluded our favorite length: three weeks. The sprint length of most teams is three weeks.
-
The product owner is a domain expert. He can guide the team's direction, but he shouldn't be involved in messy details.
I personally think that this book is a rare good book as a need to understand agile project management and implement agile management team. Follow WeChat and reply "scrum" to get the e-book.
reference---------------------------
[1]http://www.scrumcn.com/agile/scrum-knowledge-library/scrum.html
[2]https://baike.baidu.com/item/xp/776028
[3]https://www.zhihu.com/question/30547608