Agenda

1. Introduction to Agile Methodology (Software Development Model)

2. Agile Process Models for Reference
3. Introduction to Scrum
4. Scrum Life cycle – Agile Model
5. Scrum Process Implementation / Practice
6. Scrum Metrics
7. Role Play - Real-Life Example / Sample Project
8. Artifacts / Videos for Reference
9. Q&A

Amazon Confidential
 Introduction to Agile Methodology (Software Development Model)

What are the known SDLC / Software Development Models ?

V model Incremental model
Waterfall model

Iterative model
Agile model
RAD model

Spiral model Prototype model

Amazon Confidential
 Introduction to Agile Methodology (Software Development Model)
Routine Software Development Model (Waterfall / V-Model)

Amazon Confidential
 Introduction to Agile Methodology (Software Development Model)

Agile Software Development

This is one of the simplest and effective processes to turn a vision for a business need into software solutions. Agile is
a term used to describe software development approaches that employ continual planning, learning, improvement,
team collaboration, evolutionary development, and early delivery. It encourages flexible responses to change. IT
promotes continuous iteration / incremental iterative approach.

This process emphasizes on the following core values.

 Individual and team interactions over processes and tools
 Working software over comprehensive documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan

Note: The term was coined in the year 2001 when the Agile Manifesto was formulated.

Amazon Confidential
 Introduction to Agile Methodology (Software Development Model)
Agile Process Flow
Concept – Projects are envisioned and prioritized
Inception – Team members are identified, funding is put in place, and initial environments and requirements are
discussed
Iteration / Construction – The development team works to deliver working software based on iteration requirements
and feedback

Release / Transition – QA (Quality Assurance) testing, internal and external training, documentation development, and
final release of the iteration into production
Production – Ongoing support of the software

Amazon Confidential
 Agile Process Models for Reference

Scrum – Scrum Master, Product Owner, Scrum Team, Sprint

Planning, Daily Scrum Meet, Product Backlogs, Backlog Grooming,
Retrospective Meet.

Crystal Methodologies – Chartering, Cyclic Delivery, Wrap Up.

DSDM – Time Boxing, MoSCoW Rules, Prototyping. It has 7 Phases

such as Pre-project, Feasibility Study, Business Study, Functional
Model Iteration, Design and build Iteration, Implementation, Post-
project.

FDD – Domain object Modeling, Development by feature,

Component/ Class Ownership, Feature Teams, Inspections,
Configuration Management, Regular Builds, Visibility of progress
and results

Amazon Confidential
 Agile Process Models for Reference

Lean Software Development – Eliminating Waste, Amplifying learning

, Defer commitment (deciding as late as possible), Early delivery,
Empowering the team, Building Integrity, Optimize the whole

Extreme Programming (XP) - The principles of XP include feedback,

assuming simplicity, and embracing change. The phases are Planning,
Analysis, Design, Execution, Wrapping, Closure

Kanban - Kanban, meaning “visual sign” or “card” in Japanese, is a visual

framework to implement Agile. It promotes small, continuous changes
to your current system. Its principles include: visualize the workflow,
limit work in progress, manage and enhance the flow, make policies
explicit, and continuously improve.

Amazon Confidential
 Introduction to Scrum - Agile Model
History:
Jeff Sutherland created the Scrum process in 1993, taking the term “Scrum” from an analogy in a 1986 study by
Takeuchi and Nonaka published in the Harvard Business Review. In the study, Takeuchi and Nonaka compare high-
performing, cross-functional teams to the Scrum formation used by Rugby teams. The original context for this was
manufacturing, but later adapted the model for software development.

Overview:
Scrum is a subset of Agile and one of the most popular process frameworks for implementing Agile. It is an iterative
software development model used to manage complex software and product development. Fixed-length iterations,
called sprints lasting one to two weeks long, allow the team to ship software on a regular cadence. At the end of each
sprint, stakeholders and team members meet to plan next steps. 

Scrum follows a set of roles, responsibilities, and meetings that never change. For example, Scrum calls for four
ceremonies that provide structure to each sprint: sprint planning, daily stand-up, sprint demo, and sprint
retrospective. During each sprint, the team will use visual artifacts like task boards or burndown charts to show
progress and receive incremental feedback.

Amazon Confidential
 Introduction to Scrum - Agile Model

When to Use Scrum ?

Recommendations to use Scrum if:

 The project requirements will change and evolve 

 Continuous feedback is required
 You have to figure out how to do a large part of the work because you haven't done it before
 You don’t need to commit to a fixed release date
 The project team wants autonomy
 You need to deliver software on a regular basis
 Scrum works well for projects that have a lot of unknowns or that evolve over time. Scrum deals with these
changes very effectively, so you can easily accommodate new information or features throughout the process.

Amazon Confidential
 Scrum Life Cycle – Agile Model
Scrum Roles
Scrum Master
Master is responsible for setting up the team, sprint
meeting and removes obstacles to progress

Product owner
The Product Owner creates product backlog, prioritizes
the backlog and is responsible for the delivery of the
functionality at each iteration

Scrum Team
Team manages its own work and organizes the work to
complete the sprint or cycle

Amazon Confidential
 Scrum Life Cycle – Agile Model
Steps in Scrum Process

Backlog Demo /
Grooming Retrospective
& Ranking Meeting

Amazon Confidential
 Scrum Process Implementation / Practice

Process flow of Scrum

 Each iteration of a scrum is known as Sprint

 Product backlog is a list where all details are entered to get the end-product
 During each Sprint, top user stories of Product backlog are selected and turned into Sprint backlog
 Team works on the defined sprint backlog
 Team checks for the daily work
 At the end of the sprint, team delivers product functionality

Amazon Confidential
 Scrum Process Implementation / Practice
User Stories: A user story describes a software feature from the customer’s perspective. It includes the type of user,
what they want, and why they want it. These short stories follow a similar structure: as a <type of user>, I want to
<perform some task> so that I can <achieve some goal.> The development team uses these stories to create code that
will meet the requirements of the stories.

Acceptance Criteria: Acceptance criteria are a formalized list of requirements that ensure that all user stories are
completed and all scenarios are taken into account. In simple words, acceptance criteria specify conditions under
which a user story is fulfilled.

Note: The terms “user stories” and “acceptance criteria” are used to ensure clear descriptions of how end-users
will use an app and how a team should fulfill each task.

Effort (Story Points Vs Hours):

 Story points rate the relative effort of work in a Fibonacci-like format: 0, 0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100.
 Story points reward team members for solving problems based on difficulty, not time spent. This keeps team
members focused on shipping value, not spending time.

Amazon Confidential
 Scrum Process Implementation / Practice

Process flow of Scrum

Epics are large bodies of work that can be
Task1
broken down into a number of smaller tasks Story 1
(called stories). Epic 1 Task 2
Initiatives are collections of epics that drive
Story 2
toward a common goal. Theme
Story 1
Themes are large focus areas that span the Epic 2
organization.
Story 2 Task 1

Amazon Confidential
 Scrum Process Implementation / Practice

Amazon Confidential
 Scrum Tools & Metrics
Scrum board: 
The Scrum board is usually divided into three categories: to do, work in progress, and done. The Scrum Team needs to
update the board throughout the entire sprint. For example, if someone comes up with a new task, he/she would
write a new card and put it in the appropriate column. 

Sprint Report:
Understand the work completed or pushed back to the backlog in each sprint. This helps you determine if your team
is overcommitting or if there is excessive scope creep.

Burndown Chart:
This chart represents all outstanding work. The backlog is usually on the vertical axis, with time along the horizontal
axis. The work remaining can be represented by story points, ideal days, team days, or other metrics. A burndown
chart can warn the team if things aren’t going according to plan and helps to show the impact of decisions. 

Velocity Chart:
Track the amount of work completed from sprint to sprint. This helps you determine your team's velocity and
estimate the work your team can realistically achieve in future sprints.

Amazon Confidential
 Real-Life Example / Sample Project – Role Play
The Management of the Wedding
Roles:
Product Owner Ranking & Backlog Sprint
Scrum Master Grooming: Planning:
Scrum Team Theme
Venue
Epic
Restaurant
Product Backlog: Stories
Wedding dress
Venue Tasks
Groom’s suite
Photographer Photographer
Flowers Flowers
Groom’s suit Rings
Wedding dress Demo & Retrospective:
Music  what was completed
Rings Gifts
Restaurant  what was not completed
Music  what impediments we had
Gifts  how to improve

Amazon Confidential
 Real-Life Example / Sample Project – Role Play

User Story Examples with Title & Acceptance Criteria

Story1:

Title:
As a fiancée, I want my wedding dress to be gorgeous in order to gain everyone’s attention towards me

Acceptance Criteria:
• The wedding dress has to cost less than 2.000€ (VAT included)
• It has to be white
• It has to be a short-sleeved wedding dress
• It has to be with strapless neckline, draped and decorated with embroidery
• The train of the wedding dress must be at least 65cm long
• Wedding dress arrangements can cost at most 150€

Amazon Confidential
 Real-Life Example / Sample Project – Role Play

User Story Examples with Title & Acceptance Criteria

Story2:

Title:
As a couple, I want the food to be spectacular so that all the invited guests leave satisfied with the food

Acceptance Criteria:
• The average cost per invited should not exceed 160€ (Tax included)
• Must have canapes, starter, first course, second course, dessert, coffee, shot and drink
• The wine has to be a Vegasicilia of the year 2003
• The second course must me sirloin steak done in a wood-fired oven

Amazon Confidential
 Artifacts and Videos for reference

Ted Talk:
https://www.ted.com/talks/bruce_feiler_agile_programming_for_your_family

Amazon Confidential