In the complimentary initial consultation, you will be able to chat and/or meet with our solutions analysts and architects to help us understand your needs better and to ensure that it makes sense for both of us to continue on this journey.
After the initial consultation, we’ll set up a two-part workshop where you can meet the team, and together we'll discuss and gain a detailed understanding of the project. Depending on the size or complexity of your project, this part of the journey will either be two half-days or two full-days.
The first half of the workshop focuses on learning about your needs and discovering what requirements will be involved. The second half of the workshop focuses on listing and prioritizing features and setting goals for your project.
We will then determine the level of effort based on your goals and help you choose one of two paths: Sprint or Hackathon. If one of these two approaches doesn’t suit your project needs, we’re also happy to customize a path for you.
A sprint is a two-week block of development. Each sprint has the goal of producing something tangible that you can review, test, or use.
We make it easy. There’s no long-term commitment. You can stop a project after any sprint.
We generally recommend a minimum of three sprints for new projects, depending on the complexity of the product:
A hackathon is a short, three-day block of development. Sometimes you just have an idea or project that you need implemented as quickly as possible. A hackathon allows you to build out your project as much as possible over a three-day period.
Generally, the best projects suited for hackathons are those that focus on the user experience or user interface. If it’s much larger than that, it’s probably more suitable to take the Development by Sprint path.
It isn’t uncommon to start a project with a hackathon and then follow it up with several sprints.