Expert level consulting for your success.

Seeking outside help is very important for a business trying to grow or trying to change. Our expert management consultants take the time to understand your company specific needs and challenges to help you develop a strategy to achieve your organizational goals.

Distributed AGILE Development

Agile development in general requires stronger interaction between peers. While in-person interaction is the best method of interaction it may not be always possible or feasible in the current world.

In a Agile development environment, the team, regardless of the location it is members, is committed to a single list of goals for a sprint. This automatically sets the "control" and "focus" most teams lack.

There are numerous ways to implement this common list of tasks or goals that can be made available to a distributed team. Something as simple as a Google document, Sharepoint list or even a well managed excel document can be used to define the tasks for a team and have each team member refer to it for their next task.

Products like Version One, Jira, and Rally offer hosted solutions for project management and collaboration platforms which create visibility and tracking from company goals to individual developer productivity. These solutions can be easily accessed by anyone anywhere and can also integrate with development environments such as Visual Studio 2008, 2010 and Eclipse.

How AGILE Development Works

Agile development aims at bringing a product that the closer to expectation at the finish line.

Most projects start with a requirements definition phase where requirements are solidified. While this is a great practice to have a clear definition of what is to be developed, in the case of a new product, the innovation continues and the product owners' view of the application changes as the product starts to shape up.

Agile methodology offers a convenient process in which product manager can make changes to the originally documented requirement or specification easily thus building a product that is evolving as it is built.

This methodology also offers scope for high level of interaction between the the product owner and the developers and facilitates discussion, analysis and critique of the requirements and the developed product in a more constructive and cohesive manner contributing to a more successful roll out of the product.

  • Create requirements as user stories.
  • Organize user stories into sprints
  • Load sprints so teams are not over committed.
  • Allow to alter or enhance future requirements.
  • Capture changes as new user stories.
  • Donot change requirements during development.
  • Follow up with a change request in next iteration.