Convivio Cookbook
  • Introduction
  • Our Business
    • The Convivio brand
    • What do we do?
    • Our work for clients
    • Our Purpose
    • Our Pulse
      • Big Rocks
      • Problems
    • Company Policies
      • Environmental Policy
      • Anti-Bribery Policy
      • Fair Tax Policy
        • Dividends policy
        • 2020 Results and Tax
        • 2019 Results and Tax
        • 2018 Results and Tax
        • 2017 Results and Tax
  • Our Team
    • Help! I'm new. How do I get started?
    • Starting at Convivio
    • Staff Benefits
    • Being a buddy
    • Having a buddy
    • Free-Range Working
    • Convivio Fridays
    • Notes: give & receive feedback
    • Security Screening
    • Submit Expenses
    • Purchases
    • Your home working environment
    • People Analytics
    • Recruitment
      • Help Card: Writing a Person Profile
      • Help Card: Writing a Job Description and Advert
      • Help Card: Publishing a Job Advert
      • Help Card: Reviewing CVs
      • Help Card: Preparing and Conducting Structured Interviews
      • Help Card: Preparing and Conducting Remote Working Interviews
    • Team Policies
      • Security Policy
        • Acceptable Use Policy
        • Business Continuity Management
        • Data Usage Policy
        • Document Access Policy
        • Mobile Equipment Policy
        • Two-Factor Authentication (2FA)
        • VPN Guide
      • Equal Opportunities
      • Grievance Procedure
      • Disciplinary Procedure
    • Taking time off work
      • Holiday
      • Sickness
    • Peer reviews
    • Mental Health
      • Mental Health Training
      • Mental Health First Aid
      • Returning to work
      • Resources
    • Continuing Professional Development
      • CPD Annual Planning
      • CPD Sprints & Scrums
      • CPD Annual Review
      • CPD Annual Retrospective
  • Our Clients
    • Principles For Building New Client Relationships
    • Researching
    • Connecting
    • Nurturing
    • Assessing
    • Learning and Thinking
    • Pre-qualification questionnaires
    • Proposing
    • Agreeing
    • Beginning
    • Inspiration
  • Our Marketing
    • Content Publishing
      • Git Repository Conventions
      • Help Card: Writing a Case Study
    • Brand Guidelines
      • Content Guidelines
      • Branded Documents and Reports
  • Our Tools
    • Infrastructure
      • External Firewalls
  • Internal Projects
    • How we improve our business
  • Client Projects
    • Delivery Launch
    • Delivery Team
      • Convivio People
      • The Coach
      • User Researcher
      • Other Team Members
    • Digital Strategy
    • Discovery
      • Discovery Briefing
      • Discovery Planning
      • Discovery Modules
      • Discovery Findings
      • Discovery Principles
      • Prepare for prototyping
    • Prototyping
      • Inputs to Prototyping
      • Prototyping Objectives
      • Prototyping Inception
      • Prototyping Sprints
      • Prototyping Outputs
    • Build
      • Inputs to Build
      • Build Kickoff
      • User Stories
      • Backlog Management
      • Backlog Scouting
      • Sprint Planning
      • Sprinting
        • Daily Standup
        • Story Lifecycle
        • Design in Sprints
        • User Testing in Sprints
        • Quality Control in Sprints
      • Sprint Review
      • Sprint Retrospective
    • Service Management
    • Digital Service Standards
      • Delivery Methodologies
        • Scrum
        • Kanban
        • Lean
          • Technical Standards
        • Code Quality
        • Testing
        • Automation
          • Security Standards
          • Quality Standards
          • Risk Standards
    • Delivery Governance
      • Steering Group
      • Risk Management
        • Risk Attitude
        • Assessing Risks
    • Delivery Help Cards
      • Help Card - Sprint Planning
      • Help Card - Sprint Review
      • Help Card - Sprint Retrospective
      • Help Card - Product Owner Feedback
      • Help Card - Common Issues
      • Help Card - Slack
      • Help Card - Github
      • Help Card - Trello
  • Our Recipes
    • Convivio Classic Cocktails
      • Ingredients
      • Tips and Techniques
      • Martini
      • Negroni
      • Manhattan
      • Old Fashioned
    • Potage Dubarry (or, creamy cauliflower soup) with spiced green pepper
    • Roasted Sweet Potato in a Herb and Nut Salad, with Maple Chilli Dressing
    • Aubergine Curry
    • Vegetarian Paella
    • Easy Ice Cream
Powered by GitBook
On this page
  • Attendees
  • Format
  • Preparation
  • Agenda
  • Output
  1. Client Projects
  2. Discovery

Discovery Planning

This is a meeting that happens either at the very start of discovery, or a little in advance.

Attendees

  • The delivery team

  • The product owner

Format

The meeting is best done in person, but can be done on a call if necessary.

The timebox is 4 hours. (allow for a good break in the middle).

Preparation

  • You need 4 different colours of sticky notes, some big wall space (or the digital equivalent if on a call).

  • Write up the names of the discovery modules, one per sticky note. Use a different colour for each subject area (eg business, design, technology)

  • Everyone will need some planning poker cards (the cards 1-5 from the deck) - or another method of quickly boting 1-5.

  • Write the mission for the discovery somewhere prominent in the room, in big bold letters.

  • Make sure there's plenty of good coffee, tea, and water. Extra points for healthy snacks.

  • Renind everyone in advance of our meeting principles.

Agenda

For the first half an hour (timeboxed), review the mission for the discovery with the product owner. Probe, ask questions.

Then, pick a module stickynote at random. Each specialist on the team pitches the modules in their area of specialism, What value would they provide here? To what depth should they be delivered? What risks would they address? What knowledge gaps would they help fill. There's a 5 minute (timeboxed) pitch per module.

Everyone then votes on that module, using the planning poker score cards, against the following Top Trumps style strengths of that module where 1 is a low score and 5 is a high score:

  • Addresses key risks

  • Addresses key knowledge gaps

  • Opportunity for innovation

  • Level to deliver module to (1 is a basic level, 5 is an advanced level)

In the same way as with planning poker normally, shared or close scores are accepted, outliers are discussed in a quickfire way. An agreed score is reached. This process is repeated for all the modules. A moderator needs to lead the meeting and keep discussion brief and focused to stay on track. In the last hour of the meeting the high scoring modules are gathered into a backlog and priorities are discussed, until there is a rough consensus on priority. The depths to which some modules are delivered may be altered. Modules may be split too, so for example you could say its a high prioirty to deliver module x to at least level 2, but a much loer priority to then deliver it to level 4 later.

Output

A prioritised backlog of discovery modules to deliver.

PreviousDiscovery BriefingNextDiscovery Modules

Last updated 7 years ago