Not reinventing the wheel again mahesh vardharajan

412 views

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
412
On SlideShare
0
From Embeds
0
Number of Embeds
40
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Not reinventing the wheel again mahesh vardharajan

  1. 1. Not Re-Inventing The Wheel Again:Agile Developers Create Their Own Identity Mahesh Varadharajan Agile Evangelist, Ericsson R&D Chennai
  2. 2. Introduction – About MyselfMahesh Varadharajan•25 years old•Certified Scrum Master – Scrum Alliance•Current Role at Ericsson: • Agile Evangelist @ R&D Chennai•Scrum Practitioner: 2 years•Total Industry Experience: 4.4 years•Association with Ericsson: Since January 2009 www.agiletour.org
  3. 3. Summary• Values, Practices & Principles: Relationship• Individuals & Interactions  Extrinsic & Intrinsic Motivation  Self Organization Practices  Geographical & Psychological Distances  Team Leadership Model  SHU-HA-RI Pattern in Team members• Software Craftsmanship  Agile Craftsperson Create their own identity• Finding your own identity www.agiletour.org
  4. 4. Values, Practices and Principles: Relationship•Values bring purpose to Practices, Practices are evidence of Values, Practices bringaccountability to Values.•Bridging the gap between Values and Practices are Principles. Principles are contextspecific guidelines. E.g. • Practice -> Pair Programming • Values -> “communication” and “feedback” • Principle -> driver-navigator principle – dual thinking hats of constructing and preventing from breaking www.agiletour.org Courtesy: Ajay Danait – Vice President – Agile Global Strategies
  5. 5. Manifesto for Agile Software Development
  6. 6. Principles Behind the Agile Manifesto Value - Individuals and Interactions• Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.• The best architectures, requirements, and designs emerge from self-organizing teams.• At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly (Retrospective)• Extrinsic & Intrinsic Motivation • My Survival Cycle Persona – Others define My identity • My Creative Cycle Persona – I define My identity• Tune the mind and conscience to be in the Creative Cycle (Intrinsic Motivation) www.agiletour.org
  7. 7. How can we bring Self-Organization in Agile Context? • Apprenticeship over Classroom Training – Tacit Knowledge • Collaboration over Document Handoff – For Knowledge Management • Argumentation over Passive Acceptance – For Logical conclusions • Constructive Conflict Mining over Artificial Harmony • Aggregating Team Intelligence over Intelligence of Individuals • Psychological distance solvent over Geographical distance solvent
  8. 8. Geographical Distance Solvent Distributed Teams
  9. 9. Psychological Distance Solvent
  10. 10. Problem - Team Dysfunction Model Patrick Lencioni
  11. 11. Solution - Team Leadership ModelTeam Leadership is a condition of a team Reduction of uncertainty Comes from clear messages Leads to focused actions that cannot easily be misinterpreted Developing channels for continuous feedback Uniform effort balance - Sustainable pace Having a very high fun factor
  12. 12. Shu-Ha-Ri Pattern In Team MembersFollowers– Initial guidance needed to come up to speed– Show progress after some hand holding– Need to be mentored to grow into volunteersVolunteers– Self inspired– Take technology and process initiatives– Come up with ideas that build the team– Implement innovative concepts– Lift the teamMentor– Servant Leader & Authority used to serve the needs of others– Genuine compassion for his people & knows the problems as a whole– Finds the solution to the problem– Has the skill to carry out the solution– Develop the next generation of leaders
  13. 13. Manifesto for Software Craftsmanship www.agiletour.org 14
  14. 14. Developer to Craftsperson What is Software Craftsmanship?Software Craftsmanship is about  Taking responsibility  Taking pride in work  “Signing” your work  Being a continuous learner  Practicing deliberately  Writing code  Having the right attitude  Contributing to the community www.agiletour.org 15
  15. 15. Developer to CraftspersonHow developers acquire skills through formal instruction and practicing? Dreyfus Model of Skills Acquisition  Novice  Needs to be told exactly what to do. No context to work from.  Advanced Beginner  Has more context, but needs rigid guidelines  Competent  Questions reasoning behind the tasks and can see consequences  Proficient  Still relies on rules, but can separate what’s important  Expert  Works mainly on intuition, except when problems occur  Innovation  Practical Wisdom www.agiletour.org 16
  16. 16. Metamorphosis of an Agile DeveloperThe Agile Transformation: To Follow Agile -> To Be Agile www.agiletour.org 17
  17. 17. THANK YOU www.agiletour.org

×