Lecture 1

Unit 3
Scrum Ceremonies:
• Sprint Planning: Sprint planning is an event where the team
determines the product backlog items they will work on during that
sprint and discusses their initial plan for completing those product
backlog items in the Scrum framework. This plan is created by the
collaborative work of the entire Scrum Team.
• Each sprint begins with a sprint planning meeting. For a one month
or four-week sprint this meeting should last eight hours. For a two-
week sprint, plan for about four hours. As a rule of thumb, multiply
the number of weeks in your sprint by two hours to get your total
sprint planning meeting length.
Daily Scrum Meeting:

• In Scrum, on each day of a sprint, the team holds a daily scrum meeting called
the "daily scrum.” Meetings are typically held in the same location and at the
same time each day.
• Ideally, a daily scrum meeting is held in the morning, as it helps set the context
for the coming day's work. These scrum meetings are strictly time-boxed to 15
minutes.
• The daily scrum meeting is not used as a problem-solving or issue resolution
meeting. Issues that are raised are taken offline and usually dealt with by the
relevant subgroup immediately after the meeting. During the daily scrum, each
team member answers the following three questions: 1. What did you do
yesterday?
2. What will you do today?
3. Are there any impediments in your way?
• Purpose of daily scrum: The purpose of the Daily Scrum is to inspect
and synchronize the team's progress towards the Sprint Goal for next
24hrs. Re-plan if needed the team's work to achieve the Sprint Goal.
• Daily Stand-up Characteristics
• Meeting takes place in the morning for 15 minutes
• Participants include all the scrum team members, especially the
scrum master and product owner
• The scrum meeting is usually not extended beyond 15 minutes with
all the people standing up
PBR

• Product Backlog Refinement, also referred to as Product Backlog

Grooming, is a method for keeping the backlog updated, clean and
orderly. It is a basic process in Scrum. PBR is a collaborative discussion
process which starts at the end of one sprint to confirm whether the
backlog is ready for the next sprint.
• The Objective of PBR meeting: A lot of time is saved at sprint planning
meetings, if the backlogs are well maintained
Sprint Review
• Sprint Review meeting is carried out once the Sprint has been done. It
is meant to inspect the Increment and adapt the Product Backlog if
necessary. When the Sprint Review meeting is taking place, the Scrum
team and stakeholders evaluate what has been done during the
Sprint.
• To ensure their success, sprint review meeting is held at the end of
each sprint. During the review, the Scrum team shows to the
stakeholders what they have accomplished by demonstrating the
newly designed features.
Scrum Sprint Planning:

• Sprint Goal
• The Sprint Goal is an objective set for the Sprint that can be met through
the implementation of Product Backlog. Sprint goals are the result of a
negotiation between the Product Owner and the Development Team.
Sprint Goals should be specific and measurable.
• Benefits of Sprint Goal:
• Provides guidance to the Development Team on why it is building the
Increment.
• Serves to test assumptions, address risks or deliver features
• Ensures a focused Daily Scrum because the Development Team can use it to
inspect their progress.
• Helps setting priorities when "the going gets tough”.
The goal for Sprint 1: “Show top-selling products on the homepage ”
• Sprint Backlog :
• Below are some of the items that ended up on the Sprint Backlog:
• Create HTML-based style guide based on visual design;
• Configure Bootstrap for basic styling elements in the homepage;
• Identify the 10 most important products for our shop and gather product details & images
• Set up and seed table for Products in the database with selected products
• Implement a page where visitors can see details of a selected product
• Test homepage in modern browsers;
• Implement basic “Call Me Back”-button for each product where potential customers can
leave their phone number behind;
• Deploy to production (multiple servers);
Sprint Goal Example 2:
Sprint Goal: Refactor our old login interface to achieve 25% better
conversion rate on the login page.
• Sprint Backlog Breakdown:
• Explore how five other products are handling logins.
• Rewrite two new login interfaces.
• User story: Support login using service X.
• Start A/B test.
Reference

• https://www.perforce.com/blog/hns/what-do-your-sprint-goals-really-n
eed-examples

• https://medium.com/the-liberators/examples-of-real-sprint-goals-670f
917ba2cd

• https://www.scrum.org/resources/blog/sprint-goal-template#:~:text=W
hen%20I%20started%20out%20in,Development%20Team%20during
%20the%20Sprint
.
User Stories
• A user story is a very high-level definition of a requirement, containing just
enough information so that the developers can produce a reasonable estimate of
the effort to implement it.
• User Stories Template:
• A user story template often uses the following type of format: As a , I want so
that .
• Example: As a user, I want to upload photos so that I can share photos with others.
As an administrator, I want to approve photos before they are posted so that I can
make sure they are appropriate.
• Estimate User Stories
• Agile emphasis to estimate a story in Story point instead of hours. What is a
Story Point? Story points represent the relative sizing of the user story. It is a
unit of estimation used by Agile teams to estimate User Stories.
• Definition of Done: In order to be able to decide when an activity from the
Sprint Backlog is completed, the Definition of Done (DoD) is used. In simple
terms, Definition of Done is a simple list of activities (writing code, coding
comments, unit testing, integration testing, release notes, design documents,
etc.) that add verifiable/demonstrable value to the product. It includes a
comprehensive checklist of necessary activities that ensure that only truly done
features are delivered, not only in terms of functionality but in terms of quality
as well.