Agile Ceremonies

AGILE ROLES🤔

 

ROLES

 

  • Product Owner

  • Scrum Master

  • Development Team

 

     Dev Team Characteristics

  • Self-organizing
  • Cross-functional and with all the skills
  • No titles for Dev Team members, regardless of the work being performed by the person
  • No sub-teams in the Dev Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis......
  • Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole.
 

AGILE CEREMONY🤔

AGILE CEREMONY

  • Daily Stand-up

  • [Backlog Refinement]

  • Sprint Planning

  • Sprint Review

  • Retrospective

Daily Stand-up

 

WHY NEED TO STAND UP

 

Stand up helps keep meeting short (< 15 mins)

WHY

 

Specifically for the benefit of the dev team.

 

The goal of this event is for the team to get in sync on a daily basis, allowing for better collaboration and transparency

HOW

 

  • What did I achieve yesterday to help us meet our sprint goal?

  • What do I hope to achieve today to help us meet our sprint goal?

  • Do I see any impediments that prevent me or my team from achieving our sprint goal?

  • Owner Rotation

 

[Backlog Refinement]

WHY

 

Determine "What" the team will be working on

 

 Pulling tickets from Backlog

into Sprint Backlog

 

HOW

 

  • PO comes to prioritize the list of items

  • Discuss the story details with the team

  • Go throw the tickets in the sprint backlog before the meeting(separate ticket)

  • Ask questions if you have any concern or suggestions

  • Raise the TI tickets which is high priority or you want working on (10%)

 

Sprint Planning

Two weeks sprint kick off

on Wednesday 

WHY

 

Dev Team determines "How" they will accomplish the work that's been pulled into the Sprint Backlog

 

HOW

 

  • Go throw the tickets in the sprint backlog before the meeting

  • BA comes to present the list of items and discuss with dev team

  • Ask questions if you have any concern or suggestions

  • Estimation

  • Sprint Goal
 
 

Sprint Review

Last day of the sprint 

WHY

 

Provides a space for the team to congratulate themselves on a successful sprint

sCan provide feedback and also get feedback from the PO and stakeholders

 

HOW

 

  • Invite designers if needed

  • Prepare the showcase with what we have done in the sprint

  • Showcase Owner can be team togather

  • Provide feedback and also ask feedback from the PO/stakeholders

 
 

Retrospective

After sprint review

WHY

 

Make sure the

product and development culture is constantly improving

from one sprint to the next

 

HOW

 

  • Review last time retro actions

  • What went well over the last sprint?

  • What didn’t go so well?

  • What could we do differently to improve?

  • Document in wiki based on the rotation

  • Remind action owners

 
 

Others

 
 

THANKS

Made with Slides.com