What your work should demonstrate
- Write a charter and measurable acceptance criteria
- Assign owners and schedule tasks with dependencies and capacity
- Estimate costs and maintain actionable risk responses
- Communicate progress, assess changes and close with a clear handoff
Build a reviewable evidence package
- Brief and source index. Name the audience, intended result, software and files included. Label fictional data and training scenarios clearly.
- Original editable work. Keep working files and dependencies. Document any external assets and the permission needed to use them.
- Checks and iterations. Show a baseline, one meaningful revision and the evidence you used to judge it. Include settings or test results where the course requires them.
- Reflection and viewing link. Explain your decisions, repaired problems and remaining limitations. Test the link while signed out, and keep passwords and personal records out of the submission.
What review looks for
Purpose
The work addresses the brief and its intended audience.
Execution
The required techniques work together, with inspectable source evidence.
Validation
Tests, comparisons or checks support your claims about the result.
Explanation
Your reflection describes decisions, permissions and limitations honestly.
The detailed requirements in your course remain the assessment brief. This public page explains the common review approach; it is not a substitute for completing the taught exercises.
Submit, receive feedback, improve
Complete all 12 chapters and pass all 6 module quizzes first. Submit through Final project & certificate in your learning space. If changes are requested, revise the work and resubmit. Approval is required before certificate issuance; there is no fixed review turnaround promised here.