Agile 2.0 - Our Road to Mastery

1,597 views

Published on

AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'

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

No Downloads
Views
Total views
1,597
On SlideShare
0
From Embeds
0
Number of Embeds
13
Actions
Shares
0
Downloads
37
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • FIR-AAA123-20100218-
  • Agile 2.0 - Our Road to Mastery

    1. 1. Agile 2.0 - Our Road to Mastery An Experience Report July 17 th & 18 th , 2010 Agile NCR, Gurgaon
    2. 2. All views to be expressed here are mine, and do not reflect my employer's views in any way.. Biju Bhaskar Email: [email_address] Blog : www.bijubhaskar.net
    3. 3. Agenda Quick overview of our agile journey till mid-2009 The Road to Mastery Agile 2.0 initiative Lessons learned from it
    4. 4. We’ve been doing Scrum for a long time..
    5. 5. We are good at it…
    6. 6. But as always, there was scope for improvement As Jim Collins says, “Good is the enemy of great!” We had good teams, but not great teams..
    7. 7. Here’s what our organization looked like at the middle of 2009: The Landscape when this story begins.. More than 40 Active Development Projects Geographically Distributed Teams Several Outsourced Development Partners Many successful Scrum projects Overabundance of awareness of Agile and Scrum All projects followed Agile practices
    8. 8. We realized that our application development teams were ready to move to the next level in our Agile adoption So what is next in our “Road to Mastery”?
    9. 9. What can we improve? Rhythm New technologies Sprint Length Feedback More Value Team Structure Prioritization Release length Staffing Support Meetings Engineering practices Transparency Sponsors Knowledge Less Waste Team Interactions and lot more…
    10. 10. After inspecting our agile adoption, we found that focusing on four key areas could help us take our agile maturity to the next level Pick the highest priorities… Better manage our stakeholder expectations Increase productivity of teams Reduce waste in our projects Improve project staffing
    11. 11. But first, get the right people on the bus… The most passionate folks in each area Folks who have been already doing some of this well in their projects Representation from all locations
    12. 12. Where do we go; what is our BHAG? The “Big Hairy Audacious Goal”
    13. 13. The four workstreams and their goals… One - One Challenge Focus Area: Reducing waste Value proposition: Promote a continuous flow culture where project teams get frequent feedback, release often and reduce waste by improving team agility. Organizational Rhythm Focus Area: Better managing stakeholder expectations Value Proposition: Create an AppDev “heartbeat” to improve the way we work, communicate and leverage each other App Dev Staffing Focus Area: Improving Staffing Value Proposition : Enhance AppDev staffing model to facilitate timely staffing of skilled team members as per project needs, and with a focus on optimizing team performance Sitting Together Focus Area: Increasing productivity Value proposition : Create a startup like environment through increased collaboration and easy, osmotic communication <ul><li>Function like a start-up </li></ul><ul><li>Each workstream has a CEO </li></ul>Guiding Principles
    14. 14. What they have achieved so far… Sitting Together <ul><li>Co-locating the group/teams: </li></ul><ul><ul><li>Everyone in the group sits on the same floor </li></ul></ul><ul><ul><li>Sitting is ‘Team-based’ (every team has a team room) </li></ul></ul>One - One Challenge <ul><li>Reduce waste campaign: </li></ul><ul><ul><li>Every team is now following one week sprints </li></ul></ul><ul><ul><li>Teams have reduce their sprint reviews to 30 minutes </li></ul></ul><ul><ul><li>Teams are beginning to following one month releases </li></ul></ul><ul><ul><li>Teams deploy to production more frequently </li></ul></ul>App Dev Staffing <ul><li>Staffing Model: </li></ul><ul><ul><li>The staffing model has been revised to facilitate timely staffing </li></ul></ul><ul><ul><li>No dedicated Scrum Master assigned to team </li></ul></ul><ul><ul><li>Product Owner assigned full time to one team </li></ul></ul>Organizational Rhythm <ul><li>Consistent and Rhythm: </li></ul><ul><ul><li>Creating a steady AppDev beat </li></ul></ul><ul><ul><li>Every team is using a common tool for their project management </li></ul></ul><ul><ul><li>Every team in a portfolio have their sprint review on the same day </li></ul></ul>
    15. 15. Our key takeaways were: We learned a lot… Good is the enemy of Great! Changing behavior can take years and so can an Agile adoption The change process needs to run on human passion A small high-performance team will be needed to inspire and guide any change implementation The top of the organization must support—and be supported
    16. 16. Our journey towards mastery continues… Email: biju_bhaskar@gmail.com

    ×