Scrum jan 22nd - manoj vadakan - conscires agile practices

64
Going Agile? What is in it for me? MANOJ VADAKKAN Manoj Vadakkan [email protected] HOSTED BY Bachan Anand Conscires Agile Practices [email protected]

Transcript of Scrum jan 22nd - manoj vadakan - conscires agile practices

Page 1: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Going Agile? What is in it for me?

M A N O J V A D A K K A N

Manoj [email protected]

H O S T E D B YBachan AnandConscires Agile [email protected]

Page 2: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Conscires Agile Practices

Who we are ::

Enabler of Agile & Scrum adoption for your organization

Agile Adoption Assessment, Training & Coaching

What we do :: Agile & Scrum Coaching – http://agile.conscires.com/services/

Agile & Scrum Trainings - http://bit.ly/allTrainings

Boston,MA

Irvine,CA

San Diego,CA

Phoenix, AZ

Page 3: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Your experience with Agile

I don’t know what Agile is

Understand the values of Agile

Started using Agile but have Challenges

I am sailing smooth on my Agile boat

3

Page 4: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Agenda

Why Agile?

What is In In It For Me?

What is Scrum?

4

Page 5: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

About your facilitator

5

Page 6: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Certifications6

Page 7: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Organizations consulted with7

Page 8: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Currently with8

Page 9: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Previous Speaking Engagements9

Page 10: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Iterative Vs. Agile

10

Page 11: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Homework Problem11

http://alistair.cockburn.us/Are+iterations+hazardous+to+your+project%3F

Page 13: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Homework Problem13

Page 14: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Homework Problem14

Page 15: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Homework ProblemThe plan

Read two book every day (M-F)

Spend Saturday to answer questions

Submit answers on Monday

15

0

2

4

6

8

10

12

Monday Tuesday Wednesday Thursday Friday Saturday

# of Books to Read

# of Questions

Page 16: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Homework ProblemWhat Really Happened

Student read books as per plan.

Status on Friday - Green

Started looking at questions on Saturday to realize that books need to be read again for the most part

Status on Saturday - Red

16

0

2

4

6

8

10

12

# of Books to Read

# of Questions

Page 17: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

What is the point?

How the student should have measured his progress?

Number of Books read?

Number of Questions answered?

How do you measure progress in your projects?

17

Page 18: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

18

Agile

Page 19: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Agile Manifestowww.agilemanifesto.org

19

Page 20: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Agile Manifestowww.agilemanifesto.org

Individuals & interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

20

That is, while there is value in the items on the right,

we value the items on the left more.

Page 21: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Responding to Change

21

Page 22: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Working Software

22

Page 23: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Working Software

Track Record

23

Page 24: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: The Plan

24

Page 25: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentThe Plan

25

Page 26: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: The Plan

26

Page 27: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: The Plan

27

Page 28: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: The Plan

28

Page 29: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: The Plan

29

Page 30: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentOct Target date

30

Page 31: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Reality?

31

Page 32: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: Reality

32

Page 33: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: Reality

33

Page 34: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: Reality

34

Page 35: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: Reality

35

Page 36: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentNew Date

36

Page 37: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentsystem testing

37

Page 38: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

bugs38

Page 39: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentProduction Release

39

Page 40: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentProduction Release

delivered in March

40

Page 41: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven developmentProduction Release

5 Months late

41

Page 42: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

The Plan Driven development: Prod. Release

no new business value for 15 months

42

Page 43: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Trust?

43

Page 44: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

How do we build the Trust?

44

Page 45: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

What if we deliver

working Software

with business value from the first week/month

45

Page 46: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

What if we deliver

working Software

Frequently

46

Page 47: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Agile Manifestowww.agilemanifesto.org

Individuals & interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

47

That is, while there is value in the items on the right,

we value the items on the left more.

Page 48: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Agile is not an Excuse for

We don’t need to plan anything

We don’t need to document anything

48

Page 49: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Lazy Agile

49

Page 50: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

50

Why Agile?

Page 51: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Why Agile?

We may have better process efficiency than we ever had before.

How do we improve now?

Is the budget/schedule getting shorter?

How about value delivered & Time to Market?

Page 52: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Business Value

Is prioritization an afterthought?

When/who prioritize features?

Late? may be when we are really sure we can not do it all within the time?

Page 53: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Applying the Pareto Principle

Page 54: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Reasons for Project Failure

54

Lack of User Input 13%

Incomplete Requirements & Specifications 12%

Changing Requirements & Specifications 11%

Lack of Executive Support 8%

Technology Incompetence 7%

Lack of Resources 6%

Unrealistic Expectations 6%

Unclear Objectives 5%

Unrealistic Timeframes 4%

New technology 4%

Other 23%

Extracted from CHAOS Report : The Standish Group 1995

Page 55: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

55

User Involvements 16%

Executive Management Support 14%

Clear statements of Requirements 13%

Proper Planning 10%

Realistic Expectations 8%

Smaller Project Milestones 8%

Competent Staff 7%

Ownership 5%

Clear Vision and Objectives 3%

Hardworking, Focused Staff 2%

Other 14%

Extracted from CHAOS Report : The Standish Group 1995

Reasons for Project Success

Page 56: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

What is in it for me?

As a customer , I want to be able to Go to market faster Faster return on investment Opportunity to provide feedback early

As a Project Manager/Leadership, I want To measure progress in terms of real progress made on product . Better engaged and accountable team

As a team member, I want A sustainable pace Satisfaction of quality product delivered Clear Priority and less interruption during development

56

Page 57: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

57

Scrum A quick Introduction Scrum

Page 58: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Scrum

A process framework for managing product development

Not a methodology

58

Page 59: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Sprint

Sprint

Sprint

Sprint

Sprint

Production

Release

Product Owner with

Stakeholders/PMO

Product Owner with

Stakeholders/PMO

Product Backlog

Feedback from Sprint

Reviews

Feedback from Releases

Sprint = Iteration

Discovery Period

During the Discovery Period, the product team identify the features, prioritize the features, and identify a

roadmap for the product. The roadmap will identify the release milestones into production and the features

contained in each releases at a high-level.

Each Sprint deliver (for a subset of Product Backlog) running tested features potentially shippable that the team

can demonstrate to the customer to get feedback

Multiple sprints

usually build up a

release

Agile Product Development

Page 60: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Product Owner with

Stakeholders/PMO

With the help of the Product Owner, the team selects a set of features from the top of the prioritized product

backlog.

Team Spends 2 to 4 hours on the first day of the sprint to break down the features to detail tasks (technical,

testing, documentation, etc) and estimate hours needed to complete them.

Within the sprint the team deliver Running Tested Features along with all the documentation for the selected

features.

The product from the sprint is demonstrated to the customer to get feedback.

Sprints are of the consistent, fixed length for a project, usually 1 week to 4 weeks.

Agile Product Development: Sprints

Product

Backlog

Sprint

Backlog

Sprint

Task List

Sprint

Demo

The team

creates working

software for the

features

selected for the

Sprint including

all the

necessary

Documentation Sprint

Potentially

shippable

product

Initial Analysis for

the sprint backlog

Acceptance

Criteria

Defined for Sprint

Page 61: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Scrum61

• Roles

• Product owner

• Scrum Master

• Team

• Ceremonies

• Daily Scrum

• Sprint Planning

• Sprint Review-Demo

• Retrospective

• Artifacts

• Product Backlog

• Sprint Backlog

• Planning

• Release plan

• Progress Tracking

• Velocity

• Burn down Chart

Page 62: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

What is in it for me?

As a customer , I want to be able to Go to market faster

Faster return on investment

Opportunity to provide feedback early

As a Project Manager/Leadership, I want To measure progress in terms of real progress made on product .

Better engaged and accountable team

As a team member, I want A sustainable pace

Satisfaction of quality product delivered

Clear Priority and less interruption during development

62

Page 63: Scrum   jan 22nd  - manoj vadakan -  conscires agile practices

Upcoming Trainings in Boston,MA

“What is Scrum” by Manoj Vadakan on Feb 19th 2011

Certified ScrumMaster Training by Alan Cyment on April 7th – 8th 2011

20% discount with code Webinar0122

Contact Bachan Anand

W : http://agile.conscires.com

E : [email protected]

P : 949-232-8900