Almost everything you produce in this course will be produced with other people. This topic is about setting up that collaboration deliberately rather than letting it happen by accident: forming a team, agreeing on who does what, writing it down in a team charter, and bounding the course project so the scope is something your team can actually finish in a semester.
The practices here come straight from project management. A team charter, a roles-and-responsibilities list, a communication plan, and a scope statement are all standard project documents, and the vocabulary around them (stakeholder, deliverable, milestone, scope creep) is vocabulary you will see again in industry. Learning it now makes your design work later in the course easier to coordinate and easier to explain to a client or instructor.
The three videos below come from a project management practitioner channel and cover the documents, the communication planning, and the terminology side of kickoff. As you watch, map what you hear onto your own team: which documents does our project actually need, how will we decide when and how we talk to each other, and where exactly does our project stop? Take notes you can paste directly into your charter and project plan drafts.
A short walkthrough of five project documents the presenter considers essential during planning, with an explanation of what each one is for and when it gets created. Expect coverage of foundational artifacts such as a charter or scope-defining document and the supporting plans that follow from it. The format is practical and aimed at people who are about to start a project rather than at theory.
It maps directly onto the "Creating the Team Charter" and "Scoping the Course Project" subtopics by showing which written artifacts a kickoff should produce and why each one exists.
A step-by-step guide to building a project communication plan: who needs information, what information they need, how often, and through which channel. The video is longer and more procedural, walking through the structure of the plan rather than just describing it. It also touches on stakeholders and why communication breakdowns derail projects.
Communication norms are the operational half of a team charter, and this video gives you a concrete template-style process for deciding meeting cadence, channels, and reporting responsibilities for your team.
An explanation of ten commonly used project management terms, with plain-language definitions and examples. Based on the title and description, expect terms around scope, deliverables, stakeholders, milestones, and similar planning vocabulary. It is the most-viewed of the three and is pitched at people new to the field.
Shared vocabulary is what lets a new team talk about scope and roles without talking past each other, so this is useful groundwork before you draft the charter and project plan.
These videos chiefly support MO3: building an initial project plan that defines scope, platform, and team roles. The documents video shows what artifacts a kickoff should produce, the communication plan video shows how to specify who is responsible for what and how the team will coordinate, and the terminology video gives you the shared language for scope, deliverables, and stakeholders that the plan is written in. They do not address MO1 or MO2 directly; the HCI history and the usability, user experience, and accessibility distinctions come from the other readings and videos in this module, and you should bring those concepts with you when you decide what your team's project is actually about.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.