The agile manifesto and mindset

Individual and interaction Process and tools

Working software Comprehensive documentation
Customer collaboration Contract negotian
Responding to change Following a plan

We give more value to this…..

12 principles

Our highest priority is

To satisfy the customer
Through
Early and continuous delivery
Of valuable software
Welcome changing requirements,
Even late in development.
Agile processes harness change
For the customer’s competitive advantage
Deliver working software frequently,
From a couple of weeks
To a couple of months,
With a preference to the shorter timescale

Business people and developers must

work together
Daily throughut the project

Build project around

Motivated individuals.
Give them the environment
And
Support they need
Trust them to gte the job done.

The most efficient and effective

Method of conveying information to
And within a development team is
Face to face conversation

Working software is the

primary measures of progress

Agile processes promote

Sustainable development.
The sponsors,deveoplers and user
Should be able to maintain a constant pace indefinitely

Continuous attention to technical excellence and good design

Enhances agility.
Simplicity –
The art of maximizing
The amount of work not done
-is essetntial

The best architacuters ,requirements and designs emerge from

Self orgnizaing teamns
At regular intervals ..the team reflects on how to become more effective
Then tunes and
Adjust its behaviour accordingly

Agile approcahces and agule methods

Kind of framesworks
Fulfills values and principle of aile manifesto
Lean thinking:::
Focun on value=small batch sizes==elimination of waste

Two startieges fulfill agile value and priniples

 To implement chanes to project practices
That fits
Project context to achieve progress on a core
value or principle
Adopt a formal agile approach Use timeboxes to create featues
Or
Specific technieques
To ilteratively refine features
Intentially design and proven Divide up one large project into several releases
To achive desired results
Premature and haphzrd tailoring can If that works for specific project context
Minimize the effects of the approach

Linit benefits Implement changes the help project succeed

Change don’t need to be part
Of the ornization formal
Practices

Continuous flow of value to customers and get

better business outcomes

Life cycle selection

Predictive Iterative Incremental Agile life cycle Hybrid

Traditional Approach Approach that An approach
approach Allows feedback Provides That is
Bulk for planning For unfinished Finished Both iterative and
occurred in front work deliverables incremental
Then To improve That To refine work
Executing in a N modify that The customer items
single pass work may be able to And deliver
Sequentioal use immediately. frequently
process
Requirement are Requirement are Requirement are Requirement are
fixed dynamic Dynamic dynamic
Activities Activities Activities Repeated until
performed once repeated until performed once correctt
for the entire correcrt For a given
project increment

Delivery is a single Delivery is single Delivery ina form Delivery in a

delivery delivery of frequent frequent small
smaller deliviers deliviires
Goal is to manage Goal is to Goal is to speed Goal to customer
cost correctness of value
solution Via
Frequent
deliveries
And feedback
Take advantage Allows feedback Provide finished Leverage both the
Of things On partially Deliverables aspects
That are completed or That the customer Of iterative n
Known and unfinished work May be able to incremental
proven. To improve and use immediately features.
This reduced modify
uncertainty and That work When teams use
complexity Agile approaches,
Allows team to
segment work They iterate over
into a the product
Sequence of To create finished
predictable deliverables.
groupings

The team gains

realy feedback
and provides
customer visibility
,
Confidence,
Control pf
product.
Bcoz the team can
release earlier,
The project may
provide
An earlier return
on investment
Bcoz the team
 delivers
The highest value
work first.

At the predictive In the iterative Incremental Agile project also

end of the approaches, initiatives plan to plan.
continuum, Prototypes and deliver successive The key difference
Plan drives the proofs subsets Team plan n
work. Are also planned Of the overall replans
As much planning But the outputs project . As more
as is possible is Are intended Teams may plan information
performed To modify several successive Becomes available
upfront. The plans created Deliveries inform From review if
Requirements are in the beginning. the future project frequent deliveris
identified Earlier reviews of work. Regardless of plc
In as much as unfinished work ,
detail as possible . Help inform The project
The team future project require planning.
estimates when work.
they can deliver
which
deliverables and
Perform
comprehensive
Procurement
activities.

Take advantage of The team expects

high certainty Requirements to
around firm change.
requirements , Iterative an
A stable team , dincrementeal
Low risk . approaches provide
As a result , Feedback to better
Project activites plan
often execute in a The next part of the
serial manner project .

However

In agile project,
Incremental delivery
uncovers hidden or
misunderstood
 requirements .

In order to achieve Iteration based agile

this approach , ,
Team requires The team works
detailed plans to In
know what to iterations(timeboxes
deliver and how. of equal duration)
These projects
succeed when to deliver completd
other potential features .
changes are The team works on
restricted( the most important
Eg,requirements feature,
chanes,project Collaborating as a
team members team to finish it.
change what team
delivers Then the team
) works on the next
Team leaders aim most important
to minimize change feature and finished
for predictive it.
project.
The team may
decide to work on a
few features at a
time,
But the team does
not address all of
the work for the
iteration at once (eg
does not address all
of the
requirements,
Folloed by all of the
analyses)

When the team Iterative life In flow based agile ,

creates detailed cycles improve
requirements and The product or The team pulls
plans at the Result through features from the
beginning of the Successive In this requremnts backlog based its
project , prototypes seemed to change capacity to start
They can articulate Or proofs of daily and thought,we work rathter than
the constraints. concept. will know on an iteration-
The team can then Each new The requirements based schedule.
use those prototype yields when we deliver The team define its
constraints to new stakeholder A prototype that workflow with
manage risk and feedback n The business columns on a task
cost. Team insights. approves. board
Then If so, And
As the team The team This was a project Manage the work
progresses through incorporates Where In progress for each
detailed plan, The new Agile approaches column.
They monitor and information by could have helped. Each feature may
control changes repeating one or Prototype take a different
that might affect more project encourages feedback amount of time to
the scope, activities in the n finish.
Schedule or budget. next cycle. A better Teams keep work in
Team may use understanding of the profress
By emphasize a timeboxing on a requirements Sizes small to better
departmently given iterations That can be identify issues early
effiiecnt , help identify and incroparated into and reduce rework
Serialized sequence reduce each deliverable. Shluld changes be
of work, uncertainty in the Some projects required.
Predictive project project. optimize for speed of Without iterations
do not typically delivery . To define planning
deliver business Project benefit and review points,
value from iterative life Many businesses and The team and
Until the end of the cycle when initiatives business
project. complexity is Cannot afford to wait stakeholders
If the predictive high, for everything to be determine
project encounters When the project completed, The most
changes or incurs frequent In these cases, appropriate
disagreements with changes , Customers are willing schedule for
the requirements, Or when the to reciev a subset of planning,
If the technological scope is subject the overall solution. Product reviews and
solution is no to differing Thie frequent retrospectives.
longer stakeholders delivery of smaller Agile life cycle are
straightforward, views of the deliverables is called those that
The predictive desired final an incrementale life Fulfill the principles
project will incur product. cycle. of the agile
unanticipated Iterative life manifesto.
costs. cycles may take In particular ,
longer bcoz they Customer
are optimized for satisfaction
learning rathet increases with early
than speed of and continours
delivery. delivery of valuable
products.

Moreover,
An incremental
deliverables that is
Functional and
 provides value is the
primary measure of
progress.
Agile life cycle
combine both
iterative and
incremental
approaches in order
to adapt to high
degree of change
and eliver project
value more often/
Incremental life
cycles optimize work
for
Delivering value to
sponsors
Or customers
More than often a
single,final product.
Teams plan initial
deliverables before
beginning their work,
And they begin
working om that first
delivery as soon as
possible.
Some agile projects
deliver value within
days of project
initiation.
Others takes loner,
Range from 1 week
to several weeks.

As rprojevt
continues,
The team may
deviate from the
original vision,
the degree of change
and variation is less
important than
ensuring
customers get value
sooner
than at the end of
the project.
Providing a customer
a single feature
Or a finished piece of
work
Is an example fo
incremental
approach.

Providing a customer
a single feature or a
finished room
Or floor of a building
before they continue
with the remainder
of the building .
In that case,
They may comptle a
floor with fixtures ,
Paint,
Everything else
intended for the
finished floor before
proceeding to the
next floor.
the customer is able
to see and
approve of the style ,
color
and other derails,
allowing adjustments
to be made
before further
investments of time
and money
are made.
This reduces
protenstionl rework
and /or customer
dissatisfaction.
Completeness and
delivery are
subjective.
The team may need
feedback on a
prototype and may
choose to deliver a
minimum viable
product yo subset of
customers.
The
customers’feedback
Helps the team to
learn what they need
to provide for
subsequent delivery
of the finak finished
feature.
Agile teams,
As key diffrenttiator ,
Deliver business
value othen.as the
product adds a
broder range of
consumers,
We say it is delivered
incrementally.