PE.V2-Decision
In the V2.Decision activity candidate solutions delivered by PE V2.Analysis of a project are evaluated in terms of:
- Technical feasibility: Is the solution technically practical? Does our staff have the technical expertise to design and build this solution?
- Operational feasibility: Will the solution fulfill the users’ requirements? To what degree? How will the solution change the users’ work environment? How do users feel about such a solution?
- Economic feasibility:Is the solution cost-effective?
- Schedule feasibility: Can the solution be designed and implemented within an acceptable time?
- Risk feasibility: What is the probability of a successful implementation using the technology and approach?
On the basis of the decision analysis a project may be continued (with additional resources), it may be suspended, merged with another project, or split into sub-projects. In all these case, project data in Repository/Portfolio will be modified accordingly.
The most common project workflow is that following V2.Analysis it must be decided whether to continue the project with V2. Construction or with V3.Requirements (not only PPAM and E&M will need changes, but also the supporting ICT may need to be changed).
Description
| Name1 | name | ||||||||||||
| Domain | |||||||||||||
| Target Outcome | outcome | ||||||||||||
| Social actors and roles | roles | ||||||||||||
| Trigger or preceding interaction | prec | ||||||||||||
| Interfaces and services | services | ||||||||||||
| Inputs and outputs | i/o | ||||||||||||
| Stores and tools |
Regarding Content that is Accurate and Reliable, this will be part of Repository for partnerships (wikiworx). tools |
||||||||||||
| Other characteristics |
|
||||||||||||
| Further reading | ref |
- Questions, answers, comments
- "PE.V2-Decision" among the interactions
- All interactions
- All events
- On the template
Add a New Comment