For each performance alert received from LC.Monitoring & Evaluation the PM1.Scope activity must have one of the following effects:

  • nothing is done and the performance alert is stored in the performance alert register at the Repository/Portfolio together with date, some classifiers, a justification of the decision, and the name of the person deciding to ignore it (for the time being);
  • a new project is started to address the performance alert, this project will start with PE-V1.Articulation and a new project is registered in the Portfolio
  • the performance alert is assigned to an existing project for analysis and solution, this assignment will be performed in the Repository/Portfolio, and must .

In cases 2 and 3 the boundaries of the project are described. The scope indicates the areas of a business that a project may (or may not) address. The scope statement must include answers to five basic questions:

  • Product, e.g. which part of the business (processes) is being addressed,
  • Quality, e.g., which performance improvements are pursued for the product,
  • Time, within which time frame,
  • Cost, at what cost,
  • Resources, what resources are available.

A statement of work is a narrative description of the work to be performed as part of a project. Common synonyms include scope statement, project definition, project overview, and document of understanding.

Regarding resources, the project team must obtain commitments for the following resources:

  • People: includes all the system owners, users, analysts, designers, builders, external agents, and clerical help that will be involved in the project in any way.
  • Services: includes services such as a quality review that may be charged on a per use basis.
  • Facilities and equipment : includes all rooms and technology that will be needed to complete the project.
  • Supplies and materials: includes everything from pencils, paper, notebooks to toner cartridges, and so on.

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
Part of par
Parts child
Succeeding Interactions suc
Alternatives alt
Action Realm Change
Risks risks
Further reading ref

Add a New Comment