Introduction to Project Management with Scrum

1Scrum by coPROcess

Scrum by coPROcess

Scrum Coach & PMO coPROcess S.A. www.scrumcenter.lu http://managingagil

e.blogspot.com/

2

Scrum by coPROcess 3

Introduce you to Scrum

Explain the basic principles

Introducing Scrum Training possibilities

Scrum by coPROcess 4

6Scrum by coPROcess

7Scrum by coPROcess

1995

Scrum by coPROcess8

PO Training - Pierre NEIS

9

2001

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

11Scrum by coPROcess

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

Scrum by coPROcess 13

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

❶14Scrum by coPROcess

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.

❷15Scrum by coPROcess

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.

❸16Scrum by coPROcess

Maximize Value

17Scrum by coPROcess

18Scrum by coPROcess

19Scrum by coPROcess

20Scrum by coPROcess

21Scrum by coPROcess

22Scrum by coPROcess

Self ManagingTeamsTraditional

Organizationcustomer-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

23Scrum by coPROcess

Responsible

Ensures

Accepts

Rejects

Maintains

Work with

24Scrum by coPROcess

25Scrum by coPROcess

Daily Meetings

26Scrum by coPROcess

27Scrum by coPROcess

28Scrum by coPROcess

Moderator: Product Owner

Participators: Team (active), ScrumMaster (passive)

Duration: 8 Hours for a 4 week Sprint

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.

29Scrum by coPROcess

30Scrum by coPROcess

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.

31Scrum by coPROcess

32Scrum by coPROcess

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?

33Scrum by coPROcess

34Scrum by coPROcess

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

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.

35Scrum by coPROcess

36Scrum by coPROcess

Moderator: ScrumMaster

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

Duration: 3 Hours for a 4 week Sprint.

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

37Scrum by coPROcess

38Scrum by coPROcess

The Product Backlog answers following questions:

What? When? For who?

39Scrum by coPROcess

40Scrum by coPROcess

41Scrum by coPROcess

Scrum by coPROcess

42

43Scrum by coPROcess

For the For 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

44Scrum by coPROcess

ForForSCRUMSCRUM 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

45Scrum by coPROcess

46Scrum by coPROcess

Scrum by coPROcess 47

Transparence

Inspection

Adaptation

48Scrum by coPROcess

Scrum by coPROcess 49

Scrum by coPROcess 50

51Scrum by coPROcess

52Scrum by coPROcess

53Scrum by coPROcess

54Scrum by coPROcess

55Scrum by coPROcess

Scrum by coPROcess

Sprint

Release

Future Releases

56

Scrum by coPROcess

57

Scrum by coPROcess 58

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

59Scrum by coPROcess

60Scrum by coPROcess

Scrum by coPROcess 61

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/

62Scrum by coPROcess

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.

63Scrum by coPROcess

64Scrum by coPROcess

65Scrum by coPROcess

That was my introduction to Project Management with Scrum

66Scrum by coPROcess

Thanks

67Scrum by coPROcess

pneis@coprocess.lu

68Scrum by coPROcess