Professional Documents
Culture Documents
SCRUM Differentiation
SCRUM Differentiation
different / unique
Shyam Singhal
Why SCRUM?
A belief
• - Small
Definition of work
working unit or
teams project
that structure is
maximize
communication,
dependent minimize
on the person’s overhead, and
understanding of Proj.
maximize
Mgmt. sharing
principles; of tacit,
CMMi do no informal
dictate theknowledge
size either
Adaptability
• -for team or
Change to unit.
work
Managementtechnical or marketplace
+ Product Architecture and
(user/customer)
Design changes
Capability; CMMi do not to have
ensure anythe bestin
saying
possible product is produced
either of those.
• Frequent "builds", +
- SDLC methodology orInternal adaptability
construction of to
project requirements
executables, that can be inspected, adjusted,
tested,
- Loose documented,
coupling and high and built on
cohesion – principle of
• architecture
Partitioningandof design;
work and should
team get translated into
assignments into
clean,
-WBS too.low coupling
Incremental partitions,
build, test, fix, regressor cycle;
packetsbasic
Constant
• principle testing and approach
of incremental documentation of a
product-as
- Each it is
incremtl. built
build should result in a “complete”
• Ability to declare a product "done" whenever
executable; of course with planned functionality for
required
given increment
06/04/08 SCRUM - What is different / unique page 5
SCRUM – Key Principles . . . Contd.
• The identification,
Risk key to the success of Scrum is and
prioritization, using measurements
MMM is the key
to maximize flexibility and risk while maintaining
– control.
CMMi do notprojects
Most restricttry
creativity
to avoid –risk.
Project defines
Yet, risk is an it
inherent part of software development. Scrum
embraces risk by identifying and managing risk-so that
the best possible
Delivery, Processes,product can be built.
Customer, and Employee – all
• A Scrum
are software
critical and project
Project / is controlled
Program by establishing,
Manager has to
maintaining, and monitoring key control parameters.
address those; are
These controls be it SCRUM,
critical whenCMMi, ISO, Six-Sigma, it
a software
development
really does not encompasses
matter. an unknown quantity of
uncertainty, unpredictable behavior, and chaos. Use of
these controls
Project is theand
Monitoring backbone
Controlofprovides
the Scrum you the
development process.
• framework to decide “what” needs to be monitored;
The variables in the systems development project are
how
risk,do you monitor
functionality, it, time,
cost, depends on the project.
and quality. These That
isvariables
why, in can
bestbe roughly estimated
managed projects, at the start of a
invariably
project. Each variable will start changing from the
monitoring
moment theisproject
one ofstarts.
the critical elements.
Variables are traded off
against each other as the project progresses (improved
functionality for later time and more money, etc.).
06/04/08 SCRUM - What is different / unique page 7
SCRUM – Controls Used
• Backlog - an identification
Requirements Management of –allTemplate
requirements that
/ Tool only
should be fulfilled in the completed product
facilitates
• Independent of methodology
Objects/Components used
- self-contained reusable things
• Packets - a group
Architecture of objects
/ Design within
principle which a backlog
– independent of
item will be implemented. Coupling between the
methodology used
objects in a packet is high. Coupling between packets is
Problem
low / Issue resolution – self correction –
• understand
Problems - that
whathelp
mustisbe
“available”
solved by a–team
independent
member toof
implement a backlog item within an object(s) (includes
methodology
Independent
bugs)
of any methodology
• Issues - Concerns that must be resolved prior to a
backlog item being assigned to a packet or a problem
being solved by a change to a packet
• Solutions - the resolution of an issue or problem
• Changes - the activities that are performed to resolve
a problem
06/04/08 SCRUM - What is different / unique page 9
SCRUM – Processes
page
06/04/08 SCRUM - What is different / unique
12
SCRUM - Cycle
• A Scrum project
Requirement starts with the
engineering customer’s
with vision of the
easy to understand
system. The vision maybe vague at first, stated in
communication aidsthan system terms. The vision will
market terms rather
become clearer as the project moves forward. A
Requirements
metaphor of theprioritization
system is alsoas per business
defined needs
to help guide
development and to provide a tangible communication
In nutshell,
model requirements
between customers and engineering
developers. “with”
An initial
vision and metaphor
customer, to address can be usually
business created in several
needs
days, if they aren’t already part of the customer’s
business
PoC plan. part
for “new”
• The customer and development team define
requirements /that
Incremental willapproach
spiral deliver thetohighest value
development,
business value from the vision. A prioritized list called a
rather
Productthan a monolithic
Backlog is created and
that rigid waterfall
consists of these
approach
requirements.
• The development team works for a short, fixed iteration
of thirty days (called Sprints) to create an executable
increment that contains the top priority business value.
The team selects as many requirements as they can
build during the Sprint. They only build the architecture
page
06/04/08 SCRUM - What is different / unique
14
SCRUM – Cycle . . . Contd.
page
06/04/08 SCRUM - What is different / unique
15
SCRUM – Cycle . . . Contd.
• The
It is acustomer
test more continues defining
for architecture requirements
/ design and
that willmanagement
change deliver highthanbusiness value. They
methodology. The are
added being
reason to themethodology
prioritized Product
suggestsBacklog. The
that changes
Product
should beBacklog
traceabledynamically
and change changes during
in vital attributes
the
of project
project as the
should be business conditions
as per impact analysischange
of the
and through
change. It doescustomer
not forbidresponse
change. to the product
increments created by the development
Review
teams. each iteration – whether with customer or
internal, it’s a project call. In fact, any S/W
• At the end of every Sprint, the customer
methodology suggests that validation and
reviews the working system increment
verification should be carried out, it does not put
any binding on “how” and “frequency”
page
06/04/08 SCRUM - What is different / unique
16
Key Learning