UCT AGP M1U2 Infographic Transcript

Download as pdf or txt
Download as pdf or txt
You are on page 1of 4

© 2019 UCT/ GetSmarter

All Rights Reserved


MODULE 1 UNIT 2
What distinguishes the Agile
and Waterfall software
development approaches?
(transcript)
Learning outcome:

LO2: Identify the differences between the Agile and Waterfall approaches to software
development.

What distinguishes the Agile and Waterfall software


development approaches?
Key characteristics of Waterfall Key characteristics of Agile

Project scope is calculated up front, and Budget and time requirements are
budget and time requirements are established first, and scope is developed
estimated, allowing for clear target and adapted throughout the project.
deliverables.

Key dependencies of the project are clear at Key dependencies of the project are unclear
the beginning. or complex, and likely to change during the
process.

Plan driven: Detailed steps are planned and Iterative: The project goes through multiple,
followed in a linear progression. short phases.

Final: The customer sees a high-quality Incremental: The customer is presented


product at the end of the development with a usable product at the end of each
cycle. iteration.

Key limitations of Waterfall Key limitations of Agile

Because time and budget are estimated Without a clear scope, it is difficult to predict
according to the scope defined at the start of the amount of effort a project will require of
the project, changes in scope mean that team members.
deadlines and budgets can overrun.

Exploration is discouraged in order to Frequent communication between


maintain the budget, scope, and time stakeholders requires more time and energy.
estimates.

Not designed to adapt to changing Constantly changing processes can be a


requirements. barrier for newcomers to the team.

© 2019 UCT / GetSmarter


All Rights Reserved

Tel: +27 21 447 7565 | Fax: +27 21 447 8344


Website: www.getsmarter.com | Email: [email protected]
Page 2 of 4
Inappropriate for small teams, since the cost The process is heavily reliant on individual
of process often exceeds the cost of the team members (e.g. what happens if a team
business deliverables. member leaves the organisation?).

Product delivery is late in the project The central focus on the customer’s needs
process, which is inappropriate where and desires can backfire (e.g. what if the
speed of delivery is a priority. customer is wrong?).

Key benefits of Waterfall Key benefits of Agile

It is easy to transfer knowledge between It enables quick response to change, such as


teams, stakeholders, and new additions to customer requirements, market
the team due to comprehensive circumstances, or competitor strategies.
documentation.

The success of the project is not so closely The product is delivered frequently
tied to the individuals on the team. throughout the project.

It provides commitment certainty for Regular customer feedback is built into the
investors and enterprise managers. model. Therefore, plans can be adjusted
early on, optimising efficiency.

It is well-suited to large companies with large Frequent communication means the team
workforces, and many deliverables to can align with customer needs faster.
consider.

Intuitively simple process and deliverables. It enables innovation. Team members can
explore uncertainty at a low cost.

Customers are held in the project through a The customer can terminate the
predetermined contract and by having relationship at any stage of the project and
provided input on what the final product leave with a finished product.
must look like.

Ideal conditions for Waterfall Ideal conditions for Agile

Projects that have a clearly defined Projects that are exploratory in nature,
outcome. requiring research and novel processes or
techniques.

© 2019 UCT / GetSmarter


All Rights Reserved

Tel: +27 21 447 7565 | Fax: +27 21 447 8344


Website: www.getsmarter.com | Email: [email protected]
Page 3 of 4
Processes with standardised, repeatable Projects that have unknown or ambiguous
steps. requirements.

Predictable environments. Environments with high rates of change and


uncertainty.

The customer has limited availability or little Environments where the customer is
interest in the process. engaged and available.

Examples: Resale of an existing software to Examples: Development of a national digital


a new customer. Previous knowledge of health system where patient records can be
other implementation and documentation accessed in all clinics and hospitals across
can be reused. the country.

Bibliography
ClydeBank Business. 2014. Agile project management: quickstart guide – the simplified
beginner’s guide to agile project management. 2nd ed. [Kindle edition]. ClydeBank
Media LLC.

Project Management Institute & Agile Alliance. 2017. Agile practice guide. (Agile Practice
Guide). 1st ed. [Adobe Digital Edition]. Pennsylvania: Project Management Institute.

Ries, M. & Summers, D. 2016. Agile project management: a complete beginner’s guide to agile
project management. [Kindle edition]. CreateSpace Independent Publishing Platform.

© 2019 UCT / GetSmarter


All Rights Reserved

Tel: +27 21 447 7565 | Fax: +27 21 447 8344


Website: www.getsmarter.com | Email: [email protected]
Page 4 of 4

You might also like