LACE (CCSQ Lean Agile Center of Excellence)

Page tree

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

Compare with Current View Page History

« Previous Version 7 Next »

HCD Team


Daily Stand-Up 
Foundation 
  • Timebox: 15 mins daily
  • Purpose: Daily checkpoint to synchronize and collaborate on achieving the Iteration Goals.
  • Attendees: Agile Team members, SM, PO
  • Facilitator: SM
  • Preparation: Updated work management tool or team board
Meeting's flow

Each Agile team member answer the questions:

  1. What did I do yesterday to advance the Iteration Goals?
  2. What will I do today to advance the Iteration Goals?
  3. Are there any impediments that will prevent the team from meeting the Iteration Goals?
Recommended practices
  • Team member collaborates and synchronizes their work around the board 
  • Alignment across the work until the next business day is created
  • Risks/impediments blocking the team are surfaced
  • Potential impacts on cross-depending teams or work items are discussed
  • Stories/enablers are moved to "Done" when they pass the DoD 
  • Sprint Burndown is shown to assess the progress toward the completion of the sprint goal & commitment
  • 16th minutes topics or follow up actions are agreed
Notes from HCD Observations

DSU on  

  • Attendees: Rob Fay, Meaghan Hudak, Chelsea Brigg, Howard Montgomery, Amy Castellani. 
  • Status report from the team 
  • Several times Scrum Master was interrupted not being empowered for SM to play the role of Scrum Master
  • Scrum Master shared (16min) parking lot for further discussions
  • Great conversations about community and HCD and how they can plug into other areas. Artifacts and knowledge sharing, personas development
  • The parking lot turned into a sharing knowledge session where Chelsea shared the functionality of a new tool with HCD team 
  • No discussion about sprint goals
  • Metrics were not shared, burn down or progress toward meeting the sprint commitment
  • Dependencies or blockers seemed a bit unclear. 
  • The waiting column on kanban board doesn't appear to have WIP limits making it difficult to assess blockers or impediments. 






Iteration Retrospective
Foundation 
  • Timebox: (1-2) hours at the end of the iteration
  • Purpose: Provides Agile team the opportunity to reflect on the committed sprint and look for opportunities for continuous improvement, and cross-functionality. What is working well, any obstacles, and action items in user stories for the next sprint.
  • Attendees – SM and Team. PO is optional
  • Facilitator: SM
  • Preparation: Cadence has been scheduled and Retro Board shared with the team in advance. 
Meeting Flow

Each Agile team member is transparent about the below questions:

  • What went well during this iteration that the team should continue doing
  • What can be improved?
  • What are any obstacles? 
  • Scrum Master helps the team in discovery – not provide answers 
Recommended Practices
  • Did the meeting start on time
  • Did all the Agile Team attend the Retrospective
  • Did team members feel safe? 
  • Retro board created and visible for the team
  • Action items created as user stories for the next sprint 
  • Were the team members actively engage
  • Did the meeting end on time
  • The team is proud of their accomplishments and can celebrate
  • The event facilitated by the Scrum Master
  • Did the team has webcam cameras on at all times 
Notes from Retrospective Observations

2022-09-02 HCD PI20 S2 Retro • Tantus Tech (mural.co)


The Scrum Process


  • No labels