A process that means business.
Our process draws heavily on the strengths of Agile development, a methodology that focuses on delivering working software on time. We combine that with our inherited focus on client service, developed while part of a highly regarded consulting company, and decades of practical experience delivering and supporting successful enterprise software applications.
1. Common Understanding
Red Arrow works with you to develop a clear, shared vision of the product across all the users of the product and ensure that this vision captures the value the product can offer.
Activities include:
- Establish any technical constraints
- Define users of the application and stakeholders in the success of the project
- Collect user stories that articulate all features and functions of the application
2. Commitment:
Keeping in mind the shared vision, Red Arrow works with you to define and prioritize the features and functions that are required to make the product as useful as possible. At this point, Red Arrow divides the product into functional modules which we will develop separately and sequentially in what we call iterations or sprints.
Activities include:
- Client prioritization of user stories
- Estimate all user stories
- Organization of user stories into releases
3. Clarity:
Armed with the plan, Red Arrow works with users to meticulously detail the first iteration (module) of the product to prepare for the first sprint. The list of what needs to be done before the iteration is complete is called a backlog.
Activities include:
- Detailed requirements of each user story in the first release
4. Create:
A particular module is architected, designed, broken down into development tasks and handed to the development team. Meanwhile, user tests are scripted to ensure that functionality works the way it was intended to work.
Activities include:
- Architecting, designing and developing code
- Quality assurance testing
5. Communicate:
During each iteration, we demonstrate the application to the client and invite feedback. This encourages consistent, regular interaction and ensures that the application is on-track. The feedback becomes part of the backlog.
Activities include:
- Review work with the client
- Record feedback to the backlog
6. Continue:
Based on feedback, we prioritize the work required for the next iteration.
Activities include:
- Complete multiple iterations in each release
7. Complete:
Once all the items in the backlog have been completed, we release the code to the client.
Activities include:
- Deliver release to client