You have a pretty good idea of what you need. Some documentation was created a while back and one of your developers already has a prototype running. However, details have not been worked out yet and it's not clear how the project's success will be evaluated.

Let's work together and build a Live SpecBook: a single and up-to-date source of business requirements that corresponds to your strategic goals and will guide development efforts. Your SpecBook will help you prioritize work, will serve as a reference for QA engineers and will be immensely helpful when in support mode.

We'll help you gather requirements, design comps, technical documentation and estimates so you can prioritize the work and get the implementation started.

Four Steps

  • The Requirement Builder
  • The Experience Validator
  • The Technical Overview
  • The Complexity ScoreCard™

Those deliverables will support the subsequent development efforts. Our experience has been that this is one of the most valuable phases in the project lifecycle, as it ensures that your wants and needs are adequately captured and planned in a way that results in successful delivery of the end-product.


1. Define strategic goals and success metrics
2. Identify personas
3. Develop User Stories
4. Assemble initial design, functional and technical requirements. 


Once we have clarified the high-level scope of work, we will want to validate the personas' experience as well as get all the project stakeholders on the same page. This phase will end with adjustments to the initial series of specifications previously developed.

To this end we help you:

  • Develop dynamic wireframes

    They let us simulate browsing and provide a much better feel for the overall experience. 

  • Develop a Site Map

    This document helps understand how the information will be organized on the site.

  • Review design comps

    We will go over the artistic design comps to make sure they match the specifications and will be smoothly translated into code. 

By the end of this phase, all involved in the project will have agreed on the proposed user journeys, user interface (UI), site map and requirements.


In this phase, we will help you document the proposed technical approach. Depending on the project, it can take the form of:

  • Architecture document
  • UML diagrams
  • Models
  • Workflow diagrams
  • Any other visual representation

This Technical Overview deliverables are a key reference for developers and QA engineers working on the project.


In this final Requirement Development phase, we help you plan and prioritize the work by developing time and budget estimates.

We start by rating the complexity of each requirement against the following criteria:

  • Difficulty of the work
  • Anticipated effort for completing the work
  • Factor of uncertainty associated with the work

Complexity estimates, expressed in points, are gathered in a Complexity ScoreCard™ spreadsheet where they are translated into effort and time estimates. This Complexity ScoreCard™ gives you the information you need to prioritize features and make investment decisions.

Thanks for filling out the form! A Six Feet Up representative will be in contact with you soon.

Connect with us