Action Points:

• Scrum Meetings alignments - Rafal
  • Sprint Review & Retro Tue: 11-12:15
  • Planning - as it is 30 min
  • Backlog Refinement - find a new slot.
• Clean product backlog - Nina, Didier, Daniel
• Acceptance Criteria - improve - Team (next Retro)
• Introduce: DoD - Rafal, Team (next Retro)
• Realign with estimations - Rafal, Team (next Retro)

Observations

Stories

• some of the stories are missing Acceptance Criteria, or
  • Acceptance Criteria
    • Implementation steps
    • Quality Assurance steps: code review, unit & functional testing, monitoring adjustments
    • Deployed in dev
    • OR :
      • Deployed in prod
      • Ready for deployment in prod + 1 story dedicated to this deployment ready to be refined
• Stories are not linked to the Epic
  • How do we work with Epics - we have plenty of them

‍How do we estimate?

Sprint progress

• “Burnup Chart” too often looks like this (pic)

• 1 day before end of the Sprint and nothing is in done column.
  • Do we have DoR or DoD?
• Backlog refinement
  • good that we have it

• How do we use Releases?
• Sprint planning
  • We plan too much for the Sprint. Why is that?
• Board
  • How do we use all the project boards?

‍

‍

Points to discuss:

• The team doesn’t use consistently epic template
  • Are we committed to use epic template?
    • Yes - we are using this template.
• Epic owner is responsible for the content of the epic including stories and tasks:
  • Anna - messy epic
  • Is Epic Owner role clear for you e.g. deliverables, responsibilities?
• Is it clear for us what each column on the board represents?
  • this is not "Implementation"
  • Can we implement something without development tasks?
• Transparency
  • Comment your epic week2week with the current status.
  • Should we create task for work not related to the epic?
    • Solutions: current board vs new board
  • Epics without tasks - is it ok?
    • Ok - we will keep it (not enforce).
• Documentation is stored in the Notion
  • Is this our standard that we want to continue?
  • How can we make it sure that it’s accessible for all the stakeholders?
  • In some cases we are using Gdrive, Figma, do we have/want to have rules for it?
    • Audience Goldbach & Goldbach neXT - we create documentation in Confluence.
    • We wait for the migration to the Goldbach Atlassian to make a final decision.
• Purpose statement for the meeting
  • timeboxing / park conversations for the further clarification
• Many items are in progress
• Flow Master role
  • What do you expect from me?
  • help productivity and reduce frustration
  • share good reads about team’s topics with insights
  • \help the team to be agile
  • protect flow and help to have flow
  • transitions on epic board - make sure we are following “the rules”

‍

‍

‍

‍

‍