Based on an agile approach the Redgum Blueprint process is designed to bridge the gap between developers and business, the goal being to get agreement from both sides before development starts. Described in terms users and business people can understand and make decisions on the Blueprint provides everything a developer needs to know in order to deliver to the businesses needs. In order to minimise wasted spending the Blueprint works in successive qualifying stages so your commitment and exposure at any one point is minimised.

Contact us for a free 1 hour workshop designed to give you a clear understanding of your options where we go through    Your specific ideas and requirements The process we use to develop software Get a feel for the cost of your project How you can qualify if it is worth it and build a case for your business.

Benefits

Lower risk. A business has a very clear picture of what they will be receiving before it commits to the expensive part of the development.

Contained spending. Each successive stage of the process is a go/no go point so you are only commiting to a small spend at a time

Managed expectations on all sides. Once the roadmap is defined at the end of the Blueprinting phase the ongoing management and change process is visible to all.

Prototyping

First stage of the process is to work through the key concepts, normally these are a few key screens around 5% of the overall system. Doing this clears up a lot of issues and helps prevent wasted effort further down stream. 

Goals	Benefits
Get an early picture between everyone Agree on key system components.	Qualify concepts before spending too much in development Put in front of a test audience to gain feedback. Test concepts with the marketplace early No need to build 95% of the system

Scope

Scoping document is a very quick, set of check list items that very rough costs and priorities can be drawn from.

Goals	Benefits
List out all expected elements to be designed Business and developers agree	Both sides aware of goals Understanding “discovery” Design process Everyone on the same page Decisions can be made to manage costs Priorities can be set Early identification of

User Interface Design

Goals	Benefits
Detail the user experience Business and developers agree	No surprises No missing elements Everyone on the same page Decisions can be made to manage costs Priorities can be set Identify additional prototyping required

Technical Design

The technical design happens in parallel to the User Interface, once agreement on the User Interface has been reached, the technical design will describe how each of the elements in the user interface will be implemented.
For standard systems this is quite a fast process, for highly complex systems clearing up a game plan early makes for a much smoother process during development.  

Goals	Benefits
Ensure UI Requirements are backed up technically.	Ensures the entire system fits together properly Provides a base line for testing and quality assurance Developers reference minimising “interpretation”

Quality Plan

Every system in every business has unique requirements.
Every system of any size has an almost infinite scope that could be tested.

The quality plan works through what is important to the project and to the business and how much

What are you building?			What does quality mean?
Computer Game Nuclear power plant Business process Compliance reporting Customer portal Internal processing engine			Fast Stable Easy to learn Quick to use Responsive Accurate

As an example

A twitter user VS surgeon using a tool during an operation. Twitter can fail early and the user is happy because its responsive.The medical tool can't fail but may not need to look as pretty or deal with 1 million tweets a second.

Frequency of use. If it gets used 10 times a minute then you would want it to be responsive, but a single failure may mean the user would just try it again.
Impact of failure. If a report is generated which is required for government or legal reporting then you might focus on its quality aspects over a weekly progress update. 

Goals	Benefits
Identify the focus of QA effort Agree on a suitable level of quality	Focusing limited resources on critical areas of the system. Gives all parties confidence in the system Validates the design effort before development effort is wasted.

Road map

A plan only lasts until the first contact with the enemy. So you need to continually adjust and work on the plan.
From the previous stages we will have

Very clear set of items to develop

Understanding of the QA effort involved

A clear set of dependencies

A set of tools the business can use to prioritize its development order

Using this we can then setup a plan for development which is broken down into roughly 2 week deliverable points. At these points the business can reassess and reorganise (within reason) to keep them adapting to the changing business environment and also to the understanding about the product..

Goals	Benefits
To decide what order to build in See the long term objectives	Everyone knows and can plan around delivery. Priorities can change along the way Impacts of changes can be managed Strategic early delivery can pay for future development Flexibility to substitute and reorder sprints

Find out more

Contact us for a free 1 hour workshop designed to give you a clear understanding of your options where we go through   

Your specific ideas and requirements

The process we use to develop software

Get a feel for the cost of your project

How you can qualify if it is worth it and build a case for your business.