Twentyseven Global’s approach to software services is a modified Agile methodology that emphasizes an iterative build process, clear definition of requirements, and a continually maintained product backlog. We start with the definition and prioritization of key user stories which allows us to lay out the vision for the site at a high level. Work is organized into releases driven by business objectives. Releases are built incrementally in 1-4 week “sprints”. This allows all stakeholders to see work in progress and make adjustments throughout the software development process.
How We Do It
Twentyseven Global’s custom software engineering methodology encapsulates the best Agile development processes along with our best practices from decades of software development experience to emphasize an iterative build, clear definition of requirements, collaboration, and testing throughout. The process begins with an up-front definition period to elicit and capture user stories and requirements, as well as define the architectural approach. Following that, work is organized into releases and releases are then organized into 1-4 week sprints. All work is regression tested prior to hand off for final User Acceptance Test and production release.
Why We Do It
In most cases it is not practical to document all requirements up front, have the development team build to spec and come back months later with an application that doesn’t require a lot of changes. At Twentyseven Global we have gone away from this Waterfall approach in favor of Agile. This allows all stakeholders to see work in progress and make adjustments along the way. In the long run, this typically leads to less rework and lower costs.