In this activity, candidate solutions delivered by V1.Articulation of a project are evaluated in terms of:
- Regulatory/Institutional feasibility: Is the solution compliant with prevailing regulations and institutions?
- Technical feasibility: Is the solution technically practical? Does our staff have the technical expertise to use this solution?
- Operational feasibility: Will the solution solve the problem? 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 acquired 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 V1.Articulation it must be decided whether to continue the project with V1.Installation (there is no need for significant changes to PPAM or to E&M) or with V2.Analysis (the PPAM and E&M must be analysed and might need changes).
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.V1-Decision" among the interactions
- All interactions
- All events
- On the template