PROJECT TYPES
Waterfall Vs. Agile: Must Know Differences
What is Waterfall methodology?
Waterfall Model methodology which is also known as Liner
Sequential Life Cycle Model. Waterfall Model followed in the sequential order,
and so project development team only moves to next phase of development or
testing if the previous step completed successfully.
What is the Agile methodology?
Agile methodology is a practice that helps continuous
iteration of development and testing in the software development process. In
this model, development and testing activities are concurrent, unlike the
Waterfall model. This process allows more communication between customers,
developers, managers, and testers.
Advantages of Waterfall Model:
It is one the easiest model to manage. Because of its
nature, each phase has specific deliverables and a review process.
It works well for smaller size projects where requirements
are easily understandable.
Faster delivery of the project
Process and results are well documented.
Easily adaptable method for shifting teams
This project management methodology is beneficial to manage
dependencies.
Advantages of the Agile Model:
It is focused client process. So, it makes sure that the
client is continuously involved during every stage.
Agile teams are extremely motivated and self-organized so it
likely to provide a better result from the development projects.
Agile software development method assures that quality of
the development is maintained
The process is completely based on the incremental progress.
Therefore, the client and team know exactly what is complete and what is not.
This reduces risk in the development process.
Limitations of Waterfall Model:
It is not an ideal model for a large size project
If the requirement is not clear at the beginning, it is a
less effective method.
Very difficult to move back to makes changes in the previous
phases.
The testing process starts once development is over. Hence,
it has high chances of bugs to be found later in development where they are
expensive to fix.
Limitations of Agile Model
It is not useful method for small development projects.
It requires an expert to take important decisions in the
meeting.
Cost of implementing an agile method is little more compared
to other development methodologies.
The project can easily go off track if the project manager
is not clear what outcome he/she wants.
KEY DIFFERENCE
Waterfall is a Liner Sequential Life Cycle Model whereas
Agile is a continuous iteration of development and testing in the software
development process.
Agile methodology is known for its flexibility whereas
Waterfall is a structured software development methodology.
Agile follows an incremental approach whereas the Waterfall
methodology is a sequential design process.
Agile performs testing concurrently with software
development whereas in Waterfall methodology testing comes after the “Build”
phase.
Agile allows changes in project development requirement whereas
Waterfall has no scope of changing the requirements once the project
development starts.
What Is Agile Methodology?
Agile methodology is a practice that helps continuous
iteration of development and testing in the SDLC process. Agile breaks the
product into smaller builds.
In this methodology, development and testing activities are
concurrent, unlike other software development methodologies. It also encourages
teamwork and face-to-face communication. Business, stakeholders, and developers
and clients must work together to develop a product.
What Is Scrum?
Scrum is an agile process that allows us to focus on
delivering the business value in the shortest time. It rapidly and repeatedly
inspects actual working software. It emphasizes accountability, teamwork, and
iterative progress toward a well-defined goal.
The Scrum Framework usually deals with the fact that the
requirements are likely to change or most of the time not known at the start of
the project.
PROJECT ROLES
SPONSOR
The person who commissions others to deliver the project and
champions the cause throughout the project.
They will normally be a senior member of staff with a relevant area of
responsibility that will be affected by the outcome of the project. They are involved from the start of the
project, including defining the project in conjunction with the Project
Manager. Once the project has been
launched they should ensure that it is actively reviewed. The Project Sponsor is usually the one who
has to negotiate a path through the tricky diplomatic areas of the project!
as champion of the project.
Is accountable for the delivery of planned benefits
associated with the project.
Ensures resolution of issues escalated by the Project
Manager or the Project Board.
Sponsors the communications programme; communicates the
programme’s goals to the organization as a whole.
Makes key organisation/commercial decisions for the project.
Assures availability of essential project resources.
Approves the budget and decides tolerances.
Leads the Project Steering Board.
Ultimate authority and responsibility for the project.
PROJECT MANAGER (Waterfall Projects)
The Project Manager is also responsible for managing the
work of consultants, allocating and utilising resources in an efficient manner
and maintaining a co-operative, motivated and successful team.
The person responsible for developing, in conjunction with
the Project Sponsor, a definition of the project. The Project Manager then
ensures that the project is delivered on time, to budget and to the required
quality standard (within agreed specifications). He/she ensures the project is
effectively resourced and manages relationships with a wide range of groups
(including all project contributors).
Managing and leading the project team.
Recruiting project staff and consultants.
Managing co-ordination of the partners and working groups
engaged in project work.
Detailed project planning and control including:
Developing and maintaining a detailed project plan.
Managing project deliverables in line with the project plan.
Recording and managing project issues and escalating where
necessary.
Resolving cross-functional issues at project level.
Managing project scope and change control and escalating
issues where necessary.
Monitoring project progress and performance.
Providing status reports to the project sponsor.
Managing project training within the defined budget.
Liaison with, and updates progress to, project steering
board/senior management.
Managing project evaluation and dissemination activities.
Managing consultancy input within the defined budget.
Final approval of the design specification.
Working closely with users to ensure the project meets
business needs.
Definition and management of the User Acceptance Testing
programme.
Identifying user training needs and devising and managing
user training programmes.
PRODUCT OWNER
The Product Owner acts in the interests of the users of the
product or the stakeholders of a project. Consequently, he is responsible for
the success of the project and must prioritize the technical requirements of
the project over the entire project period, adding new ones and discarding
obsolete ones as necessary.
SCRUM MASTER (Agile Projects)
This person is responsible for ensuring that all processes
are followed correctly. As a kind of moderator, he ensures that the team can
communicate successfully, shields them from external disruptions, and helps
with methodological issues. In short, his job is to eliminate obstacles
preventing effective teamwork.
Each Scrum team working on a product should be no larger
than five to ten people. Each team member should be goal-oriented and be able
to work independently on their own tasks.
Last, but certainly not least, are stakeholders. Although
they don’t have a central role within the Scrum process, considering their
wishes and feedback is key for the project success. Stakeholders can be either
a) the clients, b) the eventual end users, or c) the management of the
corresponding project.
USEFUL LINKS AND REFERENCES
About Agile
https://www.guru99.com/waterfall-vs-agile.html
https://www.guru99.com/waterfall-vs-agile.html
About Waterfall and the leading approach to Waterfall which
is PRINCE2
https://prince2.wiki/
ABOUT THE BLOG
This is a series of coaching blogs that eventually will become a book. By blogging each item I hope to share each element in easy to read bite size chunks, maybe invite some people to subscribe to see the next posting and hopefully encourage some comments, feedback and suggestions which will improve the content for the blog and eventually the book. All comments and feedback are therefore welcome.
