This section provides a high-level description of some commonly used models, methods, and artifacts that are useful in managing projects. The items listed in this section are not intended to be exhaustive or prescriptive, but rather to help project teams think about the options available to them.
In the context of this guide, terms are defined as follows:
- Model. A model is a thinking strategy to explain a process, framework, or phenomenon.
- Method. A method is the means for achieving an outcome, output, result, or project deliverable.
- Artifact. An artifact can be a template, document, output, or project deliverable.
As project teams consider the tailoring questions in Section 3.5 and decide on specific responses to those questions, they will start to build a framework for structuring their efforts to deliver the project outcomes. For example, project teams select specific methods to enable capturing and sharing the applicable information so they can track progress, improve project team performance in real time, and engage stakeholders.
Figure 4-1 shows how tailoring includes the models and methods used to perform work in the project performance domains. The deliverables and the artifacts are also tailored to the project, internal environment, and external environment.
Figure 4-1. Tailoring to Fit the Project Context and Environment
As with any process, the use of models, methods, and artifacts has associated costs related to time, level of expertise/proficiency in use, impact on productivity, etc. Project teams should consider these implications when deciding which elements to use. As much as possible, project teams should avoid using anything that:
- Duplicates or adds unnecessary effort,
- Is not useful to the project team and its stakeholders,
- Produces incorrect or misleading information, or
- Caters to individual needs versus those of the project team.
Leave a Reply