journey to next level of agility- charkrvarthy

25
Journey to next level of Agility చరవత ి http://about.me/Chakravarthy www.agiletour.org

Upload: india-scrum-enthusiasts-community

Post on 13-Jan-2015

1.161 views

Category:

Technology


0 download

DESCRIPTION

 

TRANSCRIPT

Page 1: Journey to Next Level of Agility- Charkrvarthy

Journey to next level of Agility

చక్రవర్తి

http://about.me/Chakravarthy

www.agiletour.org

Page 2: Journey to Next Level of Agility- Charkrvarthy

•Started IT career on April 4th 1996

•Worked with various companies & played all roles of SDLC

•Certified by Microsoft as

• Technology Spécialist

• Professional Developer

•Certified by Scrum allience as

• Scrum Master

•Awarded as MVP by Microsoft

•For more information… Post Session

Who am I

www.agiletour.org Ghost

Page 3: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org Agenda

Page 4: Journey to Next Level of Agility- Charkrvarthy

•What’s not « Agile »

•What’s « Agile »

•How to attain the next « Agility »

•Important stages

•For more information…

Agenda

www.agiletour.org GroundRules

Page 5: Journey to Next Level of Agility- Charkrvarthy

• Electronics by exception

•One conversation at a time

•Participation & Respect

•Timeliness

• Anything else.. ?

Ground Rules

www.agiletour.org Not Agile

Page 6: Journey to Next Level of Agility- Charkrvarthy

What’s not “Agile”

www.agiletour.org

Page 7: Journey to Next Level of Agility- Charkrvarthy

Everything is Agile

• Resource location is agile

• Resource reporting is agile

• Requirement is agile by every day / every hour

• Team composition is agile

Manager says

• You are everything

• You directly talk to the client and do what ever he asks you

• d

# Agile

www.agiletour.org Large Projects

Page 8: Journey to Next Level of Agility- Charkrvarthy

Agile doesn’t suite for large projects, because

• Architecture can’t be build in small iterations

• That is built on small iterations wouldn’t sustain for huge business application

• It is always like chasing the moving target

• Work assigning is a tedious task

• Audit history for Change requests is uncontrollable

• Product Owner is the paymaster and thus he dictates

• what is to be done

• when is to be done

• d

Agile is not meant for large projects

www.agiletour.org What’s Agile

Page 9: Journey to Next Level of Agility- Charkrvarthy

Bing has beyond ample list of web docs

You can bing for Agile methodologies and it is easy to lost in the web hive with the tons of information that is available for you. Be careful, too much information is also fatal

Local communities help you

Now-a-days, Agile is being a buzz word within the industry as well as with venture capitalists, it is giving ample scope for the communities to come together. There are few local communities, please join them and get the different people’s understanding and implementation of Agility within their work space

dictionary.reference.com

“quick and well-coordinated in movement”

No definition @ either wikipedia (or) wikitionary

They have definition for “Agility”, but not of agile.

d

What’s Agile

9 www.agiletour.org Plan&Routes

3 Steps

3 Phases

Page 10: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

Sometimes things don’t go as planned. Sometimes the original plan is the WRONG one!

How do you know which is right? How do you know where you are? (answer: incremental development with feedback)

What do you do at the moment of crisis? route to planned goal

(1969 lunar landing)

route to better goal

getting lost route to worse goal

Step1:HowNextLevel

Page 11: Journey to Next Level of Agility- Charkrvarthy

How to next level? Step 1

The first Question is..

Are we professional?

- Ken Schwaber

http://bit.ly/RvProf

There is a difference between “Profession” and “Professional”

One is a standard & the other is Behavior

- David Starr

www.agiletour.org Step2:What2BAgile

Page 12: Journey to Next Level of Agility- Charkrvarthy

• Increasing the Customer Involvement [[Not to an extent of dictating who does what.. ]]

• Improving the prioritization of Features [[Higher value features generate revenue.. ]]

• Increasing the Team Buy-in & involvement [[Self organised teams doesn’t need work allocation ]]

• Adapting to change During the Development [[Iterate methodology helps to reassess the features & Project Timeline ]]

Step 2 – What has to be more Agile

12 www.agiletour.org BusinessValue

Page 13: Journey to Next Level of Agility- Charkrvarthy

• Mowing the lawn analogy

– 4 “functions” to mow the law to get to “done, done, done”

– Completing 1 “function” does not deliver “business value”

• Deadline – Time Boxed

• My kid is going to mow the lawn – will he do a good job?

www.agiletour.org

System Evolution vs. Slices of BV

Pick Up Trash

Mow

Trim & Edge

Sweep Clippings

Front

BecomeWithin

Back

Sides

Page 14: Journey to Next Level of Agility- Charkrvarthy

Become Agile within

www.agiletour.org

Your Goal should not the be Next Level, but the Right level

1. Assess your organization to determine where you should begin adding agility.

2. Obtain executive support for the move to the Next level of Agile process.

3. Get the development team involved in the migration process to ensure buy-in.

4. Develop a clear understanding of your current processes by documenting them.

5. Identify a coach or consultant to help you with your migration.

That’s where I can help you..

1. Review your current process, and look for areas that can be shifted to more Agile

methods. Focus on areas with the most potential for improvement and the most

value to the customer and your organization. The readiness assessment will also

help with this task.

2. Outline a custom process based on the findings from the previous step

3. Try the new process on a pilot project.

4. Review the findings after the pilot, make changes, and continue to scale out your

new methodology.

Source: http://msdn.microsoft.com/en-us/library/hh273005.aspx

Elders&Kids

Page 15: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org 05/11/10 Step3:5Whys

Page 16: Journey to Next Level of Agility- Charkrvarthy

The big ? is…

16 www.agiletour.org

Step 3 – Five Whys

ProvenFacts

Not “Why”

Why 5

Why 4

Why 3

Why 2

Why 1

but “How”

dafsdf

Page 17: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

The Proven Facts

1. There are two villages, Attari and Wazirgunj in Gaya, separated by a big hill.

2. Who does the layout for the Road between these villages?

3. Do we have to follow the below

1. Take permission from Govt

2. Govt does an ariel study for the path plan

3. Govt invites tenders ..

4. Blah .. Blah ..

5. ..

But one man at the age of 60, Manjhi had single-handedly carved out a 360 feet

long, 30 feet high and 30 feet wide passage by cutting through a hill near Gahlaur

with a hammer, chisel and nails, working day and night, resulting

• The road between the villages

• A notice from the Medical agency for the treatment to the man

How is this possible ?

IterateModel-ALM

Page 18: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

Phase 1 – Small & Iterate

Iterate Model : Application Life Stages

IteratePlan

Source :

http://en.wikipedia.org/wiki/Iterative_and_incremental_development

Page 19: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

Phase 1 – Small & Iterate Iterate Model : Requirements Planning - Generic

IterateNewModel

http://www.testfocus.co.za/featurearticles/v10n3_09_3rdquarter.html

Page 20: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

Phase 1 – Small & Iterate : Right Level

Iterate Model :

DefectReason

Page 21: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

Phase 2 – Testing : Next Level is Right Choice

Defe

ct

Identification

RallyRelease

Page 22: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org ReleaseNotIterations

Phase 3 – Release Planning : Iterations

Source: http://www.rallydev.com/learn_agile/agile_planning/release_planning/

Page 23: Journey to Next Level of Agility- Charkrvarthy

Release (vs) Iterations

• Focused on User Stories supporting a theme

• Based on a healthy, historical velocity

• Usually 1-4 months in length consisting of 2-4 iterations

• “What” focused – what can we deliver

• Story writing

• Shippable product – features are made available to the customer

• Focused on tasks decomposed from user stories

• Based on velocity and capacity of the team

• Usually 1-4 weeks in length

• “How” focused – how are we going to get there?

• Task estimating

• Potentially shippable product – features are demo-able

www.agiletour.org ReleaseCycle

Phase 3 – Release is Not Iterations

Source: http://www.rallydev.com/learn_agile/agile_planning/release_planning/

Page 24: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org QA

Phase 3 – Agile Release Structure : Release Cycle

Planning

2 – 12 weeks Sprint 1

Sprint 2

Sprint 3

Sprint 4

Hardening

Sprint

Hardening

Sprint

Sprint Transition

5 – 10% Backlog grooming

Scrum

Master

System test involved

1 or 2 sprints depending on

the product complexity

• Team building (Staffing,

Scrum Master

• Release Timeline

• Architecture Definition

(coarse grain)

• Dependencies identified

• Release cost forecast

• Release Backlog

• Prioritized

• Sized

• Detailed

• Estimated

•Sprint goal for 1 or 2 sprint

•May not be formal sprint

Page 25: Journey to Next Level of Agility- Charkrvarthy

www.agiletour.org

Q&A

Tx

Thanks