agile 2.0 - our road to mastery
Post on 17-Oct-2014
1.807 views
DESCRIPTION
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'TRANSCRIPT
1 |
Agile 2.0 - Our Road to MasteryAn Experience Report
July 17th & 18th, 2010
Agile NCR, Gurgaon
2 |
All views to be expressed here are mine, and do not reflect All views to be expressed here are mine, and do not reflect my employer's views in any way..my employer's views in any way..
Biju BhaskarEmail: [email protected] : www.bijubhaskar.net
3 |
Quick overview of our agile journey till mid-2009
The Road to Mastery
AgendaAgenda
Agile 2.0 initiative
Lessons learned from it
4 |
We’ve been doing Scrum for a long time..We’ve been doing Scrum for a long time..
5 |
We are good at it…We are good at it…
6 |
But as always, there was scope for But as always, there was scope for improvementimprovement
As Jim Collins says, “Good is the enemy of great!”
We had good teams, but not great teams..
7 |
Here’s what our organization looked like at the middle of 2009:
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
The Landscape when this story begins..The Landscape when this story begins..
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”?So what is next in our “Road to Mastery”?
9 |
Rhythm
New technologies
Sprint Length
FeedbackMore Value Team
Structure
PrioritizationRelease
length
Staffing
Support
Meetings
Engineering practices
Transparency Sponsors
Knowledge
Less Waste
Team Interactions
and lot more…
What can we improve?
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…Pick the highest priorities…
Better manage our stakeholder expectations
Increase productivity of teams
Reduce waste in our projects
Improve project staffing
11 |
But first, get the right people on the bus… 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 |
Where do we go; what is our BHAG?Where do we go; what is our BHAG?
The “Big Hairy Audacious Goal”
13 |
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 leverageeach 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
• Function like a start-up• Each workstream has a CEO
Guiding Principles
The four workstreams and their goals…The four workstreams and their goals…
14 |
Sitting Together
Co-locating the group/teams:▪ Everyone in the group sits on
the same floor▪ Sitting is ‘Team-based’ (every
team has a team room)
One - One Challenge
Reduce waste campaign:▪ Every team is now following
one week sprints▪ Teams have reduce their sprint
reviews to 30 minutes ▪ Teams are beginning to
following one month releases▪ Teams deploy to production
more frequently
App Dev Staffing
Staffing Model: ▪ The staffing model has been
revised to facilitate timely staffing
▪ No dedicated Scrum Master assigned to team
▪ Product Owner assigned full time to one team
Organizational Rhythm
Consistent and Rhythm:▪ Creating a steady
AppDev beat▪ Every team is using a
common tool for their project management
▪ Every team in a portfolio have their sprint review on the same day
What they have achieved so far…What they have achieved so far…
15 |
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
Our key takeaways were:
We learned a lot…We learned a lot…
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 |
Our journey towards mastery continues…Our journey towards mastery continues…
Email: [email protected]