Milestone map
Milestone map
2 milestones
Do the course work in public
3–6 weeks (2 hrs/week)
Take Design and Build a Data Warehouse for Business Intelligence Implementation for free and do the Zoomcamp course project: a pipeline, a warehouse and a dashboard on one dataset. Keep everything in one public repo or notebook as you go. OSSU lists a Coursera capstone, where graded work is paid. We use the free Zoomcamp project and its criteria.
Proof required
Link your public repo or notebook with the Zoomcamp course project: a pipeline, a warehouse and a dashboard on one dataset, and a screenshot or log showing the self-check passed.
What gets checked
- Every part runs from the README.
- The project meets the posted criteria (your scoring shown).
- The dashboard has at least two charts that answer a stated question.
Common mistakes
- Copying posted answers: verifiers read the history.
- Skipping the self-check, then asking for review too early.
Powstik Guide
A public repo or notebook with the Zoomcamp course project: a pipeline, a warehouse and a dashboard on one dataset.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Score your project against the posted criteria before you ask for review.
- Write a short README: what is here and how to run it.
- Ask three people who know the topic to check it.
Template
README Course: Design and Build a Data Warehouse for Business Intelligence Implementation (Data Engineering Zoomcamp (DataTalks.Club), course project) What is here: How to run it: Self-check result: What was hardest:
What gets sent back
- No history, just one big upload.
- Self-check not shown.
- Code that does not run from the README.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Every part runs from the README.
- The project meets the posted criteria (your scoring shown).
- The dashboard has at least two charts that answer a stated question.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Write up your warehouse design
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a design note for your warehouse (diagram, tables, how data flows, what you would change), linked from the repo. Keep it small enough to finish in about two weeks.
Proof required
Link a design note for your warehouse (diagram, tables, how data flows, what you would change), linked from the repo, with a README that says how to run or read it.
What gets checked
- The diagram matches the code.
- Two trade-offs are named honestly.
- Someone else could rebuild it from the note.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A design note for your warehouse (diagram, tables, how data flows, what you would change), linked from the repo.
Steps
- Write one line: what it does and for whom.
- Build the smallest version that works.
- Test it on someone else's machine or with someone else reading it.
- Write the README.
- Ask three people to check it.
Template
README What it does: Who it is for: How to run it: What I would do next:
What gets sent back
- Does not run from the README.
- Not clearly the person's own work.
- Claims more than it does.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- The diagram matches the code.
- Two trade-offs are named honestly.
- Someone else could rebuild it from the note.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.
Part of