agile mëtteg series session 8

45
Agile Mëtteg – 14 October 2010 The Customer role in agile projects

Upload: agile-partner-sa

Post on 20-Aug-2015

4.317 views

Category:

Business


1 download

TRANSCRIPT

Agile Mëtteg – 14 October 2010The Customer role in agile projects

Agile Mëtteg - The Customer role in agile

2

OBJECTIVES & AGENDA

ObjectivesGet a short introduction to agile and the implications and benefits of an agile transition from the customer point of view.

AgendaIntroductionMain issuesAgile Project management overviewAgile management of requirementsGuidelines for successThe Product Owner roleTo conclude

14 October 2010

Agile Mëtteg - The Customer role in agile

3

LET’S GET TO KNOW EACH OTHER

14 October 2010

Agile Mëtteg - The Customer role in agile

AGILE PARTNER SERVICES

Custom Software Development & Maintenance

Our core business to answer customer needs

IS servicesThanks to our expertise we can support IT team to reach their productivity & quality objectives (Assessment, Coaching, Support, Training, Resource delegation…)

IS SolutionsTake benefit from commercial or Open Source platform to answer as quick as possible to specific needs

IS users servicesWe can support Product & Services owners to work closely with the IT team (Assessment, Coaching, Support, Training, Resource delegation…)

14 October 2010 4

IS users

Services

Software

Development

& Softwa

reMaintenance

ISSolutions

IS Services

1 23

4

1

3

2

4

5

SPEAKERS

14 October 2010 Agile Mëtteg - The Customer role in agile

Guy FABIEN Sylvain CHERY

Senior Consultant DirectorCSM CSM - CSP

Agile Evangelists

6

PARTICIPANTS

Who are you?What is your role?What do you know about agility?What are your expectations?

14 October 2010 Agile Mëtteg - The Customer role in agile

7

MAIN ISSUES

14 October 2010 Agile Mëtteg - The Customer role in agile

Agile Mëtteg - The Customer role in agile

8

COMPLETE UPFRONT SPECIFICATIONS

14 October 2010

Sources : J.Johnson, Keynote speech, XP 2002 Italie

Agile Mëtteg - The Customer role in agile

10

AGILE PROJECT MANAGEMENTTHE PRINCIPLES

14 October 2010

Agile Mëtteg - The Customer role in agile

11

ADAPTATION vs. ANTICIPATION

Source: Succeeding with Agile: Software Development using Scrum, Mike Cohn , Addison-Wesley, 2009

14 October 2010

Agile Mëtteg - The Customer role in agile

12

THE 4 VALUES

Extract from Manifesto for Agile Software Development:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

14 October 2010

Source: http://www.agilemanifesto.org/

Agile Mëtteg - The Customer role in agile

13

EXTRACT FROM THE 12 PRINCIPLES

Satisfy the customer through early and continuous delivery of valuable software.

Deliver working software frequently with a preference to the shorter timescale.

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

Business people and developers must work together daily throughout the project.

Face-to-face conversation for conveying information to and within a development team.

14 October 2010

AGILE PROCESS

14 October 2010 Agile Mëtteg - The Customer role in agile

14

Pri

ori

ty

Needs

Iterations System in progress

Iterative and incremental process Adaptive planningIterations time-boxed

15

AGILE MANAGEMENT OF THE REQUIREMENTS

14 October 2010 Agile Mëtteg - The Customer role in agile

16

PRINCIPLE

Just-In-Time,

Just-enough

Requirements

14 October 2010 Agile Mëtteg - The Customer role in agile

Agile Mëtteg - The Customer role in agile

17

GUIDELINES FOR SUCCESS

14 October 2010

18

PRINCIPLE

Team-Customer

Collaboration

14 October 2010 Agile Mëtteg - The Customer role in agile

Agile Mëtteg - The Customer role in agile

19

OBJECTIVES

Build knowledge

Build a solution that fits the real

needs

Optimize delivered value

Build trust relationship

14 October 2010

Agile Mëtteg - The Customer role in agile

20

BUILDING KNOWLEDGE

Create a short feedback loop with users

Deliver working software frequently

Planning as a knowledge building activity

Agree on a “Definition of done”Decompose, clarify and validate requirements for reaching a common understanding and allowing the team estimating the effort

Iterations as Learning cyclesLearn about the product expected featuresLearn about the best way to build it

14 October 2010

Agile Mëtteg - The Customer role in agile

21

THE CUSTOMER IS EXPECTED TO

Evolve from Project to Product ManagementElaborate and share a visionManage product lifecycle with ReleasesUnderstand and communicate the requirementsEvaluate business valueHave the power and responsibility to decideBe available to collaborate with the team continuouslyRespect team capacity limit

14 October 2010

Agile Mëtteg - The Customer role in agile

22

THE CUSTOMER CAN EXPECT THE TEAM TO

Estimate effort (on a relative scale)Commit for achieving short-term goalsBuild quality inAccept changes in requirementsImprove continuously

14 October 2010

Agile Mëtteg - The Customer role in agile

23

BENEFITS

Drive the development effort to optimize value under time and budget constraints

14 October 2010

Agile Mëtteg - The Customer role in agile

24

THE PRODUCT OWNER ROLE IN SCRUM

14 October 2010

Agile Mëtteg - The Customer role in agile

25

SCRUM

14 October 2010

Sprint Planning

Review

Retrospective

Product Owner

Scrum Master

Team

Agile Mëtteg - The Customer role in agile

26

PRODUCT OWNER – ROLE SUMMARY

Responsible for the ProductDefines product vision and featuresPlans releases (dates and content)Prioritizes features according to market value Can change features and priority before every iterationAccepts or rejects work resultsIs responsible for the profitability of the product (ROI)

14 October 2010

Agile Mëtteg - The Customer role in agile

27

PRODUCT OWNER DAILY DUTIES

14 October 2010

IterationStart: • Provide priorities

for iteration planning

• Obtain team commitment on scope

End: • Validate the results

(features delivered)• Update the Release

plan• Helps the team

improve the process

On-going: • Coordinate with other stakeholders to define

requirements• Collaborate with the team to communicate and clarify

requirements• Groom the product backlog• Decide on priorities

Agile Mëtteg - The Customer role in agile

28

PRODUCT BACKLOG… Main tool

14 October 2010

ModularityGranularity

VisionEpicsUser Stories

Business valueEffort estimationPriority

Agile Mëtteg - The Customer role in agile

29

USER STORY… A mean

The 3 Cs

14 October 2010

<Title>

As a <role>

I want to <do something>

So that <goal>

Priority Effort estimation

Card

Confirmatio

n

Conversati

on

+ acceptance criteria

Agile Mëtteg - The Customer role in agile

30

OTHER MEANS & TOOLS

14 October 2010

Indicators based on criteriaProfitability (Cost, Revenue, Margin…)Market shareClient satisfactionEnterprise imageInnovation…

Examples of values model KANO modelCost of delay model…

Agile Mëtteg - The Customer role in agile

31

CONCLUSION

14 October 2010

Agile Mëtteg - The Customer role in agile

32

TIME-TO-MARKET

Sources: Mah 2008. Moutain Goat Software, LLC14 October 2010

Agile Mëtteg - The Customer role in agile

33

SALESFORCE.COM

Source: Greene and Fry 2008. Moutain Goat Software, LLC

568% more value delivered in the first year of being agile.

14 October 2010

Agile Mëtteg - The Customer role in agile

34

SATISFACTION

Improved

Significantly Improved

Enhanced ability to manage changing priorities

41% 51%

Improved project visibility 42% 41%

Improved alignment of IT and business goals 39% 27%

Reduced project risk 48% 17%Source: VersionOne, 2008 State of Agile Development Survey

14 October 2010

Agile Mëtteg - The Customer role in agile

35

QUESTIONS

14 October 2010

READY to TRY

Agile Mëtteg - The Customer role in agile

36

TRAINING PATH

Introduction (1 day)Agile Software Development Methods

Scrum basics (2 days)Agile Project Management with Scrum

Product Owner focus (2 days)Become a Scrum Product Owner

In depth (3 days)Scrum in practice

14 October 2010

Agile Mëtteg - The Customer role in agile

37

CERTIFICATIONS

Certifications are delivered by the Scrum Alliance. You need to attend a course and pass a test to be certified.

14 October 2010

Agile Mëtteg - The Customer role in agile

38

Certifications Duration Date

Certified Scrum Master 2 days To plan in 2011

Certified Scrum Product Owner

2 days 8-9 Nov. 2010

NEXT TRAININGS & CERTIFICATIONS

Courses Duration

Oct Nov Dec

Agile methods 1 day 11 8 13

Scrum 2 days 12 9 14

Scrum in practical 3 days 24 - -

Scrum Product Owner

2 days - 25 -

14 October 2010

Complete calendar on: http://www.agilepartner.net/training/focus-on/

Agile Mëtteg - The Customer role in agile

39

RESOURCES

Agile Partner: www.agilepartner.net NEW! blog.agilepartner.net

Agile Interest Group Luxembourg: www.aiglu.org

Agile Alliance: www.agilealliance.org Scrum alliance: www.scrumalliance.org Scrum.org

14 October 2010

Agile Mëtteg - The Customer role in agile

40

CONTACTS

Thank You

14 October 2010

Guy FABIEN Sylvain CHERY

Senior Consultant [email protected] [email protected]

+352 621 256 436 +352 691 555 221

Agile Mëtteg - The Customer role in agile

41

RESOURCES

14 October 2010

Agile Mëtteg - The Customer role in agile

42

THE 12 PRINCIPLES (1/3)

Satisfy the customer through early and continuous delivery of valuable software.

Agile processes harness change for the customer's competitive advantage.

Deliver working software frequently with a preference to the shorter timescale.

Working software is the primary measure of progress.

14 October 2010

Agile Mëtteg - The Customer role in agile

43

THE 12 PRINCIPLES (2/3)

Business people and developers must work together daily throughout the project.

Face-to-face conversation for conveying information to and within a development team.

Build projects around motivated individuals. 

Sustainable pace for the sponsors, developers, and users.14 October 2010

Agile Mëtteg - The Customer role in agile

44

THE 12 PRINCIPLES (3/3)

Continuous attention to technical excellence and good design enhances agility.

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

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

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

Agile Mëtteg - The Customer role in agile

45

VARIOUS METHODS & PRACTICES

14 October 2010

Methods / practices Primary goal

Lean Software Development

Software development process improvement

KANBAN Process management

SCRUM Project management

XP Software engineering practices

TDR Test-driven requirement practice

TDD Test-driven development practice