EVOLVE for Instructors Materials; PMP, PMI-ACP, PMI-RMP, Soft Skills, Prince2 https://evolvetrainingmaterials.com/

1. Agile
Project Management
2019

3. Introduction
• Today, project leaders and teams find themselves in an environment
disrupted by exponential advances in technology and demands from
customers for more immediate delivery of value. Agile techniques and
approaches effectively manage disruptive technologies.
• In order to stay competitive and relevant, organizations can no longer be
internally focused but rather need to focus outwardly to the customer
experience.
• This speed of change will continue to drive large organizations to adopt an
agile mindset in order to stay competitive and keep their existing market
share.

4. Agile vs. Waterfall

5. Agile VS Traditional
The Agile Manifesto
Agile
Customer Collaboration
Responding to Change
Working Solutions
Highest Business Value in The Shortest Time
Traditional
Contract Negotiation
Following A Plan
Documentation
Deferred Business Value Via Longer Delivery Time
VS
AGILE MYTHOLOGY
Agile is an iterative method of managing product development projects in a highly flexible and interactive manner. The overarching
focus of agile development is frequent delivery of high-quality, working, software. Agile ensures optimal business value is delivered
through ongoing alignment between technology and the business.

7. Enter your subhead line here
Waterfall VS. Agile
VS
WATERFALL
MODEL
AGILE
Conception
Initiation
analysis
Design
Construction
Testing
Deployment
Conception
Initiation
analysis
Design
Construction
Testing
Deployment

8. Enter your subhead line here
Waterfall VS. Agile
Agile Projects
Traditional Projects (Waterfall)
Fixed
Estimated
PLAN
DRIVEN
Scope
Costs Time
Part of Contract Flexible
VALUE
DRIVEN
Scope
Costs Time
The plan create cost/ Schedule estimates Software release themes and features determine the time
and cost estimate

9. A
B
C
D
Features Planned Features Developed
A
B
C
D
Enter your subhead line here
Waterfall VS. Agile
BUDGET
TIME
Waterfall
Development of the software flow sequentially from start point to the end point.
Strategy &
Recommendations
AI / Wire Fire
Visual Design
& Copy
Development &
Coding
Testing &
Validation
Deployment

10. Enter your subhead line here
Waterfall VS. Agile
BUDGET
TIME
Agile
Agile method proposes and increment and iterative approach to software design.
Features Developed
Features Planned
A
B
C
D
Strategy & Recommendations
AI / Wire Fire
Visual Design & Copy
Development & Coding
Testing & Validation
Deployment
Handoff
to
Dev
A
B
C
D
Features Developed
Features Planned
Strategy & Recommendations
AI / Wire Fire
Visual Design & Copy
Development & Coding
Testing & Validation
Deployment
Handoff
to
Dev
A
B
C
D
4
Weeks
4
Weeks

11. Enter your subhead line here
Waterfall VS. Agile
WATERFALL
Development of the
software flow sequentially
from start point to the end
point.
Requirements
Design
Implementation
Verification
AGILE
Agile method proposes and
increment and iterative
approach to software
design.
TIME
BUDGET
TIME
BUDGET

12. Enter your subhead line here
Waterfall VS. Agile
WATERFALL
Development of the
software flow sequentially
from start point to the end
point.
Requirements
Defined and
Documented
Design And
Architecture
Development
And Coding
Testing and
Verification
AGILE
Agile method proposes and
increment and iterative
approach to software
design.
TIME
BUDGET
TIME
BUDGET
Deployment
Deliver Code
Sprint Sprint Sprint Sprint Sprint
Deliver Code

13. Agile vs. Waterfall
• Waterfall project methodology is a model in which every stage of a
product’s life cycle takes place in sequence. The progress flows steadily
downwards through these phases like a waterfall.
Agile software development methodology is the model that proposes a
sequential, linear and iterative approach.

14. • In Waterfall model software development, the process is divided into
different phases. Agile proposes to segregate the development lifecycle
into sprints.
• In Waterfall, development process should be implemented as one single
project. Then this project is divided into phases. Agile contains a set of
different projects that are the iterations of the different stages. They are
focused on improving the quality and feedbacks from users.
Agile vs. Waterfall

15. • Waterfall software development model is structured and often rigid. Often
project managers prefer Agile as a more flexible model.
• According to the iterative Waterfall model in software engineering, all the
project phases are completed at a time. In Agile they follow an iterative
development approach. So some of the phases can appear more than
once.
• There is no chance to change the requirements once the Waterfall project
development starts. Agile is more flexible and allows changes in the project
development requirements. Even after the planning has been completed.
Agile vs. Waterfall

16. • One more difference between Waterfall and Agile is their individual
approach towards testing and quality. According to Agile, testing is usually
performed concurrently with programming. In Waterfall, testing phase
comes after the build phase.
• Waterfall approach does not require the participation of customers, as it is
an internal process. However, Agile methodology focuses on clients
satisfaction and involves them to participate throughout the development
phase.
• Waterfall iterative model is good for projects with clearly defined
requirements and without expected changes. Agile allows changing and
evolving the requirements.
Agile vs. Waterfall

17. We are uncovering better ways of developing software by doing it and helping others do it.
The Agile Manifesto
Individual and Interactions
Working Software
Customer Collaboration
Responding to Change
Over Processed and Tools
Over Comprehensive
Documentation
Over Contract Negotiation
Over Following a Plan

18. Uncertainty
and
complexity
Model
inspired by
the stacey
Complexity
Model

20. Agile Methodologies Used
Agile Methodologies Used
What is Scrum?
Scrum is a lightweight management framework with broad
applicability for managing iterative and incremental projects of all
types. In the Scrum, work is confined to a regular, repeatable one-
week to one-month work cycle, known as Sprint
What is KANBAN?
KANBAN is a pull-based planning and execution method in which
the team signals when they are ready for more work and pulls it into
their queue. Teams track their work with cards that are kept on a
KANBAN board.
What is XP?
Extreme programming known as XP is software development
methodology intended to improve software quality and
responsiveness to changing customer requirements.
58%
SCRUM
10%
Scrum / XP
HYBIRD
8%
Custom
7%
SCRUMBAN
5%
KANBAN
2%
LEAN
<1%
XP

21. 12 Principles Behind the Agile Manifesto
The Agile Manifesto - 12 Principles
Measure Of Progress
Through Working Product
Promote Sustainable
Development
Continuous Attention To
Technical Excellence
Regularity Reflect On
Continuously Improving
Self-organizing Teams
Simplicity Is Essential
Satisfy
The Customer
Welcome Changing
Requirements
Deliver Working Software Frequently
Face-to-face Conversation
Motivated Individuals
Collaborate Daily
12
Principles
Of Agile

22. 12 Principles Behind the Agile Manifesto
The Agile Manifesto - 12 Principles
Satisfy
The Customer
Welcome Changing
Requirements
Deliver Working
Software Frequently
Collaborate
Daily
Motivated
Individuals
Face-to-face
Conversation
Measure Of Progress
Through Working Product
Promote Sustainable
Development
Continuous Attention To
Technical Excellence
Simplicity
Is Essential
Self-organizing
Teams
Regularity Reflect On
Continuously Improving

23. 12 Principles Behind the Agile Manifesto
The Agile Manifesto - 12 Principles
Our highest priority is to satisfy the customer through early and
continuous delivery of valuable software.
1
Welcome changing requirements, even late in development. Agile
processes harness change for the customer's competitive
advantage
2
Deliver working software frequently, from a couple of weeks to a
couple of months, with a preference to the shorter timescale.
3
Business people and developers must work together daily
throughout the project.
4
Build projects around motivated individuals. Give them the
environment and support they need, and trust them to get the job
done.
5
The most efficient and effective method of conveying information to
and within a development team is face-to-face conversation.
6
Working software is the primary measure of progress.
7
Agile processes promote sustainable development. The sponsors,
developers, and users should be able to maintain a constant pace
indefinitely.
8
Continuous attention to technical excellence and good design
enhances agility.
9
Simplicity--the art of maximizing the amount of work not done--is
essential.
10
The best architectures, requirements, and designs emerge from
self-organizing teams.
11
At regular intervals, the team reflects on how to become more
effective, then tunes and adjusts its behavior accordingly.
12

24. The Continuum of Life Cycles

25. Predictive, Classic or Planning-Focused Life Cycles
Also known as classic or planning-focused life cycles) are those in
which the scope, deadline and cost are determined as soon as
possible in the project life cycle and efforts are focused on meeting
the commitments established for each one of these factors.
Predictive life cycles

26. Predictive, Classic or Planning-Focused Life Cycles
• These projects are normally organized into a series of sequential or consecutive
phases, where each one is focused on a specific sub-product or activity.
• From the start, project management focuses on defining the scope and drawing up
a detailed plan of the necessary activities. From there, work is focused on following
the plan.
• Any project scope change must be managed explicitly and usually leads to a review
of the plan and formal acceptance of the new plan.
• Predictive life cycles are chosen when the product to be delivered is well-defined.

28. Iterative Life Cycle
• A project life cycle where the project scope is generally determined early in the
project life cycle, but time and cost estimates are routinely modified as the project
team’s understanding of the product increases.
• Iterations develop the product through a series of repeated cycles, while
increments successively add to the functionality of the product”

29. Like a yearlong project will have three months iterations. And, each iteration will
execute Planning, Analysis, Design, Code, testing phases, and deliver the result at the
end of the iteration. This delivered result may not be usable, but it is shown to give a
feel of the final product.
Iterative Life Cycle

30. Software Development
Agile Methodology
Development
1
Development
2
Development
N
Release
Feedback
Review
Accept
NO
Next
Iteration
Adjust &
Track
Record &
Incorporate
Changes
AGILE
LIFECYCLE
RELEASE TO
MARKET
INTEGRATE
AND TEST
START
Initiate Project
Define Requirements
High Level
Requirements
Continuous Visibility
Client
Developer
s
Users
YES