Our Process

We believe successful projects use a process that encourages regular and active communication between us and our clients.

 We create solutions in close partnership with our clients applying Agile principles with Scrum process to ensure our solution is on target and on budget.

Our projects follow, at a high level, the following pattern.

  1. Initiation - discovery of requirements & project kickoff
  2. Planning - create user stories, prioritize stories & create a release plan
  3. Implementation - graphic design, iterative application development typically in two week time boxes, testing & integration
  4. Close-Out - training, site launch & warranty period

 

Each step of the project involves the creation of a product for which we ask for your sign-off before we move forward. We will work with you to agree on an appropriate length of time for any sign-off period. This is a critical point in the process because any delay in this sign off period means we might not be able to deliver to you what is stated in the schedule. This process ensures that we only move ahead upon successful completion of the current project phase and goals for the next phase are clear.

We perform most of our work during the Implement step of a project. During this step, we employ Agile project methodology and Scrum process. We have found that, particularly for technical projects with a diverse set of stakeholders, Scrum is well-suited allowing us to be responsive to a dynamic environment where priorities and deliverables may change. Scrum helps us stay continually focused on the most valuable work at all times with usable product being released at the end of each iteration.

agilebuddy-open source.jpgThroughout your project we manage the Scrum process using a best-of-breed web tool called AgileBuddy. We are big fans of this easy-to-use service and strongly recommend it to anyone interested in managing their Scrum projects with no more and no less than what the project requires.

For a great eight minute overview of the Scrum process, see this video:

 

 

Document Actions
Personal tools