Agile Whiteboard - V1.0-To Be Sent

What is Agile
Agile Transformation : Vision and Mission

4
Agile Values
1.Individuals and Interactions Over Processes and Tools
“Individuals and interactions over processes and tools” is the first
value in the Agile Manifesto. It basically refers to valuing
individuals more highly than processes or tools because it is
individuals who respond to the business/customer needs and take
the process forward.
Tip: Make sure that communication is fluid and happens when a

need arise
5
Agile Values
1.Individuals and Interactions Over Processes and Tools
It basically refers to valuing individuals more highly than processes
or tools because it is individuals who respond to the
business/customer needs and take the process forward.
Tip: Make sure that communication is fluid and happens when a

need arise
6
Agile Values
2.Working Software Over Comprehensive Documentation
• Documentation is an important part of Agile manifesto – but
working software is even more important.
• The Agile approach focuses on streamlining data (technical
specifications, technical requirements, technical prospectus,
interface design documents, test plans, etc) so that the team
can begin and keep up the pace at work without getting bogged
down into the details.
Tip: Ditch manual documentation and consider an automated file

management system.
7
Agile Values
3.Customer Collaboration Over Contract Negotiation
• Negotiation is when the customer and the manager/teams
work out the details right before the project delivery.
• However, in the Agile Manifesto, the customer is not only
engaged at the time of the final delivery.
• Instead, the Agile approach engaged and collaborated with the
customer throughout the development process.
Tip: Engage and collaborate with the customer at intervals for

periodic demos. Make sure that your customer becomes an
essential part of the daily process, thereby ensuring that you meet
the needs of the customer. 8
Agile Values
4. Responding to Change Over Following a Plan
Traditionally, change was seen as an added expense, so it was to
be avoided. However, in the Agile manifesto, change is seen as a
potential opportunity to improve, develop better results.
Tip: Review your plans, priorities, and dependencies after a regular

interval of time
9
About Agile Methodology
11
12
13
14
15
Why Agile
Waterfall Vs
Agile
Incremental vs Iterative
18
Iterative, Incremental Product Development
Example of Monalisa in Agile Way
Iterative Vs Incremental
21
Incremental Vs Iterative?
Incremental Vs Iterative?
Traditional Vs Agile
Characteristics Agile approach Traditional approach
Organizational structure Iterative Linear
Scale of projects Small and medium scale Large-scale
User requirements Interactive input Clearly defined before implementation
Involvement of clients High Low

Development model Evolutionary delivery Life cycle
Customers are involved from the time work Customers get involved early in the project
Customer involvement
is being performed but not once the execution has started
When problems occur, the entire team Escalation to managers when problem
Escalation management
works together to resolve it arise
Model preference Agile model favors adaption Traditional model favors anticipation
Less focus on formal and directive More serious about processes than the
Product or process
processes product
Test documentation Tests are planned one sprint at a time Comprehensive test planning
Project manager provides estimates and
Scrum master facilitates and the team does
Effort estimation gets approval from PO for the entire
the estimation
project
Reviews and approvals Reviews are done after each iteration Excessive reviews and approvals by leaders
Waterfall - Pros and Cons
PROs CONs
Well defined, tried Defined requirements leave

less room for creativity
and tested
Stakeholders changing
requirements – costly affairs
Defined in detail
from the beginning Requirements interpretation
different by different teams
Requirements are
Documentation focus rather
more predictable than building product
Agile - Pros and Cons
PROs CONs
Offers flexibility The outcomes and timelines are

less predictable
Empowers team
The customer (Product Owner)
must have skin in the game
Time to market is accelerated
Documentation is not a
Failure and learning is deliverable
encouraged and embraced
More opportunities for Rework is inevitable

creativity
Project Lifecycles and Characteristics
Types Characteristics
Predictive • Fixed requirements
• Activities performed once per project
• Single delivery
• Goal: Manage cost
Adaptive Iterative • Dynamic requirements
• Activities repeated until correct
• Single delivery
• Goal: Correct solution
Incremental • Dynamic requirements
• Activities performed once per increment
• Frequent small deliveries
• Goal: Speed
Agile • Dynamic requirements
• Combines iterative repetition of activities with incremental deliveries
• Goal: Customer value
Hybrid • Includes adaptive and predictive components
• Shorter, iterative time frames
• High stakeholder involvement
• More in-depth requirements 27
Assessment of Project Needs, Complexity, and Magnitude
Methodology Best Suited When Examples
• Changes are relatively easy, and waste is not costly.
Software projects or projects based on
Agile • Complex environment where end product is not fully
intellectual property and research.
known and user feedback is very valuable.
Construction projects or projects that have

Predictive / • Changes are expensive due to scrap and waste.
many physical assets or have similar projects
Plan Driven • Predictability and coordinated timing is important.
that been completed in the past.
Projects where learning and correction is

• Dynamic requirements and activities are repeated until
Iterative expected to eventually get to the ideal
they are deemed correct.
solution.
• Dynamic requirements, as well as frequent small Projects where customers or business is
Incremental deliveries. wanting or expecting to see outputs or
• Speed to deliver small increments is a major goal. partial outputs early and often.
• There are some costs to changes. Projects with a mix of resources and
Hybrid • Stakeholders are interested in another method, but not experience levels or projects seeking or
comfortable to fully adopt one method. willing to learn new methods or techniques.
28
When to use
Agile
Iron Triangle
has changed
Different Types
of Agile
Frameworks
Agile Framework at a Glance
Agile Release Planning
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition, 34
Project Management Institute, Inc., 2017, Page 216.
• THANK YOU

Agile Whiteboard - V1.0-To Be Sent

Uploaded by

Copyright:

Available Formats

Agile Whiteboard - V1.0-To Be Sent

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Agile Whiteboard - V1.0-To Be Sent

Uploaded by

Copyright:

Available Formats

What are the four values of agile?

What are some differences between waterfall and agile approaches?

What is Agile

Agile Transformation : Vision and Mission

Tip: Make sure that communication is fluid and happens when a

Tip: Make sure that communication is fluid and happens when a

Tip: Ditch manual documentation and consider an automated file

Tip: Engage and collaborate with the customer at intervals for

Tip: Review your plans, priorities, and dependencies after a regular

User requirements Interactive input Clearly defined before implementation

Involvement of clients High Low

Well defined, tried Defined requirements leave

Offers flexibility The outcomes and timelines are

More opportunities for Rework is inevitable

Construction projects or projects that have

Projects where learning and correction is

You might also like