A sprint.docx

download A sprint.docx

of 3

Transcript of A sprint.docx

  • 7/28/2019 A sprint.docx

    1/3

    A sprint is a get-together of people involved in a project to give a focused development on the

    project. Sprints are typically two to seven days long. Sprints have become popular events among

    someOpen Sourceprojects. For example, thePyPyproject is mostly developed during regularlyheld sprints where most of the international developer team gathers.

    The sprints are often held near conferences which most of the project team attend, but they canalso be hosted by some involved party at their premises or some interesting location.

    Sprints are organized around the ideas of theExtreme Programmingdiscipline of softwaredevelopment. The sprint is directed by the coach, who suggests tasks, tracks their progress and

    makes sure that no one is stuck. Most of the development happensin pairs. A large open space is

    often chosen as a venue for efficient communication.

    Sprints can vary in focus. During some sprints people new to the project are welcomed and get

    an intensive hands-on introduction pairing with an experienced project member. The first part ofsuch sprints is usually spent getting ready, presenting the tutorials, getting the network setup and

    ensuring that configuration/source control software and processes are installed and followed.

    Sprint

    The Scrum process

    A sprint is the basic unit of development in Scrum. The sprint is a "timeboxed" effort, i.e. it is

    restricted to a specific duration.[9]

    The duration is fixed in advance for each sprint and is

    normally between one week and one month.[7]

    Each sprint is preceded by a planning meeting, where the tasks for the sprint are identified and anestimated commitment for the sprint goal is made, and followed by a review or retrospectivemeeting,

    [4]where the progress is reviewed and lessons for the next sprint are identified.

    During each sprint, the team creates finished portions of a product. The set of features that gointo a sprint come from the product backlog, which is an ordered list ofrequirements. Which

    backlog items go into the sprint (the sprint goals) is determined during the sprint planning

    meeting. During this meeting, the Product Owner informs the team of the items in the product

    http://en.wikipedia.org/wiki/Open_Sourcehttp://en.wikipedia.org/wiki/Open_Sourcehttp://en.wikipedia.org/wiki/Open_Sourcehttp://en.wikipedia.org/wiki/PyPyhttp://en.wikipedia.org/wiki/PyPyhttp://en.wikipedia.org/wiki/PyPyhttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Scrum_(development)#cite_note-Sprint_2009-9http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-Sprint_2009-9http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-Sprint_2009-9http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-autogenerated1-4http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-autogenerated1-4http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-autogenerated1-4http://en.wikipedia.org/wiki/Requirementhttp://en.wikipedia.org/wiki/Requirementhttp://en.wikipedia.org/wiki/Requirementhttp://en.wikipedia.org/wiki/File:Scrum_process.svghttp://en.wikipedia.org/wiki/File:Scrum_process.svghttp://en.wikipedia.org/wiki/File:Scrum_process.svghttp://en.wikipedia.org/wiki/File:Scrum_process.svghttp://en.wikipedia.org/wiki/Requirementhttp://en.wikipedia.org/wiki/Scrum_(development)#cite_note-autogenerated1-4http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-Sprint_2009-9http://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Pair_programminghttp://en.wikipedia.org/wiki/Extreme_Programminghttp://en.wikipedia.org/wiki/PyPyhttp://en.wikipedia.org/wiki/Open_Source
  • 7/28/2019 A sprint.docx

    2/3

    backlog that he or she wants completed (the ones with the highest priority). The team then

    determines how much of this they can commit to complete during the next sprint, and records

    this in the sprint backlog.[7]

    The sprint backlog is property of the development team, i.e. during asprint, no one is allowed to edit the sprint backlog except for the development team. The sprint

    goals should not be changed during the sprint. Development istimeboxedsuch that the sprint

    must end on time; if requirements are not completed for any reason they are left out and returnedto the product backlog. After a sprint is completed, the team demonstrates how to use thesoftware.

    Scrum enables the creation of self-organizing teams by encouraging co-location of all team

    members, and verbal communication between all team members and disciplines in the project.

    A key principle of Scrum is its during a recognition that project the customers can change their

    minds about what they want and need (often called requirements churn), and that unpredicted

    challenges cannot be easily addressed in a traditional predictive or planned manner. As such,

    Scrum adopts anempiricalapproachaccepting that the problem cannot be fully understood or

    defined, focusing instead on maximizing the team's ability to deliver quickly and respond toemerging requirements.

    Like otheragile development methodologies, Scrum can be implemented through a wide range

    of tools. Many companies use universal tools, such as spreadsheets to build and maintain

    artifacts such as the sprint backlog. There are also open-source and proprietary packagesdedicated to management of products under the Scrum process. Other organizations implement

    Scrum without the use of any tools, and maintain their artifacts in hard-copy forms such as paper,

    whiteboards, and sticky notes.[10]

    Meetings

    [edit] Daily Scrum

    A daily scrum meeting in the computing room. This choice of location lets the team start on time

    Each day during the sprint, a project team communication meeting occurs. This is called a dailyscrum, orthe daily standup. This meeting has specific guidelines:

    http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7http://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Empiricalhttp://en.wikipedia.org/wiki/Empiricalhttp://en.wikipedia.org/wiki/Empiricalhttp://en.wikipedia.org/wiki/Agile_software_developmenthttp://en.wikipedia.org/wiki/Agile_software_developmenthttp://en.wikipedia.org/wiki/Agile_software_developmenthttp://en.wikipedia.org/wiki/Scrum_(development)#cite_note-10http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-10http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-10http://en.wikipedia.org/w/index.php?title=Scrum_(development)&action=edit&section=5http://en.wikipedia.org/w/index.php?title=Scrum_(development)&action=edit&section=5http://en.wikipedia.org/w/index.php?title=Scrum_(development)&action=edit&section=5http://en.wikipedia.org/wiki/File:Daily_sprint_meeting.jpghttp://en.wikipedia.org/wiki/File:Daily_sprint_meeting.jpghttp://en.wikipedia.org/wiki/File:Daily_sprint_meeting.jpghttp://en.wikipedia.org/wiki/File:Daily_sprint_meeting.jpghttp://en.wikipedia.org/w/index.php?title=Scrum_(development)&action=edit&section=5http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-10http://en.wikipedia.org/wiki/Agile_software_developmenthttp://en.wikipedia.org/wiki/Empiricalhttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaber-7
  • 7/28/2019 A sprint.docx

    3/3

    All members of the development Team come prepared with the updates for the meeting The meeting starts precisely on time even if some development team members are missing The meeting should happen at the same location and same time every day The meeting length is set (timeboxed) to 15 minutes All are welcome, but normally only the core roles speak

    During the meeting, each team member answers three questions:[11]

    What have you done since yesterday? What are you planning to do today? Any impediments/stumbling blocks? Any impediment/stumbling block identified in this meeting

    is documented by the ScrumMaster and worked towards resolution outside of this meeting. No

    detailed discussions shall happen in this meeting.

    http://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Timeboxinghttp://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaberp135-11http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaberp135-11http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaberp135-11http://en.wikipedia.org/wiki/Scrum_(development)#cite_note-schwaberp135-11http://en.wikipedia.org/wiki/Timeboxing