Search results
Results From The WOW.Com Content Network
The meetings are usually timeboxed to between 5 and 15 minutes, and take place with participants standing up to remind people to keep the meeting short and to-the-point. [6] The stand-up meeting is sometimes also referred to as the "stand-up" when doing extreme programming, "morning rollcall" or "daily scrum" when following the scrum framework.
A daily scrum in the computing room. Each day during a sprint, the developers hold a daily scrum (often conducted standing up) with specific guidelines, and which may be facilitated by a scrum master. [3] [26] Daily scrum meetings are intended to be less than 15 minutes in length, taking place at the same time and location daily. The purpose of ...
Cohn is a proponent of stand-up meeting, particularly emphasizing actual standing during them. [10] Teams are encouraged to come up with their own rules for improving these meetings, for example fining people who are late to them. A 2011 survey of tech employees from around the world found that 78% held daily stand-up-meetings. [11]
A common characteristic in agile software development is the daily stand-up (known as daily scrum in the Scrum framework). In a brief session (e.g., 15 minutes), team members review collectively how they are progressing toward their goal and agree whether they need to adapt their approach.
Scrum involves a cross-functional team creating a list to work on. [11] The team consists of three specific roles, the Product Owner, the Developers and the Scrum Master. [12] The team then works through three phases: a pre-sprint planning, the sprint and then a post-sprint meeting. [14] The group has daily meetings and keeps a Product Backlog ...
Scrum was influenced by ideas of timeboxing and iterative development. [16] Regular timeboxed units known as sprints form the basic unit of development. [17] A typical length for a sprint is less than 30 days. [18] [19] Sprint planning, sprint retrospective and sprint review meetings are timeboxed. [18]
Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating, mostly used for timeboxing in Agile principles. In planning poker, members of the group make estimates by playing numbered cards face-down to the table, instead of speaking them aloud. The cards are revealed, and the estimates are then discussed.
The main planning process within extreme programming is called the Planning Game. The game is a meeting that occurs once per iteration, typically once a week. The planning process is divided into two parts: Release Planning: This is focused on determining what requirements are included in which near-term releases, and when they should be ...