3.3 Determine how to document project controls for an adaptive project

Agile Frameworks/Methodologies


3.3.1Identify artifacts that are used in adaptive projects

3.3.1 Identify artifacts that are used in adaptive projects

Here’s a comprehensive list of artifacts used in adaptive projects, organized into relevant groups:

Project Planning and Initiation Artifacts

  • Project Charter: A document that outlines the project’s objectives, stakeholders, and high-level risks.
  • Project Vision Statement: A concise description of the project’s core purpose and desired outcome.
  • Product Roadmap: A high-level visual representation of the product’s goals, milestones, and deliverables.
  • Release Plan: A high-level plan outlining the schedule, scope, and goals for each release, including multiple iterations or sprints.

Refer to Agile Planning for more details.

Requirements and Backlog Artifacts

  • User Stories: Short, simple descriptions of desired functionality from the end user’s perspective.
  • Product Backlog: A dynamic, ordered list of user stories, features, and requirements that need to be developed.
  • Iteration Backlog: A detailed, prioritized list of user stories, tasks, and requirements to be completed during a specific iteration or sprint.
  • Definition of Ready (DoR): A set of criteria that ensures user stories or requirements are clear, concise, and actionable before development begins.

Iteration Planning and Tracking Artifacts

  • Sprint Plan: A detailed plan for the work to be completed during a specific iteration or sprint.
  • Task Board: A visual representation of the work items, their status, and progress during an iteration, often using a Kanban-style board.
  • Burndown Chart: A graphical representation of the remaining work in an iteration, used to track progress and forecast completion.

Architecture and Design Artifacts

  • Architecture Vision: A high-level description of the system’s architecture, including key components, relationships, and constraints.
  • Design Documentation: Detailed descriptions, diagrams, and specifications of the software or product’s design, including any changes made during the project.

Collaboration and Communication Artifacts

  • Project Dashboard: A centralized location for tracking project progress, key performance indicators (KPIs), and other relevant data.
  • Meeting Agendas and Minutes: Documentation of meetings, including goals, discussions, decisions, and action items.

Quality and Performance Artifacts

  • Definition of Done (DoD): A set of criteria that ensures a work item or user story has been completed to a high standard and is ready for release.
  • Test Cases and Test Plans: Documentation of the testing process, including test scenarios, expected results, and actual outcomes.
  • Performance Metrics and Reports: Data and analysis of the project’s performance, such as cycle time, lead time, and throughput.

Risk and Issue Management Artifacts

  • Risk Register: A document listing potential risks, their likelihood and impact, and any mitigation or contingency plans.
  • Impediments Log: A record of identified issues, their status, and actions taken to resolve them.

Review and Adaptation Artifacts

  • Retrospective Reports: Documentation of lessons learned, successes, and areas for improvement gathered during regular team retrospectives.
  • Project Change Log: A record of changes to project scope, requirements, or objectives throughout the project lifecycle.
Last updated: April 22, 2024