IT Knowledge Center

Page tree

Versions Compared

Old Version 18

changes.mady.by.user ABELIAN-ext, Sevak

Saved on

compared with

New Version Current

changes.mady.by.user LYAKH-ext, Marina

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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



IWASIECZKO-ext, Lukasz

Data Squad

Data Squad JIRA boardData 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
  •  30min-1h
  •  The Product Owner must set a sprint goal.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
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

DataLab Squad

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.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
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 
  •   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 here
  •  The Product Owner must set a sprint goal.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
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
  •  Duration here
  •  The product owner reviews what has been "Done" and what has not been "Done".
  •   The product backlog is reviewed.
Sprint retrospective
  •  Duration here
  •  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:

SolvExtract

SolvExtract board

Image Removed

  •  The length is (2 weeks)
  •  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 number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
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
  •  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






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

Image Added

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

Image Added



  •  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


Image Added



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

Image Removed

  •  The length is (2 weeks)
  •  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.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
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
  • 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

Usage

Transformation


Data
Usage
Transformation board

Image Modified



  •  
The length is (2 weeks) 
  • 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.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
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

System

Data Transformation


System board

NOT SCRUM

Image Modified

  •  The length is (2 weeks)







Jaiye-ext, Bola   

Pricing Data Lake

  Image Added



  •  Has consistent durations. (starts - ends on
Monday
  • Mondays)
  •  New sprints start immediately after the previous concludes is (true)
  •   A sprint goal is always set and is (
N/A
  • 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
  •  
30min.
  • 1 hour
  •  The Product Owner must set a sprint goal.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
Scrum daily
  •   The duration is 15 minutes.
  •  It is held every day
Scrum bi-weekly
  •   The duration is 15 minutes.
 It is held twice per week
  • .
  •  Detailed discussions, adaptations,
replannings
  • re-planning are outside this meeting.
  •  The scrum master ensures that the meeting takes place.
  •  The development team conducts the meeting.
Sprint review
  •  
60-90min.
  • 1 hour
  •  The product owner reviews what has been "Done" and what has not been "Done".
  •   The product backlog is reviewed.
Sprint retrospective
  •  
45-60min.
  • 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
is ABELIAN
  • 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
Scrum Master:

Jaiye-ext,

Sevak 

Squad name:

System

System board

Image Removed

  •  Kanban 
 

Bola   

Execution and Campaign

  Image Added



  •  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
  •  
N/A - Kanban
  • 1 hour
  •  The Product Owner must set a sprint goal
. The number of Product Backlog items selected for the sprint backlog, solely depends on the development team
  • .
.
Scrum
bi-weekly
daily
  •   The duration is 15 minutes.
  •  It is held
twice per week
  • every day.
  •  Detailed discussions, adaptations,
replannings
  • re-planning are outside this meeting.
  •  The scrum master ensures that the meeting takes place.
  •  The development team conducts the meeting.
Sprint review
  •  
60-90min.
  • 45 minutes
  •  The product owner reviews what has been "Done" and what has not been "Done".
  •   The product backlog is reviewed.
Sprint retrospective
  •  
N/A
  • 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

Jaiye-ext, Bola   

Pricing Data Lake
Price Optimisation

 

Image Removed
  •  The length is (2 weeks)

Image Added



  •  Has consistent durations. (starts - ends on
which days of the week
  • 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
  • 45 mins
  •  The Product Owner must set a sprint goal
. The number of Product Backlog items selected for the sprint backlog, solely depends on the development team
  • .
.
Scrum daily
  •   The duration is 15 minutes.
  •  It is held every day.
  •  Detailed discussions, adaptations,
replannings
  • 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
  • 30 minutes
  •  The product owner reviews what has been "Done" and what has not been "Done".
  •   The product backlog is reviewed.
Sprint retrospective
  •  
1h30
  • 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
is
  • 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

Bongiorno-ext, Alix 

PCF Jira BoardPCF Team Composition



  •  
The length is 3 weeks 
  • 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.
  •  The number of Product Backlog items selected for the sprint backlog, solely depends on the development team..
Scrum daily
  •   The duration is 15 minutes.
  •  It is held every day.
  •  Detailed discussions, adaptations,
replannings

CRM Services

Jira Board

TechEx

Jira Board

  • 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

BENETT-ext, Lou-Ann 

Squad Names

  • Lead & Sample
  • Tech Excellence Squad
  • CRM Services


    • This team will no longer exist

    Lead & Sample

    Jira Board

    Lead & Sample


    Image Modified

    Maintenance

    Tech Excellence Squad

    Image Removed

    CRM Services

    Image Removed


















    •  
    The length is (2 weeks) 
    • 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
    • 1 hour
    •  The
    number of Product Backlog items selected for the sprint backlog, solely depends on the development team
    •  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
    • 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

    Technical Excellence Squad

    BENETT-ext, Lou-Ann 

    TechEx

    Jira Board

    Maintenance - Technical Excellence 


    Image Added


    Tech Ex Mission statement is to work on Technical improvements based on release, make the system robust and align with Salesforce guidelines


    The team of Lou is the RUN team. With the managed services an outsourced provider.


    Dina Mendes - Proxy PO

    Julien Gasqueton - Security Lead & Analyst

    Mohan Devarapu - Tech Lead & Analyst

    Artur Alves - Tech Lead for Managed Services (CGI)

    Bartosz Borowiec - Architect / Developer

    Lukasz Kiwinski - Advance Administrator / Developer

    Manuel-Moya Ferrer - DevOps

    Valeriya KHrebtova - Release Manager & DevOps

    Lou-Ann Benett - Scrum Master


    •  Has consistent duration. (2 week/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 




    Susana Alves - Lead Business Analyst

    Leila Radjah - Business Analyst

    Nina Song - Business Analyst (Dedicated)

    Nikola Milic - Business Analyst (Dedicated)

    Helia Grilo - Lead Developer for Managed Services (CGI)

    Dina Mendes - Architect

    Josiane Peytraud - Lead Business Analyst

    Sandra Martins - Business Analyst

    Simona Roman-Croitoru - Technical Analyst

    Artur Alves - Tech Lead for Managed Services (CGI)

    Marta Machado - Lead Developer for Managed Services (CGI)

    Lou-Ann Benett - Scrum Master

    Image Added


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

    		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 (in Jira and Miro) 
    •  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

    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
    •  Development team expresses any blockers they may have encountered
    •  Scrum team is ensuring that there is transparency on the blockers
    •  Scrum Master ensures timebox is respected

    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 

    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
    •  The length is (2 weeks)
    •  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) 












    Corporate contents

    Community

    Feedback Form & Contacts