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
  • Who should attend?
  • The purpose
  • The process
  1. Client Projects
  2. Build
  3. Sprinting

Daily Standup

The daily standup is an important meeting that we hold at the same time, same place, every day during each sprint.

Who should attend?

The meeting must be attended by the Delivery Team, the Service Delivery Manager and the Product Owner. Other people can join but only as observers, they don’t contribute.

The purpose

The reason we have a daily standup is due to the fast paced, ever changing nature of the work we deliver. The daily standup is the opportunity for each member of the team to share what they’ve completed and what they’re working on. It’s a great way to communicate progress, challenges with the rest of the team and with the Product Owner.

The process

Each member of the delivery team takes turns to discuss the stories they worked on the previous day, what they plan to work on today and to raise any issues that they’ve encountered. The Delivery Manager will facilitate the meeting, making sure everyone speaks up, keeping everyone on topic and keeping the non-participants out of the conversations.

This is a quick meeting, timeboxed to 15 minutes, so the discussions are to the point and relevant to the sprint. Any issues that need a more lengthy discussion are taken away from the meeting.

  • Yesterday - what stories did I work on? What stories did I complete? Any issues?

  • Today - what do I have planned for today?

  • Blockers - Do I need any support? Are there any risks to raise?

The sprint is a team effort so if anyone is struggling with the complexity of a story, if they need input, if a story turns out to be way bigger than expected or they just need to throw ideas around, then this is the time to ask for that support. If you need help from outside the team then the Product Owner or Delivery Manager will support you with that.

Importantly, people need to listen to what’s being said. If one person is wrestling with an issue that affects what they can complete then that will affect the whole team. It’s better that two people solve a problem in 1 hour than one person struggle for a day.

We're strict about the 15 minute time box for this meeting. Anything that needs more discussion will happen outside of this meeting. Holding those extra discussions in this meeting will involve some people who don’t need to be involved. We need to keep the process lean and relevant to everyone. Only take people away from their sprint tasks if it's necessary.

At the end of the standup each member of the team and the Product Owner will have a clear idea of where the sprint is at and whether the sprint is on track.

PreviousSprintingNextStory Lifecycle

Last updated 7 years ago