are customers ready for agile?

Post on 18-Dec-2014

366 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

This lecture aims at giving insights into the importance of customer for the Information Systems project success, as one of its critical factors, focusing on customer’s involvement in project development process, understanding his requests and dealing with his resistance to change. After demonstrating the rates of project failures caused by customer related factors, based on findings of empirical study carried out with involvement of 603 IT professionals from 53 different countries, the lecture is expected to explain the solutions Agile creates for this kind of success roadblocks and ways in which Product Owners together with Scrum Masters should educate their customers and involve them in the process.

TRANSCRIPT

SARAJEVO, 27.10.2014

NERMINA DURMIC

Are Customers Ready for Agile?

Product Manager, Lecturer, Trainer, Researcher……Learner!

nermina@agile.bahttps://www.linkedin.com/in/nerminadurmic@durmicnermina

Who are customers?

Customer collaboration – project failure

Failure + Challenge

52%

Success48% Unsuccess

ful71%

Successful29%

Customer Collaboration

62%

30%

8%

RegionEuropean

American

Other

34%

15%

51%

Role in Organization

Software Developer

QA Engineer

Other

25%

22%

53%

Experience 1 - 5

11 - 15

Other

What about Bosnian IT Community?

Failure + Challenge42%Success

58%

Successful38%Unsuccessful

62%

Customer Collaboration

So, are customers ready for Agile?

Agile Principles

“The change to Agile methodologies was appropriated and part of our success!”

Product Manager, Ecuador,12 years of professional experience

Customer role in Scrum

Scrum does not define customer as a role !!!

PO as a Customer Voice (1)

PO as a Customer Voice (2)

PO as a Customer Voice (3)

The biggest challenge in Agile

Welcome changing requirements, even late in development

Responding to change over following a plan

Working software over detailed documentation

I don’t have to plan and I can make the changes all the time!!!

SO

Scarlett O’Hara method

“I’ll think about that tomorrow”

Educate your customers

They’re willing to learn!

Sprints

Product backlog

Prioritizing

Feature definition

Acceptance criteria

Release contents

Product success

Business success

Time

Money

Sprint goal and plan

Sprint velocity

Real Project Example

0

13 12

0

47

30

310

5

10

15

20

25

30

35

40

45

50

Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Sprint 6 Sprint 7 Sprint 8

Sprint Velocity

Product Owner’s Responsibility

“This project was an example of the cliché: “You start programming, I’ll go find out what they want”.”

Software Engineer, USA15 years of professional experience

Help Your Customers

Don’t ask them what they want

Ask them about the problems they have and how they’re dealing with it now

Customers in development phase

Available for answering questions

Not requesting changes or changing the sprint goal

Customers in verification phase

Sprint Review

Fix this!

Failure + Challenge

52%

Success48% Unsuccess

ful71%

Successful29%

Customer Collaboration

Q&A

Thank You

top related