Methodology
Commandtext employs rapid software development techniques in client solution engagements. These techniques are adaptations of the classic software life cycle, permitting solutions to be deployed rapidly and cheaply but without sacrificing the level of rigor required to meet the client's underlying business objectives.
Our preferred strategy is to separate engagements into a series of small, discreet, rapidly-deployed project cycles. We start small, gain user acceptance early on, and then continue iteratively to add layers of complexity to the deployment. Through a series of quick wins, we provide real value and deliverables well before the projected end of the engagement.
Each project cycle has four distinct phases:
- Definition
- Design
- Development
- Deployment
Each phase has one or more milestone events or deliverables from which work in later phases is derived. For example, a Requirements Document is drafted to define the goals and boundaries of the project cycle. For the majority of engagements, both time and cost cannot be determined until a Project Plan is derived from the Requirements Document. The Design Document is derived from the Requirements Document and serves as a common framework to communicate expectations of the client, end user, developer, and QA staff. The solution can then be Developed and Deployed — that is, delivered, integrated, installed, and tested to the client's satisfaction.
