Agile and Iterative
Gaea implements business solutions through the application of a company-wide, best-practice approach to software implementation. The hybrid software development approach applies the best practice from both Agile and waterfall methodologies. With this hybrid approach, Gaea and our clients jointly design, iteratively configure, test, and prepare a production environment with a client-specific user interface (UI). Our implementation is comprised of seven phases and two concurrent work streams. Business change management is accounted for from a technology, functional, and resource perspective.
Each iteration begins with a planning meeting. During the meeting, the product owner (person requesting the work, representing the business) and the development team agree upon the work to be accomplished during the iteration. The development team has the final say when it comes to determining how much work can realistically be accomplished during the iteration, and the product owner has the final say on what criteria needs to be met for the work to be approved and accepted.
The scrum master, or team facilitator, determines the iteration duration. Once the team reaches a consensus for how many days an iteration should last, all future iterations should remain the same. Traditionally, an iteration lasts 30 days. After an iteration begins, the product owner steps back and lets the team work. During the iteration, the team holds daily stand-up meetings to discuss progress and brainstorm solutions to challenges. The project owner (client) may attend these meetings as an observer, and can answer specific questions. The project owner may not make change requests during an iteration and only the scrum master has the ability to interrupt or stop the iteration. At the end of the iteration, the team presents its completed work to the project owner and the project owner uses the criteria established at the iteration planning meeting to either accept or reject the work.