Skip to main content

Effective Scrum Meeting

Overview:

The Daily Scrum Meeting is held every day through the sprint.

At the meeting, the Scrum team gathers to review and synchronize about the project status.

In theory, each team member should provide his/her status based on three (03) Q:

  1. What did you do yesterday?
  2. What do you intend to do today?
  3. Is there any issues that blocks your work?
# The participants should come prepared:
  1. Stop participants that don't come prepared and waste the meeting time. The team members should come prepared to share their updates.
  2. You should describe how to answer these questions effectively to increase the synchronization among the team members.
  3. The team members should know what is your expectations from them while answering these questions.
# Validate that each individual describe the full picture:
  1. Validate that each individual can answer the 3 questions (Do not continue until you get the answers or the reasons for why he can't provide them).
  2. Validate that each team member is participating in the meeting (MANDATORY for this meeting).
  3. Validate that each individual answers the truth about each one of the questions.
# This is not a technical meeting:
  1. REMEMBER, these meetings are done to synchronize the team members. It's not about problem solving.
  2. When a technical problem is raised, the Scrum Master will resolve it after the meeting.
  3. You can't run an effective Scrum meeting while wasting time on technical solutions.
# The meeting should run with a specific timeframe:
  1. Each individual should know how much he/she can speak (2-3 min at max.)
  2. Meeting that run more than the defined time frame, are less effective.
  3. You should define the start/end time of the meeting.
  4. You should enforce the timelines.
  5. The meeting is relevant per day, there is no real reason to make it for more than 15 min.
# The team members should understand the meeting target:

http://www.slideshare.net/DavidTzemach/how-to-run-an-effective-scrum-meeting-in-10-steps























Comments

Post a Comment

Popular posts from this blog

GitHub- how it works

GitHub: GitHub is a platform for hosting and collaborating on projects. We don’t have to worry about losing data on our hard drive or managing a project across multiple computers — sync from anywhere. GitHub Essentials:   Repositories ,   Branches , Commits ,   Issues   and   Pull Requests . A   repository   is the basic unit of GitHub, most commonly a single project.  Repositories can contain folders and files, including images – anything our project needs. Repository = single project = single folder which contains subfolders and files. Sometimes GitHub users shorten this to “repo.” Branching   is the way to work on different parts of a repository at one time. When we are working on a project, we are going to have a bunch of different features or ideas in progress at any given time – some of which are ready to go, and others which are not. Branching exists to help we manage this workflow. When we create ...
Post a Comment
Read more

Quality Assurance vs. Quality Control

            Quality Assurance             Quality Control Definition:    QA is a set of activities for ensuring quality in the processes by which products are developed. QC is a set of activities for ensuring quality in products. The activities focus on identifying defects in the actual products produced. Focus on:    QA aims to prevent defects with a focus on the process used to make the product. It is a proactive quality process. QC aims to identify (and correct) defects in the finished product. Quality control, therefore, is a reactive process. Goal:   The goal of QA is to improve development and test processes so that defects do not arise when the product is being developed. The goal of QC is to identify defects after a product is developed and before it's released. How:   Establish a good quality management system and the assessment of its adequacy. Periodic conforman...
Post a Comment
Read more