There is no better way to ensure we're on the same page as our clients than working together closely.
Our process is streamlined for efficiency and the creation of successful projects. Each project needs its own mix of services so there is no one-size-fits-all approach, but we always remain agile and follow the smaller teams of smarter people approach.
After coming in and meeting with us, a typical engagement may follow this type of process:
2 weeks of product definition
Before a line of code is written ideas need to be molded into products that can flourish in the marketplace. The management and senior talent at CitrusByte have dozens of combined years in strategy experience for large companies and start-ups alike. We know what goes into a successful application, and a successful company.
We like to ensure our clients are creating applications that have a higher chance of success.
6-weeks of development
Using two development sprints of 3 weeks each, we'll rock out Version 1.0 of your website that will help you evaluate your initial business concept and give you a solid application base to continue expansion upon. This really works: for RipeTV.com we launched three applications for them that needed to serve hundreds of thousands of uniques the day it went live.
Agile is Adaptive Engagement.
We use an Agile methodology called SCRUM. We focus on creating a useable product that grows over time by using Rapid, Iterative Development practices.
Agile is a process of working together closely
In SCRUM we work in-person with our clients on project planning, brainstorming, product definition, scope, timelines and even cost. By being transparent about our estimates and costs we can work together to create a project plan that works within your business constraints (time, cost, features, etc.).
Agile allows for flexibility and response to market changes.
Things move so quickly on the web and so should you. We generally do releases in 3 week cycles or faster.
Estimating how long something will take to develop in software is difficult.
Software estimation is notoriously unpredictable and compounded by the speed at which the marketplace changes. Features a site may need now will need to be modified in a few weeks or months, so accounting for those changes is difficult. In SCRUM we focus on what we'll be delivering in the next 3 week cycle, reducing the complexity of the estimation greatly. We've found we typically undershoot our estimations*
Software evolves rapidly while it's being built.
Applications need to change and adapt as feedback comes in and company priorities change. At the end of each sprint the client works with the team to decide what will be done during the next sprint. By building incrementally and planning small pieces at a time the product can change as its being built.
We have custom tools that allow SCRUM to be even more efficient
We built a custom tool with a working name, "Hprium". As a client you'll be able to track your backlog in our online tool as well as team members hours, tasks and burndowns.
