Agile Scrum Ceremonies

Abstract

Many of us are very familiar with the inputs, tools, techniques, and outputs (ITTOS) of traditional project management in a Project Management Institute way. I am making an attempt here to map the Scrum model into ITTOs for anyone’s understanding and easy implementation.

Introduction

To become expert in any system, one must understand the ecosystem by knowing the inputs to the system, the tools and technologies used to process the inputs, and finally the outputs of the system. In the Agile/Scrum delivery model we have various inputs, tools, and technologies to process, and finally there will be outputs.

Scrum in nutshell

Scrum suggests three roles: the team, ScrumMaster, and product owner; four ceremonies: the sprint planning meeting, Daily Scrum, sprint review meeting, and sprint retrospective meeting; and three artifacts: the product increment, product backlog, and sprint backlog. We will try to understand the various elements that support these ceremonies in terms of ITTOs. The complete Scrum team attends all the ceremonies except the retrospective, which the product owner may or may not attend.

Sprint planning meeting

Timebox: Eight hours for a four-week sprint, proportionately shorter for shorter sprints
Attendees: The complete Scrum team, including all roles
Most important: Team capacity and DoD (Definition of Done)

Daily Scrum

Timebox: Fifteen minutes is standard, irrespective of the duration of the sprint length
Attendees: The complete Scrum team, including all roles
Most important: To speak about any impediments

Sprint review meeting

Timebox: Four hours for a four-week sprint, proportionately shorter for shorter sprints
Attendees: The complete Scrum team, including all roles, plus any other stakeholders who are interested in the project success
Most important: Demo of working software and assessing the feedback

Sprint retrospective meeting

Timebox: Three hours for a four-week sprint, proportionately shorter for shorter sprints
Attendees: The complete Scrum team, including all roles; the product owner’s attendance is optional
Most important: To brainstorm and agree on what is working and what is not

Conclusion

I think this helps map Scrum for those familiar with PMI, and any PMP can easily relate the concepts of Agile/Scrum that would be useful in transitioning from a Waterfall delivery model to an Agile delivery model. These ITTOs can be extended to a few other Scrum practices, such as Sprint Zero, Sprint H, and a mid-sprint health check. As these best practices are not prescribed in the Scrum framework, I do not focus on them here.