Once a project has been created in the portfolio for a stakeholder, following a performance alert involving that stakeholder, the project will be linked to values and/or risks that have already been identified for the worksystem or habitat. The portfolio is connected to the worksystem or habitat for a certain time window (from a point in the past to a point in the future).
For its (given set of related) problems and risks, each project will include three phases:
- fact-finding (analysis): what facts give rise to the problem or to the risk? and what facts must be considered when deciding the solution of the problems, or the mitigation of the risks?
- decision: what combination of actions (and value exchanges) is selected to solve the problem and/or mitigate the risk?
- execution: the selected actions are executed in the worksystem or habitat.
Depending on the complexity of the problems and risks and their solutions, as evidenced by the inability to take a well-founded decision following the prior fact-finding activity, analysis will have to dig deeper into the system to articulate the problems, risks and components of a solution.
This situation-dependent depth of analysis (and as a consequence of decision and execution) is reflected in the 3V model that is explained below, and in the structure of the supporting repository.
In this way, one can articulate the need for the system development techniques that Whitten et al (2004) have compiled for the 8 development process phases of FAST (1. Scope Definition, 2. Problem 3. Analysis, 4. Requirements, 5. Logical Design, 6. Decision Analysis, 7. Physical Design & Integration, and 8. Installation & Delivery). These development phases afford multiple project scripts geared at information systems development and implementation. (For more details and references, see Cross-scale Assets)
It is executed according to a project script (see Project Scripts for options).
Each project charter held in Repository/Portfolio may be created or updated following the evaluation of a performance alert in PPM1.Scope or following project-related decisions in PE-V1.Decision, PE-V2.Decision or PE-V3.Decision.
The Project's script will consist of activities selected from:
- Direct Decision (V1): PE V1.Articulation, PE V1.Decision and PE V1.Installation
- Operations Project (V2): In addition to the V1 activities, there are PE-V2.Analysis, PE-V2.Decision and PE-V2.Construction.
- ICT Project (V3): In addition to the V2 activities, there are PE-V3.Requirements, PE-V3.Logical Design, PE-V3.Decision and PE-V3.Physical Design & Integration.
- PE.V1-Articulation
- PE.V1-Decision
- PE.V1-Installation
- PE.V2-Analysis
- PE.V2-Construction
- PE.V2-Decision
- PE.V3-Decision
- PE.V3-Logical Design
- PE.V3-Physical Design & Integration
- PE.V3-Requirements
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
- "Project Execution" among the interactions
- All interactions
- All events
- On the template