Engineering
  • Welcome!
  • First Principles
  • Communication tools
  • Acronyms
  • Vital reading material
  • Engineering Onboarding
    • Onboarding Guide
    • Mobius onboarding Guide
    • Lessons
      • 001 - Function Purity
      • WIP - Shared Mutable State
  • System design & Architecture
    • Introduction
    • Refactoring
    • Architecture Decision Records
  • Meetings
    • Iteration Planning Meetings
    • Daily Standup Meetings
    • Retro meetings (retrospective)
  • Release Engineering
    • Introduction
    • Git commit messages
    • Code reviews & pull requests
    • Trunk-based development
      • Our methodology
    • Service Dependencies
    • Tooling & infrastructure
    • Git commands & workflows
  • Project Management
    • Product Requirements Document
    • Pivotal Tracker
Powered by GitBook
On this page

Was this helpful?

  1. Meetings

Daily Standup Meetings

DSMs happen every day, usually with the full team of a project -- this includes people from the client’s org who are working with us, and other external contractors.

In the spirit of agile engineering, the advantage of a DSM is to surface issues/blockers as soon as possible, and keep the team aware (on a broad level) of what is happening elsewhere in the project. Seeing everyone face-to-face daily builds trust and accountability. We encourage people to ask questions across the team to get increased clarity on a specific thing, if needed.

The “standup” part of the meeting is important; everyone remains on their feet, keeps the focus on quick updates, and tries to finish the entire meeting in a few minutes. Inadvertently... it may happen that someone’s update leads to a set of people discussing the thing in full detail -- this wastes everyone else’s time, and should be moved out of standup into a separate discussion.

PreviousIteration Planning MeetingsNextRetro meetings (retrospective)

Last updated 5 years ago

Was this helpful?