Introduction to Scrum stand-up meetings

Scrum is an iterative incremental software development process, often used for agile software development. Scrum includes a series of procedural skeletons that practice and pre-define roles. The main roles in scrum include the role of the scrum leader, similar to the project manager, responsible for maintaining processes and tasks, the product owner representing the benefit owner, and the development team including all developers. Although scrum is developed for managing software development projects, it can also be used to run a software maintenance team, or as a plan management approach: Scrum of Scrums.

Scrum is a process skeleton that includes a series of practices and pre-defined roles (a process, plan, pattern for efficient software development). The main roles in scrum include the role of the scrum leader , similar to the project manager, responsible for maintaining processes and tasks, the product owner representing the benefit owner, and the development team including all developers.

In each sprint (a 15-30-day cycle, length is determined by the development team), the development team creates an increment of available (ready-to-roll) software. The characteristics of each sprint are derived from the product order (the product backlog, which I think translates into "product goals" more appropriately), and the product order (goal) refers to the need for a summary of the work to be done in order of priority (target). Which order items (target items) are added to a sprint are determined by the sprint planning meeting. During the meeting, the product owner tells the development team what order items he needs to complete in the product order. The development team decides how many order items they can commit to complete in the next sprint. During the sprint, no one can change the sprint order, which means that demand is frozen in a sprint.

    Daily stand-up meetings is a key practice in the scrum approach, a seemingly simple activity that is rich in content and is not easy to become if it becomes a habit. Its features for:   1  stand-up meeting through daily face-to-day communication, you can:      (1) To quickly synchronize progress, so that the team's internal staff understand each other's progress, so as to understand the overall progress of the project.       (2) give everyone a mental pressure to keep their promises. This is a face-to-head mental stress that confronts the progress of the project.      (3) Culture of the team, let everyone realize: I am not alone in the fight, we are a team.       so standing meetings can not be replaced by mail, not at the computer, you must look at other members of the eye, not the computer.   2  every day in a fixed time, fixed place, usually every morning to work, so do not have to notice each meeting. The extension of the    3  project is postponed daily, so keep track of progress every day, and stand-up meetings must be open every day.    4  Each meeting for no more than 15 minutes; If technical issues are to be discussed, meetings will be held separately and a small number of participants can participate in the discussion. Note that standing meetings must not be a long meeting. Why stand, is to short!    5  Standing meeting usually have a whiteboard, pasted on the whiteboard is the task status of this project group: Not started tasks, ongoing tasks, interrupted tasks, completed tasks. In fact, there are some agile tools, can be electronic sprint backlog, but still less than the physical whiteboard more visual impact.   6  The progress status of each task should be updated to move the task sticker directly on the whiteboard. Intuitive Kanban for working status is also an effective means of understanding progress and defining goals, and you can always remind team members where we are. How far are we from the target?    7  in the event of a standing meeting, not every member reports to the project manager, but everyone is equal, and is in sync with everyone in the project team. This is also a culture of cultivation.    8  Project team outside the management staff can attend, especially the competent leadership, but can not speak, can not under the instruction, can only audit. In scrum, team self-management is advocated.    9  If someone is always late for a meeting, there is a need for punitive measures to develop a culture of punctuality, a culture of the team。 Note:    To avoid opening a long meeting, each member must answer only 3 questions:      What did you accomplish yesterday,      what to do today,       is there anything else I can help you with?       Other issues are not discussed at this meeting, but will be discussed later.  

Reviews: I think the standing meeting is very good.

Introduction to Scrum stand-up meetings