At2011 7 habits_of_highly_effective_agilists
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

At2011 7 habits_of_highly_effective_agilists

on

  • 650 views

 

Statistics

Views

Total Views
650
Views on SlideShare
525
Embed Views
125

Actions

Likes
0
Downloads
8
Comments
0

2 Embeds 125

http://www.isec.co 113
http://isec.co 12

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • 11/05/10 www.agiletour.org

At2011 7 habits_of_highly_effective_agilists Presentation Transcript

  • 1. 7 habits of highly effective agilists Amoli Upadhye (Tata Consultancy Services)
  • 2. Index
    • Why ‘habits’ ?
    • Which habits do effective agile teams embrace ?
    • What induces agilists to practice them ?
  • 3. Why habits ?
    • Motivation gets you started, habits keep you going
      • Grant a strong sense of mission
      • Fill you with commitment
      • Are, generally, the missing ingredient in most teams trying to emulate successful teams
    Image source - http://collegethrive.com/creating-good-habits-in-college
  • 4. Which habits do successful agilists embrace ? Sharpen your saw Be Proactive Begin with the end in mind Put first things first Average agilists Effective agilists Think Win/Win Seek first to understand.. Synergize
  • 5. Habit 1 – Be Proactive
      • Ability to assess a situation and develop a positive response to it
      • Effective agilists work on their response to conditions, instead of worrying about conditions
      • Self – organize, sprint 0
    Image source - http://www.123rf.com 1 2 3 4 5 6 7
  • 6. Habit 2 – Begin with the end in mind
      • Continuous attention to technical excellence and good design enhance agility
        • Go beyond short term goals
        • Rally teams around a shared purpose
      • Story – Gutting of Chrysler’s culture
    Image source - http://www.123rf.com 1 2 3 4 5 6 7
  • 7. Habit 3 – Put first things first
    • Organize and execute around priorities
    Image source - http://www.123rf.com Important Less Important Urgent Less Urgent 1
    • Sprint reviews
    • Sprint planning meetings
    2 3 4
    • Sprint retrospectives
    • Break functional stories
    • Relationship building among team and other stakeholders
    • Raise deployment tickets
    • Creating review decks
    • Unproductive documentation
    • Non – prioritized stories
    1 2 3 4 5 6 7
  • 8. Habit 4 – Think Win/Win
    • Bring out the best in each player
    Option 2: Continue as is and miss the target date Option 1: Increase velocity to meet target date Actual 1 2 3 4 5 6 7 Option 3: Reduce scope to meet target date Start date Target date Time Planned Amount of pending work for release
  • 9. Habit 5 – Seek first to understand..
      • Listen to understand, do not listen to just reply
      • Analysis stories, technical stories, spikes
      • Consider using tools like analysis matrix
    ..And then be understood Image source - http://www.123rf.com 1 2 3 4 5 6 7
  • 10. Habit 6 – Synergize
    • True test and manifestation of all 6 habits put together
    • Less of me and more of ‘We’
    1 2 3 4 5 6 7
  • 11. Habit 7 – Sharpen your saw
    • At regular intervals, team reflect, on how to become more effective, then tunes and adjusts its behavior accordingly
    Image source - http://www.123rf.com 1 2 3 4 5 6 7
  • 12. Habit 7 – Sharpen your saw (contd.) 1 2 3 4 5 6 7
  • 13. What induces agilists to practice 7 habits ? http://www.wow-tcs-maitree.org/
  • 14. Thank You www.agiletour.org
  • 15. Solutions for changing existing behavior of new user sign – up form Pros Estimated Effort Level Cons
      • Less complex changes
    POC Required Medium Have users obtain admin approval in system and ---
      • Business prefers this approach
      • Testing may involve simpler scenarios
    Very large Send an automated email to admin and allow users to sign – up anyways ---- Same as #2. Plus, introduce a validation to check for user’s employee id, joining date, etc. ----
      • Very complex code changes
      • System performance may degrade
      • Absence of data for old employees may rip up/downstream systems
      • Business does not support this approach
      • Testing would involve more complex scenarios
     Large 
      • Less complex changes
      • ABC field consistency ensured
      • Business does not support this approach
      • Invalid users may still not be weeded out
      • Testing would involve more complex scenarios