Posted on

Simple Roadmap Templates to help with your Presentation

Our Simple Roadmap Templates use successful Roadmap design formats that are popular the world around. Download these Simple Roadmap Templates now.

We’ve been developing a variety of Roadmap Templates for a few years now, and we would like to offer these ones for a reduced price!

Simple Roadmap TemplatesSimple Roadmap Templates
The Simple Roadmap Templates communicate your product or project plans simply on 1 side of paper

Features of our Simple Roadmap Templates.

  1. A4 Page size (premium are A3)
  2. Title area
  3. “Version” area
  4. Roadmap Legend
  5. Four Roadmap Workstreams
  6. Activity bars in each workstream
  7. Configurable Timeline
  8. Milestones

Our Simple Roadmap Templates are A4 Roadmap formats. For our larger and more elaborate roadmap templates, see the Roadmap Template Samples and Examples.

See all of our Roadmap Templates.

Posted on

Managing Stakeholders in Agile Projects

Managing Stakeholders in Agile Projects can be tough in large or old organisations. Have you heard this: “YES. We are agile. But you must tell me what I will get and when!” It’s painful.

The natural tension between Agile and Senior Stakeholder Structures

Upper management in large organisations and Programme Management structures (e.g. PMO) have a natural conflict of interests (or ‘tension’) with agile principles – i.e.

  1. Management and PMO want details on what is going to be delivered and when – i.e. Definition Up Front! – and
  2. The Agile product delivery team want to adapt and change dates and features as & when the customer/audience change – i.e. Definition When it’s NEEDED!

Addressing the tension – how to run Agile in large Stakeholder structures

So – how should we approach the comms around an Agile Project / Programme, and stakeholder management?

The Powerpoint Agile Roadmap Dashboard slide shows project status + Roadmap
The Powerpoint Agile Roadmap Dashboard slide shows project status + Roadmap

Clear “Release” / “Goal” Planning

  1. Describe your Releases (i.e. the significant product drops / deliveries) clearly
  2. Provide a clear 1-sider about each release, outlining what the business goals are

Manage expectations with “The Cone of Uncertainty”

  1. For each aspect of the release, clearly define the expected variance of estimates, according to degree of certainty
  2. So, if you have allowed e.g. 2 sprints / iterations for a feature, but do not plan to unpack the user stories until later on, assign an appropriate +/- 40% caveat to the estimation
  3. For more info
    1. see Agile 101’s understanding the cone of uncertainty.
    2. or Wikipedia’s entry on Cone of Uncertainty.

Focus on Epic User Stories / High-level Features

i.e. use High Level Requirements (EPICS / Features / Themes) to define the delivery

  1. Do not break down your Epics / Features into user stories unless:-
    1. They are about to go into iteration, or
    2. They are very high risk or unknown, and you can’t attach any estimation.
  2. So – avoid breaking down the WHOLE delivery into User Stories.
    1. It is in direct conflict with Agile and Lean to invest in definition unless you NEED to.
    2. So – only spend the teams’ time on defining user stories at the point of implementation.
  3. Keep these high level requirements flexible – this gives you agile wiggle room and scope flexibility at the point of implementation.
  4. Estimate the Epics in Story Points or T-Shirt sizes.
    1. See estimation recommendations here from Agile 101.

Keep Progress Clear

  1. Update your stakeholders regularly on where you are with Features / Epics implementation.
  2. Use a simple format (e.g. Release Plan) to explain which workstreams are delivering which features, and when.
Excel RAID Log & Dashboard Template
Excel RAID Log & Dashboard Template

Run a High-Level RAID Log and reference your Epics

  1. Use a RAID log to speak in Senior Stakeholder ‘lingo’.
  2. Keep this light, and do not go into too much detail.
  3. Update each sprint, or as serious RAID changes emerge.

Leave room to manoeuvre within your Epics

  1. When defining your high level features or “Epics”, keep the scoping high-level.
  2. Be clear and strategic about the scenarios and success criteria.
  3. Assign risk information to your Epics – raise stakeholder awareness of which features are risky / giving issues.
    1. This will enable them to help you prioritise.
    2. In healthy organisations, this provides a diologue in which to descope and reprioritise high level features.

Include High Level “Non Functional Requirements” (NFR s)

  1. Be sure to include any significant NFRs.
  2. e.g. (and not limited to-) :
    1. Ingegration requirements.
    2. Load testing, User testing, Stakeholder Acceptance testing requirements.
    3. Performance testing.
    4. contingency for all of the above.

Communicate Agile Plans to Senior Stakeholders

Here are some reporting formats that you can use to communicate Agile plans to Senior Stakeholders:

Posted on

Roadmap Styles

Business Documents UK has a variety of Roadmap Styles.

Roadmap Styles

Powerpoint Roadmap Styles

[downloads tags=”379″  number=”12″ columns=”2″ buy_button=”no” price=”no”]

Visio Roadmap Styles

[downloads tags=”383″ number=”12″ columns=”2″ buy_button=”no” price=”no”]

Keynote Roadmap Styles

Strategic Roadmap with PESTLE on the Keynote Roadmap Template with SWOT & PESTLE
Strategic Roadmap with PESTLE on the Keynote Roadmap Template with SWOT & PESTLE
Step-by-step Keynote Roadmap Template Example
Step-by-step Keynote Roadmap Template Example
Posted on

Define your Product Rollout Plan

The Rollout Plan Template - Powerpoint Presentation
The Rollout plan Powerpoint Presentation

Planning your Product Rollout is crucial. You need to design the workstreams, and put project controls in place to be sure your rollout stays on track.

[purchase_link id=”2080″ style=”button” color=”blue” text=”Download the Rollout Plan NOW”]

You can see our ready-made, tried-and-tested Rollout Plan Template here.

How to Plan your Product Rollout

Define “Success” – Your Rollout Objectives & KPIs

  1. What does success look like? – you must document this with measurable success criteria.
  2. Once you have this, you can identify some points in the rollout when you expect to be able to measure the “Performance” of the rollout.
  3. You can record these as Milestones, and as KPIs to focus the team on.

Understand your Risks, Assumptions, Issues and Dependencies

  1. In order to ensure the best possible rollout, you to understand what might affect your success negatively, and manage each of these factors.
  2. In project management terms, this is your RAID log, and includes documenting and managing your:
    1. Risks
    2. Assumptions
    3. Issues
    4. Dependencies
    5. View RAID templates here
  3. Track, mitigate and manage your RAID items through the Rollout process

Define your Phases & Timeline

  1. With the above points in mind, set your timeline for the Rollout.
  2. Base the timeline on a realistic and achievable timescale, and with your RAID items in mind.
  3. If it makes sense to the whole project, split your timeline into Phases, and name them

Define your Milestones

  1. Along with your KPI points, set milestones so that you can monitor project progress
  2. Be sure to get regular Status Updates, and ensure the wider team and stakeholders get Status Reports

Set out your Workstreams & Project Activities

  1. In Agile projects, and in larger Programmes, your team and activities should be arranged in Workstreams
  2. Each Workstream should represent a team, or a particular area of delivery; e.g. “HR”, “DEV”, “CATERING”, “FINANCE”
  3. Plan the project activities, and the KPIs out into these workstreams, along the timeline
  4. Ensure the Workstream participants have contributed, and helped form each workstream plan

Communicate your Rollout Plan!

  1. Agree the Timeline, Workstream, KPI and Activity plans with your team
  2. Create a Rollout Plan Presentation, with your team
  3. Present to all teams and stakeholders
  4. Give your team and Stakeholders Status Reports frequently throughout the Rollout

[purchase_link id=”2080″ style=”button” color=”blue” text=”Download the Rollout Plan NOW”]

Business Documents UK Rollout Templates

[downloads tags=”193″ buy_button=”no” price=”no” number=”12″ order=”ID, DESC” columns=”2″ pagination=false]

 

Posted on

Agile Resource Planning – build your workstreams!

Powerpoint Resource Plan Template for Agile Projects

These Agile Resource Planning formats will help you plan and communicate resource plans. Ideal for Product Development & Business Transformation.

The Powerpoint Resource Plan shows resource types, workstreams, milestones and named individuals
The Powerpoint Resource Plan shows resource types, workstreams, timeline, milestones and named individuals within each workstream.

Resource Planning document formats enable you to form and communicate your resource plans. Particularly with agile workstreams, you will want to assign a workstream team, and support them in working to the product backlog.

Agile Resource Planning

  1. Shows capacity
  2. Shows team members
  3. Shows workstream focus
  4. Shows allocation
  5. Shows key delivery milestones
  6. Shows risk status

This screenshot shows the Powerpoint Resource Plan Template.

Agile Resource Planning formats