SCRUM Meetings: Difference between revisions

From A Technological Wiki
Jump to navigation Jump to search
← Older editNewer edit →
VisualWikitext
imported>Unknown user
No edit summary
imported>Unknown user
No edit summary
Line 1: Line 1:
With SCRUM (literally "an ordered formation of players") we define a set of tasks that must be completed in a concrete time interval. The most common way is establishing which tasks are going to be done in a two-week-time period (Sprint) and materialize them in that time. If objectives could not be accomplished, it is necessary to analize what went wrong.


{{AttachmentsSectionStart}}
[[File:UserDocumentation_Knowledge_Central_KC_Project_Project_management_achieve_objectives_SCRUM_Meetingsimage-20250419-085840.png|760px|center]]
* [[Media:UserDocumentation_Knowledge_Central_KC_Project_Project_management_achieve_objectives_SCRUM_Meetingsimage-20250419-085840.png]]
* [[Media:UserDocumentation_Knowledge_Central_KC_Project_Project_management_achieve_objectives_SCRUM_Meetingsimage-20250419-085840.png]]


{{AttachmentsSectionEnd}}
These are the different meetings defined for each Feature development phase.


<span id="grooming"></span>
= Grooming =
In this meeting, features are presented to the departments leaders in order to have an approximate estimation of the cost of implementing the feature.
* departments:
** Product
** Design
** Development
** QA
* periodicity: Bi weekly
* duration: 1 hour
<span id="refinement"></span>
= Refinement =
Each department holds a meeting to present the feature to the team. All team members need to have clear what the feature is about, identify possible missing documentation and define a detailed time to complete the task.
* departments:
** Design
** Development
** QA
** Data
* periodicity: Bi weekly
* duration: 1 hour
<span id="sprint-planning"></span>
= Sprint planning =
It defines what will be done during the next sprint. It will include features that were not completed in the previous Sprint and the ones that Product want to start.
* departments
** Development
** QA
** Data
* periodicity: Bi weekly
* duration: 1 hour
<span id="daily"></span>
= Daily =
All employees that are in the development phase, need to be present in order to comment quickly the status of the development. If anything to discuss takes more than two minutes, make a separate meeting just after the daily.
* what comment
** what was done yesterday
** what will be done today
** possible impediments
* departments
** Product
** Design
** Development
** QA
** Data
* periodicity: daily
* duration: 1-2 minutes per team member
<span id="retrospective"></span>
= Retrospective =
Useful for identifying those aspects of the Sprint that have been good or bad in order to improve them in the next Sprints.
* departments
** Product
** Design
** Development
** QA
** Data
* periodicity: bi weekly
* duration: 2 hours
<span id="example-of-two-weeks-meetings"></span>
= Example of two weeks meetings =
{| class="wikitable" table-width="760" layout="default" ac:local-id="5b519a77-42ac-4640-b822-7c268cde2ed1"
|-
! '''Monday'''
! '''Tuesday'''
! '''Wednesday'''
! '''Thursday'''
! '''Friday'''
|-
| daily
| daily
| daily
| daily
|
|-
| Sprint planning
|
|
|
|
|-
|
|
|
|
|
|}
{| class="wikitable" table-width="760" layout="default" ac:local-id="11e24533-189b-4121-b68d-0bce7feac7ef"
|-
! '''Monday'''
! '''Tuesday'''
! '''Wednesday'''
! '''Thursday'''
! '''Friday'''
|-
| daily
| daily
| daily
| daily
|
|-
| Grooming
|
| Refinement
|
| Retrospective
|-
|
|
|
|
|
|}
  <!-- From bodyContent 1542815.mraw -->
  <!-- From bodyContent 1542815.mraw -->


Revision as of 09:58, 19 April 2025

With SCRUM (literally "an ordered formation of players") we define a set of tasks that must be completed in a concrete time interval. The most common way is establishing which tasks are going to be done in a two-week-time period (Sprint) and materialize them in that time. If objectives could not be accomplished, it is necessary to analize what went wrong.

These are the different meetings defined for each Feature development phase.

Grooming

In this meeting, features are presented to the departments leaders in order to have an approximate estimation of the cost of implementing the feature.

  • departments:
    • Product
    • Design
    • Development
    • QA
  • periodicity: Bi weekly
  • duration: 1 hour

Refinement

Each department holds a meeting to present the feature to the team. All team members need to have clear what the feature is about, identify possible missing documentation and define a detailed time to complete the task.

  • departments:
    • Design
    • Development
    • QA
    • Data
  • periodicity: Bi weekly
  • duration: 1 hour

Sprint planning

It defines what will be done during the next sprint. It will include features that were not completed in the previous Sprint and the ones that Product want to start.

  • departments
    • Development
    • QA
    • Data
  • periodicity: Bi weekly
  • duration: 1 hour

Daily

All employees that are in the development phase, need to be present in order to comment quickly the status of the development. If anything to discuss takes more than two minutes, make a separate meeting just after the daily.

  • what comment
    • what was done yesterday
    • what will be done today
    • possible impediments
  • departments
    • Product
    • Design
    • Development
    • QA
    • Data
  • periodicity: daily
  • duration: 1-2 minutes per team member

Retrospective

Useful for identifying those aspects of the Sprint that have been good or bad in order to improve them in the next Sprints.

  • departments
    • Product
    • Design
    • Development
    • QA
    • Data
  • periodicity: bi weekly
  • duration: 2 hours

Example of two weeks meetings

Monday Tuesday Wednesday Thursday Friday
daily daily daily daily
Sprint planning
Monday Tuesday Wednesday Thursday Friday
daily daily daily daily
Grooming Refinement Retrospective
Retrieved from "http://wikitechia.top/index.php?title=SCRUM_Meetings&oldid=774"