Blog

4 steps to create a perfect roadmap for your project

Management
by Don Lowe CEO
| 5 min read

Every successful project needs to be able to coordinate technology and business development. Without a proper plan, your project will waste resources and time. A good project plan is based on a roadmap that shows exactly how the choices we make today will affect our future.

Nothing planned, nothing gained

The long-term effect of not having a plan manifests itself in many ways. A common symptom is that you have started using quick fixes to speed up the project – only to find that it is actually taking longer. This leads to poor quality work. Work is assigned to keep developers busy because they are just waiting for others to complete their tasks. Jobs are no longer done in order. As a result, a team has to re-do functionality that probably won’t match. It is time-consuming and leads to delays and increased costs.

You also end up losing trust in each other. You are faced with endless frustration for the developers and the end customer. Without a road map, you cannot develop a meaningful breakdown of work, your project will waste people’s time, and resources and cost more to deliver.

What you need is a well-planned project roadmap that is simple to understand. It is a vital component of the project to succeed. A road map clearly shows what has been done and what is still outstanding. It helps reach an agreement about what the needs are and in identifying the most suitable solution to deliver on those needs.

Using the roadmap as a communication tool

With a roadmap, you can easily plan in when other parties need to be scheduled in for work. Most importantly, it is built on what our client-partners and their end-users will find useful because that is what gives you the best business value for money.

​You can use the roadmap as a communication tool to:

  • ​Identify a logical way to build your solution
  • ​Identify dependencies between different components and users
  • ​Implement rolling wave planning so that you make the most effective use of your limited time and resources
  • ​Build more detailed work breakdown structures for project management purposes
  • ​​Detailed planning for the effective allocation of people and resources
  • Present the progress of the work done to the wider audience in a very simple and easy to understand format

When the Capability Breakdown Structure (CBS) is done, it is time to hit the roadmap! Think of a roadmap as a jigsaw puzzle. Which of the different sub-components (epics), when put together will give your business value early on. Here is a brief outline of how it is done.

Let’s build the perfect roadmap

​Step 1: Selecting epics from your CBS

Take the lowest sub-components (epics) in your CBS and along with your team decide which order to assemble your epics. Number all the components. For example, “Management” would be labeled as number 1 with its sub-products listed as “1.1 warehouse management” and “1.2 staff management” etc.

​Step 2: Build your roadmap

Start to build the road map by deciding in which order you will build your e-commerce solution. Start with the ones which will give you the most business value early on.

Look at the example above and notice that the numbers of the components are no longer in numerical order but the order in which you are going to build your e-commerce solution. The arrows are pointing in the direction of the workflow.

Step 3: Identify your development sequence

The components can now be assembled into work packages (WP). Identifying what needs to be done in each work package makes it easier to identify which component products or features should be developed in sequence and which can be developed in parallel to each other.

​Step 4: Showing progress

To indicate progress in the roadmap you can use color coding to show when components in the WP is done. Green for done. Orange for work in progress and red for when the component needs to be broken down into its lowest component or needs additional information. You may want to use red to show epics that need detailed requirements in the form of user scenarios and acceptance tests on the road map. The ​capability breakdown structure is for breaking down components.

***

​Good luck and be in touch if you have any comments or want some more guidance in this matter.

Need a reliable software partner? Contact Forbytes

This website is using cookies to give you the best experience. Continue using this site you agree with our Privacy and Cookies Policy.