Introduction to Project Management with Scrum

  • View
    8.018

  • Download
    2

Embed Size (px)

DESCRIPTION

It's a small presentation to give the basic principles of scrum.The presentation mode is made interactively with the audience.The progression of the slides are scaled on progessive learning and fixing process: starting from theory to practice.It's not enough to start a Scrum Project and do not replace a mature scrum training delivered by a senior Scrum Trainer.

Text of Introduction to Project Management with Scrum

Scrum?

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcessScrum Coach & PMOcoPROcess S.A.www.scrumcenter.luhttp://managingagile.blogspot.com/*

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

Introduce you to Scrum

Explain the basic principles

Introducing Scrum Training possibilities

Scrum by coPROcess*

Scrum by coPROcess

The relay race approach to product developmentmay conflict with the goals of maximum speed and flexibility. Instead a holistic or rugby approachwhere a team tries to go the distance as a unit, passing the ball back and forthmay better serve todays competitive requirements.Hirotaka Takeuchi and Ikujiro Nonaka, The New New Product Development Game,Harvard Business Review, January 1986*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

PO Training - Pierre NEIS

*

PO Training - Pierre NEIS

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*

Scrum by coPROcess

*Scrum by coPROcess

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

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcess*

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

The Team has a time-box to reach this goal: the Sprint*Scrum by coPROcess

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

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

Scrum by coPROcess

Maximize Value*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Self ManagingTeamsTraditional Organizationcustomer-drivenmanagement drivenmulti-skilled workforceworkforce of isolated specialistsfew job descriptionsMany Job DescriptionsInformation widely sharedInformation limitedFew levels of managementMany levels of ManagementWhole-business focusFunction/department focusShared goalsSegregated goalsSeemingly chaoticSeemingly organizedPurpose achievement emphasisProblem-solving emphasisHigh worker commitmentHigh Management commitmentContinuous improvementsIncremental improvementsSelf-controlledManagement-controlledValues/principles basedPolicy/procedure based

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

Scrum by coPROcess

Ensures

Helps

Coaches

Protects

Removes

Responsible

Work with

*Scrum by coPROcess

Scrum by coPROcess

Responsible

Ensures

Accepts

Rejects

Maintains

Work with*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Daily Meetings*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

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/ users prioritized product backlogPresents 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.

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

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:DevelopementUnit testAcceptanceIntegrations testSystem testsPerformance

Co-management of impediments with the ScrumMaster.

Co-maintenance of the Sprint Backlog with Product Owner.

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

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:What did you do yesterday?Which impediments?What do you plan for today?

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

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

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

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 communicationRelationship between team membersProcesses and ToolsTraining issuesetc*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

The Product Backlog answers following questions:What? When? For who?*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Code corresponds to the standard

Code isproperRe-factoredUnit testedchecked inbuiltHas a number of applied unit tests.

To achieve this, the development environment is constituted by :A Source-Code LibraryCodes Standards Automatic Build A Unit-tests Environment*Scrum by coPROcess

Scrum by coPROcess

A Story/Item is done when theTeam has reached its Level-of-Done.

Sprint/Iteration is done whenAll items are doneWhen the Sprint reaches its goal.And when Acceptance criteria are met.

Release is donedone for Integrationdone for Production*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

Transparence

Inspection

Adaptation*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcessSprintReleaseFuture Releases*

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

DeveloperAnalystArchitectTesterDBAAnyone(not an authority role)Not necessarily a developer.Product ManagerBusiness AnalystFunctional Project ManagerBusiness*Scrum by coPROcess

Scrum by coPROcess

*Scrum by coPROcess

Scrum by coPROcess

Scrum by coPROcess*

Scrum by coPROcess

Scrum AllianceCertified ScrumMasterCertified Product OwnerCertified Scrum DeveloperCertified Scrum ProfessionalCertified Scrum TrainerCertified Scrum Coach

Scrum.org http://www.scrum.org/Professional Scrum MasterProfessional Scrum Master 1Professional Scrum Master 2Professional Scrum DeveloperPSD .NetPSD Java

http://www.scrumalliance.org/*Scrum by coPROcess

Scrum by coPROcess

Basics :Introduction to ScrumScrumMaster in depth TrainingProduct Owner in depth TrainingCoaching Scrum TeamsHyper Productivity &amp