Agile vs Waterfall

12 658 vues

Publié le

Agile and Waterfall are two distinct methods of project management.

The Waterfall model can essentially be described as a linear model of project development. Like its name suggests, waterfall employs a sequential process. Development flows sequentially from start point to end point, with several different stages: Conception, Initiation, Analysis, Design, Construction, Testing, Implementation, and Maintenance.

In contrast, the Agile method proposes an incremental and iterative approach to project development. It was essentially developed in response to the limitations of Waterfall, as a way to give more freedom. The process is broken into individual models that team work on. There is no pre-determined course of action or plan with the Agile method. Rather, team-mates are free to respond to changes in requirements as they arise and make changes as the project progresses. Agile is a pretty new player to the development management. However, it has made substantial gains in use and popularity in the last couple of years.

9 commentaires
187 j’aime
Statistiques
Remarques
Aucun téléchargement
Vues
Nombre de vues
12 658
Sur SlideShare
0
Issues des intégrations
0
Intégrations
193
Actions
Partages
0
Téléchargements
537
Commentaires
9
J’aime
187
Intégrations 0
Aucune incorporation

Aucune remarque pour cette diapositive

Agile vs Waterfall

  1. AGILE VS WATERFALLI’M AHMED BARKHIA AGILE PM & DIGITAL COACH
  2. I’M AN AGILE PROJECT MANAGER AND DIGITAL COACH I INNOVATION I’M THIRTY (TWO) I’M AVAILABLE FOR WORK AHMED BARKHIAaka Ahmed Abdel Rahman
  3. WICH PROJECT MANAGEMENT STYLE IS RIGHT FOR YOU? WATERFALL REQUIRES DETAILED PLANNING AT THE BEGINNING OF A PROJECT. AGILE IS FAST AND FLEXIBLE BASED ON PRINCIPLES OF COLLABORATION, ADAPTABILITY AND CONTINUOUS IMPROVEMENT FRAMEWORKS SOMETIMES, THE SECRET OF A SUCCESSFUL PROJECT IS SELECTING THE RIGHT PROJECT MANAGEMENT STYLE. ESTABLISHING AN EFFECTIVE FRAMEWORK IS CRUCIAL FOR ANY PROJECT TO RUN SMOOTHLY. BUT WHEN YOU HAVE WATERFALL AND AGILE PLANNING METHODS TO CHOOSE FROM, HOW DO YOU KNOW WICH IS THE BEST FOR YOUR PROJECT AND TEAM?
  4. The WATERFALL Methodology 
 
 The waterfall model is a sequential design process, used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of conception, initiation, analysis, design, construction, testing, production/implementation and maintenance. The waterfall development model originates in the manufacturing and construction industries: highly structured physical environments in which after-the-fact changes are prohibitively costly, if not impossible. Since no formal software development methodologies existed at the time, this hardware- oriented model was simply adapted for software development. -Wikipedia WATERFALL MODEL ALL STEPS ARE LAID OUT, DEPENDENCIES MAPPED, AND YOU MOVE TO THE NEXT STAGE ONLY AFTER COMPLETING THE PREVIOUS ONE.
  5. THE WATERFALL PROS. BEST FOR PROJECTS THAT DEAL WITH PHYSICAL OBJECTS - FROM A CONSTRUCTION PROJECT TO A HARDWARE INSTALLATION BEST FOR PROJECTS WITH DEFINED TASKS AND PHASES THAT MUST BE COMPLETED IN A SPECIFIC SEQUENCE PROJECT PLANS ARE REPEATABLE FOR IDENTICAL SIMILAR PROJECTS IN THE FUTURE
  6. THE WATERFALL CONS. REQUIRES SUBSTANTIAL SCOPE AND SCHEDULE PLANNING BEFORE WORK BEGINS. SCOPE CHANGES CAN BE SLOW AND REQUIRE FORMAL CHANGE CONTROL PROCESSES. LESS EFFECTIVE FOR SOFTWARE, DESIGN AND OTHER NON-PHYSICAL OR SERVICES-BASED PROJECTS.
  7. The AGILE Methodology 
 
 Agile modeling (AM) is a methodology for modeling and documenting software systems based on best practices. It is a collection of values and principles, that can be applied on an (agile) software development project. This methodology is more flexible than traditional modeling methods, making it a better fit in a fast changing environment.[1] It is part of the Agile software development tool kit. Agile modeling is a supplement to other agile methodologies such as Scrum, extreme programming (XP), and Rational Unified Process (RUP). It is explicitly included as part of the disciplined agile delivery (DAD) framework. As per 2011 stats, agile modeling accounted for 1% of all agile software development. -Wikipedia AGILE MODEL AGILE PROJECT MANAGEMENT IS TYPICALLY SET UP IN QUICK AND PROVIDING ITERATIVE PROJECT RELEASE CYCLES.
  8. THE AGILE PROS. BEST FOR PROJECTS THAT DEAL WITH SERVICES- ORIENTED AND NON-PHYSICAL DELIVERABLES ALLOWS QUICK COURSE CORRECTION BASED ON STAKEHOLDER FEEDBACK EMPOWERS PROJECT TEAMS TO WORK CREATIVELY AND EFFICIENTLY INCLUDES ENGAGEMENT AND COLLABORATION FROM ALL TEAM MEMBERS
  9. THE AGILE CONS. NOT SUITED FOR PROJECTS WITH STRICTLY DEFINED REQUIREMENTS AND SCOPE UNCERTAINTY AROUND SCOPE AND SCHEDULES CAN MAKE STAKEHOLDERS AND EXECUTIVES NERVOUS (AT FIRST) REQUIRES VIGILANT BACKLOG AND DOCUMENTATION MAINTENANCE, AND TECH DEBT MANAGEMENT
  10. MY FAVOURITE SET UP HINT THE PROJECT MANAGEMENT METHOD YOU CHOOSE WILL VARY BASED ON THE PROJECT, YOUR TEAM AND GOALS. ONCE YOU SELECT A PLANNING STYLE, MAKE SURE YOU USE PROJECT MANAGEMENT SOFTWARE THAT LETS YOU AND YOUR TEAM SET UP YOUR PROJECTS THE WAY YOU WANT. Find your people Set up your tools Keep up the performance GIVE YOUR BEST RESULTS Start the project
  11. TO FINISH
  12. Q&APut your questions TO FINISH
  13. THANKS.FOR YOUR ATTENTION TO FINISH
  14. TO FINISH FACEBOOK.COM/AHMED.BARKHIA TWITTER.COM/AHMEDBARKHIA ME@AHMEDBARKHIA.CO Call me +971 56 625 0316 I WHEN YOU ADD ME ON ON SOCIAL NETWORK

×