Agile development process [Scrum]

Agile is a methodology in project management. It is suitable for projects with " unclear scope and requirements ". It adopts a small-step approach, completes an iteration every 1-4 weeks, puts it into use, collects feedback, and then iterates again , so as to continuously approach the real demand of a methodology!

Scrum is the most representative methodology in agile! The methodology consists of three roles and four meetings :
insert image description here

three roles

  1. Product Owner: The person in charge of the product ; mainly responsible for determining the function of the product and meeting the required standards, specifying the release date and delivery content of the software, and having the power to accept or reject the work results of the development team.
  2. Scrum Master: Similar to the project leader ; protect the team, take into account the needs of the product manager, and ensure the on-time delivery of the project.
  3. The Team: Development and testing team .

The total number of agile teams should be controlled between 7-11 people, not too many.

four conferences

  1. Sprint Planning Meeting: Sprint planning meeting ; the entire team moves user stories from the Product Backlog to the Sprint Backlog according to priority, indicating that the entire team is committed to the tasks to be completed in this iteration. The criterion of done is that the test passes, unless the task is not testable.
  2. Daily Scrum Meeting: Daily stand-up meeting; during the sprint phase, team members will talk about what they did yesterday, what they plan to do today, when they will be completed, and what problems they encountered.
  3. Sprint Review Meeting: Sprint review meeting ; after a sprint is completed, the team needs to demonstrate the phased results and review whether the results pass or fail.
  4. Sprint Retrospective Meeting: Sprint review meeting ; team members take turns to speak, review problems encountered, cost deviations, collaboration process, refine well done and areas that need improvement, and formulate improvement plans; at this time, PO will also collect based on Based on user feedback and online data, we will discuss the optimization plan together, and roughly plan the next Sprint, so that members can prepare in advance.

Guess you like

Origin blog.csdn.net/weixin_45658354/article/details/127714788