When is Agile not suitable for a project?
Agile is not suitable when there are immutable requirements that cannot be negotiated, such as in military or medical systems, or when there is a defined process order (sequential order).
Requirements and deliverables cannot be compromised
An example would be military systems, such as a plane that must fly at a specific speed to fulfill its mission.
What does “immutable requirements” mean?
Immutable requirements are those that cannot be changed without compromising the system’s integrity.
What are some scenarios where Waterfall is preferred?
Waterfall is preferred when requirements are well-defined, and strict management control is needed.
What keywords indicate a preference for Agile methodology?
Keywords include flexibility, evolution, user involvement, and changing requirements.
How does team size affect the choice between Agile and Waterfall?
Large teams typically prefer Waterfall, while Agile teams are usually limited to about seven members.
What approach is preferred if users have limited availability?
Waterfall is preferred because it allows for upfront requirements gathering without ongoing user involvement.
How does risk management differ between Agile and Waterfall?
Waterfall uses classic risk analysis with contingency funds, while Agile employs a more flexible approach to risk management.
What does it mean if requirements are likely to change?
It implies uncertainty in requirements, which leans towards using Agile methodology.
What is a “proof of concept,” and which methodology does it align with?
A proof of concept is a demonstration to validate ideas, and it aligns with Agile methodology.
When is it appropriate to use Agile for funding risks?
Agile is appropriate when funding is unstable, allowing for adjustments based on available resources.