Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to Government of Rwanda Projects
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.

    • Help and support
    • Upgrade to Enterprise edition
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support

    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Boards
  • Project library
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showProject library
        • Expanded. Click to collapseCollapsed. Click to show00 Scope
          • Hierarchy leaf00 Project charter (empty)
        • Expanded. Click to collapseCollapsed. Click to show10 Requirements
          • Hierarchy leaf00 Requirements assessment
          • Hierarchy leaf10 Requirements traceability matrix
        • Expanded. Click to collapseCollapsed. Click to show20 Stakeholders & Communication
          • Hierarchy leaf00 Stakeholder analysis (empty)
          • Hierarchy leaf10 Communication plan
        • Hierarchy leaf30 Team & Resources
        • Hierarchy leaf40 Architecture
        • Hierarchy leaf50 Reporting
        • Hierarchy leaf60 Risks (empty)
        • Hierarchy leaf70 Contract Documents
        • Expanded. Click to collapseCollapsed. Click to show80 Deliverables
          • Hierarchy leafSome deliverable
        • Expanded. Click to collapseCollapsed. Click to show90 templates
          • Hierarchy leaf010 project charter
          • Hierarchy leaf020 reporting template
          • Hierarchy leaf030 Default ToR for Government of Rwanda IT projects
        • Expanded. Click to collapseCollapsed. Click to show95 Standards & Processes
          • Expanded. Click to collapseCollapsed. Click to show00 PM methodology at RISA
            • Hierarchy leafMeeting Structure
          • Hierarchy leaf01 Standards for the "Definition of Done" (DoD)
          • Hierarchy leaf04 Severity of Incidents
          • Hierarchy leaf05 Acceptance procedure
          • Hierarchy leaf10 Architecture principles
          • Hierarchy leaf20 Service Digitization Guideline
          • Hierarchy leaf30 Service request process
          • Hierarchy leaf40 Test Management
          • Hierarchy leaf50 Version Managment
          • Hierarchy leaf60 CI/CD
          • Hierarchy leaf70 Contract Management
You are here:
  • Project library
  • 95 Standards & Processes
  • 00 PM methodology at RISA
  • Meeting Structure

Content

Meeting Structure

  • More
    • Print
    • Table of contents

Daily Stand-ups

Daily stand-ups are a standard approach as part of the SCRM methodology. The collocated team meets at a dedicated fixed and short time slot (usually 15 minutes) and answers one by one the following questions:

  • What did I do yesterday?
  • What will I do today?
  • What are obstacles on my way?

Based on experience we have the DO’s and DON’T DO’s:

DO’s

  • Create and support an open environment and atmosphere
  • Schedule follow ups for identified obstacles
  • Be firm, be brief, be open

Don't DO’s

  • Don’t use it for individual tracking
  • Don’t expand the timeslot by going too much into the details (rather schedule follow up)
  • Don’t blame.

Demo

The demo will be used to demonstrate deliverables to the team or to the customer. They can be regularly scheduled or on request. Best practice is to block a slot which can be used or dropped. In addition it is useful to ensure that whatever gets shared/presented with the team went at least through one quality cycle before (as in, at least one feedback loop with another team member took place). If there is nothing to showcase, the meeting will not take place. Showcased items can be any deliverables. If possible, share a link to them one day ahead of the meeting, so the team can have a look at them ahead of the meeting.

Retrospective & Review

As the iterations in GoR are quite short, best practice has been established to combine retrospective and review. They do not (!) include the demo and can be rather short if well prepared. They usually happen on last day of the sprint. During this session the following activities are to be performed:

  • Review the result of the features planned for the current sprints based on the “definition of done”
  • Accept or reject completion status
  • Review the “definition of done”
  • let the team assess what went well and what to be improved
  • celebrate success

Planning

Planning session usually happens at the first day of each sprint. Activities include:

  • Review the preparation of features in the backlog
  • Plan features or user stories for the current sprint
  • Adjust the approach if necessary
Loading...