The project and chosen Project Management method

The chosen Project to manage is a bespoke software for a specific customer. The chosen Project
Management methodology is Agile. In the text that follows I will explain why I see Agile to be better
suited than Waterfall and CCPM.

Why choose Agile?

Agile inherently presents itself as a very logical choice by the fact that it's very inception was brought
about by Software Developers who saw an urgent need for a project management approach that
would provide a much more suitable way to manage of software development projects. A flexible
approach with a focus on the customer’s needs and an approach of customer collaboration and
iteration to reach the best possible result to meet the customer requirements.

Being quite familiar with the dynamics of software development from the early stages of the
software lifecycle as well as later maintenance and development of additional features I can
recognise how Agile offers a range of important benefits that sets itself apart from other
approaches. Agile is defined through the articulation of 4 core values and 12 principles, these are
listed below. Following these two listings I will highlight what forms the most significant strengths
that Agile offers to managing software development projects.

The four core values are:

1. Individuals and interactions over process and tools

2. Working software over full documentation
3. Customer collaboration over contract negotiation
4. Respond to change over sticking to plans

The twelve principles are:

1. Our highest priority is to satisfy the customer through early and continuous delivery of
valuable software
2. Welcome changing requirements even late in development
3. Deliver working software frequently
4. Businesspeople and developers must work together daily throughout the project
5. Build projects around motivated individuals. Give them the environment and support they
need and trust them to get the job done
6. The most efficient and effective method of conveying information to and within a
development team is face to face conversation
7. Working software is the primary measure of progress
8. Agile processes promote sustainable development. Stakeholders should be able to maintain
a constant pace indefinitely
9. Continuous attention to technical excellence and good design enhances agility
10. Simplicity is essential
11. The best architecture, requirements and designs emerge from self-organising teams
12. At regular intervals, the team reflects on how to become more effective, then tunes and
adjusts its behaviour accordingly.

The principles have been derived from the values are also reflected in the values. These values
reflect where the emphasis must be in decision making in the path to achieving the best manageable
customer satisfaction. From this articulation it can be seen that to end up with a working software is
of much greater importance than having everything meticulously documented. Waterfall
methodology requires the opposite which makes it much less suited. Developing software that
works to the customer’s satisfaction can only be achieved by means of collaboration with the
customer and understanding their specific needs. From these customer collaborations it becomes
clear where changes are needed and what changes must be made to the plans. Finally, the software
development team needs to have the right working methods and proper communications internally
to deliver the software that the customer asked for.

Agile compared to Waterfall

In comparing Agile to Waterfall it is very quickly clear how the latter does not meet the requirements
for software development as it is too rigid and has the emphasis on the wrong elements. The
Waterfall method does not allow for change once the project plan has been drawn up, this rigidity
forms a point of weakness to this approach. Software development is highly complex and needs
flexibility instead. This flexibility and the constant of change that is a natural part of software
development would cause an impossible amount of work to keep up with all the documentation that
Waterfall methodology would require. Waterfall methodology embodies the shortcomings of older
project management approaches that lead to the creation of Agile and other project management

Agile compared to Critical Chain Project Management (CCPM)

Although CCPM does not make for a decidedly unsuitable option to use for a software development
project, it does lack in pronounced advantages that would positively distinguish it as the best option.
This method has a greater focus on managing time and resource constraints, and whilst it is also
used for software development projects it finds greater use within construction, manufacture and
product development. The method does not encourage the closer communications with the
customer and lacks the focus continuous improvement through iteration for example.

References:

 Rigby, D. (2021, August 27). The Secret History of Agile Innovation. Harvard
Business Review. Retrieved April 16, 2023, from https://hbr.org/2016/04/the-secret-
history-of-agile-innovation
 Project Management Institute. (2022, February). What is Agile. PMI. Retrieved April
16, 2023, from https://www.pmi.org/disciplined-agile/agile/whatisagile
 PMI. (2017). Agile Practice Guide. Agile Alliance. Retrieved April 16, 2023, from
https://www.agilealliance.org/wp-content/uploads/2021/02/AgilePracticeGuide.pdf
 Kissflow, Inc. (2022b, September 19). 7 Best Project Management Methodologies
and Frameworks Explained. https://kissflow.com/project/project-management-
methodologies-and-frameworks/#What-is-Project-Management-Methodology
 The Critical Chain Project Management method explained. (n.d.). Critical Chain.
Retrieved April 16, 2023, from https://www.critical-chain-projects.com/the-method
 Reaiche, C. (2022, August 5). The traditional, sequential methodologies. James Cook

University. Retrieved April 16, 2023, from

https://jcu.pressbooks.pub/pmmethods/chapter/traditional-sequential-methodologies/