Milestone map
Milestone map
2 milestones
Do the course work in public
3–6 weeks (3–4 hrs/week)
Take Process Mining: Data Science in Action for free and do process discovery, conformance checking and performance analysis on the sample event logs, in a notebook. Keep everything in one public repo or notebook as you go. OSSU lists a Coursera course, where graded work is paid. We use the free PM4Py library, its docs and its sample event logs.
Proof required
Link your public repo or notebook with process discovery, conformance checking and performance analysis on the sample event logs, in a notebook, and a screenshot or log showing the self-check passed.
What gets checked
- Each step runs and shows its model.
- Conformance results are explained in plain words.
- The slowest step in the process is found and shown.
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 process discovery, conformance checking and performance analysis on the sample event logs, in a notebook.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Run the getting-started examples on the sample event log and match the models and numbers they show.
- 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: Process Mining: Data Science in Action (PM4Py (free, open-source process mining library and docs)) 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
- Each step runs and shows its model.
- Conformance results are explained in plain words.
- The slowest step in the process is found and shown.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Map a real process from its event log
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a process map from a real or public event log (support tickets, orders, a hospital or loan log), with the slowest step and one change you would make. Keep it small enough to finish in about two weeks.
Proof required
Link a process map from a real or public event log (support tickets, orders, a hospital or loan log), with the slowest step and one change you would make, with a README that says how to run or read it.
What gets checked
- The log is real and its source is named.
- The map matches the log (counts shown).
- The suggested change follows from the data.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A process map from a real or public event log (support tickets, orders, a hospital or loan log), with the slowest step and one change you would make.
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 log is real and its source is named.
- The map matches the log (counts shown).
- The suggested change follows from the data.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.