Different methods are more likely to be useful in each of the performance domains. While the needs of the delivery approach, product, and organizational environment will determine which methods are most applicable for a specific project, there are some performance domains that are more likely to make use of specific methods. Table 4-2 suggests the performance domain(s) where each method is most likely to be of use; however, the project manager and/or project team have the ultimate responsibility for selecting the right methods for their project.
Table 4-2. Mapping of Methods Likely to Be Used in Each Performance Domain
4.6 COMMONLY USED ARTIFACTS
An artifact is a template, document, output, or project deliverable. There are many documents or deliverables that are not described here, either because (a) they are somewhat generic, such as updates; (b) they are industry specific; or (c) they are a result of a specific method that was used to create it, for example, while cost estimates are an important artifact, they are the result of various estimating methods.
The content in this section is not meant to describe how to develop or create an artifact. The descriptions are presented at a high level as project managers and/or project team members are expected to tailor the use of these artifacts to meet the needs of their particular project. There is more detailed information on these and other artifacts from many sources, including PMIstandards+.
4.6.1 STRATEGY ARTIFACTS
Documents that are created prior to or at the start of the project that address strategic, business, or high-level information about the project. Strategy artifacts are developed at the start of a project and do not normally change, though they may be reviewed throughout the project.
- Business case. A business case is a value proposition for a proposed project that may include financial and nonfinancial benefits.
- Business model canvas. This artifact is a one-page visual summary that describes the value proposition, infrastructure, customers, and finances. These are often used in lean start-up situations.
- Project brief. A project brief provides a high-level overview of the goals, deliverables, and processes for the project.
- Project charter. A project charter is a document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities.
- Project vision statement. This document is a concise, high-level description of the project that states the purpose, and inspires the project team to contribute to the project.
- Roadmap. This document provides a high-level time line that depicts milestones, significant events, reviews, and decision points.
Leave a Reply