Waterfall Model
The Waterfall model is a more stringent and process-driven style, where the project is broken down into project activities through structured phases with toll gates established to formulate review progress.
In Waterfall, each phase typically depends on the deliverables of the previous one.
The focus is on the work to be done and not delivering functional vertical slices.
Waterfall is quite common for elements of high capital expenditure engineering projects.
Best Model For Project
When Not to use agile
No clear vision or roadmap: if there is a lack of agreement and clarity in terms of both the requirements and as well as process, then an Agile approach will not magically help with such chaos
Straight-forward Requirement: When there is near certainty on both the requirements and process upfront, then there may not be as much value in utilizing. Agile principles because there isn't much need for iterative learning and adapting.
When to use Agile
Agile works best in an environment of complexity and some uncertainty, where an adaptive approach is needed to deliver maximum value.
Agile is also useful in delivering valuable results when working with complicated requirements.
They need iterative cycles to understand that genuine needs of the end users.
Common Misconceptions of Agile
Here are 5 of the more common Agile misconceptions that should be avoided keeping the Agile Mindset in focus:
Scheduling Agile ceremonies makes a team Agile - Holding ceremonies for the sake of holding ceremonies does not deliver benefits. Ceremonies must adhere to the core principles of Agile.
The Facilitator role is just like a traditional Project Manager - The Facilitator role is different from the Project Manager role. A Facilitator should be a Servant Leader who assists with whatever the team needs to forward.
Large teams are okay - Agile recommends small cross-functional teams that allow the team to be nimble and powerful.
The product backlog can be managed like a traditional requirements document - The backlog should not be a process-driven document. It should focus on customer value and strategic objectives.
Documentation and audit trails for compliance are not important in Agile - Agile does not mean no documentation -- it just removes low-value documents and documents what is valuable to maintain and sustain the product.