Scrum in Agile

PT. Barakah Teknologi Indonesia

at Happy CoCreative, September 2020
What is Agile?

Agile methodology is a practice that helps continuous iteration of

development and testing in the SDLC process. Agile breaks the
product into smaller builds.
In this methodology, development and testing activities are concurrent,
unlike other software development methodologies. It also encourages
teamwork and face-to-face communication. Business, stakeholders,
and developers and clients must work together to develop a product.
What is Scrum?

Scrum in Agile is a process that allows software development teams to

focus on delivering business values in shortest time by rapidly and
repeatedly inspecting actual working software. It focuses on
accountability, teamwork and iterative progress towards well-defined
goals. Scrum Framework usually deals with fact that requirements are
likely to change or mostly not known at the beginning of project.
 Roles

Product Owner Scrum Master Development Team

Artifacts
Ceremonies
Sprint
“A Good Product backlog is shaped like an iceberg: small items at the top,
bigger items below there, and who knows what under the waterline.”
Rumus bikin user story/product backlog
As a (role), I want (feature) so that (benefit).
Sprint Backlog
Sprint Backlog is a set of Product Backlog items
selected for the current Sprint, plus plans for
delivering product increments for achieving Sprint
goals. Sprint Backlog is the development team’s
expectation of what functions will be included in
the next increment and what work will be
required to deliver those functions.
Sprint Burndown Chart shows the cumulative
remaining workload in Sprint, which is a trend for
reflecting the status of workload completion. The
Y axis represents the remaining workload and the
X axis represents the Sprint workday.
A sprint planning meeting is conducted before the start
of a sprint. The purpose of this meeting is to determine
the sprint plan and set a sprint goal.
Sprint planning includes agreeing on the number of
backlog items in the sprint that is the responsibility of
the development team and as well as to define the goal
for the current sprint and sprint backlog.
• Uniknya sprint planning ini ada waktu meetingnya
• Kalo sprint 4 minggu maka rapat nya 8 jam kalo 3 minggu 6 jam begitu
seterusnya

Below are some of the benefits of running a successful Sprint Planning meeting:

• Enables the Team to agree on the sprint goal and commitment.

• Enables task discovery, sign up, prioritization and estimation
• Creates the platform to communicate dependencies and identify team capacity
to set and commit to an achievable sprint goal.
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. This keeps the discussion brisk but
relevant.
Stand up meeting
So at the end of each sprint, a sprint review meeting is
held. During this meeting, the Scrum team shows what
they accomplished during the sprint. Typically this
takes the form of a demo of the new features.
The sprint review meeting is intentionally kept very
informal, typically with rules forbidding the use of
PowerPoint slides and allowing no more than two
hours of preparation time for the meeting. A sprint
review meeting should not become a distraction or
significant detour for the team; rather, it should be a
natural result of the sprint.
Participants in the sprint review typically include the product owner,
the Scrum team, the ScrumMaster, management, customers and
developers from other projects.
The Sprint Retrospective occurs after the Sprint Review
and prior to the next Sprint Planning. This is at most a
three-hour meeting for one-month Sprints. The
retrospective session is basically an “improvement”
meeting held to find ways and means to identify
potential pitfalls, past mistakes, and seek out new ways
to avoid those mistakes, which are attended by all – the
product owner, scrum master, development team
members, and optionally with the stakeholders.
The Sprint Retrospective occurs after the Sprint Review
and prior to the next Sprint Planning. This is at most a
three-hour meeting for one-month Sprints. The
retrospective session is basically an “improvement”
meeting held to find ways and means to identify
potential pitfalls, past mistakes, and seek out new ways
to avoid those mistakes, which are attended by all – the
product owner, scrum master, development team
members, and optionally with the stakeholders.
Pros and Cons