Sneak preview of the FROST Innovation Framework structure.Continue reading The FROST Innovation Framework – Overview
A little heads-up – we’re starting on a new range of templates as part of the FROST Innovation Framework from GAS LABS.
This is a useful new framework that supports medium-to-large organisations in creating productive and strategic in-house innovation capabilities.
The FROST Innovation Framework is structured around five key characteristics:
- Focused – You articulate the challenge using the “How might we … ?” question template.
- Regular – You ensure that the innovation sessions are regular, recurring, and are protected against “emergencies”.
- Open – You ensure that the challenge is open, unrestricted, and importantly has no implementation details stipulated.
- Safe – Your staff and all participants, really do honestly feel safe to take risks, and to try anything they want to.
- Tangible – The outputs must be working prototypes of some form (NOT just pictures or people waving their arms).
We have been busy with Spring Cleaning! The Visio Roadmap Templates needed a good dusting off.
My timeline keeps breaking… please HELP ME!
Some of our customers using Visio 2010+ were seeing compatibility issues. Well, we have fixed them!
What breaks in Visio Roadmap Templates?
These are some of the symptoms that customers have reported
- The text within shapes is not editable.
- The timeline breaks when the dates are changed.
- The timeline format goes STRANGE when the dates are changed.
- The timeline COMPLETELY BREAKS when the intervals are changed.
(And we have fixed them!)
Why? What caused these issues?
- People ask Microsoft for new features.
- New features get introduced.
- The new features break existing implementations.
Some of our Visio formats have been popular for 10 years. So it is not surprising they need updating!
Visio Templates that have been fixed and upgraded.
- Supplier Procurement Tender Tool Timeline Template (Visio)$ 15.97
- Cultural Change Template (Visio)$ 15.99
- Project Manager Visio Planning Templates Discount Bundle$ 62.97
- Visio Agile Roadmap Template Discount Bundle$ 53.99
- Simple Roadmap Template (Visio)$ 14.97
- Product Roadmap Template 2016 – Visio Design$ 15.97
- Visio Agile Release Plan for Scrum Teams (Story Mapping)$ 13.99
- Timeline Template Formats Discount Bundle: >60% off$ 55.60
- Visio Roadmap Template – the Original since 2005$ 11.99
Argghhh – the Project has GONE WRONG!… too often we freak out in an self loathing, whining mess. Especially when there’s more than one team involved. OK.
OK. Take a moment. Stop your teams from running around in circles and screaming.
We usually forget the good things! And,… there will be good things again.
Take a breath, and plan a “Lessons Learned” Project Retrospective:-
- to put things back in balance,
- to establish what needs to be done differently next time,
- to emphasise what was great about the project,
- to draw a line under the project so that negativity can’t damage us any further, and
- to get the teams talking again.
One tendency though, is that negativity can be brought into the Lessons Learned session.
So – how do we keep the Lessons Learned Positive and Productive?
Getting the Right Facilitator is really IMPORTANT!
Important attributes for your Facilitator:
- Neutral – was not directly involved in the project
- Positive – is self-starter, positive and always pushing for the best
- Pragmatic – has a grip on what is feasible and reasonable
- Some sense of humour – sees the humorous side of things
- Has knowledge of the area – understands the business in question
A good Facilitator must:
- take all points as valid, and record them carefully
- prevent defensive behaviour – “it’s happened, let’s get this point recorded”
- prevent arguments or tempers from flaring – “we’ll record everyone’s points – they are all now valid – remember the Prime Directive :)”
- keep track of time – be sure that everyone is getting their opinions in, and that noone is allowed to monopolise the available time
- encourage insights from quieter participants – there are likely to be dominant characters, so make sure the quieter ones get a chance to share
- be fair, and praise contributions – keep the atmosphere positive and light by being fair, listening well, and giving praise to brave or focussed insights
Focus on “How to do better next time”
Focus on “how to do better next time” rather than “Who got it wrong / what was wrong this time”.
Use Norm Kerth’s “Prime Directive”
Norm Kerth’s Prime Directive is generally accepted as a great way of staying positive in your retrospectives :
Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.
Set out your Lessons Learned Agenda
You can use this Agile Lessons Learned template as a good basis and structure on which to build.
[purchase_link id=”2246″ style=”button” color=”blue” text=”Add the Project Lessons Learned Template to Cart”]
- Make it short and clear.
- Set the times for each section.
- Prepare the room for what’s going to happen.
- Stick to your times.
Further help with your Lessons Learned Session
You can find a complete guide to how to run an Agile Lessons Learned Project Review here.
More Project Review and Lessons Learned Templates
This guide will explain the important parts of a Project Roadmap. It includes workstreams, activities, timelines, risk levels and other elements needed for an effective project roadmap.
1. Quickly communicates project plans and goals.
2. Manages stakeholder expectations.
3. Generates a shared understanding across the teams involved.
4. Communicates plans with other important teams/organisations.
1. Must Have: The Project Goals articulated; at least in the deliverables listed.
2. Must Have: A timeline – to show when things will happen.
3. Must Have: The high level titles for the big deliverables (don’t get into the detail!!).
4. Should Have: The workstreams in separate “Swim Lanes”.
5. Should Have: Milestones of key events, when you expect them.
6. Could Have: Areas of high risk.
7. Could Have: Areas where you have dependencies.
It gives a sense of the Project Goals: Either explicitly in plain words: “The goal is …”.
It shows the plans for a project in simple terms: not too detailed – just the high-level titles! (keep to 4 or less in each workstream).
It fits on 1 side of paper (or 1 slide in a presentation) to keep it simple!
It shows project plans alongside a timeline.
You can read it and understand it in 3 minutes or less.
It avoids acronyms and team jargon, so that anyone can understand it!
It has your name on it – so people can contact you with questions.
The best project roadmap presentation is one that tells your story simply and quickly. You must give a sense of time, the important project elements, and any key messages you want to highlight.
Step-by-Step guide to creating a Roadmap
See our Creating a Roadmap guide here.
Creating a Roadmap can have useful side-effects
The process of creating a roadmap, with key project stakeholders and team members, can be a very useful exercise for your team, because it:-
- Ensures that the team and stakeholders understand capacity
- Forces priority decisions
- Promotes a shared understanding in the wider team
Roadmap Examples and Samples
- Project Report$ 11.99
- Transition Plan Powerpoint$ 17.85
- Google Sheets Compatible Roadmap Template (Excel)$ 13.03
- Risk Log and Transition Management Template Deal (PPT & Excel)$ 32.45
- Excel Transition Plan Template$ 17.98
- Gantt Chart Excel Template$ 17.56
- Powerpoint Mobile-Friendly Roadmap Template$ 13.22
- PPT Roadmap With Milestones$ 14.99
- New Product Definition Template$ 17.97
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.
- Management and PMO want details on what is going to be delivered and when – i.e. Definition Up Front! – and
- 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?
Clear “Release” / “Goal” Planning
- Describe your Releases (i.e. the significant product drops / deliveries) clearly
- Provide a clear 1-sider about each release, outlining what the business goals are
Manage expectations with “The Cone of Uncertainty”
- For each aspect of the release, clearly define the expected variance of estimates, according to degree of certainty
- 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
- For more info
Focus on Epic User Stories / High-level Features
i.e. use High Level Requirements (EPICS / Features / Themes) to define the delivery
- Do not break down your Epics / Features into user stories unless:-
- They are about to go into iteration, or
- They are very high risk or unknown, and you can’t attach any estimation.
- So – avoid breaking down the WHOLE delivery into User Stories.
- It is in direct conflict with Agile and Lean to invest in definition unless you NEED to.
- So – only spend the teams’ time on defining user stories at the point of implementation.
- Keep these high level requirements flexible – this gives you agile wiggle room and scope flexibility at the point of implementation.
- Estimate the Epics in Story Points or T-Shirt sizes.
Keep Progress Clear
- Update your stakeholders regularly on where you are with Features / Epics implementation.
- Use a simple format (e.g. Release Plan) to explain which workstreams are delivering which features, and when.
Run a High-Level RAID Log and reference your Epics
- Use a RAID log to speak in Senior Stakeholder ‘lingo’.
- Keep this light, and do not go into too much detail.
- Update each sprint, or as serious RAID changes emerge.
Leave room to manoeuvre within your Epics
- When defining your high level features or “Epics”, keep the scoping high-level.
- Be clear and strategic about the scenarios and success criteria.
- Assign risk information to your Epics – raise stakeholder awareness of which features are risky / giving issues.
- This will enable them to help you prioritise.
- In healthy organisations, this provides a diologue in which to descope and reprioritise high level features.
Include High Level “Non Functional Requirements” (NFR s)
- Be sure to include any significant NFRs.
- e.g. (and not limited to-) :
- Ingegration requirements.
- Load testing, User testing, Stakeholder Acceptance testing requirements.
- Performance testing.
- 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:
Project Handover PowerPoint $ 24.99 Add to cart
Google Sheets Compatible Roadmap Template (Excel) $ 13.03 Add to cart
Hackathon Business Case Guide & Template (PPT and Keynote) $ 28.34 Add to cart
Resource Plan with Workstream Resource Changes Template $ 18.21 Add to cart
Innovation Pipeline Structure: The Three Horizons Template $ 17.21 Add to cart
Powerpoint User Story Mapping Template $ 23.97 Add to cart