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
  • What is a steering group?
  • What is the purpose of a steering group?
  • How often should a steering group meeting be held?
  • What happens in the meeting?
  1. Client Projects
  2. Delivery Governance

Steering Group

What is a steering group?

A steering group is generally made up of stakeholders within the client’s business. Steering groups are set up to provide direction to a project, programme of work or a constant organisational change.

What is the purpose of a steering group?

The steering group is put in place to maximise the value delivered by the stream of work, and to minimise and manage the risks.

It’s the group’s job to listen to the updates from the project team, to help resolve any issues and to discuss and make decisions about proposals for the future. Those proposals can include a change in direction for the project, a change in budget, risk management requests for support. The people in the steering group are usually in a position to support and remove blockers when required by the project.

How often should a steering group meeting be held?

This depends on the project and whether there is enough change to discuss but generally there should be a steering group meeting every 4 to 6 weeks. It’s important that the steering groups remains up to date with the progress of the project and that they continue to support it and that they support the plans that the project team has planned for the next 4-6 phases.

What happens in the meeting?

The meetings begin with a presentation usually by the scrum master and/or product owner. The presentation will usually cover the following items:

  • Project objective - remind people of the reasons for the project

  • Project overview - the main building blocks for the project, which have been completed and which are planned

  • Risks - details of the known risks, how they’re being managed and how their likelihood and impact has shifted since the last meeting

  • Budget - the total budget, what’s been spent, what’s remaining and where that budget is expected to put the project

  • Summary and proposals - a quick wrap up and discuss the proposals for the project (recommend to move to the next phase)

Following the presentation the group will discuss the details and ask questions. This is not meant to be a test of any sort. This is a discussion with management to describe how the project is aligning with the overall business objectives and to agree the course of action for the remaining phases.

The scrum master and product owner should see this as a good opportunity to get decisions made quickly because those people in the room should be able to provide that support.

For the members of the steering group, this meeting is a chance for them to bring themselves up to date with the progress being made by the project so that they can communicate that around the organisation.

PreviousDelivery GovernanceNextRisk Management

Last updated 7 years ago