A Typical Project Process

We use a highly flexible, iterative development process based on a flavor of agile development called Scrum.

What does that mean for you? It means that we create reliable, high quality apps with flexibility for changes while building working products earlier than typical.

Quick Basic Explanation

  1. You have an idea, vision, product, process you need to build (needs)
  2. We discuss and review your needs with you and your staff to develop a 60,000 foot view and solution
  3. Repata provides ballpark estimates on timelines and costs
  4. We continue to create a complete Feature List that includes all potential features
  5. Based on business value and/or ROI, we force rank / prioritize the list
  6. Now we carve up each feature into tasks that are at most 2-3 days worth of work
  7. Create a sprint log (or mini project), based on the backlog above, that is 2-4 weeks long and results in a production worthy product
  8. Repata does the work and demonstrates to you
  9. Repeat steps 5-8 until desired product is done.

Now for an explanation with a little more depth…

Step 1 – Vision

You present your vision, ideas, objectives or needs to us and we’ll help you fine tune them as well as provide a 60,000 foot level assessment of how to implement and how we may be able to help.

This step could be only a few hours of conversations and emails or a few days of discussions and interviews. It is meant to be a short timeline to discover high level solutions, ballpark costs, project timelines, and the high level feature list.

Step 2 – Design

Brainstorm and document all potential features / requirements and needs to generate a Feature List also known as the product backlog. We continue to work with you to prioritize each item usually based on either ROI or business value.

Now that we have a prioritized feature list, we can break these down into tasks (usually a task is a unit of work less than 3 days). And from these tasks we can create a sprint backlog. This is essentially a list of tasks that fit into a small timeline or mini project, between 2-4 weeks.

So we have flushed out your ideas and objectives, and now it is time to figure out exactly what to build by documenting requirements, use cases and even creating wireframes / mockups to get a concise picture of what you want and what we’re building.

Step 3 – Build

We have our sprint backlog, so now we build it. Each developer has either quality assurance or other developer as their counterpart and acts as there QA person. This allows each task completed to be quickly tested and approved by a different person, thus increasing reliability and quality. Bottom line is less bugs and happier clients.

Step 4 – Release / Review

Once all the tasks are completed and tested, we have a working product. It may not be final or feature complete yet, but it should work well and be production worthy. We will demonstrate the new functionality with you. Once approved, we start the process all over again. 1) Review the product backlog and make changes if necessary either based off the demo we just gave you or business changes that happened along the way. 2) Create a Sprint Backlog (mini project), 3) Build It, 4)

We do all this until we have a releasable product but continue the process until we meet all objectives.