Exam NP-Con-102 Topic 1 Question 13 Discussion

The organization's requirements-fixed budget, fixed scope, and deliverables defined upfront-are the classic characteristics of the Waterfall methodology.
In a Waterfall implementation for Nonprofit Cloud:
* Linear Progression: The project follows a strict sequence: Requirements -> Design -> Build -> Test -> Deploy. You do not move to the next phase until the previous one is "signed off."
* Upfront Requirements: As mentioned in the prompt, the organization believes they already know exactly what they need. A consultant spends a long "Discovery" phase at the beginning documenting every single field, report, and automation.
* Predictability: This model provides the nonprofit's board with a clear "end date" and a total cost, which is often attractive for organizations with rigid fiscal year budgets.
Why this is different from other methods:
* Agile (Option B): Agile assumes the scope will change as the users learn more about the system. It prioritizes flexibility over a fixed upfront scope.
* Kanban (Option C): Kanban is a "just-in-time" delivery system focused on visualizing work and managing flow. It is typically used for ongoing support or "business-as-usual" tasks rather than a structured implementation with a fixed SOW and predefined deliverables.
For a consultant, while the organization wants Waterfall, it is important to warn them that translating
"spreadsheets and notepads" into a sophisticated cloud system often reveals new requirements that Waterfall's rigid structure may struggle to accommodate without costly "Change Orders."