Structured approach to start distributed agile project


Criteria for selection of Partner

  • Experience in running agile projects
  • Talk directly to teams executing agile projects
  • Talk to the clients that are executing agile projects with the partner

Agile Working Model

  • Involve agile coach(with distributed agile experience)
  • Take good practices from both onsite and offshore teams(code reviews, communication models,tools,….)
  • Discuss and agree the model with both teams

Recruitment of the Team

  • Recruitment should check the agile fitment
    • Skill fitment(refactoring,…..)
    • Strong concepts
    • Readiness to learn.
    • Some members in a team with domain knowledge.

Infrastructure in Place

  • Communication and collaboration tools(wikis, messaging, video conference,…)
  • Access speed to the existing  infrastructure(dev,test,…)
  • Development and Test
    • Continuous Integration(common for entire project)
    • Developer setup(tdd, static code analysis, code coverage,…)
    • Access to test infrastructure or setup of local test environments

Knowledge Transition Plan

  • Multiple models
    • Offshore team members can embed in current agile teams
    • Travel of existing projects members to offshore location on rotating basis
  • Prepare backlog items(less complex, with less dependencies, …) that the offshore team can pick up in initial sprints

Training the team

  • Technical skills – Refactoring, Test Driven Development, …
  • Specific technology/tools used in the project

Scaling the Teams

  • Start with 2-4 team and then grow after the current team stabilises

About aslamhirani

I am working from last 19+ years in areas of Product development, agile coaching, software R&D process consulting. I have been working in agile development model from last 10 years and coaching agile teams from last 6 years in areas of agile assessment, agile adoption, agile transformation, agile scaling, distributed agile development and agile competency development. I work with software R&D organizations to help them improve their effectiveness and efficiency with reuse, process improvement in development and testing, competency development, innovation in R&D, collaboration improvement across teams, automating devops and so on
This entry was posted in Uncategorized and tagged , , , . Bookmark the permalink.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s