Scrum Notes
Scrum Notes
CERTIFICATIONS RPOCESS
OVERVIEW OF SCRUM
WHAT IS SCRUM
A SCRUM project involves a collaborative effort to create a new product/service/result as per Project
Vision Statement
Time
Cost
Scope
Quality
Organisational capabilities
Other constraints
BENEFITS OF SCRUM
SCRUM PRINCIPLES
PRINCIPLES:
SCRUM ASPECTS
SCRUM PROCESSES
OVERVIEW OF AGILE
What is Agile’
Agile is Possessing ability to create and respond to change to profit in a turbulent business
environment
Being adaptive to change, being flexible, ability to cope with change
Minimises risk involved with changes in the long term vision of a project
Adaptive methods for project management (iterative and incremental approach to develop and
deliver solutions in stages method, using feedback methods
Any industry facing rapid changes needs agile methodology to manage projects.
Agile technics
AGILE MANIFESTO
We are uncovering better ways of developing software by doing it and helping others do it. We value:
While there is value in the items on the right, we value items on the left more.
AGILE VS WATERFALL
WATERFALL AGILE
Scope Achieve max business value
Cost and schedule altered to ensure desired scope is Quality and constraints are altered to achieve max
achieved business value
Suitable for ordered and predictable projects in which Successful in current market marked by
all requirements are defined and estimated accurately unpredictability and volatility(inspect adapt cycles)
Most important Principle of Agile is satisfying the customer through early and continuous software
delivery. Working software is the primary measure of progress
KANBAN/LEAN METHOD- Visualisation of top priority items is used, and a pull system of work
assignment is used.
Achieving Working Software- Achieved by limiting W.I.P.
SCRUM- Value based prioritisation with production of shippable software with every sprint.
Sprint review meetings are held to demonstrate sprint features to the customer.
Achieving Working Software- Produced at end of each sprint.
EXTREME PROGRAMMING(XP)- Customers and developers work together to plan releases.
Achieving Working Software- Employs the No Technical Debt Strategy(TDD) & egoless
software.
DSDM- Builds on customer feedback for each iteration to converge on an effective business
solution.
Achieving Working Software- Deliver “good enough early” instead of “perfect too late”.
CRYSTALS- Employ early victory, walking skeleton, and frequent customer feedback to deliver
valuable software.
Achieving Working Software- Uses walking skeleton; automated tests, frequent
integration.
FEATURE DRIVEN DEVELOPMENT(FDD)- Develops client value-based features and uses short
ramp-up for modelling.
Achieving Working Software- Uses inspections and unit tests.