Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 33 Next »

One line per scrum team should be added.


Scrum Team name/ SM name

Jira BOARD (link)

Where are sprints documented?

Team's composition (link)

Who is part of my team?

The User Story flowSprint validation

Sprint backlog



Scrum mastering


Scrum ceremonies


Product backlog



Data Squad JIRA boardData Squad



  • Has consistent durations. (starts - ends on Wednesday for one team and Thursday for the other)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (tracked in Jira and Confluence) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 30min-1h
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, replannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 30 min
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 45 min - 1h
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

DataLab Squad JIRA boardDataLab Squad
  • The length is (2 weeks)
  • Has consistent durations. (starts - ends on Wednesday for one team and Thursday for the other)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (tracked in Jira and Confluence) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 30 min
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, replannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 30 min
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 45 min - 1h
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

IWASIECZKO-ext, Lukasz

Labware LIMS Squad

Labware LIMS Squad JIRA Board

Labware LIMS Squad

NOT SCRUM

 
  • Kanban 





Scrum Master: ABELIAN-ext, Sevak 

Squad name:

SolvExtract


The creation of digital services webapps to provide value, insights and optimization on the Mineral and Metal Extraction processes at Syensqo with a focus on solvent extraction.

SolvExtract board

Jean-Philip Poulin: Product Owner

Zackary Therrien: Lead Developer

Annie Durand: Senior Developer

Emilie Vaudrin: Developer

Cassandre Pochet: Developer

Beatrice Lopez: Developer

Rachel Michaud: Developer

Grégory Paul: Project Manager

Todd Tupper: Data Architect (point to point connections, model of the data, basically "whatever needs to be done" ) 

Juan Mantilla: Application Owner (SME like)

Sevak Abelian: Scrum Master



  • Has consistent durations. (starts - ends on Monday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (N/A) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 60min.
  • The Product Owner must set a sprint goal.
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, replannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 60-90min.
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 45-60min.
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Scrum Master: ABELIAN-ext, Sevak 

Squad name:

SmartFloat


SmartFloat board



  • Has consistent durations. (starts - ends on Tuesday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (N/A) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 60min.
  • The Product Owner must set a sprint goal.
Scrum bi-weekly
  •  The duration is 15 minutes.
  • It is held twice per week
  • Detailed discussions, adaptations, replannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 60min.
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 60min.
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Scrum Master: ABELIAN-ext, Sevak 

Squad name:

Data Usage


Data Usage board




  • Has consistent durations. (starts - ends on Monday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (N/A) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 30min.
  • The Product Owner must set a sprint goal.
Scrum bi-weekly
  •  The duration is 15 minutes.
  • It is held twice per week.
  • Detailed discussions, adaptations, replannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 60-90min.
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 45-60min.
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Scrum Master: ABELIAN-ext, Sevak 

Squad name:

Data Transformation


Data Transformation board



  • Has consistent durations. (starts - ends on Monday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (N/A) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 30min.
  • The Product Owner must set a sprint goal.
Scrum bi-weekly
  •  The duration is 15 minutes.
  • It is held twice per week.
  • Detailed discussions, adaptations, replannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 60-90min.
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 45-60min.
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Scrum Master: ABELIAN-ext, Sevak 

Squad name:

System


System board

NOT SCRUM








Pricing Data Lake

 



  • Has consistent durations. (starts - ends on Mondays)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (Jira) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 1 hour
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-planning are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 1 hour
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 1hour
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner and Business Analysts are responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Execution and Campaign

 



  • Has consistent durations. (starts - ends on Mondays)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (Jira) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 1 hour
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-planning are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 45 minutes
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 45 minutes
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Price Optimisation

 



  • Has consistent durations. (starts - ends on Mondays)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (Jira) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 45 mins
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-planning are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 30 minutes
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 20 minutes
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner and Data Scientists are responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

PCF Jira BoardPCF Team Composition



  • Has consistent durations. (starts on mondays - ends on fridays)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (in Jira Sprint goals) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 1 hour
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-plannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 1 hour
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 1h30
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

Squad Names

  • Lead & Sample

Lead & Sample

Jira Board



















  • Has consistent weeks duration. (starts on Monday- ends on Friday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (tracked in Jira) 
  •  Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
  • min
  • Frequency - everyday, except the days of Demo, retro and Planning

Backlog Refinement

  • Duration - 45 min
  • Frequency - once a week
  • POs review the stories from



Technical Excellence Squad

TechEx

Jira Board

Maintenance - Technical Excellence 



  • Has consistent duration. (starts on Monday - ends on Friday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (WIP) 
  • Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.

 Sprint Planning

  • 1 hour
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-planning are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 1 hour
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.Sprint retrospective
    • 1h
    • It takes place after the sprint review and before the sprint planning.
    • The meeting is positive and productive.
    • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready

CRM Services

CRM Services

Jira Board

Maintenance - CRM Services 



  • Has consistent duration. (starts on Monday - ends on Friday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (WIP) 
  • Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.

Sprint Planning

  • 1 hour
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-plannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 1 hour
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 1h
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.


Squad - MSP team

Scrum Master - LYAKH-ext, Marina 

MSP Jira board

MSP team mission is to provide customers with innovative and user friendly tools that will ease their digital journey and help company to save time and money while working together as a team and having fun in a process.

Squad composition (invited in all Scrum events):

  • Product Owner - Aude Trepier
  • Project manager - Jessica Ternier (data tasks related with PIM)
  • Lead Analyst - Gonçalo Silva
  • Developer - Andre Vieira
  • Developer - Jose Fischer (split 50/50 with Lead&Sample team)
  • Scrum Master - Marina Lyakh

Team participants on request:

  • Architect - Dina Mendes
  • Tech Lead - Mohan Devarapu
  • Security - Julien Gasqueton
  • Release Manager - Valeria Khrebtova



  • Has consistent durations. (starts on Monday - ends on Friday)
  • New sprints start immediately after the previous concludes is (true)
  •  A sprint goal is always set and is (WIP) 
  • Makes visible all the work to meet the sprint goal.
  •  Must have at least one improvement plan identified in previous sprint retrospective.
  • Only the development team manages the sprint backlog.
  • It must represent a live picture of the work done and remaining.
  • All items must meet the definition of done before are considered finished
  • Promotes and supports the scrum process.
  • Helps everybody to understand the Scrum theory, practices, rules and values.

Helps product owner to:

  •  Ensure that goals, scope and domain are understood by everyone.
  • Find techniques to maintain product backlog effectively.
  • Facilitate scrum events as requested or needed.

Helps development team to:

  • Remove progress blockers.
  • Facilitates scrum events as requested or needed.

Helps the organization to:

  •  Lead and coach in scrum adoption.
  • Work with other scrum masters to increase scrum effectiveness.
Sprint Planning
  • 1 hour
  • The Product Owner must set a sprint goal.
Scrum daily
  •  The duration is 15 minutes.
  • It is held every day.
  • Detailed discussions, adaptations, re-plannings are outside this meeting.
  • The scrum master ensures that the meeting takes place.
  • The development team conducts the meeting.
Sprint review
  • 1 hour
  • The product owner reviews what has been "Done" and what has not been "Done".
  •  The product backlog is reviewed.
Sprint retrospective
  • 1h
  • It takes place after the sprint review and before the sprint planning.
  • The meeting is positive and productive.
  • Create a plan to improve how the scrum team works.
  •  The product owner is responsible for its content, availability and ordering.
  • Product backlog refinement  takes place iteratively.
  • The items on top (higher priority) must be clear and meet the definition of ready












  • No labels