Scrum@accenture

Introduction to Project Management with Scrum

1Scrum@ Accenture Technology Solutions | PCS

Who am I?

Scrum@ Accenture Technology Solutions | PCS

PMO │ Scrum Coach @ coPROcess S.A. www.coprocess.lu http://managingagile.blogspot.com/ http://paper.li/elPedroMajor

2

http://www.scrumcenter.lu/

http://managingagile.blogspot.com/

http://managingagile.blogspot.com/

http://paper.li/elPedroMajor

About this Workshop

Scrum@ Accenture Technology Solutions | PCS 3

Objective

Introduce you to Scrum

Explain the basic principles

Introducing Scrum Training possibilities


The Process !!!

• Stand-up meeting

Inspect & Adapt

• Basics• Principles• Roles• Mission

Introduction to Scrum • Interacting

session• Case study• Testing Scrum

Planning Game

• Build a Q/A Backlog

• Estimate• Prioritize• Deliver

Q/A


Inspect & Adapt

3 questions:

1. Who am I?2. What’s my job?3. What aims today?


Introduction to Scrum



Why “Scrum” ?

We’re losing the relay race

“The… ‘relay race’ approach to product development…may conflict with the goals of maximum speed and flexibility. Instead a holistic or ‘rugby’ approach—where a team tries to go the distance as a unit, passing the ball back and forth—may better serve today’s competitive requirements.”

Hirotaka Takeuchi and Ikujiro Nonaka, “The New New Product Development Game”,

Harvard Business Review, January 1986 9Scrum@ Accenture Technology Solutions | PCS

Origins

1984•Managing the New Product Development Process

1986•article by about a new holistic approach

•Moving the Scrum Downfield„

1990•Scrum Downfield "Wicked Problems, Righteous Solutions

1995•SCRUM

1999•A Pattern Language for Hyper productive Software Development“


The Manifesto for Agile Software Development


Individuals & Interactions• Working Software• Customer

Collaboration• Responding to

ChangeProcesses & Tools• Comprehensive

Documentation• Contract

Negotiation• Following a Plan

11

2001

Introduction by Ken Schwaber Scrum is not a methodology. Scrum

does not provide the answers to how to build quality software faster.

Scrum is a framework within which the game of product development is played.

Your team plays and how good or not-good it is becomes highly visible.

Your team gets to continuously improves itself.



How?

Scrum is an innovative approach to complete your work

Scrum is a flexible framework for complex projects.

Originally Scrum has been formalized for software development. But it also works well for complex and innovative projects.

The Scrum framework is deceptively simple.14Scrum@ Accenture Technology Solutions | PCS

The Theory


Scrum Framework

The Product Owner sets a List of Features called Product Backlog

During the Sprint Planning, the Team “pulls” a piece of the top of that list: the Sprint Backlog; and decide how to implement it.

The Team has a time-box to reach this goal: the Sprint

❶16Scrum@ Accenture Technology Solutions | PCS

Scrum Framework

Each day, the Team measures its progress during a 15’ meeting: the Daily Scrum

During the whole project, the ScrumMaster ensures that the Team is still focused on its objective.

At the end of the Sprint, the work has to be potentialy shipable. This work is considered as done.

❷17Scrum@ Accenture Technology Solutions | PCS

Scrum Framework

The Sprint ends with the Sprint Review and the Retrospective.

When the next Sprint starts, the Team selects a new piece of the Product Backlog and restarts the process.

The process is done when all Features are implemented, or the budget is consummed, or when the time is over.

❸18Scrum@ Accenture Technology Solutions | PCS

Objective

Maximize

Value 19Scrum@ Accenture Technology Solutions | PCS

Scrum Roles


Pigs & ChickenPig

s: the Scrum Tea

m• Team

• ScrumMaster

• Product Owner Chic

ken: the

stakeholders

• Management

• Customer

• Users


❶ The Scrum Team


5 to 7 People

Constituted by

generalists/speciali

sts

Self-Managed-Team


❷ The Team

Self-Managed-Team vs. Traditional

Organisation


Self ManagingTeams Traditional Organizationcustomer-driven management drivenmulti-skilled workforce workforce of isolated specialistsfew job descriptions Many Job DescriptionsInformation widely shared Information limitedFew levels of management Many levels of ManagementWhole-business focus Function/department focusShared goals Segregated goalsSeemingly chaotic Seemingly organizedPurpose achievement emphasis Problem-solving emphasisHigh worker commitment High Management commitmentContinuous improvements Incremental improvementsSelf-controlled Management-controlledValues/principles based Policy/procedure based

Source: "Leading self-directed work teams" by Kimball Fisher

❸ ScrumMaster

Ensures

Helps

Coaches

Protects

Removes

Responsible

Work with


❹ Product Owner

Responsible

Ensures

Accepts

Rejects

Maintains

Work with


Cycle of Ceremonies


Ceremonies are time-boxed.

Spri

nt P

lann

ing

Spri

nt R

evie

w

Retr

ospe

ctiv

eSp

rint

Pla

nnin

g

SPRINT

Daily Meetings


❶ Sprint Planning Meeting



The “Pull” Principle

❶ Sprint Planning Meeting

Moderator: Product Owner

Participators: Team (active), ScrumMaster (passive)

Duration: 8 Hours for a 4 week Sprint

2 PARTS: Sprint Planning 1: the WHAT? Sprint Planning 2: the HOW?

PRODUCT OWNER: Provides the customer ‘s/

user’s prioritized product backlog

Presents the Release Plan. Explain theVision

TEAM: Estimates the Product Backlog

in terms of feasibility (functional estimation)

Slice the Product Backlog to Sprint Backlogs with Product Owner

Slice Sprint Backlog in Tasks

TEAM AND PRODUCT OWNER:

Define the Sprint objective

Establish “Definition of Done” for the Sprint.


❷Sprint


❷Sprint

Moderator: Team

Participators : Team, ScrumMaster, Product Owner

Duration: 2-4 Weeks

Development of the applications from the Sprint Backlog in which the team is involved.

Maintenance of the Level of Done:

Developement Unit test Acceptance Integrations test System tests Performance

Co-management of impediments with the ScrumMaster.

Co-maintenance of the Sprint Backlog with Product Owner.


❸ Daily Scrum


❸ Daily Scrum

Moderator: Team

Participators : Team (active), ScrumMaster (passive), Product Owner (passive)

Duration: 15 min

It is the Inspect-and-Adapt fromTeam: Synchronization and Commitment.

The 3 Questions:1. What did you do

yesterday?2. Which

impediments?3. ¨What do you plan

for today?


❹Sprint Review


❹Sprint Review

Moderator: Product Owner

Participators: Team (active), ScrumMaster (passive), Management (active), Customer (active), Users (active)

Duration: 4 Hours for a 4 week Sprint.

It is the Inspect-und-Adapt from Customer, Users and Management.

The team presents the results of the Sprint.

Users/Customer/ Management express their comments and find a compromise with the team.

The Product Owner accepts or rejects Sprint Backlog Items according to Definition of Done.

The Product Owner has the last word here.


❺Retrospective


❺Retrospective

Moderator: ScrumMaster

Participators: Team (active), ScrumMaster (active), Product Owner (active als Scrum Team Member)

Duration: 3 Hours for a 4 week Sprint.

Scrum Process Analysis: How How can we improve

ourselves?

Inspection priorities : Team communication Relationship between

team members Processes and Tools Training issues etc


Artifacts

Product Backlog

Release Burndow

n

Sprint Burndow

n

Sprint Backlog


Product Backlog

The Product Backlog answers following questions:

What? When? For who?


Release Burndown


Sprint Backlog


Sprint Burndown


44

Definition of Done


Level of DoneFor the TEAM Code corresponds to the standard

Code is proper Re-factored Unit tested checked in built Has a number of applied unit tests.

To achieve this, the development environment is constituted by :

A Source-Code Library Codes Standards Automatic Build A Unit-tests Environment


Definition of DoneFor

SCRUM A Story/Item is “done” when

theTeam has reached its Level-of-Done.

Sprint/Iteration is “done” when All items are “done” When the Sprint reaches its goal. And when Acceptance criteria are met.

Release is “done”“done” for Integration“done” for Production


Done?

Half done is not done


Scrum Values


Tranparence

Transparence

Inspection

Adaptation



Inspection

51


Adaptation

52

In fact, how does it work?


First an idea


Then a Vision


The Vision


Then a Product Backlog


Product Backlog


Sprint

Release

Future Releases

Med

ium

Pr

iorit

yHi

gh

prio

rity

58

Product Backlog - Examples


59

Then build the Team


Team Building

The TeamDeveloper

Analyst

Architect

Tester

DBA

Scrum Master

Anyone(not an authority role)Not necessarily a developer.

Product Owner

Product Manager

Business Analyst

Functional Project Manager

Business


Scrum Cycle


Scrum Principles Summary

Ask the

Team

Inspect &

Adapt

Deliver

every 30

days

Treat people

as adults


Planning Game


45’ immersion in Scrum

Exercise: Deliver a brochure for the Earth Tourist Board located on Mars

Create cover art, brand, and/or logo Define major topics for Martian Tourism Describe an “Art Interests in Europe” tour Describe a tour based on Photosynthesis Outline a “7 wonders of the world” Expedition Set prices for the tours Outline warning messages (gravity, oxygen, fungi, etc.) Suggest clothing options Explain travel options to/from Mars Describe a “Human Sports” tour Outline refund policy Suggest related services Define advertisers Define a 12-month campaign Set-up how to get more information


You have

45’

Setting up a Q/A


• 15’ build a Q/A Backlog

•15’ estimate & prioritize

•30’ deliver

Scrum Trainings Scrum Alliance

Certified ScrumMaster Certified Product Owner Certified Scrum Developer Certified Scrum Professional Certified Scrum Trainer Certified Scrum Coach

Scrum.org http://www.scrum.org/ Professional Scrum Master

▪ Professional Scrum Master 1▪ Professional Scrum Master 2

Professional Scrum Developer▪ PSD .Net▪ PSD Java

http://www.scrumalliance.org/


http://www.scrum.org/

http://www.scrumalliance.org/

My Trainings Basics :

Introduction to Scrum ScrumMaster in depth Training Product Owner in depth Training Coaching Scrum Teams Hyper Productivity & Rapid Scrum ScrumBan Scrum Certification on-demand

“Short Tracks”:▪ Format: 4 Hours, 4 Trainees, 1 Problem, 1 Solution, 1 Example, 1

Counterexample, 1 Tool, 1 Template▪ Themes: PID, ROI, Scaling Teams, Visual Management, Visioning,

Scrum Tools, Magic Estimation.


Scrum Resources


Companies using SCRUM


That was my introduction to Project Management with Scrum


Thanks72Scrum@ Accenture Technology Solutions | PCS

[email protected]


Documents

Scrum@accenture