• 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

• 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

• 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

• 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

• 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

• 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

• Has consistent durations. (starts - ends on which days of the week)
• 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, replannings 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

• 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, replannings 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
• Tech Excellence Squad
• CRM Services

CRM Services

Jira Board

TechEx

Jira Board

Lead & Sample

Jira Board

Maintenance

Tech Excellence Squad

CRM Services

• 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.

Sprint Planning

• Duration 45 min
• Frequency - once every two weeks
• PO sets the Sprint goals
• Development team does estimation for the stories for the sprint
• Scrum Master prepares the presentation for Demo, retro,  Planning and reports
• Scrum Master reviews the backlog with PO and sprint goals before Sprint Planning
• Scrum Master ensures that the capacity is at 80% to provide bandwith for the sprint
• Scrum Master is facilitating the meeting and ensures that timebox is respected

Scrum Dailys

• Duration 15 min
  
• Frequency - everyday, except the days of Demo, retro and Planning
• Scrum Master is making team is attending
• Scrum Master facilitates the meeting and helps the team gets focus on the topics at hand
• Development team talks about the work from the day before, the day of and the day after
•  

Backlog Refinement

• Duration - 45 min
  
• Frequency - once a week
• POs review the stories from the backlog based on complexity with Development team for future Sprints
• Scrum Masters ensure that the meeting stays on topic and timebox is respected
• Based on the Stories, BAs and Devs provide high estimation to be reviewed during Sprint Planning
• Scrum Team ensures that stories are under Qualified status before the sprint starts

Sprint Demo / Review

• Duration 45 min
  
• Frequency - Once every 2 weeks
• The product owner reviews what has been "Done" and what has not been "Done".
•  The product backlog is reviewed.
•  

Sprint Retrospective

• Duration 45 min
  
• 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.
• Scrum Master ensures that the environment is safe for the team to express their feedbacks and concerns
• Scrum Master ensures that there is transparency and timebox is respected
• Scrum Master ensures that previous actions agreed on from previous goals have been implemented

•  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 - MSP team

Scrum Master - LYAKH-ext, Marina 

• 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)