There are three phases in scrum the initial phase is

This preview shows page 32 - 38 out of 42 pages.

There are three phases in Scrum.The initial phase is an outline planning phase where youestablish the general objectives for the project and designthe software architecture.This is followed by a series of sprint cycles, where eachcycle develops an increment of the system.The project closure phase wraps up the project, completesrequired documentation such as system help frames anduser manuals and assesses the lessons learned from theproject.Chapter 3 Agile software development32
The Sprint cycleSprints are fixed length, normally 2–4weeks. They correspond to thedevelopment of a release of the systemin XP.The starting point for planning is theproduct backlog, which is the list of workto be done on the project.The selection phase involves all of theproject team who work with the customerto select the features and functionality tobe developed during the sprint.Chapter 3 Agile software development33
The Sprint cycleOnce these are agreed, the team organizethemselves to develop the software. Duringthis stage the team is isolated from thecustomer and the organization, with allcommunications channelled through the so-called ‘Scrum master’.The role of the Scrum master is to protect thedevelopment team from external distractions.At the end of the sprint, the work done isreviewed and presented to stakeholders. Thenext sprint cycle then begins.Chapter 3 Agile software development34
Teamwork in ScrumThe ‘Scrum master’ is a facilitator who arrangesdaily meetings, tracks the backlog of work to bedone, records decisions, measures progress againstthe backlog and communicates with customers andmanagement outside of the team.The whole team attends short daily meetingswhere all team members share information,describe their progress since the last meeting,problems that have arisen and what is planned forthe following day.This means that everyone on the team knows what isgoing on and, if problems arise, can re-plan short-termwork to cope with them.Chapter 3 Agile software development35
Scrum benefitsThe product is broken down into a set ofmanageable and understandable chunks.Unstable requirements do not hold up progress.The whole team have visibility of everything andconsequently team communication is improved.Customers see on-time delivery of incrementsand gain feedback on how the product works.Trust between customers and developers isestablished and a positive culture is created inwhich everyone expects the project to succeed.Chapter 3 Agile software development36
Scaling agile methodsAgile methods have proved to be successfulfor small and medium sized projects that canbe developed by a small co-located team.It is sometimes argued that the success ofthese methods comes because of improvedcommunications which is possible wheneveryone is working together.Scaling up agile methods involves changingthese to cope with larger, longer projectswhere there are multiple development teams,perhaps working in different locations.

Upload your study docs or become a

Course Hero member to access this document

Upload your study docs or become a

Course Hero member to access this document

End of preview. Want to read all 42 pages?

Upload your study docs or become a

Course Hero member to access this document

Term
Spring
Professor
Olsen

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture