Sprinting

We are big believers in Agile development principles. The emphasis on embracing change, feedback loops, high test coverage, duplication reduction, refactoring, reuse, etc. are cornerstones of our solution delivery approach. From a management perspective, we prefer the Scrum framework, which we have employed successfully over the years. We build software solutions iteratively and incrementally in 2 to 4 week chunks called sprints.

By focusing on potentially shippable “mini-releases” at the end of each sprint, we gain the ability to:

• Demonstrate progress to the client, obtain valuable feedback, adapt to refined requirements, and implement what the client really needs.
• Test the solution repeatedly against a growing set of acceptance tests, making the solution much more durable.
• Fine tune the deployment and release process into a well-understood, well-oiled process thus eliminating a risk before it is time for an actual release.
• Have a better handle on project timelines based on empirical data such as team velocity, outstanding backlog, informed sizing, etc.
• Improve team productivity using Scrum‘s principles of collaboration, open communication, and self-governance.