Design project charters and scope statements (ti3798)

Design project charters and scope statements (ti3798)

logo

Contribution Exchange

info@contributionexchange.org

Making contribution visible, trusted, and portable.

Contribution Exchange is an international organization headquartered in Ottawa, Canada, building shared infrastructure for recognizing learning and capability developed through contribution.

Through an international federation of National Contribution Exchanges, Contribution Exchange stewards common standards for work-based learning, professional practice, recognition, and quality assurance. Its systems help organizations structure, validate, and recognize learning developed through work, community, civic, cultural, and other purposeful contributions.

Contribution Exchange also stewards the Work-Based Learning Numbering System (WBLNS®) and PathLedger®, providing interoperable infrastructure to index learning standards, record verified contributions, and make trusted evidence of capability portable across organizations, sectors, and borders.

Tags:

charters, CIM, contribution, design, item, learning, management, project, training, work-based
This Training Item focuses on project charters, scope statements, project purpose, stakeholder expectations, desired project outcomes, assumptions, constraints, risks, approval needs, trade-offs, and initiation requirements.

Criteria

Contribution recognized

The contributor designs project charters and scope statements through a situated workplace or civic/community contribution that produces a usable output for another person’s planning, coordination, decision, or action.

Learning Goal

  • LG034 — Learners will develop their ability to design project initiation documents that support stakeholder value.

Learning Outcomes

  1. LO100 — Upon completion, the learner will be able to identify required elements of a project charter.
  2. LO101 — Upon completion, the learner will be able to define project scope within a management scenario.
  3. LO102 — Upon completion, the learner will be able to summarize project purpose and desired outcomes for stakeholders.

Aligned Knowledge, Skills, and Behaviours

  • K001 — Knowledge: Understands organizational structures and management functions in order to contribute to coordinated activity.
  • K012 — Knowledge: Understands project management concepts in order to contribute to project planning, coordination, delivery, and review.
  • S001 — Skill: Identifies, classifies, and summarizes management issues, structures, processes, and desired outcomes using available organizational information to support decisions.
  • S003 — Skill: Builds supported arguments using claims, evidence, reasoning, and stakeholder context to influence decisions and coordinated action.
  • S004 — Skill: Negotiates strategically using interests, options, constraints, trade-offs, and agreed next steps to support stakeholder alignment.
  • S012 — Skill: Supports project planning and delivery using charter information, scope, schedules, tasks, resources, risks, and progress information.
  • B002 — Behaviour: Demonstrates clear and respectful communication by adapting language, tone, and message structure to stakeholders and context.
  • B003 — Behaviour: Demonstrates systems awareness by connecting people, functions, resources, processes, and outcomes in contribution contexts.
  • B004 — Behaviour: Demonstrates evidence-informed decision-making by using relevant information, analysis, and context when contributing to decisions.

Acceptable Artifact Element

AE003 — Project Documentation

Evidentiary purpose: Makes the contributor’s situated role and use of LO100, LO101, LO102 visible through a naturally occurring project documentation.

Minimum characteristics: - A genuine workplace or civic/community context. - An attributable contributor role. - A usable output aligned to the selected Learning Outcomes. - Sufficient context for AC001 and AC002 validation.

Workplace example

A workplace project charter, scope statement, project brief, stakeholder requirement note, desired outcome summary, initiation document, assumptions and constraints note, risk note, approval note, or management planning worksheet that defines project purpose, scope, stakeholders, intended value, constraints, or approval needs.

Civic/community example

A civic/community project charter, event scope statement, initiative brief, stakeholder requirement note, desired outcome summary, committee planning worksheet, assumptions and constraints note, risk note, approval note, or civic project initiation document that defines project purpose, scope, stakeholders, intended value, constraints, or approval needs.

Experience Context

  • Autonomy: Follow — Develops the artifact using an established approach with regular direction and review.
  • Complexity: Follow — Works with familiar information and a defined situation; direct reproduction without situated interpretation is insufficient.
  • Contribution scope: Follow — Produces an output that is used within an assigned task or immediate contribution activity.

Assessment Components

AC001 — STARR Reflection

Redo (R): The STARR Reflection is missing, is not attributable to the contributor, does not sufficiently address one or more required STARR elements, or does not establish a credible connection to LO100, LO101, LO102 and the aligned KSBs.

Pass (P): The STARR Reflection is complete, situated, and attributable. It addresses Situation: The participant identifies a workplace or civic/community setting where a project, initiative, event, improvement activity, or coordinated task required a charter, scope statement, project purpose, stakeholder alignment, or desired outcomes.; Task: The participant explains the responsibility, planning need, scope question, stakeholder expectation, desired outcome, assumption, constraint, risk, trade-off, approval need, or project initiation objective connected to designing project initiation documents.; Action: The participant describes how they identified required project charter elements, defined project scope, summarized project purpose and desired outcomes, and considered stakeholder interests, constraints, and approval needs.; Result: The participant describes the planning clarification, stakeholder alignment, scope control, project initiation support, coordination improvement, decision support, approval readiness, or shared understanding that resulted from the contribution.; Relevance: The participant explicitly connects the reflection to LG034, LO100–LO102, and the Training Unit-Level KSBs K001, K012, S001, S003, S004, S012, B002, B003, and B004. It explicitly connects the contribution to LO100, LO101, LO102 and the aligned KSBs K001, K012, S001, S003, S004, S012, B002, B003, B004.

AC002 — Contribution Witness Statement

Redo (R): The Contribution Witness Statement is absent, unattributable, provided by a person unable to confirm the contribution context, or does not sufficiently confirm the contributor’s role, situated contribution, relationship to LO100, LO101, LO102, and claimed KSB alignment.

Pass (P): An identifiable and contextually appropriate witness provides a credible statement that addresses Context Confirmation: The witness confirms the participant participated in a workplace or civic/community context involving project initiation, scope definition, stakeholder planning, desired outcomes, assumptions, constraints, risks, approvals, or coordinated project activity.; Contribution Confirmation: The witness confirms the participant contributed to identifying, drafting, summarizing, communicating, or organizing project charter, scope, purpose, stakeholder, risk, constraint, approval, or outcome information.; LO Confirmation: The witness confirms the contribution reasonably relates to identifying project charter elements, defining project scope, and summarizing project purpose and desired outcomes for stakeholders.; KSB Confirmation: The witness confirms the contribution supports developmental alignment to K001, K012, S001, S003, S004, S012, B002, B003, or B004 and does not contradict the claimed alignment.; Credibility: The witness is identifiable and has sufficient relationship to the contribution context to confirm the evidence.

Completion requirement

Both AC001 and AC002 must achieve Pass (P). A Redo (R) on either component returns the Training Item for revision. Distinction is not available at Training Item level.

Your RPL Submission Must Include:

1. STARR Reflection Statement A structured, first-person account that addresses all Learning Outcomes (LIs) and related Knowledge, Skills, and Behaviours (KSBs) through a real experience.

2. Contribution Witness Statement An endorsement from someone who directly observed or received the written product. Please provide:

Full Name

Email Address

Their Role and Relationship to You (e.g., “Project Lead,” “Board Chair,” “Small Business Owner”)

3. Submission Evaluation Once your STARR reflection is sent to your contribution witness, a Contribution Exchange staff member will review the file for completion, record your evidence for PathLedger, and you will receive your badge.

Please use the format: X0X 0X0 (ANA NAN)
**STARR FORMAT** ----- Use the following STARR format and ensure your story aligns with the Learning Goal (LG), all Learning Outcomes (LIs) and addresses each of the KSBs.
Situation: What was the setting or challenge?
Task: What did you need to communicate and why?
Action: How did you plan, write, revise, and format your communication?
Result: What was the impact or outcome?
Reflection: What did you learn? How did it build your writing capability and support collaboration or leadership?
Please provide a valid email address for your witness.
Please use the format - First Name Last Name.
Example: “Project Lead,” “Board Chair,” “Small Business Owner”
- or -

Powered by

CanCred Factory logo