Difference between revisions of "Beneficiary Development"
(→Beneficiary Benefit Acceptance) |
|||
| Line 1: | Line 1: | ||
[[Beneficiary Development]] is a [[Development Tracks|development track]] that may need to be developed in the [[enablement]] of the [[eDream]]. | [[Beneficiary Development]] is a [[Development Tracks|development track]] that may need to be developed in the [[enablement]] of the [[eDream]]. | ||
| + | |||
| + | [[Beneficiary Development]] is a component of [[execution]]. | ||
==[[Beneficiary Requirements]]== | ==[[Beneficiary Requirements]]== | ||
Revision as of 18:20, 2 August 2014
Beneficiary Development is a development track that may need to be developed in the enablement of the eDream.
Beneficiary Development is a component of execution.
Contents
Beneficiary Requirements
Beneficiary Requirements is the development of the minimum requirements that must be achieved or addressed in order for beneficiary(ies) to try and adopt the solution. The requirements are listed in a grid in the Enablement Strategy along with the strategy of you the requirement will be satisfied.
Beneficiary Validation/Plussing
Beneficiary Validation/Plussing is done during each phase of the solution development and after any changes to the solution to ensure it addresses the needs of the beneficiary.
Beneficiary Commitment
Beneficiary Commitment is the development of the commitment from the beneficiary(ies) to try and adopt the solution. The plan and approach to achieve the commitment is in the Commitment Plan. It also includes the beneficiary(ies) Degree of Influence over the entire eDream, Commitment Criteria and Commitment Status.
Beneficiary Benefit Acceptance
Beneficiary Benefit Acceptance is the development of the benefit the beneficiary(ies) receive from trying and adopting the solution.
