Assignment 3: Knowledge Transfer Video
Assignment: Project Knowledge Transfer Video
This assignment is due Friday May 8, 2026 at 11:59 PM. NO LATE SUBMISSIONS WILL BE ACCEPTED. NO EXCEPTIONS.
Objective
The purpose of this assignment is to create a professional, high-quality video that documents your team’s project for future student groups. This video should serve as both a showcase of your work and a practical onboarding resource that helps others understand, set up, and extend your project.
This is a group assignment. All members of the group are expected to contribute in some capacity. Each group member will receive a separate grade.
Overview
Each team will produce a 10–15-minute recorded video that clearly explains and demonstrates your project. The video should be structured, concise, and professional in tone, as if it were being presented to a new development team taking over your codebase.
Your goal is not just to describe the project, but to teach it.
Required Content
Your video must include the following sections:
- Project Overview (1–2 minutes) • What is the purpose of your project? • What problem does it solve? • Who are the intended users? • Key features and functionality • Where to find information.
- Environment Setup (4–7 minutes) • Required tools, frameworks, and dependencies • Step-by-step setup instructions • Configuration details (environment variables, database setup, etc.) • Any common setup issues and how to resolve them
- Running the Application (2–3 minutes) • How to start the application • Demo of the application in use • Key workflows or features demonstrated live
- Technical Decisions & Architecture (2–3 minutes) • Key design decisions (architecture, frameworks, libraries) • Trade-offs considered • Challenges encountered and how they were addressed • Any technical debt or known limitations
- Future Direction (1 minute) • Planned features or improvements • Suggested next steps for future teams • Areas that need refactoring, scaling, or optimization
Professional Expectations
Your video should: • Be well-organized and clearly structured • Include clear audio and readable visuals • Use screen sharing and/or slides effectively • Maintain a professional tone (think onboarding/training material) • Be edited (remove dead time, mistakes, unnecessary pauses) • If you are visible in the video, you should be professionally dressed (business casual is acceptable)
Deliverables
• A video file • Any supporting materials (slides, documentation links, etc.) • A group reflection indicating who contributed to the project video and each group members level of effort towards producing the video and supporting materials. Each group member should indicate what they expect to receive as a grade for this assignment. • Items should be submitted in Canvas and also posted into your Repo.
Grading Criteria (100 points)
Category Points Description Content Completeness 30 All required sections are present and sufficiently detailed Clarity & Organization 20 Logical flow, easy to follow, well-structured Technical Accuracy 20 Instructions and explanations are correct and usable Professional Quality 15 Audio, visuals, editing, and presentation quality Depth of Insight 10 Thoughtful discussion of decisions, trade-offs, and challenges Future Guidance 5 Clear and useful direction for future teams
Additional Guidance
• This as a handoff to a new development team, make sure that all information included in the video has significant relevance and purpose to a handoff • Avoid assuming prior knowledge of your project • If a future team followed your video, could they successfully: o Set up the environment? o Run the project? o Understand how to extend it? If the answer is no, refine your video.
Optional (but strongly encouraged): • Include a short “lessons learned” reflection (how did working on this project help you?) • Add visual diagrams (architecture, data flow, etc.) • Provide a quick-start guide companion document