AGILE SCRUM

SOFTWARE DELIVERY FRAMEWORK

PAYTREN - 2019
 SOFTWARE DELIVERY PROSES

DESIGN MPV
AGILE
THINGKING BASIC

Explore the problem Build the Right thing Build the thing Right
WATERFALL VS AGILE
Scrum Agile

Scrum is a framework for developing, delivering, and

sustaining complex products

Scrum Concept consist of:

a. Scrum’s roles
b. Events and Rules
c. Artefacts
 Scrum’s Roles

Scrum
Stakeholders Team
(Marketing, Legal,
etc)
Feeder
Team

Product
The Scrum Team consists of a Product Delivery
Owner
Owner, the Development Team, and a Scrum
Master
Team
Scrum
Scrum Teams are self-organizing and cross-
Master
functional
Product
Owner
- Product owner is represents stakeholders and is the voice of the customer. Focused on understanding
business and market requirements, then prioritizing the work to be done by the engineering team.

- Product Owner Responsibities: Negotiates priorities, scope, funding, schedule.

- The Product Owner is the sole person responsible for managing the Product Backlog.
Writes user stories, requirements, ranks and prioritizes them, and adds them to the product backlog.

- Product Backlog management includes:

a. Clearly expressing Product Backlog items;
b. Ordering the items in the Product Backlog to best achieve goals and missions;
c. Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum
Team will work on next; and,
d. Ensuring the Development Team understands items in the Product Backlog to the level needed.

SCRUM’S ROLES
FEEDER TEAM PROSES

Feeder Team collaboration:

1. Product Owner
2. Stakeholder
3. Designer
4. Analyst
 SCRUM MASTER
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters
do this by helping everyone understand Scrum theory, practices, rules, and values.

Scrum Master Service to the Product Owner

Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible
Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value

Scrum Master Service to the Development Team

Coaching the Development Team in self-organization and cross-functionality
Helping the Development Team to create high-value products;
Removing impediments to the Development Team’s progress
Facilitating Scrum events as requested or needed

Scrum Master Service to the Organization

Leading and coaching the organization in its Scrum adoption;
Planning Scrum implementations within the organization
Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization

SCRUM’S ROLES
Product Owner & Scrum Master

Product Owner Scrum Master

Represents Stakeholders and Customers Scrum team

Focus Product Process

Strives for Business value Predictable, quality releases

Communicates Priorities, releases to stakeholders, Impediments, release readiness, tradeoffs to

tradeoff decisions, product metrics be made, process metrics

Product backlog Use cases & requirements Backlog refinement/grooming

Success Metrics User activity, Conversion & retention, Quality, Velocity, Predictability, Morale
Revenue, Cost, Quality, Velocity, Morale

SCRUM’S ROLES
Development Team

Development Teams have the following characteristics:

a. They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn
Product Backlog into Increments of potentially releasable functionality;
b. Development Teams are cross-functional, with all the skills as a team necessary to create a product
Increment;
c. Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed
like testing, architecture, operations, or business analysis; and,
d. Individual Development Team members may have specialized skills and areas of focus, but accountability
belongs to the Development Team as a whole.

Typically consists of 3 – 9 individuals with cross-functional skills. The Product Owner and Scrum Master roles
are not included in this count unless they are also executing the work of the Sprint Backlog.

SCRUM’S ROLES
Scrum Events
Scrum Events
Time-bound or on-going activities or meetings that keep the Scrum process moving and product development
churning.

Sprint

Scrum Event
Sprint planning
Daily Scrum
Sprint/Iteration Review
Sprint Retrospective

Backlog grooming

SCRUM EVENTS
Sprint
Sprint
The heart of Scrum is a Sprint, a time-box of one month or less during which a "Done", useable, and potentially
releasable product Increment is created. Sprints have consistent durations throughout a development effort.

Time-boxed effort restricted to a specific duration, fixed in advance, between 2 and 4 weeks.

During the Sprint:

a. No changes are made that would endanger the Sprint Goal;
b. Quality goals do not decrease; and,
c. Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is
learned.

2 week sprints x 12 sprints = 6

Day 10 months
Day 1

SCRUM EVENTS
Sprint Ceremonies Timeline

Sprint Start Sprint End

Sprint
Product Design Sprint Sprint
Showcase
Outlook Checkin Grooming Planning
& Retro

• Tuesday • Tuesday • Thursday • Tuesday • Tuesday

Week - 1 Week - 2 Week - 2 Week + 2

• Product Roadmap • UX Wireframe • Ticket Grooming • Ticket Sizing • End Product showcase
• Prioritization • UI Design • For Dev Team • Dev Team Review

Ceremonies are formal meetings at the beginning, end, and every day in between to drive agile development and
success in the current sprint

SCRUM EVENTS
Sprint Planning
When: At the beginning of a sprint for 1-2 hours per of weeks in the sprint.
Audience: This plan is created by the collaborative work of the entire Scrum Team (Product Owner, Development
team and Scrum Master)

Activity:
Topic One: What can be done this Sprint?
The Development Team works to forecast the functionality that will be developed during the Sprint.
The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would
achieve the Sprint Goal.
The input to this meeting is the Product Backlog, the latest product Increment, projected capacity of the Development Team during the Sprint, and
past performance of the Development Team

Topic Two: How will the chosen work get done?

Having set the Sprint Goal and selected the Product Backlog items for the Sprint, the Development Team decides how it will build this functionality
into a "Done" product Increment during the Sprint. Work may be of varying size, or estimated effort

SCRUM EVENTS
Daily Scrum – Daily Stand up
When: Once per day, typically in the morning, The Daily Scrum is a 15-minute time-boxed event for the
Development Team, and stand up!

Activity: Have each team member answer the following questions:

What did I complete yesterday?
What will I work on today?
Am I blocked by anything?

There's an implicit accountability in reporting what work you completed yesterday in front of your peers. No
one wants to be the team member who is constantly doing the same thing and not making progress.

SCRUM EVENTS
Sprint Review (Demo Session/Showcase)
When: At the end of a sprint for about 60 minutes.
Purpose: During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the
Sprint.

Activity:
1. The Development Team demonstrates the work that it has "Done" and answers questions about the Increment
2. Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
3. The Development Team discusses what went well during the Sprint, what problems it ran into, and how those
problems were solved;
4. Feedback from stakeholder to Scrum team

Exit Criteria: Action items resulting from sprint/iteration review. Revised Product Backlog that defines the
probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet
new opportunities.

SCRUM EVENTS
Sprint Retrospective
When: At the end of a sprint for about 60 minutes.

Purpose: The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for
improvements to be enacted during the next Sprint

The purpose of the Sprint Retrospective is to:

1. Inspect how the last Sprint went with regards to people, relationships, process, and tools.
2. Identify and order the major items that went well and potential improvements; and,
3. Create a plan for implementing improvements to the way the Scrum Team does its work.

POSITIVE – NEGATIVE - REWARD

SCRUM EVENTS
Continuous Backlog Grooming

The ongoing process of reviewing product

backlog items and checking that they are
appropriately prioritized and prepared.

Stories in the product backlog should be

clear and executable for scrum teams
once they enter sprints during sprint
planning.

Story writing & sprint backlog grooming

Product Outlook & Design Checkin

Scrum Artefacts
Product Roadmap (Product Backlog)

Our Product Roadmap is defined by a set of

prioritised Epics

Epics can be represented as story maps (aka

user journeys or scenario maps)

In general, all stories within the Epic must be

completed in order for those stories to be
released and advertised to the end user as a
feature

Story map: Goal + Activities + Tasks

Product Roadmap vs Sprint Backlog

EPIC STORY DELIVERABLE ITEM

As a Customer I want to transfer money As a Customer, I want

to someone in list book so that I don't to transfer money to a (An) Marked a contact as favourite
have to enter in Account # contact I have marked
as favourite

(API) Save a contact as favourite

As a Customer, I want
to transfer money to
someone by entering in
their list
(An) Remove a contact from
favourites

As a customer I want to
be aware if I'm trying to
transfer an amount
greater than my …
available balance
Sprint Backlog
Scrum Wall
Sprint Burndown
Summary
Sprint cycle

Sprint goals Sprint backlog development Sprint backlog grooming

* As a new user I want to be able to sign up

for Paytren using my Facebook account so
that I can start to use Paytren for transactions
* As Paytren user I want to be able to sign in
to my Paytren account using my registered
Facebook account
* As a Paytren user I want to be able to
purchase internet data packages so that I can
continue to use their services

Sprint planning

Sprint showcase Sprint delivery

Next sprint
Scrum References

http://en.wikipedia.org/wiki/Scrum_%28software_development%29

http://scrumguides.org - by http://scrum.org

http://www.scrumalliance.org/why-scrum

Scrum BTPN - Scrum OVO – Scrum Commonwealth Bank