Models, Methods & Artifacts — Overview
Section 4 is a toolbox, not a checklist. As you answer the tailoring questions (§3.5), you pick the models that shape thinking, the methods that get work done, and the artifacts that capture and share information. None of the lists are exhaustive or prescriptive.
Model
A thinking strategy to explain a process, framework or phenomenon — a simplified view of reality that shapes behaviour and points to approaches for solving problems.
Method
A means for achieving an outcome, output, result or deliverable — how the work actually gets done (gathering data, estimating, meeting, etc.).
Artifact
A template, document, output or deliverable — the tangible records produced and shared, tailored to the project and its environment.
How they fit together (Figure 4-1)
All three are tailored to the project, the internal environment and the external environment — and sit on the foundation of the 12 principles and the system for value delivery.
The three families at a glance
- Models (4.2): situational leadership, communication, motivation, change, complexity, team development, other.
- Methods (4.4): data gathering & analysis, estimating, meetings & events, other.
- Artifacts (4.6): strategy, logs & registers, plans, hierarchy charts, baselines, visual data, reports, agreements, other.
Choose wisely — avoid waste
Every model, method and artifact has a cost: time, expertise, and impact on productivity. As much as possible, avoid anything that duplicates effort, isn’t useful to the team or stakeholders, produces misleading information, or serves an individual rather than the team. Sections 4.3 / 4.5 / 4.7 map each item to the performance domains where it is most likely useful — but the team always makes the final call.