Why Agile Does Not Work!
Overview
Less than 1 minute to read
Last Updated: Thu 9 May 2024 08:36
draft
This page is in draft and may include errors or omissions. Please check the discussions for any pending updates and changes to the content or to suggest your own changes.
Agile is a buzzword of software development, and so all software development projects are, almost by default, now declared to be “agile”. The purpose of this page is to provide guidance to program executives and acquisition professionals on how to detect software projects that are really using agile development versus those that are simply waterfall or spiral development in agile clothing (“agile-scrum-fall”).
Recommended Content
-
notFound:
-
We are uncovering better ways of developing software by doing it and helping others do it. These are our values and principles.
-
The Scrum Guide (Guide)The Scrum Guide contains the definition of Scrum.
-
Kanban Guide for Scrum Teams (Guide)The flow-based perspective of Kanban can enhance and complement the Scrum framework and its implementation.
-
Evidence-Based Management (EBM) is an empirical approach that helps organizations to continuously improve customer outcomes, organizational capabilities, and business results under conditions of uncertainty.
notFound: