scrum methodology: managing project efficiently and accurately

Scrum Methodology

Managing Projects Efficiently and Accurately

Introduction • What this is about:

−Antithesis of Waterfall: Agile−Specifically: Scrum

• Learning objectives:−To understand how to migrate to

Scrum

Agenda• Agile Methodology• Scrum Methodology• Migrating to Scrum• Simulation

THE CASE OF AGILE

FBI’s Sentinel• Purpose: To digitize case files.

− To rapidly compare cases and discover connections between them.

• Estimation: starts March 2006, completes December 2009, costs $451 million, includes 4 phases.

• Reality: reached August 2010, spent $405 million, employed 400 staff, delivered 2 of 4 phases, might require additional money and time to finish.

• Agile: started November 2010, completed November 2011, spent $30 million, employed 45 staff, delivered 4 of 4 phases.

FBI’s “Agile” Sentinel• Initiate “Scrum Studio”.• Development iteration: every 30 days.• Release iteration: every 3 months.

−Release type: field pilot.• National scale deployment finished by June,

2012.• Highlights:

−More than 90% cost saving.−More than 70% time saving.

Why Agile? Requirements...

• ... are not easy to define at the start.• ... are not easy to be completely

collected at the start.• ... are vulnerable to changes in:

−business processes,−regulations,−target users, etc.

AGILE METHODOLOGY

Individuals and interactions

Working software

Customer collaboration

Responding to change

Processes and tools

Comprehensive documentation

Contract negotiation

Following a plan

Agile ManifestoOVER

Agile Principles1. Our highest priority is to satisfy the customer through early and

continuous delivery of valuable software.2. Welcome changing requirements, even late in development. Agile

processes harness change for the customer's competitive advantage.3. Deliver working software frequently, from a couple of weeks to a

couple of months, with a preference to the shorter timescale.4. Business people and developers must work together daily throughout

the project.5. Build projects around motivated individuals. Give them the

environment and support they need, and trust them to get the job done.

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

Agile Principles (2)7. Working software is the primary measure of progress.8. Agile processes promote sustainable development. The

sponsors, developers, and users should be able to maintain a constant pace indefinitely.

9. Continuous attention to technical excellence and good design enhances agility.

10.Simplicity--the art of maximizing the amount of work not done--is essential.

11.The best architectures, requirements, and designs emerge from self-organizing teams.

12.At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

SCRUM METHODOLOGY

Roles• Product Owner• Scrum Master• Scrum Team

Ceremonies• Sprint Planning• Daily Scrum (Standup Meeting)• Sprint Demo• Sprint Retrospective

Process

Estimation• Estimate:

−User Story−Story Points−Velocity

• #NoEstimate

MIGRATING TO SCRUM

Total Implementation• Disseminate the implementation of Scrum.

−To every single person in the organization, especially the people involved in software development.

• Adopt Scrum as a whole.−Avoid partial adoption, i.e. cherry-picking.

• Put a time constraint.−It’s a project, not a process.

• Provide a project room.−To improve communication and collaboration.

Policy Adjustment• Adjust the Development Phase.

−Needs to be iterative and incremental.• Adjust the artifacts.

−URS, SRS, and SDD might need adjustments.

−Make it as simple as possible.• Make sure the adjustments run well.

−Assign separate technical writer to write URS, SRS, or even SDD.

SIMULATION

Let’s Play a Scrum Game• Decide on a “project”:

−Draw something!• Pick a role:

−Product Owner−Scrum Master−Scrum Team

• Begin!

END