2. THANK YOU FOR TAKING PART IN THIS
PRESENTATION
Created by Makaulule Pandelani
3. WATERFALL METHODOLOGY
WHAT IS THE WATERFALL MODEL?
THE WATERFALL MODEL IS A LINEAR PROJECT MANAGEMENT APPROACH, WHERE STAKEHOLDER AND
CUSTOMER REQUIREMENTS ARE GATHERED AT THE BEGINNING OF THE PROJECT, AND THEN A
SEQUENTIAL PROJECT PLAN IS CREATED TO ACCOMMODATE THOSE REQUIREMENTS. THE WATERFALL
MODEL IS SO NAMED BECAUSE EACH PHASE OF THE PROJECT CASCADES INTO THE NEXT, FOLLOWING
STEADILY DOWN LIKE A WATERFALL.
IT’S A THOROUGH, STRUCTURED METHODOLOGY AND ONE THAT’S BEEN AROUND FOR A LONG TIME,
BECAUSE IT WORKS. SOME OF THE INDUSTRIES THAT REGULARLY USE THE WATERFALL MODEL INCLUDE
CONSTRUCTION, IT AND SOFTWARE DEVELOPMENT. HOWEVER, THE TERM “WATERFALL” IS USUALLY
USED IN A SOFTWARE CONTEXT.
GANTT CHARTS ARE THE PREFERRED TOOL FOR PROJECT MANAGERS WORKING IN WATERFALL. USING A
GANTT CHART ALLOWS YOU TO MAP SUBTASKS, DEPENDENCIES AND EACH PHASE OF THE PROJECT AS IT
MOVES THROUGH THE PROJECT LIFE CYCLE. PROJECTMANAGER.COM’S WATERFALL SOFTWARE OFFERS
THESE FEATURES AND MORE.
4. STEPS FOR WATERFALL METHODOLOGY
DESIGN: THE DESIGN PHASE IS BEST BROKEN UP INTO TWO SUBPHASES: LOGICAL DESIGN AND PHYSICAL
DESIGN. THE LOGICAL DESIGN SUBPHASE IS WHEN POSSIBLE, SOLUTIONS ARE BRAINSTORMED AND
THEORIZED. THE PHYSICAL DESIGN SUBPHASE IS WHEN THOSE THEORETICAL IDEAS AND SCHEMAS ARE
MADE INTO CONCRETE SPECIFICATIONS.
IMPLEMENTATION: THE IMPLEMENTATION PHASE IS WHEN PROGRAMMERS ASSIMILATE THE
REQUIREMENTS AND SPECIFICATIONS FROM THE PREVIOUS PHASES AND PRODUCE ACTUAL CODE.
VERIFICATION: THIS PHASE IS WHEN THE CUSTOMER REVIEWS THE PRODUCT TO MAKE SURE THAT IT
MEETS THE REQUIREMENTS LAID OUT AT THE BEGINNING OF THE PROJECT. THIS IS DONE BY RELEASING
THE COMPLETED PRODUCT TO THE CUSTOMER.
MAINTENANCE: THE CUSTOMER IS REGULARLY USING THE PRODUCT DURING THE MAINTENANCE PHASE,
DISCOVERING BUGS, INADEQUATE FEATURES AND OTHER ERRORS THAT OCCURRED DURING
PRODUCTION. THE PRODUCTION TEAM APPLIES THESE FIXES AS NECESSARY UNTIL THE CUSTOMER IS
SATISFIED.
5. AGILE METHODOLOGY
AGILE METHODOLOGIES ARE APPROACHES TO PRODUCT DEVELOPMENT THAT ARE
ALIGNED WITH THE VALUES AND PRINCIPLES DESCRIBED IN THE AGILE MANIFESTO FOR
SOFTWARE DEVELOPMENT. AGILE METHODOLOGIES AIM TO DELIVER THE RIGHT
PRODUCT, WITH INCREMENTAL AND FREQUENT DELIVERY OF SMALL CHUNKS OF
FUNCTIONALITY, THROUGH SMALL CROSS-FUNCTIONAL SELF-ORGANIZING TEAMS,
ENABLING FREQUENT CUSTOMER FEEDBACK AND COURSE CORRECTION AS NEEDED.
IN DOING SO, AGILE AIMS TO RIGHT THE CHALLENGES FACED BY THE TRADITIONAL
“WATERFALL” APPROACHES OF DELIVERING LARGE PRODUCTS IN LONG PERIODS OF
TIME, DURING WHICH CUSTOMER REQUIREMENTS FREQUENTLY CHANGED, RESULTING
IN THE WRONG PRODUCTS BEING
6. 4 CORE VALUES OF AGILE MANIFESTO
INDIVIDUALS AND INTERACTIONS OVER PROCESSES AND TOOLS – THE FIRST VALUE EMPHASIZES TEAMWORK
AND COMMUNICATION. WE MUST UNDERSTAND THAT SOFTWARE DEVELOPMENT IS A HUMAN ACTIVITY AND
THAT THE QUALITY OF INTERACTION BETWEEN PEOPLE IS VITAL. TOOLS ARE AN IMPORTANT PART OF
SOFTWARE DEVELOPMENT, BUT MAKING GREAT SOFTWARE DEPENDS MUCH MORE ON TEAMWORK, REGARDLESS
OF THE TOOLS TEAM MAY USE.
WORKING SOFTWARE OVER COMPREHENSIVE DOCUMENTATION – DOCUMENTATION HAS ITS PLACE AND CAN BE
A GREAT RESOURCE OR REFERENCE FOR USERS AND COWORKERS ALIKE. THE MAIN GOAL OF SOFTWARE
DEVELOPMENT, HOWEVER, IS TO DEVELOP SOFTWARE THAT OFFERS BUSINESS BENEFITS RATHER THAN
EXTENSIVE DOCUMENTATION.
CUSTOMER COLLABORATION OVER CONTRACT NEGOTIATION – DEVELOPMENT TEAMS MUST WORK CLOSELY
AND COMMUNICATE WITH THEIR CUSTOMERS FREQUENTLY. BY LISTENING TO AND GETTING FEEDBACK, TEAMS
WILL UNDERSTAND WHAT ALL STAKEHOLDERS REALLY WANT.
RESPONDING TO CHANGE OVER FOLLOWING A PLAN – CHANGES ARE A REALITY IN SOFTWARE DEVELOPMENT, A
REALITY THAT YOUR SOFTWARE PROCESS SHOULD REFLECT. A PROJECT PLAN MUST BE FLEXIBLE ENOUGH TO
CHANGE, AS THE SITUATION DEMANDS.
7. WHICH DESIGN METHODOLOGY IS MOSTLY
IS FLEXIBLE TO CHANGES BY CUSTOMERS:
WATERFALL
METHODOLOGY
AGILE
METHODOLOGY