Please enable JavaScript.
Coggle requires JavaScript to display documents.
Waterfall Method - Coggle Diagram
Waterfall Method
advantages of waterfall method
time management is easy
plans or requirements are established and defined
other benefits of waterfall method
early detection of bugs in design or analysis phase
avoiding errors in implementation
project cost can be accurately estimated
Late joining of developers can catch up fast
all need to know in project requirements
Disadvantages of waterfall method
A clearly defined approach and sticking to it
changes and modifications along the process
time-consuming
painful
costly
Other reasons
takes longer to complete
clients incomplete front end preparation knowledge
changes or additions along the process
hard to accomodate
clients not involved in designing and implementation
deadline creep
delay in one phase delays the other phases
Project management approach
Linear progression
Consecutive execution
forms a basis on upfront preparation
advance documentation
advance research
early planning
advance preparation
project focus on fixed plan
5 common stages of waterfall
requirements
project requirements
detailed understanding of project sponsor's requirement
project requirements specification
describe each stage of the project
costs
assumptions
risks
dependencies
success metrics
timelines for completion
heart of the waterfall model
what needs to be done
blueprint of the project
guidelines
design
technical solutions to problems
by project requirements
includes layouts scenarios and data models
implementation
shortest phase
actual coding
base on project requirement and specification
significant changes in this phase
go back to design phase
verification or testing
no errors
all requirements met
testing team
turn into design documents
personas
user case scenarios
supplied by the product manager to create their test cases
Deployment and maintenance
maintenance phase
deployed in the market or released to customers
what is handled
defects
user request changes
how
updates and new versions
who uses the waterfall method?
project managers faced with development projects that
dont have ambiguous requirements
offer a clear picture how things will proceed from the beginning