Why the "A" in A-Game Stands for Agile
-
Upload
information-services-group-isg -
Category
Technology
-
view
363 -
download
2
Transcript of Why the "A" in A-Game Stands for Agile
© 2016 Information Services Group, Inc. All Rights Reserved.
Chuck Walker and Bill Shoemaker
Why the “A” in A-Game Stands for Agile
© 2016 Information Services Group, Inc. All Rights Reserved 22
Service providers are seeing: 30% growth in projects completed with a
distributed agile delivery model
75% of their development projects are now completed in a distributed agile model
© 2016 Information Services Group, Inc. All Rights Reserved 33
Agile Adoption Challenges
Organization
Pricing & Contracting
Governance
© 2016 Information Services Group, Inc. All Rights Reserved 44
Big challenges remain in agile adoption.
How to integrate: 1. The best attributes of a
geographically distributed delivery model
2. Agile development methods
3. A robust contract that fosters collaboration, feedback, quality and frequent delivery.
© 2016 Information Services Group, Inc. All Rights Reserved 55
Delivery Team Structure
Agile Organization
© 2016 Information Services Group, Inc. All Rights Reserved 66
Agile Development Pods
Pods are small, dedicated teams responsible for completing stories, new features and functionalities.
They consist of: • An embedded scrum
master• Proxy product owner(s)• A development team • Quality assurance team.
© 2016 Information Services Group, Inc. All Rights Reserved 77
Small Agile Development Pods
Shared ProxyProduct Owner
Scrum Master& Developer
Developer Developer Tester Tester
© 2016 Information Services Group, Inc. All Rights Reserved 88
Medium Agile Development Pods
Shared ProxyProduct Owner
Scrum Master Developer DeveloperOffshore Scrum& Developer
Developer
Developer Tester Tester Tester
© 2016 Information Services Group, Inc. All Rights Reserved 99
Large Agile Development Pods
Proxy ProductOwner
Scrum Master
DeveloperOffshore Scrum & Developer
Developer Developer
TesterDeveloper or Tester
TesterTester
Offshore Scrum & Developer
Developer Developer Developer
Developer or Tester
Tester Tester
© 2016 Information Services Group, Inc. All Rights Reserved 1111
Governance, the Agile Challenge
Cost
QualityDelivery
© 2016 Information Services Group, Inc. All Rights Reserved 1212
Agile Governance Best Practices
1. Adopt pragmatic governance2. Promote self-organizing teams3. Build a business-driven project
pipeline4. Ensure continuous improvement
© 2016 Information Services Group, Inc. All Rights Reserved 1414
Pricing Agile Development
Scope
Schedule Budget
Traditional
Schedule Budget
Scope
Agile
Versatile
Fixed
© 2016 Information Services Group, Inc. All Rights Reserved 1515
Pod-Based PricingPOD Type Throughput Onsite Offshore Integrate
d
Small 20-25 Story Point/Month $$ $ $ ½
Medium 30-40 Story Points/Month $$$ $ ½ $$
Large 60-80 Story Point per Month $$$$ $$ $$$
© 2016 Information Services Group, Inc. All Rights Reserved 1717
Contracting Agile Development
Fix duration and cost. Estimate scope. Focus on collaboration,
feedback and quality.
© 2016 Information Services Group, Inc. All Rights Reserved 1818
Agile Delivery Cycle and Acceptance
Base acceptance on: 1. Conformance to a prior agreed-on acceptance-test set
—or in the case of a scrum—the “definition of done.” 2. The “definition of done” as defined by users of the new
system.
© 2016 Information Services Group, Inc. All Rights Reserved 1919
Agile Service LevelsMetric Parameter Measurement MethodologyRatio of successful sprints
Degree to which the team is able to meet their commitment.
Measured as the ratio of successful sprints as a percentage by dividing the number of successful sprints by the total number of sprints.
Reliability The ability of teams to meet the story points they committed to for a sprint.
Measured as a percentage by dividing the amount of committed story points by the amount of earned story points.
Velocity The velocity is a relative measure of the amount of work delivered during a sprint.
Measure the velocity in story points.
© 2016 Information Services Group, Inc. All Rights Reserved 2121
Best Practices1. Establish product owners and proxy product owners for each Pod2. Establish onshore and offshore scrum masters; make agile
coaches available in offshore locations3. Create strong governance to monitor, report and manage
processes and stakeholder impacts.4. Deploy automated environments and agile collaboration tools
like Jira, Confluence and Rally; deploy continuous integration tools like Maven, Jenkins, Chef and Perforce.
5. Construct teams of 10 or less; and ensure at least two working hours of time zone overlap between onshore and offshore locations.
6. Virtualize the application test environments and test data management.
© 2016 Information Services Group, Inc. All Rights Reserved 2222
And finally…the biggest agile success factor
A culture of openness and transparency on the team and organization level.
www.isg-one.com
imagine your future™let’s connect…