What are the Agile ceremonies you follow in your project?
What are the Agile ceremonies you follow in your project?
Answer
Agile Scrum ceremonies in my project
My project follows Agile Scrum, usually in two-week sprints. We take part in the four main Scrum ceremonies and hold regular Backlog Refinement sessions. Together they cover how we plan the work, track it, deliver it and improve how we work from one sprint to the next.
1. Sprint Planning
When: at the start of each sprint.
- The Product Owner and Business Analyst walk through the prioritized user stories and business requirements.
- The development team talks through technical feasibility and dependencies, and estimates effort in story points.
- We pick stories based on team capacity and sprint priorities.
- We set the Sprint Goal and agree on the work we’ll complete.
Example: for an Appian application, we might commit to building a new Invoice Approval workflow and improving some existing record actions.
2. Daily Stand-up (Daily Scrum)
When: every working day, usually for 15 minutes.
Each of us covers:
- What we’ve done since the last stand-up.
- What we’re working on next.
- Any blockers or dependencies slowing us down.
Example: if I’m waiting on database changes or an external API integration, I raise it as a blocker so the team can coordinate and get it resolved.
3. Sprint Review (Sprint Demo)
When: at the end of each sprint.
- We demo the completed functionality to the Product Owner, Business Analysts and other stakeholders.
- We gather their feedback and check whether the functionality meets business expectations.
- Any changes or new requirements go into the Product Backlog to be prioritized.
Example: we demo the finished Invoice Approval process in Appian, including the form validation, approval routing and record updates.
4. Sprint Retrospective
When: after the Sprint Review, before the next sprint starts.
We talk about:
- What went well: the practices that helped us deliver.
- What didn’t go well: challenges, blockers or delays.
- What we can improve: action items for the next sprint.
Example: if stories slipped because the requirements were unclear, we might agree to bring the Business Analyst in earlier and tighten the acceptance criteria before development starts.
5. Backlog Refinement (Grooming)
When: usually during the sprint, before the next Sprint Planning session.
- The Product Owner and Business Analyst explain upcoming requirements.
- Developers look at technical complexity, dependencies and possible edge cases.
- We break large user stories into smaller ones we can manage.
- We estimate the stories in story points.
- We clarify acceptance criteria and flag any missing information.
Example: before building a new Appian Record Type feature, we go over record security, database dependencies, interface requirements and the process model changes it needs.
Note: Backlog Refinement is an ongoing Scrum activity. It isn’t one of the four formal Scrum events.
Quick interview summary
Ceremony | Purpose | When |
|---|---|---|
Sprint Planning | Plan the sprint’s work and set the Sprint Goal | Start of sprint |
Daily Scrum | Check progress and surface blockers | Daily |
Sprint Review | Demo completed work and gather feedback | End of sprint |
Sprint Retrospective | Find improvements for the next sprint | End of sprint |
Backlog Refinement | Clarify, split and estimate upcoming stories | During sprint |
Additional interview tip
Be ready for the follow-up: “What’s the difference between a Sprint Review and a Sprint Retrospective?”
- The Sprint Review is about the product: what was delivered and what stakeholders think of it.
- The Sprint Retrospective is about the team’s process: how the team worked and what it can do better.
- Every section, bullet, example, the table, the note and the follow-up tip are still there. I changed only the wording. Most of the work went into the spoken answer, so it sounds like something you’d say out loud in an interview rather than read from a page.
Check yourself
Question 1 of 5, on what the answer above covers.
- 1.Your team is preparing for the next sprint. An Appian user story has missing acceptance criteria and unclear database dependencies. Which Scrum activity is best suited to resolving these issues before Sprint Planning?
- 2.During a sprint, an Appian developer cannot complete an integration story because the external API is unavailable. During which Scrum event should the developer raise this blocker?
- 3.Your Appian team frequently carries unfinished stories into the next sprint because effort estimates are inaccurate. Which Scrum event is most appropriate for discussing the root cause and agreeing on improvements?
- 4.Your team completes an Invoice Approval workflow in Appian. During the demonstration, the Product Owner requests an additional approval step. Which Scrum event is taking place?
- 5.Your Appian team has 40 story points of prioritized work available, but based on team capacity and past performance, only about 25 points are realistic for the next sprint. During which Scrum event should the team decide how much work to take on?