Agile Manifesto & Agile doesn't fit everywhere Flashcards
Agile manifesto
Agreed upon a set of agile values and principles. (4 values and 12 clarifying principles, along with core practices)
When might it make more sense to use an agile approach?
When there is a high uncertainty of work.
Stacey complexity model
The Stacey Complexity Model helps determine the best approach to decision-making and management based on the level of certainty and agreement about a project or problem. It divides scenarios into four zones. This model helps identify when traditional project management works versus when adaptive, flexible methods are needed. (tech vs requirement uncertainty)
Simple zone (Stacey model)
High certainty and agreement. Use standard processes and best practices.
Complicated zone
Certainty is high, but agreement requires expert analysis. Use expert judgment and structured approaches.
Complex zone
Low certainty and agreement. Use iterative methods (e.g., Agile) and experimentation.
Chaotic zone
No certainty or agreement. Immediate action is required to stabilize the situation before planning.
Predictive (waterfall) approach
The frequency of delivery is low, and the degree of change is low. Fixed requirements, activities performed once for the entire project, single delivery, the goal is to manage cost.
Iterative approach
We get feedback all the time. Deliveries are low-frequency and high-degree of change. Dynamic requirements and activities are repeated until correct, and there is a single delivery. The goal is the correctness of the solution. Practical when a product or result must go through successive prototypes or proofs of concept before final release.
Incremental approach
Delivering in increments. High degree of delivery and low degree of change. Dynamic requirements, activities performed once for a given increment, frequent smaller deliveries, goal is speed.
Adaptive (Agile) approach
The frequency of delivery is high, and the degree of change is high. Dynamic requirements and activities are repeated until correct, with frequent small deliveries and customer value via frequent deliveries and feedback.
Hybrid approach
A mix of various approaches with retrospectives. It may be used as a transition strategy to a different approach. Uses some parts of predictive and some parts of agile.
Retrospective
A structured meeting held at the end of a project or a specific project phase (common in Agile/Scrum) to reflect on what went well, what didn’t, and how processes can improve in the future.
Mostly agile with some predictive (hybrid)
Integrating an external component developed in full by an external vendor means that a single iteration might be required after their component is delivered.
Mostly waterfall with some agile
Delivering a straightforward project but trialing a new material in incremental releases.