Journey to Next level Agility
Download as PPTX, PDF0 likes640 views
1) The document discusses achieving the next level of agility through three main steps: assessing whether the organization is truly agile, identifying areas that need to be more agile such as customer involvement and prioritization, and using the "five whys" technique to understand root causes. 2) It emphasizes focusing on delivering business value through iterative development of high priority features rather than completing all functions at once. 3) Achieving the right level of agility is discussed, including starting small, obtaining support, and focusing on high impact areas through a readiness assessment and custom process tailored to the organization.
Journey to Next level Agility
- 1. Journey to next level of Agilityచక్రవర్తిhttp://about.me/Chakravarthy0www.agiletour.org
- 2. Who am IStarted IT career on April 4th 1996
- 3. Workedwithvariouscompanies & played all roles of SDLC
- 4. Certified by Microsoft as
- 8. Scrum Master
- 9. Awarded as MVP by Microsoft
- 10. For more information… Post Session1 Ghostwww.agiletour.org
- 13. What’s « Agile »
- 14. How to attain the next « Agility »
- 15. Important stages
- 17. Ground RulesElectronics by exception
- 18. One conversation at a time
- 20. Timeliness
- 21. Anythingelse.. ? 4Not Agilewww.agiletour.org
- 23. # AgileEverything is AgileResource location is agile
- 24. Resource reporting is agile
- 25. Requirement is agile by every day / every hour
- 26. Team composition is agileManager saysYou are everything
- 27. You directly talk to the client and do what ever he asks you
- 29. MythTechnical DebtAgile is not meant for large projectsAgile doesn’t suite for large projects, becauseArchitecture can’t be build in small iterations
- 30. That is built on small iterations wouldn’t sustain for huge business application
- 31. It is always like chasing the moving target
- 32. Work assigning is a tedious task
- 33. Audit history for Change requests is uncontrollable
- 34. Product Owner is the paymaster and thus he dictates
- 35. what is to be done
- 36. when is to be done
- 38. 3 Steps3 PhasesWhat’s AgileBing has beyond ample list of web docsYou 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 spacedictionary.reference.com“quick and well-coordinated in movement”No definition @ either wikipedia (or) wikitionaryThey have definition for “Agility”, but not of agile.d8Plan&Routes9www.agiletour.org
- 39. www.agiletour.orgSometimes 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?planned route to planned goalroute to planned goal (1969 lunar landing)Moment of crisis!route to better goalroute to worse goalgetting lost9Step1:HowNextLevel
- 40. How to next level? Step 1The first Question is..Are we professional? - Ken Schwaberhttp://bit.ly/RvProfThere is a difference between “Profession” and “Professional”One is a standard & the other is Behavior - David Starrwww.agiletour.org10Step2:What2BAgile
- 41. Step 2 – What has to be more AgileIncreasing the Customer Involvement[[Not to an extent of dictatingwhodoeswhat.. ]]Improving the prioritization of Features[[Higher value featuresgenerate revenue.. ]]Increasing the Team Buy-in & involvement[[Self organised teams doesn’tneedwork allocation ]]Adapting to change During the Development[[Iteratemethodologyhelps to reassessthe features & Project Timeline ]]11BusinessValue12www.agiletour.org
- 42. www.agiletour.orgSystem Evolution vs. Slices of BVMowing the lawn analogy
- 43. 4 “functions” to mow the law to get to “done, done, done”
- 44. Completing 1 “function” does not deliver “business value”
- 45. Deadline – Time Boxed
- 46. My kid is going to mow the lawn – will he do a good job?FrontBackSidesPick Up TrashMow Trim & Edge Sweep ClippingsBecomeWithin12
- 47. Become Agile withinwww.agiletour.orgYour Goal should not the be Next Level, but the Right levelAssess your organization to determine where you should begin adding agility.Obtain executive support for the move to the Next level of Agile process. Get the development team involved in the migration process to ensure buy-in. Develop a clear understanding of your current processes by documenting them.Identify a coach or consultant to help you with your migration. That’s where I can help you.. 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.Outline a custom process based on the findings from the previous stepTry the new process on a pilot project.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.aspx13Elders&Kids
- 49. Step 3 – Five WhysWhy 5Why 4Why 2Why 3Why 1The big ? is…Not “Why”but “How”dafsdf15ProvenFacts16www.agiletour.org
- 50. www.agiletour.orgThe Proven FactsThere are two villages, Attari and Wazirgunjin Gaya, separated by a big hill.Who does the layout for the Road between these villages?Do we have to follow the belowTake permission from GovtGovt does an ariel study for the path planGovt invites tenders ..Blah .. Blah ....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, resultingThe road between the villages
- 51. A notice from the Medical agency for the treatment to the manHow is this possible ?16IterateModel-ALM
- 52. www.agiletour.orgPhase 1 – Small & IterateIterate Model : Application Life StagesSource : http://en.wikipedia.org/wiki/Iterative_and_incremental_development17IteratePlan
- 53. www.agiletour.orgPhase 1 – Small & IterateIterate Model : Requirements Planning - Generichttp://www.testfocus.co.za/featurearticles/v10n3_09_3rdquarter.html18IterateNewModel
- 54. www.agiletour.orgPhase 1 – Small & Iterate : Right LevelIterate Model : 19DefectReason
- 55. www.agiletour.orgPhase 2 – Testing : Next Level is Right ChoiceDefect Identification20RallyRelease
- 56. www.agiletour.orgPhase 3 – Release Planning : IterationsSource: http://www.rallydev.com/learn_agile/agile_planning/release_planning/21ReleaseNotIterations
- 57. Release (vs) IterationsFocused on tasks decomposed from user stories
- 58. Based on velocity and capacity of the team
- 59. Usually 1-4 weeks in length
- 60. “How” focused – how are we going to get there?
- 61. Task estimating
- 62. Potentially shippable product – features are demo-able
- 63. Focused on User Stories supporting a theme
- 64. Based on a healthy, historical velocity
- 65. Usually 1-4 months in length consisting of 2-4 iterations
- 66. “What” focused – what can we deliver
- 67. Story writing
- 68. Shippable product – features are made available to the customerwww.agiletour.orgPhase 3 – Release is Not IterationsSource: http://www.rallydev.com/learn_agile/agile_planning/release_planning/22ReleaseCycle
- 69. www.agiletour.orgSprint TransitionPhase 3 – Agile Release Structure : Release CycleScrum Master1 or 2 sprints depending on the product complexityPlanning2 – 12 weeksSprint 1Sprint 2Sprint 3Sprint 4Hardening SprintHardening Sprint Team building (Staffing, Scrum Master
- 70. Release Timeline
- 71. Architecture Definition (coarse grain)
- 74. Release Backlog
- 75. Prioritized
- 76. Sized
- 77. Detailed
- 78. Estimated
- 79. Sprint goal for 1 or 2 sprint
- 80. May not be formal sprint5 – 10% Backlog groomingSystem test involved23 QA
Editor's Notes
- #4: Through out this session, neither I’m not going to show the ghost nor am going to do a ghost buster action. Am going to speak about what is already in practice and how we can take to much better situation
- #11: There are common questions that worry during the progress of the project. We need to understand the moment of crisis and act in the right manner to reach either the better goal or the planned goal. It all depends on how we have laid out our business process. It all depends on the nature of agile team.Agile is not a path but a practice with spirit. See the Agile as a spirit rather than as a process.
- #15: Here is the gist of everything, “doing it right is right” is next level
- #18: http://www.thaindian.com/newsportal/uncategorized/relief-for-family-of-man-who-carved-road-through-hill-in-bihar_10086397.html
- #19: This is the generic spirit of Agile practice. According to the book, it is said that pickup small chunk of work and follow all the principles of SDLC, such that the small chunk of work is ready to release at any given point.
- #20: In most cases, this kind of practice is in place. This is the real spirit of Iterate model and organizing the product backlog. But to make better use of this model, you need to realize how and when to rearrange the product backlog.There is also a chance that change requests / new product items / priority changes for each (or) every item in product backlog. Identifying that change is a real challenge and one has to be genius enough to handle the situation.
- #21: Within Iteration model, we have to make sure that the new work items can be added depending on the weight of the task points. Work items may be removed / postponed or rearranged at any given time.
- #22: Identifying the bugs is the right level. But again, it depends on how we can identify them at the early stage. Here it is very important to have an automated build mechanism and continuous integration on a daily basis. Once the project has such tools, identifying the bugs is only with a day of latency.The testers are happy to get their work recognized on the very moment.
- #23: RallyDev pictorial description of the release planning. Diagrammatically, it is very clear that final delivery consignment is increasing by size and finally reaches to the real size.
- #24: In the early stages of Agile practice it is misunderstood that Iteration's output is the Release, but that is not. Here are the few differences between these ideas.
- #25: Finally, it is a good practice to have any agile project as presented here.
- #26: Take 1 or 2 questions and be available for the offline discussion.