Create project plans, schedules, and work breakdown structures (ti3678)

Create project plans, schedules, and work breakdown structures (ti3678)

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:

CIM, contribution, create, item, learning, management, plans, project, training, work-based
This Training Item focuses on project plans, work breakdown structures, schedules, tasks, timing, dependencies, milestones, coordination logic, resource needs, stakeholder expectations, risks, constraints, and follow-through.

Criteria

Contribution recognized

The contributor creates project plans, schedules, and work breakdown structures through a situated workplace or civic/community contribution that produces a usable output for another person’s planning, coordination, decision, or action.

Learning Goal

  • LG035 — Learners will develop their ability to create project plans that support organized delivery.

Learning Outcomes

  1. LO103 — Upon completion, the learner will be able to create a basic work breakdown structure from a project scope.
  2. LO104 — Upon completion, the learner will be able to develop a project schedule based on planned work.
  3. LO105 — Upon completion, the learner will be able to connect project tasks, timing, and stakeholder expectations.

Aligned Knowledge, Skills, and Behaviours

  • K001 — Knowledge: Understands organizational structures and management functions in order to contribute to coordinated activity.
  • K003 — Knowledge: Understands management information and evidence systems in order to contribute to informed planning, monitoring, and decision-making.
  • 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.
  • 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.
  • S014 — Skill: Coordinates stakeholders, resources, tasks, and information using action pathways to support implementation, delivery, or improvement.
  • 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.
  • B006 — Behaviour: Demonstrates constructive collaboration by supporting inclusion, cooperation, and shared responsibility in group or stakeholder settings.

Acceptable Artifact Element

AE003 — Project Documentation

Evidentiary purpose: Makes the contributor’s situated role and use of LO103, LO104, LO105 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 plan, work breakdown structure, schedule, task list, milestone tracker, dependency map, coordination plan, project delivery worksheet, implementation planning file, responsibility matrix, action pathway, or monitoring tracker that organizes planned work, timing, resources, roles, and stakeholder expectations.

Civic/community example

A civic/community project plan, event work breakdown structure, volunteer schedule, task list, milestone tracker, dependency map, coordination plan, civic initiative worksheet, implementation planning file, responsibility matrix, action pathway, or monitoring tracker that organizes planned work, timing, resources, roles, and stakeholder expectations.

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 LO103, LO104, LO105 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 project work, tasks, timing, dependencies, milestones, stakeholders, resources, risks, or coordinated delivery needed to be organized.; Task: The participant explains the responsibility, delivery need, scheduling issue, dependency, coordination challenge, stakeholder expectation, resource need, risk, constraint, trade-off, or planning objective connected to creating project plans and schedules.; Action: The participant describes how they created a basic work breakdown structure, developed a project schedule, connected project tasks, timing, and stakeholder expectations, and supported coordination through roles, resources, information, and follow-up.; Result: The participant describes the improved coordination, clearer delivery path, scheduling clarity, stakeholder alignment, task organization, dependency awareness, project delivery support, shared responsibility, or follow-through that resulted from the contribution.; Relevance: The participant explicitly connects the reflection to LG035, LO103–LO105, and the Training Unit-Level KSBs K001, K003, K012, S001, S004, S012, S014, B003, B004, and B006. It explicitly connects the contribution to LO103, LO104, LO105 and the aligned KSBs K001, K003, K012, S001, S004, S012, S014, B003, B004, B006.

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 LO103, LO104, LO105, 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 planning, work breakdown, scheduling, task coordination, dependencies, timing, stakeholder expectations, resources, roles, risks, or delivery coordination.; Contribution Confirmation: The witness confirms the participant contributed to creating, organizing, documenting, communicating, coordinating, or maintaining project plans, schedules, work breakdown structures, task coordination materials, role information, or dependency information.; LO Confirmation: The witness confirms the contribution reasonably relates to creating a work breakdown structure, developing a project schedule, and connecting tasks, timing, and stakeholder expectations.; KSB Confirmation: The witness confirms the contribution supports developmental alignment to K001, K003, K012, S001, S004, S012, S014, B003, B004, or B006 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 -