Scrum Team established
Team Name: 22#
Team goal: Do the task of each assignment and improve yourself
Team slogan: Do now, look to the future
Team member: Chen, Changyu, Chen Ze exhibition, Peng Yijian
Role Assignment
Product Owner (determines the value of development content and prioritization, maximizing product and development team work): Chen
Scrum Master (responsible for ensuring that the team follows the theory, practice, and rules of Scrum.) Scrum Master is a service leader in the team): Changyu
PM Project Manager (team leader, lead, balance, push, motivate, target, negotiate, equal work outside steward): Chen Ze Exhibition
Users (the user experience of developing software from the perspective of the end user, team work must respond and meet user needs): Peng Yijian
Sixth chapter
Scrum is a framework for developing and sustaining complex products and is an incremental, iterative development process. In this framework, the entire development process consists of a number of short iterations, a short iteration cycle called a sprint, and the recommended length for each sprint is 2-4 weeks in scrum, using the product backlog to manage the product's needs, A product backlog is a list of requirements sorted by business value, and the form of a list entry is usually a user story. The scrum team is always first to develop requirements that are of high value to the customer. In Sprint, the scrum team picks 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 a list of tasks that we call the sprint backlog. At the end of each iteration, the scrum team submits a potentially deliverable product increment. Scrum originates from software development projects, but it is suitable for any complex or innovative project.
Agile methods use time to manage, make up a few, and finally form a continuous version of the update. Break down the idea by a strict time-limited way.
Seventh Chapter
MSF does not have a manifesto like agile, but it has a framework of ideas-9 basic principles
(1) Promoting information sharing and communication (Foster Open Communications)
(2) Working for a common vision (work toward a shared vision)
(3) Full authorization and trust (Empower team members)
(4) Responsible for the project (establish clear accountability and shared responsibility)
(5) Value of delivery increment (deliver incremental value)
(6) Maintain agility, anticipation and adaptation (stay agile, expect and adapt change)
(7) Quality of investment (Invest in quality)
(8) Learn all the experience (learn from all experiences)
(9) Cooperation with customers (Partner with internal and external customers)
Scrum team, 6th to 7th chapter of the Law of construction