The document outlines the De Agile model, a tailored agile approach for distributed teams. It discusses challenges of distributed teams like time zone differences and availability. It proposes tools like collaboration software, video conferencing, and frequent travel to overcome these challenges. The model includes initial on-site training, graded task allocation, and additional roles like an SPOC. Metrics will measure productivity, quality and trends. Additional activities like documentation and reviews are planned. While time consuming initially, the model aims to stabilize delivery in 3 months and has succeeded in multiple projects, though it may not be very cost effective. Willingness to make it work and additional effort are important for its success.

1. The De Agile Model
(Tailored for Offshore)
Chakra M. Venkataramana
Director
SPAN Infotech

2. Distributed Agile
• Context is Testing and Development teams
being distributed geographically
• Multiple Test requirements including
–
–
–
–
–
Regression
System
Compatibility
Automation
Technical Testing – Perf, Security and Compliances
• Can be applied to distributed Dev teams too
– with minor tweaks
2

3. Against De-Agile
Time zone differences
Conflicting work hours, Personal Sacrifices in terms of time management
Availability – F2F Meetings, Information sharing, planning, daily-standups, retrospectives
Parallel work – Peer coding/testing, immediate requirements
Work allocation and Scheduling, Effort deviations
Staffing and Shared Understanding
Self motivating and Self Organizing resources
Misunderstanding requirements
Delay or reluctance for clarifications / time consuming
Trust and Communication
Capabilities – Technical, Domain, Standards, Personal
Cultural and Language barriers
Unseen speaker
Two way communication
3

4. Need for Distributed Teams
Programming
Paired Resources
Streamlined processes – Comm & Collaboration, Source Control, Automation, CI
Follow the Sun Model for faster deployment
Capabilities
All rounder resources are rare
Domain, Tech, Design, Dev, Test, Tech-Test
Vendor Org support to offshored resources – draw up on support structures
Innovation and Value Adds
Cost
Globally distributed teams reduce cost, Contract Employees as needed – required
competency at a short notice
Offshore resources at lower cost
Implicit additional hours - reasonable
4

5. When would De-Agile Work?
Cost Advantages
Pros outweigh Cons
Capability
Specific Technology Requirements (expensive or not available)
Available at short notice
Staff on demand / reduce when needed
Willing to accept that there are challenges
Us vs Them
Working FOR and not AGAINST Them
Acceptance
5

6. Tools and Techniques that enable De-Agile
• Dedicated Meetings rooms / Conf bridges
• Collaboration Tools – TFS (requirements repositories, SCM,
management, Automatic build and deployment setup, Continuous Testing,
Automated defect tracking, and project management tools
)
• Communication - IM, Skype, IP Phones, Video
Conference and Web Cams
• Daily Standups on Skype boards
• Frequent (not too frequent) travel and work from
other locations
• Classification of tasks Simple to complex
• Overlap and Hand-shake
- grow with time
6

7. Diagrammatic Model
• Project Initiation / Initiation of resource
into the project
Travel – Either Direction
(4-6 weeks), every six months, Intro to
stakeholders including POs, most
affected people
Training – Domain, Standards,
Technology, Architecture and Design
Overview, SCM, Process inclusion
Task Allocation –
Onsite execution under supervision,
Graded tasks (complexity), Constant
reviews initially, offsite tasks – graded
tasks
7

8. Offsite Delivery – Testing Specific
Roles (Additional?)
SME Review
PO
Scrum
Master
SPOC
SC Manager
Reviewer Temporary
Stakeholder
IM, Skype, Phone
WEBEX/GotoMtg
Video Conference
TFS
TFS
Client
Collab
oration
tools
Activities (Additional?)
Measure Metrics
Statistical
Trends
Productivity
and Quality
Tool based Review
Feedback
Continuous
Improvement
Documentation
8

9. Planned Additional Activities
•
•
•
•
•
•
Sprint and Retrospective (Video or In Person)
Sprint Grooming
SPOC Discussions
Work in Progress testing
Automate for CI & CT
Metrics – Online Dashboards, Burndown and Burndown
charts, Velocity, Defect Trend, Requirement Stability,
Productivity, Quality
• Frequent planned Demos
• Reviews
9

10. Will all this work?
• We have multiple projects which have
inherited processes from this model to
succeed
• There needs to be strong incentive for this
to work
• It is time and effort consuming but will
stabilize in time (3 months)
• May not be very cost effective as it will not
be a pyramid model of delivery
10

11. Implications of De-Agile
• Willingness to make it work is important
• Additional effort from the Agile team to
manage distributed deliveries – atleast initially
• Slow onboarding – takes time to deliver
• Additional processes and metrics
• Additional documentation – adequacy can be set
• Dependence on Collaboration tools
• Additional Travel costs
11

12. Q&A
12