Assist with Project Management Activities (tu9618)

Contribution recognized

Support project initiation and planning using charter, scope, schedule, cost, and stakeholder-value documentation.

Training Unit structure

This Training Unit aggregates exactly three child Training Items:

1. ti3798 — Design project charters and scope statements (73.3.CA6532/ti3798D)
2. ti3678 — Create project plans, schedules, and work breakdown structures (73.3.CA6532/ti3678D)
3. ti3033 — Estimate costs and establish cost baselines (73.3.CA6532/ti3033D)

Completion requires two naturally occurring Artifact Elements that together provide substantial evidence across the three child Training Items.

Aggregated Learning Goals

• LG034 — Learners will develop their ability to design project initiation documents that support stakeholder value.
• LG035 — Learners will develop their ability to create project plans that support organized delivery.
• LG036 — Learners will develop their ability to estimate project costs and establish cost baselines to support controlled project delivery.

Aggregated 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.
4. LO103 — Upon completion, the learner will be able to create a basic work breakdown structure from a project scope.
5. LO104 — Upon completion, the learner will be able to develop a project schedule based on planned work.
6. LO105 — Upon completion, the learner will be able to connect project tasks, timing, and stakeholder expectations.
7. LO106 — Upon completion, the learner will be able to identify cost elements in a project plan.
8. LO107 — Upon completion, the learner will be able to estimate project costs for a defined project scenario.
9. LO108 — Upon completion, the learner will be able to prepare a basic project cost baseline for management review.

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

Indicative Content

ti3798 — Design project charters and scope statements

• LO100 — Project Management Purpose: Project value, stakeholder needs, project objectives, project lifecycle awareness, coordinated delivery, and responsible management of moving parts.
• LO101 — Project Charters: Project purpose, objectives, deliverables, sponsor or authorizing party, stakeholders, assumptions, constraints, risks, success criteria, approval needs, and authority boundaries.
• LO102 — Scope Management: Scope statements, inclusions, exclusions, boundaries, constraints, deliverables, acceptance criteria, scope control, and stakeholder alignment.
• LO102 — Project Communication: Project briefings, stakeholder updates, presentation of scope/schedule/cost implications, supported project rationale, alignment communication, and clear project documentation.

ti3678 — Create project plans, schedules, and work breakdown structures

• LO103 — Work Breakdown Structures: Work packages, activities, phases, deliverables, task hierarchy, responsibilities, dependencies, and connection between scope and planned work.
• LO104 — Project Scheduling: Milestones, sequencing, dependencies, timelines, due dates, schedule assumptions, critical timing considerations, and schedule control.
• LO105 — Stakeholder Value: Stakeholder expectations, intended value, beneficiary needs, communication requirements, decision points, approvals, and value delivery.
• LO105 — Risks, Constraints, and Trade-Offs: Project risks, dependencies, constraints, unresolved issues, escalation needs, change-control considerations, scope/schedule/cost trade-offs, resource limitations, and mitigation actions.

ti3033 — Estimate costs and establish cost baselines

• LO106 — Cost Estimating and Cost Baselines: Cost elements, resource estimates, assumptions, budget categories, cost estimates, baseline amounts, cost tracking, and cost-control points.
• LO107 — Coordination and Follow-Through: Role clarity, action pathways, handoffs, task ownership, approvals, communication routines, monitoring points, reporting needs, and implementation readiness.
• LO108 — Contextual Application: Workplace or civic/community settings where projects, events, service initiatives, improvement activities, coordinated tasks, or temporary initiatives require structured planning and stakeholder coordination.

Artifact Element 1

AE003 — Project Documentation

Evidentiary purpose: Captures an integrated project charter and planning package showing how the participant organized project purpose, stakeholder value, scope, work breakdown structure, schedule, cost estimate, cost baseline, responsibilities, authority relationships, assumptions, constraints, risks, trade-offs, approvals, monitoring, and coordination logic. this Artifact Element record is designed to evidence project management concept knowledge, project planning support, management information use, stakeholder coordination, systems awareness, evidence-informed planning, and constructive collaboration across people, resources, timing, costs, deliverables, and outcomes.

Minimum characteristics: - Identifies the project, purpose, problem/opportunity, intended value, beneficiary or stakeholder group, and organizational or civic/community context. - Identifies objectives, deliverables, sponsor or authorizing party, project manager/coordinator role, stakeholders, assumptions, constraints, risks, approval needs, and success criteria. - Defines what is included, excluded, bounded, or constrained in the project. - Breaks the project into major work packages, activities, outputs, phases, or deliverable components. - Identifies contributors, role holders, responsible parties, decision points, approvals, communication responsibilities, authority boundaries, or accountability points. - Provides milestones, sequencing, dependencies, timeline, due dates, phases, schedule assumptions, or critical timing considerations based on the project plan. - Identifies cost categories, resource estimates, assumptions, budget limits, baseline amount, cost-control points, or financial tracking logic. - Identifies risks, dependencies, constraints, unresolved issues, escalation needs, change-control considerations, scope/schedule/cost trade-offs, mitigation actions, or assumptions requiring monitoring. - Identifies tracking approach, review points, progress measures, reporting needs, stakeholder updates, approval gates, handoffs, or next steps. - Explains how stakeholders, tasks, resources, approvals, information, responsibilities, progress, risks, or follow-up will be coordinated. - Describes the participant’s role in preparing, coordinating, documenting, estimating, scheduling, communicating, monitoring, or using the project documentation.

Workplace example

A workplace project charter and planning package, including project charter, scope statement, work breakdown structure, schedule, cost estimate, cost baseline, stakeholder plan, coordination plan, responsibility matrix, risk/constraint note, approval pathway, monitoring tracker, or integrated project planning file used to coordinate a workplace project. The artifact must show project purpose, stakeholder value, scope, WBS, schedule, cost baseline, roles, approvals, risks, trade-offs, and coordination logic.

Civic/community example

A civic/community project charter and planning package, including community project charter, event scope statement, task plan, volunteer schedule, cost estimate, resource baseline, stakeholder plan, coordination plan, responsibility matrix, risk/constraint note, approval pathway, monitoring tracker, or integrated civic initiative planning file used to coordinate a community project. The artifact must show project purpose, stakeholder value, scope, WBS, schedule, cost baseline, roles, approvals, risks, trade-offs, and coordination logic.

Experience Context

• Autonomy: Apply — Frames and develops the artifact independently within agreed authority, seeking direction for material exceptions.
• Complexity: Apply — Integrates ambiguous or competing information, constraints, and implications to produce a defensible output.
• Contribution scope: Assist — Produces a usable output that supports another person’s planning, coordination, decision, or action.

Insufficient evidence conditions

• required characteristics absent
• role cannot be attributed
• no credible situated use
• required validation missing

Assessment Components

AC005 — Artifact Authenticity Declaration

Redo (R): Artifact Authenticity Declaration is missing when yes or does not credibly confirms that the participant produced or materially contributed to the artifact submitted for the Training Unit.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Artifact Authenticity Declaration is present when yes, attributable to an eligible validator, and credibly confirms that the participant produced or materially contributed to the artifact submitted for the Training Unit.; together with the Artifact Element it supports the reposited purpose: Captures an integrated project charter and planning package showing how the participant organized project purpose, stakeholder value, scope, work breakdown structure, schedule, cost estimate, cost baseline, responsibilities, authority relationships, assumptions, constraints, risks, trade-offs, approvals, monitoring, and coordination logic. this Artifact Element record is designed to evidence project management concept knowledge, project planning support, management information use, stakeholder coordination, systems awareness, evidence-informed planning, and constructive collaboration across people, resources, timing, costs, deliverables, and outcomes.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

AC003 — Host Organization Confirmation

Redo (R): Host Organization Confirmation is missing when conditional or does not credibly confirms that the artifact relates to a genuine project, event, initiative, improvement activity, or coordinated work context and that the participant had a legitimate role in producing, supporting, coordinating, documenting, or using the artifact.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Host Organization Confirmation is present when conditional, attributable to an eligible validator, and credibly confirms that the artifact relates to a genuine project, event, initiative, improvement activity, or coordinated work context and that the participant had a legitimate role in producing, supporting, coordinating, documenting, or using the artifact.; together with the Artifact Element it supports the reposited purpose: Captures an integrated project charter and planning package showing how the participant organized project purpose, stakeholder value, scope, work breakdown structure, schedule, cost estimate, cost baseline, responsibilities, authority relationships, assumptions, constraints, risks, trade-offs, approvals, monitoring, and coordination logic. this Artifact Element record is designed to evidence project management concept knowledge, project planning support, management information use, stakeholder coordination, systems awareness, evidence-informed planning, and constructive collaboration across people, resources, timing, costs, deliverables, and outcomes.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

AC006 — Source Data / Record Confirmation

Redo (R): Source Data / Record Confirmation is missing when conditional or does not credibly confirms that the artifact draws from appropriate project records, stakeholder requirements, cost information, resource information, schedule information, scope inputs, meeting records, organizational records, or source inputs where such inputs are not public or self-generated.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Source Data / Record Confirmation is present when conditional, attributable to an eligible validator, and credibly confirms that the artifact draws from appropriate project records, stakeholder requirements, cost information, resource information, schedule information, scope inputs, meeting records, organizational records, or source inputs where such inputs are not public or self-generated.; together with the Artifact Element it supports the reposited purpose: Captures an integrated project charter and planning package showing how the participant organized project purpose, stakeholder value, scope, work breakdown structure, schedule, cost estimate, cost baseline, responsibilities, authority relationships, assumptions, constraints, risks, trade-offs, approvals, monitoring, and coordination logic. this Artifact Element record is designed to evidence project management concept knowledge, project planning support, management information use, stakeholder coordination, systems awareness, evidence-informed planning, and constructive collaboration across people, resources, timing, costs, deliverables, and outcomes.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

AC007 — Peer / Team Corroboration

Redo (R): Peer / Team Corroboration is missing when conditional or does not credibly confirms contribution in collaborative project, event, initiative, improvement, or coordinated task contexts where the artifact was produced by, informed by, reviewed by, or used within a team or stakeholder group.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Peer / Team Corroboration is present when conditional, attributable to an eligible validator, and credibly confirms contribution in collaborative project, event, initiative, improvement, or coordinated task contexts where the artifact was produced by, informed by, reviewed by, or used within a team or stakeholder group.; together with the Artifact Element it supports the reposited purpose: Captures an integrated project charter and planning package showing how the participant organized project purpose, stakeholder value, scope, work breakdown structure, schedule, cost estimate, cost baseline, responsibilities, authority relationships, assumptions, constraints, risks, trade-offs, approvals, monitoring, and coordination logic. this Artifact Element record is designed to evidence project management concept knowledge, project planning support, management information use, stakeholder coordination, systems awareness, evidence-informed planning, and constructive collaboration across people, resources, timing, costs, deliverables, and outcomes.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

Artifact Element 2

AE002 — Presentations & Slide Decks

Evidentiary purpose: Captures a stakeholder-facing project planning briefing that communicates project purpose, scope, desired outcomes, stakeholder value, charter logic, work breakdown structure, schedule, cost baseline, assumptions, risks, constraints, trade-offs, coordination requirements, and recommended next steps. this Artifact Element record is designed to evidence issue summarization, stakeholder communication, supported project argument, strategic alignment logic, project planning communication, systems awareness, evidence-informed rationale, and constructive stakeholder collaboration.

Minimum characteristics: - Explains the project purpose, intended value, stakeholder need, beneficiary need, and reason the project matters. - Summarizes objectives, deliverables, stakeholders, authority or approval needs, assumptions, constraints, risks, and success criteria. - Presents project scope, boundaries, deliverables, phases, major work packages, or WBS logic. - Presents timeline, milestones, sequencing, dependencies, schedule assumptions, and critical timing considerations. - Presents cost categories, resource assumptions, budget estimate, cost baseline, financial constraints, or cost-control logic. - Identifies project risks, constraints, dependencies, scope/schedule/cost trade-offs, resource limitations, change considerations, or unresolved issues. - Identifies key stakeholders, responsibilities, approvals, communication needs, decision points, reporting needs, or coordination requirements. - Connects the project plan to evidence, reasoning, stakeholder value, constraints, trade-offs, approval needs, implementation steps, monitoring actions, escalation points, documentation needs, or next decision points. - Describes the participant’s role in preparing, presenting, communicating, coordinating, or supporting the project briefing.

Workplace example

A workplace project planning presentation, project approval briefing, stakeholder alignment deck, project charter briefing, project plan presentation, schedule and cost briefing, implementation readiness presentation, or management review deck explaining project purpose, scope, desired outcomes, stakeholder value, coordination logic, timeline, resource or cost considerations, risks, trade-offs, and next steps.

Civic/community example

A civic/community project planning presentation, event approval briefing, committee alignment deck, project charter briefing, initiative plan presentation, schedule and cost briefing, implementation readiness presentation, or governance review deck explaining project purpose, scope, desired outcomes, stakeholder value, coordination logic, timeline, resource or cost considerations, risks, trade-offs, and next steps.

Experience Context

• Autonomy: Apply — Frames and develops the artifact independently within agreed authority, seeking direction for material exceptions.
• Complexity: Apply — Integrates ambiguous or competing information, constraints, and implications to produce a defensible output.
• Contribution scope: Assist — Produces a usable output that supports another person’s planning, coordination, decision, or action.

Insufficient evidence conditions

• required characteristics absent
• role cannot be attributed
• no credible situated use
• required validation missing

Assessment Components

AC005 — Artifact Authenticity Declaration

Redo (R): Artifact Authenticity Declaration is missing when yes or does not credibly confirms that the participant produced or materially contributed to the artifact submitted for the Training Unit.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Artifact Authenticity Declaration is present when yes, attributable to an eligible validator, and credibly confirms that the participant produced or materially contributed to the artifact submitted for the Training Unit.; together with the Artifact Element it supports the reposited purpose: Captures a stakeholder-facing project planning briefing that communicates project purpose, scope, desired outcomes, stakeholder value, charter logic, work breakdown structure, schedule, cost baseline, assumptions, risks, constraints, trade-offs, coordination requirements, and recommended next steps. this Artifact Element record is designed to evidence issue summarization, stakeholder communication, supported project argument, strategic alignment logic, project planning communication, systems awareness, evidence-informed rationale, and constructive stakeholder collaboration.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

AC003 — Host Organization Confirmation

Redo (R): Host Organization Confirmation is missing when conditional or does not credibly confirms that the artifact relates to a genuine project, event, initiative, improvement activity, or coordinated work context and that the participant had a legitimate role in preparing, supporting, presenting, coordinating, or using the artifact.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Host Organization Confirmation is present when conditional, attributable to an eligible validator, and credibly confirms that the artifact relates to a genuine project, event, initiative, improvement activity, or coordinated work context and that the participant had a legitimate role in preparing, supporting, presenting, coordinating, or using the artifact.; together with the Artifact Element it supports the reposited purpose: Captures a stakeholder-facing project planning briefing that communicates project purpose, scope, desired outcomes, stakeholder value, charter logic, work breakdown structure, schedule, cost baseline, assumptions, risks, constraints, trade-offs, coordination requirements, and recommended next steps. this Artifact Element record is designed to evidence issue summarization, stakeholder communication, supported project argument, strategic alignment logic, project planning communication, systems awareness, evidence-informed rationale, and constructive stakeholder collaboration.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

AC007 — Peer / Team Corroboration

Redo (R): Peer / Team Corroboration is missing when conditional or does not credibly confirms contribution in collaborative project, event, initiative, improvement, or stakeholder alignment contexts where the presentation was developed, reviewed, presented, or used within a team or coordinated activity.; the Artifact Element therefore does not yet provide sufficient, attributable evidence of the reposited purpose.

Pass (P): Peer / Team Corroboration is present when conditional, attributable to an eligible validator, and credibly confirms contribution in collaborative project, event, initiative, improvement, or stakeholder alignment contexts where the presentation was developed, reviewed, presented, or used within a team or coordinated activity.; together with the Artifact Element it supports the reposited purpose: Captures a stakeholder-facing project planning briefing that communicates project purpose, scope, desired outcomes, stakeholder value, charter logic, work breakdown structure, schedule, cost baseline, assumptions, risks, constraints, trade-offs, coordination requirements, and recommended next steps. this Artifact Element record is designed to evidence issue summarization, stakeholder communication, supported project argument, strategic alignment logic, project planning communication, systems awareness, evidence-informed rationale, and constructive stakeholder collaboration.

Distinction (D): Not reposited — optional LMO decision. Distinction is unavailable for this component unless the LMO authors and approves a D criterion.

Completion and result

• Each Artifact Element is assessed through its own reposited Assessment Components.
• Each required Assessment Component must achieve at least Pass (P) for its Artifact Element.
• Both Artifact Elements must achieve Pass (P) or Distinction (D) to complete the Training Unit.
• Any Redo (R) returns the Training Unit for revision.
• Distinction is available only when the LMO reposits D criteria, and both Artifact Elements achieve D. D is not assumed or inferred.
• Formal Assessment Methods are not used at TI or TU level; they are reserved for EPA/EA.