Idea Flow
Models
Idea Flow
  • Welcome!
    • Why Models?
    • Why Principles?
  • Agility & Transformations
    • Intro to Agile
      • What Does Agile Mean?
      • What Is An Agile Mindset?
    • Intro to Transformation
      • Why Transform?
      • How Is The Transformation Done?
      • Who Transforms?
      • Which Areas or Functions Transform?
      • How Long Does A Transformation Take?
  • Agile Transformation (Idea Model)
    • Intro to IDEA
      • Leadership-Strip (Tanzaku)
      • Managing The Change
      • Metrics
      • Coaching Plan
        • Coaching Assessment
    • Initial Exposure
      • Training & Coaching
      • Assessment
    • Develop Basics
      • Training & Coaching
      • Assessment
    • Evolve & Reflect
      • Training & Coaching
      • Assessment
    • Accelerate & Kaizen
      • Training & Coaching
      • Assessment
  • Delivery Approach (Flow Model)
    • Intro to Flow
      • Flow of Work
      • Dev Sec Ops
    • Conceptualise
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Commence
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Construct
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Confirm
      • Purpose
      • Inputs
      • Process
      • Outputs
    • Complete
      • Process
      • Outputs
    • Check
      • Process
  • Scrum, Kanban & Other Agile Frameworks
    • Double-Loop Scrum
    • Kanban
  • 3D Work-Breakdown
    • Intro to Work Breakdown
    • Direction
    • Discovery
    • Delivery
    • Flow & 3D Work-Breakdown
  • Roles & Responsibilities
    • Overview
      • Trust Circles
      • Enterprise View
    • Core Team Roles
      • Scrum Master / Iteration Manager
      • Product Owner
      • Developer
      • Tester
      • Business Analyst
      • Infrastructure
    • Extended Team Roles
      • Product Manager
      • Test Lead
      • Tech Lead
      • Subject Matter Expert (SME)
      • UX/UI Designer
      • Infrastructure Lead
      • Project Manager
      • Solution Architect
      • Delivery Manager
      • Change Analyst
    • Trusted Advisor Roles
      • Project Sponsor
      • Stakeholders
  • Topics
    • Prioritisation
    • Estimation
      • Estimation Overview
      • Epic Estimation
      • Initiative Estimation
    • Planning
      • Sprint / Iteration Planning
      • Release Planning
      • Quarterly Planning
      • Problem Statement
    • Ceremonies
      • Showcase
      • Scrum of Scrums
      • Stand-up
      • Retrospective
      • Elicitation
      • Elaboration
      • Acceptance Criteria (AC)
    • Artefacts
      • Tech Spike
      • Definition of Done
      • Social Contract
      • Personas
      • Lean Canvas
      • User Stories
    • Toolkit
      • Success Sliders
      • ICaRuS Scoring
      • Accountability Cards
    • Quality
      • Test Strategy
      • Test Plan
      • Quality Attribute Definitions
      • Test Type Definitions
      • Regression Test Suite Definitions
      • Defect Definitions
      • Defect Severity
      • Defect Priority
      • Agile Testing Quadrants
      • Risk-Based Testing
    • Templates
      • 3rd Party Handover Template
      • Audit Logs
    • Data
      • Information Management
    • Kanban
  • Agile Testing (4Aces Model)
    • Intro to Agile Testing
      • Test Principles
        • Test Automation Principles
      • Test Artefacts
      • Test Triangle
      • Agile Testing Quadrant
    • Arrange
    • Act
    • Assert
    • Annihilate
  • INCIDENT MANAGEMENT (TRACeR MODEL)
    • Intro to TRACeR
      • What is Incident Management
      • Incident Management Workflow
    • Triage
    • Review
    • Action
    • Check
    • Resolve
  • Change Management (3C Change Model)
    • Intro to 3C Change
      • What is Change?
      • What is Change Management?
      • 7Rs of Change Management
      • Model States
      • Implementation
    • Capture
      • Priority
      • Experience
      • Impact
      • Change Types
    • Consider
      • Risk
    • Conduct
      • Plan
        • Change Activities Matrix
      • Perform
        • Rollback or Roll-forward
      • Prove
        • Change Result/Status
  • Faciliation
    • Intro to Faciliation
      • Agile Facilitation
      • Planning and Running a Workshop
    • Meetings
      • Meeting Prep
    • Workshops
      • Quarterly Planning Workshop
      • Integrated Culture Workshop
    • Games
      • Dice Game
      • Battleships
      • Kanban Pizza Game
    • Icebreakers
      • Check Your Personal Thinking Style
  • Agile Coaching (A6 Model)
    • Intro to Coaching
    • Agree
    • Address
    • Assess
    • Align
    • Assign
    • Account
  • Agile Leadership
    • Intro to Agile Leadership
  • Strategy
    • What is Strategy?
    • What is Vision?
    • What is a Mission?
    • What are Values and Drivers?
    • Intent-based Outcomes
    • MunroMaps
  • OKRA
    • OKRS + ACTIONS = OKRA
      • Implementation
      • Cycle Cadence
    • Objectives
      • OKRs
    • Key Results
    • Actions
  • Agile Software Architecture (C4 Model)
    • Intro to Architecture
      • Role of the Architect
      • SOLID Principles
      • DRY Principle
      • Single Source of Truth (SSOT)
    • Context
      • Examples
    • Container
      • Examples
    • Component
      • Examples
    • Code
      • Examples
    • Patterns
      • Back-end for Front-end (BFF)
      • Event-Driven Microservices
  • Portfolio Management (PMO Practice Model)
    • Intro to Portfolio Management
      • Practices & Flow
      • Objectives
      • Types
      • Maturity Assessment
      • Setting Up
        • Charter
    • Demand Practice
    • Risk Practice
    • Performance Practice
      • Cost of Delay (CoD)
      • Metrics
    • Report Practice
    • Delivery Practice
    • Asset Practice
    • Change Practice
  • RAFT
    • RAFT Framework
  • Tools
    • Jira
      • Best Practice
      • Printing Physical Cards
    • Confluence
      • Best Practice
      • Example Confluence Layout
    • Power BI
      • Power Query M
    • Miro
      • Best Practice
  • FAQs
    • Frequently Asked Questions
    • Glossary of Terms
  • Thanks & Contributors
    • Thanks
    • License
Powered by GitBook
On this page
  • Keep it short
  • Team Attendance
  • Start the day with a daily stand-up
  • Capture action items and track them

Was this helpful?

  1. Topics
  2. Ceremonies

Stand-up

We use this to make a quick plan for the day so that we can understand what is going on in the team and plan out any interactions that may be required to get work items done.

A stand-up is a simple on-the-go, time-boxed 15-minute session where all members of the squad either stand or virtually get together and set the context for the coming day's work. The daily stand-up is important because it gives the team an opportunity to talk about both the negative and positive effects of their work. The team learn from one another and sees what can be improved upon.

The Scrum Master is usually the facilitator of this ceremony, but the stand-up can successfully be facilitated by any team member.

The primary goal is to identify areas where the squad may be blocked or impeded and to plan for the upcoming day.

This is often done in front of a visual or virtual wall that displays the team's work in the form of user stories.

The daily stand-up consists of each squad member answering three quick questions:

  1. What did I do yesterday?

  2. What am I doing today?

  3. What impediments or blockers are in my way? - and then respond to any updates from their peers.

Note: Usually, only the squad attends, but it should be open to stakeholders that are curious to know more about the project’s progress.

Keep it short

If people are asked to stand, it is because it should be short.

Do not let conversations develop for too long, capture it as an action and encourage team members to take it up offline. Everyone needs to have time to go through the questions.

Team Attendance

It is important that the whole team is attending. If one team member cannot attend, make sure to capture their input beforehand and inform the team accordingly.

This is helpful for transparency reasons so that the whole team knows who is doing what. It helps to deal with impediments. The earlier they are reported, the earlier it can be solved.

Make sure that you work with the team to develop “norms” around what to do if someone is not present.

For example, it may be agreed to start without them or go ahead on time regardless. Also, consider how technology can be used to assist if someone cannot be present. A phone call or video conference link can help.

Start the day with a daily stand-up

The daily standup should inaugurate the working day, so make sure to keep the squad energized!

Agree this time with the team. As people may be in different time zones or have differing start times, other times of day may suit them better.

Capture action items and track them

This may take several shapes. For instance, it may be clear that an impediment will open the door to corrective actions. However, discussions among team members may be as well. Possibilities to collaborate, but also tensions within the squad can be spotted during a daily stand-up, so make sure to observe and take public (agreed with the squad) as well as more private (based on observations on the squad collaboration) actions.

Want to switch it up? Try a reverse stand-up!

A reverse stand-up takes the same three questions as the classic stand-up and flips the order. This results in the most important questions being tackled first:

  1. What impediments or blockers are in my way?

  2. What am I doing today?

  3. What did I do yesterday?

Reverse stand-ups are useful when blockers or impediments are not being called out as often as they should or if stand-ups are turning into status updates.

A reverse stand-up can also be useful to change things around periodically to re-energize the squad.

Last updated 2 years ago

Was this helpful?