BR.3 Define and prioritise the requirements of the first project

Download

OVERVIEW

The aim of this activity is to define and prioritise the requirements for the first project for eco-innovation from the roadmap.

INPUT

• Roadmap for eco-innovation implementation from the activity BR.2 Do a roadmapping workshop with input from value chain partners.

• Details of the innovation ideas to be implemented within the first project for eco- innovation. This comes from the relevant activities of the step ‘Generating ideas at the individual building block level’, and the activity BR.2 Do a roadmapping workshop with input from value chain partners.

OUTPUT

  • Systematically captured set of requirements for the first project for eco-innovation used in the activity IM.1 Create a project plan.

TEMPLATE

HOW TO GO ABOUT IT

Work through the life cycle of the emerging project to identify key areas where requirements need to be defined. Record each area for focus in a list.

Take the Requirements Specification template and begin filling in the fields – one row per key area identified. The fields of the template are as follows:

  • Number or code: This simply helps the project manager to keep track of each requirement and creates a reference to check performance against.
  • Mandatory requirement: This field is where the requirement is described. Take care to fill in the requirements by stating “what” but not “how” each requirement should perform. Describing the “what” sets a measurable target for the project, whereas describing “how” (even though tempting) may limit the solution space and cut out valuable innovation opportunities.
  • Comments:This field leaves room for members of the project to remind themselves of reasons for including the requirement, general questions about the technological elements of the solution, recommendations from other colleagues or similar projects, etc.
  • Priority: This field helps to communicate the relative importance of various parameters of the solution.

M – MUST have this.
S – SHOULD have this if at all possible.
C – COULD have this if it does not affect anything else.

W – WON’T have this time but would like in the future

  • Review date: This field helps to keep track of the date for review of each parameter.
  • Reviewed/Approved:This field allows for the assigned reviewer and/or approver to sign on each requirement, which must be completed prior to starting work on that requirement.

Tips & Tricks

HELP WITH TECHNOLOGY

If the innovation idea that will be tackled during the project involves a significant technology element then it will be useful to read the accompanying publication ‘Technologies for Eco-innovation’ (UN Environment, 2016), which provides guidance on technology development and technology transfer for eco-innovation.

UPDATE PRIORITIES REGULARLY

Once the project has started, the requirement prioritization should be regularly updated.

KEEP PRIORITIES FOCUSED

When prioritising the requirements, it is important to be disciplined and avoid making every requirement a ‘must’. Keep in mind that there may be deadlines for the development and implementation of the innovation idea, and it is usually better to deliver on time with a limited set of requirements fulfilled than delivering late with more requirements fulfilled.

— Success story from Vietnam

An Ecological Catalyst for Vietnam’s Guava Farms

On the banks of the Red River in northern Vietnam,… >> read more.