Difference between revisions of "Beneficiary Requirements"
From WikiDreams
Line 2: | Line 2: | ||
==[[Problem/UnMet Need]] Importance== | ==[[Problem/UnMet Need]] Importance== | ||
− | + | What is the importance of addressing the [[Problem/UnMet Need]]? | |
+ | ==[[Solution Incumbant]]== | ||
+ | * What is the [[Solution Incumbant]]? | ||
+ | ==[[Realities]]== | ||
+ | * What [[Realities]] are impacting the [[solution]] choice? | ||
==[[Solution Design]]== | ==[[Solution Design]]== | ||
+ | * Does the [[Solution Design]] address the [[Problem/UnMet Need]]? | ||
+ | * Does the [[Solution Design]] encourage [[Solution Adoption]]? Easy to try? Easy to change? Easy to experience benefits? | ||
+ | * Does the [[Solution Design]] provide enough [[Solution Benefits]]? Easy to experience the benefits? | ||
+ | * How does the [[Solution Design]] compare with the [[Solution Incumbant]]? | ||
+ | * How would the [[Solution Design]] be impacted by the [[Realities]]? | ||
+ | ==[[Solution Acceptance Criteria]== |
Revision as of 18:09, 2 August 2014
Beneficiary Requirements are a subset of the minimum requirements that must be achieved or addressed to satisfy each of the eDream Components and Enablement Components. The requirements are listed in a grid in the Enablement Strategy along with the strategy of you the requirement will be satisfied.
Contents
Problem/UnMet Need Importance
What is the importance of addressing the Problem/UnMet Need?
Solution Incumbant
- What is the Solution Incumbant?
Realities
Solution Design
- Does the Solution Design address the Problem/UnMet Need?
- Does the Solution Design encourage Solution Adoption? Easy to try? Easy to change? Easy to experience benefits?
- Does the Solution Design provide enough Solution Benefits? Easy to experience the benefits?
- How does the Solution Design compare with the Solution Incumbant?
- How would the Solution Design be impacted by the Realities?