Introduction to Agile

Approach
“A good plan violently executed now is better than a
perfect plan executed next week” - General George S.
Patton
 History of Agile Manifesto

The agile movement officially began with the creation of the Agile Manifesto
in February 2001 (Beck 2001)

Agile Manifesto Value:

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

 Agile Project Approach

Work as a team

Work in short iteration

Delivering each iteration

Focus on Business Priority

Inspect and adapt

Onion Agile Planning
Agile Software Development Overview
Scrum Essential

Scrum is an agile approach for developing innovative products and

services

Scrum is based a small set of core values, principles, and practices

With an agile approach, you begin by creating a product backlog, a

prioritized list of the features and other capabilities needed to
develop a successful product
The work itself is performed in short, time boxed iterations, which
usually range from a week to a calendar month in length

During each iteration, a self-organizing, cross-functional team does all

of the work—such as designing, building, and testing—required to
produce completed, working features that could be put into
production
 Scrum Origin

Honda, Canon, and Fuji-Xerox produced world-class results using a

scalable, team-based approach to all-at-once product development in
1986
Scrum is not an acronym, but rather a term borrowed from the sport
of rugby, where it refers to a way of restarting a game after an
accidental infringement or when the ball has gone out of play
Scrum with concepts from object-oriented development, empirical
process control, iterative and incremental development, software
process and productivity research, and complex adaptive systems
 Why Scrum

Scrum can be use on software project that operated in a complex

domain where more was unknown than known

Scrum can be use to avoid big up-front architecture design

Scrum are more balanced approach to design, which included some

design up front combined with a healthy dose of emergent, just- in-
time design

Scrum make teams to be more cross-functional

 Scrum Benefit

Delighted customer

Improve return to investment

Reduce Cost

Fast Result

Confidence to succeed in a complex world

More Joy
Scrum Frameworks
Product Owner
Roles Scrum Master
Development Team
Sprint
Sprint Planning

Scrum Practice Daily Scrum

Activities Sprint Exec
Sprint Review
Sprint Retrospective
Product Backlog Grooming
Product Backlog

Artifacts Sprint Backlog

Potentially shippable
Rules
product increment
 Scrum Roles

Scrum development efforts consist of one or more Scrum teams, each

made up of three Scrum roles: product owner, ScrumMaster, and the
development team