{"id":7735,"date":"2018-06-05T00:05:32","date_gmt":"2018-06-05T04:05:32","guid":{"rendered":"http:\/\/mgrush.com\/blog\/?p=7735"},"modified":"2026-04-21T13:17:31","modified_gmt":"2026-04-21T17:17:31","slug":"agile-vs-waterfall","status":"publish","type":"post","link":"https:\/\/mgrush.com\/blog\/agile-vs-waterfall\/","title":{"rendered":"Agile vs Waterfall? Don’t Risk Failure By Using the Wrong One"},"content":{"rendered":"

A professional facilitator handles several types of assignments, from planning to design. However, most facilitators must also provide a method for securing the deliverable. Although a different role, the \u2018methodologist\u2019 responsibilities make up the most important part of preparing for many meetings.<\/h2>\n

How will you lead the group successfully\u00a0with meeting design from the Introduction<\/a>\u00a0<\/em>through the Wrap<\/em><\/a>? You will find more than one right answer. Therefore, when weighing Agile<\/a> vs. Waterfall benefits, consider how the Stacey Matrix arrays projects from the simple through the chaotic.<\/span><\/p>\n

An Adapted Stacey Matrix: Agile vs Waterfall<\/strong><\/h3>\n
\"Agile

Agile vs Waterfall — Stacey Matrix<\/span><\/strong><\/p><\/div>\n

Stacey\u2019s original two dimensions included Agreement (among stakeholders) and Certainty (about cause and effect relationships within the project). Hence Agilists made Stacey\u2019s matrix popular by substituting Requirements for Agreement and Technology for Certainty. Therefore, Requirements capture WHAT solution must be built and Technology unveils HOW to provide the solution. Consequently, the primary dimensions range from the clear or known, to the vague or unknown. The quantity of people involved gives a softer, yet third dimension that also directly increases the complexity. Therefore, the balance of this article discusses the five primary zones or areas delineated on the matrix. They include:<\/span><\/p>\n

    \n
  1. The Simple<\/strong><\/span><\/li>\n
  2. Politically Complicated<\/strong><\/span><\/li>\n
  3. Technically Complicated<\/strong><\/span><\/li>\n
  4. Zone of Complexity<\/strong><\/span><\/li>\n
  5. The Chaotic<\/strong><\/span><\/li>\n<\/ol>\n

    Five Zones Overview: Agile vs. Waterfall<\/strong><\/span><\/h3>\n

    The Waterfall mindset demands substantial, up-front planning. Agile frameworks launch quicker, with a much narrower scope during each increment (or Sprint when using Scrum). When the cause and effects are clear and mastered, Waterfall optimizes resources and returns on investment. However, as the customer\u2019s scenario constantly changes, Agile permits adaptation and quick adjustment. Waterfall works especially well with large construction projects and broad-scoped hardware installations. Hence, Agile may be better suited for software products, where the market demands constant and frequent change. When tasks are clearly defined, the waterfall optimizes the sequencing and resource allocation. Therefore, results ought to be consistent, predictable, and repeatable. As tasks require frequent collaboration<\/a> and adjustments, Agile lends a sense of quick response and flexibility not associated with Waterfall. The following table compares the attributes of the five zones. Most models apply identical content to the Complicated Zones. We split the zone into two because the challenges of each demand a different method. When the lack of clarity derives from stakeholders, plan carefully before proceeding (Waterfall). When uncertainty derives from the technology or software, consider the Agile approach, and prepare to change along the way. A brief discussion follows about each.<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
    \n

    Zones\u00a0\u00a0 <\/span> \u00a0 <\/span>Attributes<\/b><\/span><\/h3>\n<\/td>\n

    		\n

    Simple<\/b><\/span><\/p>\n<\/td>\n

    		\n

    Politically Complicated<\/b><\/span><\/p>\n<\/td>\n

    		\n

    Technically Complicated<\/b><\/span><\/p>\n<\/td>\n

    		\n

    Complex<\/b><\/span><\/p>\n<\/td>\n

    		\n

    Chaotic<\/b><\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Positioning<\/b><\/span><\/h4>\n<\/td>\n

    		Telling<\/b>: Rational decision-making and control, orderly, traditional project management, and organizational development<\/span><\/td>\nSelling<\/b>: Political decision-making and control; compromise, negotiation, persuasion, coalition building, relationship building<\/span><\/td>\nConsulting<\/b>: Judgmental decision-making, ideological control, intuition, learning organizations, systems thinking<\/span><\/td>\nCo-creation: <\/b>Collaborative ideation, visioning, iterative improvement, knowledge management, creativity, innovation<\/span><\/td>\nDisintegration or massive avoidance<\/span><\/td>\n<\/tr>\n
    \n

    Focus or Control<\/b><\/span><\/h4>\n<\/td>\n

    		Monitoring, Standards, Guidance. Evidence-based<\/span><\/td>\nNegotiation<\/span><\/span><\/td>\nStrategic or Adaptive Planning<\/span><\/td>\nLearning, Creativity, Trial and Error, Empirical<\/span><\/td>\nDisorder and chaos until novel patterns emerge.<\/span><\/td>\n<\/tr>\n
    \n

    Planning Type<\/b><\/span><\/h4>\n<\/td>\n

    		Operational or Predictive Planning<\/span><\/td>\nStrategic or Adaptive Planning<\/span><\/td>\nStrategic or Scenario Planning<\/span><\/td>\nAdaptive or Scenario Planning<\/span><\/td>\nRapid action and improvising skills<\/span><\/td>\n<\/tr>\n
    \n

    Cause & Effect<\/b><\/span><\/span><\/h4>\n<\/td>\n

    		Relationships between cause and effect are evident.\u00a0<\/span>Apply best practices and use defined process controls.<\/span><\/td>\nCause and effect can be understood by analyzing or investigating the system and its mechanisms. Apply good practices.<\/span><\/td>\nCause and effect can be understood by analyzing or investigating the system and its mechanisms. Apply good practices.<\/span><\/td>\nThe relationship between cause and effect can only be perceived in retrospect, but not in advance. Inspect and Adapt.<\/span><\/td>\nNo clear relationships between cause and effect even if inspected.\u00a0 <\/span>The approach is to Act, Sense, and Respond and we can discover novel practices.<\/span><\/td>\n<\/tr>\n
    \n

    Example<\/b><\/span><\/h4>\n<\/td>\n

    		Drilling for oil in the Permian Basin.<\/span><\/td>\nImproving air quality or building an oil pipeline through North America.<\/span><\/td>\nSending a payload to Mars or beyond the edge of our known solar system.<\/span><\/td>\nRaising a child. Every child is unique resulting in unpredictable outcomes.<\/span><\/td>\n\u201cRunning of the Bulls\u201d (event held in Spain), or the turbulence in the tip vortex from an airplane wing<\/span><\/td>\n<\/tr>\n
    \n

    Comments<\/b><\/span><\/h4>\n<\/td>\n

    		A ‘right’ answer exists, best practices and detailed recipes, fact-based, traditional management<\/span><\/td>\nFrequent disagreement about the value and purpose of the project<\/span><\/td>\nMore than one right answer possible, fact-based, coordination of expertise, reliance on techno-rationale<\/span><\/td>\nEmpirical methods focused on the identification, selection, and development of increments<\/span><\/td>\nHigh turbulence, no patterns, tension, need to create stability, experience may hinder progress<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    1. The Simple Zone: Agile vs. Waterfall<\/strong><\/h3>\n

    When the final result or \u201cDONE\u201d of a project resonates with everyone, especially large projects, Waterfall stays an obvious choice. Relying on fact-based and evidence-based<\/a> decisions, projects will advance in an orderly fashion, generating few surprises. You have all worked with recipes in the kitchen before. Not only are the activities clear and sequenced, but the results are repeatable as well. Best practices serve as the benchmark for both guiding tasks and comparing results.<\/span><\/p>\n

    2. Politically Complicated Zone: Agile vs. Waterfall<\/strong><\/h3>\n

    As requirements\u00a0become less clear, or even conflicting<\/a>, waterfall may remain the best choice. How many project dollars have you seen wasted because people could not agree on the purpose or value of the project? Agile affords productivity while people are negotiating, but you risk working on the wrong stuff without the coalition building encouraged by Waterfall. Always remember –\u00a0 WHY before\u00a0WHAT before HOW<\/a>.<\/em><\/span><\/p>\n

    3. Technically Complicated Zone: Agile vs. Waterfall<\/strong><\/h3>\n

    As the value of adaptive thinking increases, such as embracing innovative technology for the first time, the Agile mindset may be favored. When cause and effect must be analyzed or investigated, the Agile mindset becomes preferred. Knowing that more than one right answer<\/a> exists, a clear and frequent feedback loop with stakeholders helps optimize decisions. Consequently, as Development Teams advance and grow, they become learning organizations, capable of increasing productivity and innovation<\/a>.<\/span><\/p>\n

    4. Zone of Complexity: Agile vs. Waterfall<\/strong><\/h3>\n

    The empirical process control method demands Agile as conditions become increasingly complex. As contrasted with a fully defined process control (Waterfall), empirical methods demand transparency, frequent inspection, and adaptation. Therefore, Agile frameworks promote all three aspects or “legs.”\u00a0Scrum<\/a>, in particular, requires inspections at the conclusion of each Sprint. Teams receive immediate and prompt feedback to help modify later Sprints, without much delay. Do not forget to look at Agile<\/a>, a mindset, as \u201cBeing\u201d while Scrum<\/a>, a framework, represents \u201cDoing\u201d. Hence, an empirical process depends on experimentation and continuous improvement to optimize the performance of project teams.<\/span><\/p>\n

    5. The Chaotic Zone: Agile vs. Waterfall<\/strong><\/h3>\n

    Most recommend Kanban as an Agile approach to deal with chaos. With Kanban, there are no Sprints. Therefore teams, using WIP (Work in Progress), continually deliver and update their product backlog. Hence, as output increases, novel patterns may emerge to help projects migrate from the chaotic to the complex. In chaotic conditions, experience may be useless. However, experimentation may be invaluable. Therefore Act, Sense, and Respond<\/a> –\u00a0<\/em>serve as one way out of chaotic conditions.<\/span><\/p>\n

    The Facilitator<\/a>: Agile vs. Waterfall<\/strong><\/h2>\n

    In conclusion, what does it all mean to facilitators? Since most of us are called upon for the best method to conduct meetings, planning, negotiations, decision-making, etc., the methodological impact trumps the facilitator\u2019s learnings. Hence, you begin to see where helping to manage the political uncertainty becomes paramount for many projects to succeed. You can also sense that \u2018removing impediments\u2019 becomes quite like \u2018making it easy.\u2019 In the Waterfall world when meetings evidence highly productive participants and output, our role shifts to that of scribe or documenter. However, with Agile, the role shifts to that of a referee, trying to clear a path so that Development Teams can do what they do best—build a new product. In both situations, when we have done our jobs well, it is time to get out of the way and be of service. Related Articles:\u00a0http:\/\/www.designisdead.com\/blog\/making-sense-of-agile<\/span><\/p>\n

    In a world where everyone can engage in decisions that affect them<\/span><\/strong><\/span><\/p>\n

    ______<\/b><\/span><\/p>\n

    Lead the Change\u2014One Meeting at a Time<\/b><\/b><\/span><\/h3>\n

    Are you ready to transform how decisions are made, problems are solved, and alignment is built in your organization?<\/span><\/p>\n

    True meeting leadership goes beyond setting an agenda.<\/b> It requires a facilitator who can navigate complexity, balance voices, and drive toward outcomes with clarity and consensus. Our Professional Meeting Leadership Workshop<\/b><\/a> and facilitation training equips you to do just that\u2014blending human-centric methods<\/b> with structured analytical tools<\/b> to foster rigor, inclusivity, and results that stick.<\/span><\/p>\n