Scribd Logo
Upload

Welcome to Scribd!

  • Ceremonies

    Uploaded by

    Abhilash Chiganmi
    9 views1 page
    The document outlines different levels of ceremonies for a company, including weekly company-level meetings to provide transparency and a big picture view, as well as POD-level ceremonies focused on execution rigor. Some examples given are weekly product and architecture meetings, sprint kick-off and planning meetings, daily scrums, retrospectives at the end of each sprint, and sprint demos. The goals are to create visibility, seek inputs and ideas, review designs, and ensure knowledge sharing and validation across teams.

    Original Description:

    Ceremonies

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document outlines different levels of ceremonies for a company, including weekly company-level meetings to provide transparency and a big picture view, as well as POD-level ceremonies focused on execution rigor. Some examples given are weekly product and architecture meetings, sprint kick-off and planning meetings, daily scrums, retrospectives at the end of each sprint, and sprint demos. The goals are to create visibility, seek inputs and ideas, review designs, and ensure knowledge sharing and validation across teams.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    9 views1 page

    Ceremonies

    Uploaded by

    Abhilash Chiganmi
    The document outlines different levels of ceremonies for a company, including weekly company-level meetings to provide transparency and a big picture view, as well as POD-level ceremonies focused on execution rigor. Some examples given are weekly product and architecture meetings, sprint kick-off and planning meetings, daily scrums, retrospectives at the end of each sprint, and sprint demos. The goals are to create visibility, seek inputs and ideas, review designs, and ensure knowledge sharing and validation across teams.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as pdf or txt
    of 1

    Ceremonies

    Company Level ceremonies

    Why ? : Create visibility , transparency

    Weekly Technology Update meeting

    Central Ceremonies

    Why ? : Big picture view, Seek inputs , Brainstorming/Idea seeking , Validation , Knowledge sharing

    Weekly Product Working Sessions : Owned by Product


    Quarter View
    Epic ( pun intended ) Solutions
    Ux & Design reviews
    Weekly Architecture & Design Working session : Owned by Engineering
    HLD , LLD and Architecture reviews

    POD Level ceremonies

    Why ? : Execution Rigor

    Kick off Meeting / Grooming : Sprint Start Day


    *To be decided and religiously followed
    Planning : Sprint Start Day
    Alternate Wednesday (Remains same for all technology teams with incremental sprint numbering)
    Scrum : Daily
    Scrum Masters to lead the daily meeting to be defined by the Engg. Managers using the roster format
    Mandatory attendance by the POD members from all relevant teams
    Retrospective : Sprint End Day
    Confluence documentation on what went well, what went wrong and what can be improved to be done by each pod
    Each retrospective to have an owner. This can be decided by the Engg. Managers using the roster format
    Sprint Demo : Sprint End day
    The day to be finalised - Engg. Managers
    Demo to happen amongst the technology team stakeholders (Engg Managers, Product Managers, Developers, QA team, Designers,
    Technical Architects,DOE/DOP, PMO)
    The video link of the demo can be shared on a slack group with the wider audience

    You might also like