Your SlideShare is downloading. ×
Inventing Agile Flavour
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Inventing Agile Flavour

1,785
views

Published on

Venkatesh's talk on why Agile is spirituality and not a religion

Venkatesh's talk on why Agile is spirituality and not a religion

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,785
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
48
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Inventing Agile Flavor Agile is spirituality and not a religion Venkatesh Krishnamurthy 17 mai 2006
  • 2. Objective Theme of my talk What you would get out of this talk Release 1 Agile Best Practices Release 2 Agile Best Practices and tools Release 3 Agile Best Practices and tools Spirituality Vs Religion and Agile Various Agile religions Foundation for inventions Values and Lean Principles Questions 2 Le pied de page 17 mai 2006
  • 3. Theme Agile = Spirituality Agile Religion 3 Le pied de page 17 mai 2006
  • 4. Spirituality Vs Religion “The main difference between Spirituality and Religion is the freedom to choose your own path towards enlightenment and ultimately, recognition of our Divine selves. There is absolutely nothing wrong with many religions and belief systems, except that they are exclusionary and limiting…… (this para with key sentence is completed in the last slide !!) http://www.omplace.com/articles/Spirituality_vs_Religion.html 4 Le pied de page 17 mai 2006
  • 5. What you would learn from this presentation ? • You will learn how to migrate your process from Traditional method to an agile way • You will get to know some of the tools that could be used to make your software development Productive • You would learn the values and principles on which you can invent/Derive practices 5 Le pied de page 17 mai 2006
  • 6. Release 3 - Where are we right now ? • Onsite and Offshore model with a distributed team • Completed successfully 37 Iterations of 2 weeks each • Stress free development • Fully Agile with “Invented”/derived set of best practices • Highly energized team • 90% accuracy in planning and estimation • Attrition – Highly Controlled • Successful 4 releases of the product with a controlled delay of 3 weeks in 2 years ! 6 Le pied de page 17 mai 2006
  • 7. Tell me the Story from Release 1 17 mai 2006
  • 8. Release 1 - Scenario • Project Type : Green Field • Agile Experience of the team : None • Total Team Size: 5 (during beginning of the project) • Development Model: Onsite/Offshore • Pricing: T & M • Developers Background: CMM I and Traditional SDLC 8 Le pied de page 17 mai 2006
  • 9. Release 1 - Team Structure On shore Product Manager Developers Project Manager Architect Developers/Testers, etc Off shore 9 Le pied de page 17 mai 2006
  • 10. Our Goal Doing the product development using Agile Methodology 10 Le pied de page 17 mai 2006
  • 11. Release 1 - UP 11 Le pied de page 17 mai 2006
  • 12. First Release – 3 Months Milestone • Started off with 3 weeks iteration Baseline Architecture Incremental Design, Development, Testing and Delivery 2 Weeks 1 Week 2 Weeks 2 Weeks 2 Weeks 1 Week 1 Week Elaboration Inception Construction Transition 12 Le pied de page 17 mai 2006
  • 13. Each Iteration Iteration Iteration ... 1 2 Ana- De- Ana- De- Code+Design+Test+Integrate Code+Design+Test+Integrate lyze sign lyze sign 3 weeks 3 weeks 13 Le pied de page 17 mai 2006
  • 14. Release 1 - Detailed look at each week. Key Practices shown Iteration Iteration ... 1 2 Ana- De- Ana- De- Code+Design+Test+Integrate Code+Design+Test+Integrate lyze sign lyze sign 3 weeks 3 weeks Week1 Week2 Week3 Feedback loop •Coding Continued • Features Selection by the customer •Design •Testing •Requirement Analysis • Coding • Build • Mockups • Testing • Integrate • Release for UAT 14 Le pied de page 17 mai 2006
  • 15. Release 1 - Development Testing Cycles i i+1 i+2 Development Test Development Test Development Test 15 Le pied de page 17 mai 2006
  • 16. Practices introduced in Release 1 • Time Boxed Iteration (3 Weeks) • Risk Driven and Priority Driven Development • Client-Driven Development • Feature Driven Development • Daily 15 minutes stand up meetings • Incremental Delivery • Use Case Driven Non-Agile Practices • Heavy Documentation • PM Controlled task allocation • Bit resistance to frequent changes • Microsoft Project Plan as the tool • Handoff 16 Le pied de page 17 mai 2006
  • 17. Release 2 Story 17 mai 2006
  • 18. Release 2 • Release review/introspection meeting • Onsite • Offshore •New Practices, recommendation and research work started 18 Le pied de page 17 mai 2006
  • 19. Release 2 - continued the 3 weeks Time boxed iteration model as we did in Release 1 Iteration Iteration ... 1 2 Ana- De- Ana- De- Code+Design+Test+Integrate Code+Design+Test+Integrate lyze sign lyze sign Week1 Week2 Week3 Feedback loop •Coding Continued • Features Selection by the customer •Design •Testing •Requirement Analysis • Coding • Build • Mockups • Testing • Integrate • Release for UAT 19 Le pied de page 17 mai 2006
  • 20. Release 2 : Requirement Analysis • Use Case based documents (UP) • “Requirement days” through Interwise with onsite team. • Newcomers to see and listen through the “recordings” to get better understanding of requirements, rather through documents. 20 Le pied de page 17 mai 2006
  • 21. Release 2 – Planning and Estimation • Discarding MPP and usage of home grown agile PM tool • Team Planning: PM Relinquishing control of assignment of tasks, and the team volunteering to get what they want to do. (XP) • Wide Band Delphi 21 Le pied de page 17 mai 2006
  • 22. Release 2 - Design • Usage of light weight tools like ArgoUML • Whiteboarding with design captured through camera (didn’t work out well due to low resolution, battery and memory issues) • Do what is necessary now (DWIN) attitude. We never spent time on building complex frameworks. 22 Le pied de page 17 mai 2006
  • 23. Release 2 – Development Testing Cycles •Pipe Line Testing Development Test i Development Test i+1 … Development Test i+2 23 Le pied de page 17 mai 2006
  • 24. Release 2 – More best practices • Common Shared Repository • Two Scrum meetings (SCRUM) • With Local Development Team • With onsite team • Iteration retrospective (SCRUM) • Release retrospective (SCRUM) • Usage of IM such as Yahoo/MSN • Peer Reviews 24 Le pied de page 17 mai 2006
  • 25. Release 3 Team became comfortable with 2 weeks time boxed iteration Iteration Iteration ... 1 2 Ana- De- Ana- De- Code+Design+Test+Integrate Code+Design+Test+Integrate lyze sign lyze sign Week1 Week2 Feedback loop • Features Selection by the customer •Design •Requirement Analysis •Coding Continued • Mockups •Testing • Start Coding with Daily Build • Daily Build • Integrate 25 Le pied de•page 17 mai 2006 Release for UAT
  • 26. Release 3 – Planning, Estimation • Velocity based estimation • Maturity increased with the team, and a very good rhythm of iterations being established. • Usage of IEH during estimation and planning • Wiki as the knowledge and information sharing medium • Scrum notes being shared via Wiki with onsite team. • Rotation of scrum master role (Invented) 26 Le pied de page 17 mai 2006
  • 27. Release 3 • Continuous Integration, with Cruise control sending emails for build failures. • Integration of Checkstyle/PMD/Junit with Cruise Control for quality control • Big Visible graphs (XP) • Daily Build • Both Dev Team and Testing team being part of CI and Daily build activities • Practicing TDD • Back log management • Feature teams 27 Le pied de page 17 mai 2006
  • 28. Release 3 • Daily 20 minutes refactoring cycle (Invented) • Introducing Skype as another mode of communication in addition to interwise and other IMs, Wiki. • Making effective use of graphs like Release Burn Down, Iteration Burn down, Discovery Rate to effectively plan, estimate the iterations • Code Freeze used to happen for iterations every Wednesday, and incomplete things to move to 17 mai 2006 backlog. 28 Le pied de page
  • 29. Spirituality Vs Religion “The main difference between Spirituality and Religion is the freedom to choose your own path towards enlightenment and ultimately, recognition of our Divine selves. There is absolutely nothing wrong with many religions and belief systems, except that they are exclusionary and limiting. The main goals and ideals of most world religions are very much the same, but in most we are taught that as followers of a particular belief system, we are right, we will be saved and the others, well, poor unenlightened ones, they will be left behind. … “ In Para 2, replace the word “religions” with “agile flavors” and you will see a new dimension of agile world. http://www.omplace.com/articles/Spirituality_vs_Religion.html 29 Le pied de page 17 mai 2006
  • 30. Various Agile Religions approximately 60 key practices from following agile religions 1. Extreme Programming (XP) 2. Scrum Development 3. Crystal Methodologies 4. Feature Driven Development (FDD) 5. Dynamic Systems Development Method (DSDM) 30 Le pied de page 17 mai 2006
  • 31. Foundations for inventions All Inventions to be based Values Principles 31 Le pied de page 17 mai 2006
  • 32. Values •What is the simplest When there is a problem •What is the simplest When there is a problem Thing that could just ask the team. Keep Thing that could just ask the team. Keep Possibly work. all mediums of Possibly work. all mediums of •Context Based communication •Context Based communication Open within a team Open within a team •Keep moving towards the •Keep moving towards the Goal rather than expecting Goal rather than expecting Communication Simplicity Instant perfection. Get the Instant perfection. Get the Feedback and keep moving Feedback and keep moving towards the goal. towards the goal. •The sooner you know the •The sooner you know the sooner you can adapt sooner you can adapt •Courage manifests as •Courage manifests as •Contribution of each and patience, to wait until finding •Contribution of each and patience, to wait until finding every team member needs to the root cause every team member needs to the root cause be respected •The courage to speak truths, be respected •The courage to speak truths, •I am important and so are pleasant or unpleasant, •I am important and so are Feedback pleasant or unpleasant, you, without which the team fosters communication and you, without which the team fosters communication and cannot survive and ultimately trust cannot survive and ultimately trust the project !!! the project !!! Courage Respect 32 Le pied de page 17 mai 2006
  • 33. Lean Principles 1. Specify what creates value from the customers perspective 2. ! Identify all steps across the whole value stream 3. ! Make those actions that create value flow 4. ! Only make what is pulled by the customer just-in-time 5. ! Strive for perfection by continually removing successive layers of waste 33 Le pied de page 17 mai 2006
  • 34. Thank you www.valtech.com 34 Le pied de page 17 mai 2006