Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Transition to agile


Published on

what the various Agile adoption issues and steps to successfully implement agile in any organization.

Published in: Technology, Business
  • Be the first to comment

Transition to agile

  1. 1. By Prashant Pund AgileSoft
  2. 2.  Moving with quick ,easy grace. Iterative and incremental approach People-centric approach Involvement of the client Minimalistic approach Ego-less team work Boss as a mentor, not the police Learn and Adapt
  3. 3. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more. Kent Beck,,Mike Beedle,Arie van Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler, James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries,Jon Kern,Brian Marick Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland Dave Thomas© 2001, the above authorsthis declaration may be freely copied in any form, but only in its entirety through this notice.
  4. 4.  Analysis of the existing methodology Decision to move to Agile Buy-in from the Sr. Management Training session for Sr. and Middle Management Choosing a pilot project Choosing a team Training session for the team Mentoring during implementation
  5. 5.  Understand the present methodology Understand the domains and types of projects Tabulate the strengths and limitations of current methodology Understand the possible participation of the Business or Client side.
  6. 6.  The decision about the methodology size can be taken based on various project parameters including criticality and the constraints. Typically, if the requirements are changing frequently, the option of Agile is considered. (Very generic statement)
  7. 7.  Moving to Agile is a change at personal, project and organizational level. Change is scary to many. Good understanding and Buy-in from the Sr. Management is essential before the implementation.
  8. 8.  The team with “Business” people attend a 2 day session on the Agile Methodology in general and Scrum in particular. This session explains the methodology with exercises and examples. Roles, Artifacts and activities are explained.
  9. 9. A pilot project is selected to try Agile and gain the confidence/learning. This is not a project which is allowed to fail! The concept of “Learn and Adapt” is to be understood.
  10. 10.  Open minded Pro-active Extrovert Experts Assertive
  11. 11.  The consultant sits with the team daily for the first sprint. The frequency of the visits decreases with further sprints/attainment of Agile maturity. The role of consultant is to guide/mentor the team; not managing project Pull out after enablement of the team