Introduction to Project Management with Scrum

Scrum by coPROcess
 Scrum Coach & PMO
 coPROcess S.A.
 www.scrumcenter.lu
 http://managingagile.blogspot.com/
2

Introduce you to Scrum
Explain the basic principles
Introducing Scrum Training possibilities
Scrum by coPROcess 4

 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.
Scrum by coPROcess 10

 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.
12Scrum by coPROcess

 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.
 TheTeam has a time-box to reach
this goal: the Sprint
❶

 Each day, theTeam 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.
❷

 The Sprint ends with the Sprint
Review and the Retrospective.
 When the next Sprint starts, theTeam
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.
❸

Maximize
Value

Self ManagingTeams Traditional Organization
customer-driven management driven
multi-skilled workforce workforce of isolated specialists
few job descriptions Many Job Descriptions
Information widely shared Information limited
Few levels of management Many levels of Management
Whole-business focus Function/department focus
Shared goals Segregated goals
Seemingly chaotic Seemingly organized
Purpose achievement emphasis Problem-solving emphasis
High worker commitment High Management commitment
Continuous improvements Incremental improvements
Self-controlled Management-controlled
Values/principles based Policy/procedure based
Source: "Leading self-directed work teams" by Kimball Fisher

 Ensures
 Helps
 Coaches
 Protects
 Removes
 Responsible
 Work with

 Responsible
 Ensures
 Accepts
 Rejects
 Maintains
 Work with

Daily Meetings

 Moderator:
Product Owner
 Participators:
Team (active),
ScrumMaster
(passive)
 Duration: 8 Hours
for a 4 week
Sprint
 Moderator:
Product Owner
 Participators:
Team (active),
ScrumMaster
(passive)
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.

 Moderator:
Team
 Participators :
Team,
ScrumMaster,
Product Owner
 Duration: 2-4
Weeks
 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.

 Moderator: Team
 Participators :
Team (active),
ScrumMaster
(passive), Product
Owner (passive)
 Duration: 15 min
 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?

 Moderator: Product
Owner
 Participators: Team
(active),
ScrumMaster
(passive),
Management (active),
Customer (active),
Users (active)
 Duration: 4 Hours for
a 4 week Sprint.
 Moderator: Product
Owner
(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.

 Moderator:
ScrumMaster
(active),
ScrumMaster
(active), Product
Owner (active als
Scrum Team
Member)
for a 4 week Sprint.
 Moderator:
ScrumMaster
(active),
ScrumMaster
(active), Product
Owner (active als
Scrum Team
Member)
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

 The Product Backlog
answers following
questions:
What? When? For who?

For theFor the
TEAMTEAM 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

ForFor
SCRUMSCRUM 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

 Transparence
 Inspection
 Adaptation

Sprint
Release
Future
Releases
56

The Team
Developer
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 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/

 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.

That was my introduction
to Project Management
with Scrum

Thanks

pneis@coprocess.lu

Introduction to Project Management with Scrum

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Introduction to Project Management with Scrum (20)

More from Pierre E. NEIS (20)

Recently uploaded (20)

Introduction to Project Management with Scrum

Editor's Notes