1. The document discusses how to attain the next level of agility through a multi-step process. It outlines what is and is not considered agile and important stages to focus on. 2. Key steps to achieving the next level of agility include increasing customer involvement, improving prioritization of features, and adapting to changes during development through iterative methodology. 3. The document recommends assessing your current processes, obtaining executive support, getting team involvement, and using a coach or consultant to help guide the transition in a customized way through pilots and reviews.

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

2. Who am I
•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
www.agiletour.org Ghost

3. www.agiletour.org Agenda

4. Agenda
•What’s not « Agile »
•What’s « Agile »
•How to attain the next « Agility »
•Important stages
•For more information…
www.agiletour.org GroundRules

5. Ground Rules
• Electronics by exception
•One conversation at a time
•Participation & Respect
•Timeliness
• Anything else.. ?
www.agiletour.org Not Agile

6. What’s not “Agile”
www.agiletour.org

7. # Agile
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
www.agiletour.org Large Projects

8. Agile is not meant for large projects
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
www.agiletour.org What’s Agile

9. 3 Steps
3 Phases
What’s Agile
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
www.agiletour.org Plan&Routes 9

10. 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)
route to planned goal
What do you do at the moment of crisis?
(1969 lunar landing)
route to better goal
getting lost route to worse goal
www.agiletour.org Step1:HowNextLevel

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

12. Step 2 – What has to be more Agile
• 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 ]]
www.agiletour.org BusinessValue 12

13. System Evolution vs. Slices of BV
• 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?
Front Back Sides
Pick Up Trash
Mow
Trim & Edge
Sweep Clippings
BecomeWithin www.agiletour.org

14. Become Agile within
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
www.agiletour.org Elders&Kids

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

16. Step 3 – Five Whys
Why 5
Why 4
Why 2
Why 3
Why 1
The big ? is…
Not “Why” but “How”
dafsdf
www.agiletour.org ProvenFacts 16

17. 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 ?
www.agiletour.org IterateModel-ALM

18. Phase 1 – Small & Iterate
Iterate Model : Application Life Stages
Source :
http://en.wikipedia.org/wiki/Iterative_and_incremental_development
www.agiletour.org IteratePlan

19. Phase 1 – Small & Iterate
Iterate Model : Requirements Planning - Generic
http://www.testfocus.co.za/featurearticles/v10n3_09_3rdquarter.html
www.agiletour.org IterateNewModel

20. Phase 1 – Small & Iterate : Right Level
Iterate Model :
www.agiletour.org DefectReason

21. Phase 2 – Testing : Next Level is Right Choice
Defect Identification
www.agiletour.org RallyRelease

22. Phase 3 – Release Planning : Iterations
Source: http://www.rallydev.com/learn_agile/agile_planning/release_planning/
www.agiletour.org ReleaseNotIterations

23. Phase 3 – Release is Not Iterations
Release (vs) Iterations
• Focused on User Stories • Focused on tasks decomposed
supporting a theme from user stories
• Based on a healthy, historical • Based on velocity and capacity
velocity of the team
• Usually 1-4 months in length • Usually 1-4 weeks in length
consisting of 2-4 iterations
• “What” focused – what can we • “How” focused – how are we
deliver going to get there?
• Story writing • Task estimating
• Shippable product – features • Potentially shippable product –
are made available to the features are demo-able
customer
Source: http://www.rallydev.com/learn_agile/agile_planning/release_planning/
www.agiletour.org ReleaseCycle

24. Phase 3 – Agile Release Structure : Release Cycle
Scrum 1 or 2 sprints depending on
Master the product complexity
Sprint Transition
Planning
Sprint 1 Sprint 2 Sprint 3 Sprint 4 Hardening Hardening
2 – 12 weeks Sprint Sprint
• Team building (Staffing,
Scrum Master 5 – 10% Backlog grooming
• Release Timeline
• Architecture Definition
(coarse grain)
• Dependencies identified System test involved
• Release cost forecast
• Release Backlog
• Prioritized
• Sized
• Detailed
• Estimated
•Sprint goal for 1 or 2 sprint
•May not be formal sprint
www.agiletour.org QA

25. Q&A Thanks
www.agiletour.org Tx