Agile Method Scrum

1
Agile Method - Scrum

• Present by Gloria Law
• April 7, 2008

2
Agenda

• Introduction
• Waterfall Life Cycle
• Agile Method
• Scrum
• Sprints
• Potentially Shippable Product Increment
• Product Owner
• Product Backlog

• ScrumMaster
• Daily Scrum Meeting
• Scrum of Scrums
• Sprint Planning
• Release Planning
• Sprint Review
• Risk Management
• System Representation
• Advantage Disadvantage

3
Introduction

• Need software management methods to decrease the
  cost
• 28 completed on time and budget
• 23 failed
• 49 challenged
• 72 not meeting original goals

4
Waterfall Life Cycle
X

5
Agile Method

• Continuous attention to technical excellence and
  good design
• Self-organizing teams
• Customer satisfaction by rapid, continuous
  delivery of useful software
• Working software is the principal measure of
  progress
• Delivered frequently

6
Agile Method (cont)

• Late changes in requirements
• Close, daily cooperation between business people
  and developers
• Face-to-face conversation is the best form of
  communication
• Time is a fixed variable

7
Agile Manifesto

• We are uncovering better ways of developing
  software by doing it and helping others do it.
  Through this work we have come to value
• Individuals and interactions over processes and
  tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan
• That is, while there is value in the items on the
  right, we value the items on the left more.

8
Scrum

• Rugby
• Eight individual
• Move the ball down the field
• One Goal

9
Sprints

• Scrum project make progress in a series of
  Sprints
• Timeboxed Period (2 4 weeks)
• During Sprint, team does
• Analysis
• Design
• Code
• Test
• Product is potentially releasable after every
  Sprint

10
Potentially Shippable Product Increment

• At the end of each Sprint, the Team must produce
  a potentially shippable product increment (commit
  by the Team)
• High Quality
• Tested
• Complete
• Done

11
Product Owner

• Represents (or is) the user or customer for the
  project
• Knowing what to build and in what sequence
• Defines goals for overall project

12
Product Backlog

• The requirements
• A dynamic list of all desired work on the project
• Prioritized by the Product Owner
• Reprioritized at the start of each Sprint

13
ScrumMaster

• Responsible for enforcing the values and
  practices of the framework and the Team
• Remove impediments
• Educate outside groups about how the Teams is
  working
• Improve productivity in any way possible
• Facilitate Team meetings
• Servant Leader

14
Daily Scrum Meeting

• Tasks that is completed
• Obstacles to complete specific task
• Plan to accomplish between now and the next Scrum
  meeting

15
Scrum of Scrum

• Synchronize inter-team work
• Issue list is up-to-date
• Discuss impediments

16
Sprint Planning

• Happens on the 1st day of the Sprint
• Scrum Team takes the Sprint Goal and decides what
  Product Backlog are necessary
• Team self-organizes around how theyll meet the
  Sprint Goal
• Sprint Backlog is created

17
Release Planning

• Several Days before Sprint Planning
• What will be built
• Identify top level priorities
• Select more than what the Team can likely do in
  one Sprint

18
Sprint Review

• Updates to Product Owner
• Plans for next Sprint
• Change in Requirements
• Demonstration

19
Risk Management

• Risk is low
• Continue testing
• Problem is notified during Daily Scrum Meeting

20
System Representation
21
Advantage Disadvantage
22
Work Breakdown Schedule

• Requirement Analysis
• Proposal (February)
• Research
• Review Case Study (March)
• Paper Analysis (March-April)
• Writing the Paper
• Proof Read

23
Reference

• Pressman, Roger S. Software Engineering.
  Software Engineering Project Management. Pp.
  30-47. IEEE. 2000.
• Highsmith, Jim Cockburn, Alistair. Agile
  Software Development The Business of
  Innovation. IEEE Computer. September 2001.
• "Agile software development." Wikipedia, The Free
  Encyclopedia. 19 Apr 2007, 1026 UTC. Wikimedia
  Foundation, Inc. 19 Apr 2007 lthttp//en.wikipedia.
  org/w/index.php?titleAgile_software_developmento
  ldid124050398gt.
• Rising, Linda Janoff, Norman. The Scrum
  Software Development Process for Small Teams.
  IEEE Software. July/August 2000.
• Brooks, Frederick. The Mythical Man-Month Essays
  on Software Engineering. MA Addison-Wesley
  Professional 1975.
• Sutherland, Jeff. Agile Development Lessons
  Learned From the First Scrum. Cutter Agile
  Project Management Advisory Service. Executive
  Update, Vol. 5, No. 20. October 2004.
• Anderson, David. Agile Management for Software
  Engineering. New Jersey Prentice Hall, 2004.
• KarlstrÖm, Daniel Runeson, Per. Combining
  Agile Methods with Stage-Gate Project Managment.
  IEEE Software. May/June 2005.
• Agile Manifesto. 19 Apr 2007, 1026 UTC.
  lthttp//www.agilemanifesto.comgt