Using complex processes to develop an outcome (internal)
Internal 6 credits Project management Decomposition Trialling Informed & refined SynthesisAS 91907, 6 credits. This standard assesses the process, not the artefact: use recognised project management tools to PLAN, DECOMPOSE the outcome into components, TRIAL them, TEST that the outcome functions as intended, and address implications. Merit develops an INFORMED outcome — effectively managing feedback/collaboration, effectively trialling MULTIPLE components/techniques, using testing/trialling information to improve functionality. Excellence develops a REFINED one — SYNTHESISING information from planning/testing/trialling and DISCUSSING how it led to a high-quality outcome.
1 Reading the notation
Five Achieved elements, then the informed/refined additions, in the standard's own words.📖 Terms the schedule grades you on
4 terms- Use complex processes (Achieved)
- Plan with recognised PM tools; decompose into components; trial components; test the outcome functions as intended; address implications.
- Develop an informed outcome (Merit)
- Effectively manage development/feedback/collaboration; effectively trial MULTIPLE components/techniques; use testing/trialling info to improve functionality.
- Develop a refined outcome (Excellence)
- SYNTHESISE information from planning, testing AND trialling; discuss how it led to a high-quality outcome.
- Recognised PM tools (standard's own list)
- Agile/waterfall, Kanban/scrum boards, version control, collaboration tools, managing assets.
2 Decomposing the outcome
Small enough to build, test and describe independently. ✕A "component" that is really three components
A component described as "the login and the dashboard and the export" cannot be built or tested as one unit, and hides which part actually failed when something breaks. Split it — each real component should be describable in one sentence, with no "and".3 Trialling components and techniques
A separate, earlier-stage requirement from testing the finished outcome.What trialling evidence needs to show
- At least ONE component or technique trialled DURING development, not just at the end.
- For Merit: MULTIPLE components/techniques trialled — ideally two approaches to the same problem compared.
- A result from each trial, and the decision it led to.
4 Planning, dependencies and milestones
A living plan, revised with reasons — not a document written to match the outcome afterward.| Stage | The tool | The evidence it leaves |
|---|---|---|
| Plan | Gantt chart or sprint plan with milestones | Dated plan, plus its revisions with reasons |
| Decompose | Task breakdown with dependencies | The component list, each describable in one sentence |
| Sequence | Dependency ordering | Blocking work scheduled first, justified |
| Build | Version control, issue tracking | Commit history with meaningful messages |
Every row leaves an artefact created AT THE TIME. That is what distinguishes an evidenced process from a written-up one.
Practice
Recall it first, then use it — testing yourself builds the memory, where rereading the notes above only feels easier.
Recall and application shuffled together — you have to work out what each item wants before you can answer it, which is the part the exam actually tests. Both kinds feed the same spacing schedule, so anything you miss comes back sooner.
Say the answer out loud before flipping — that attempt is where the learning happens, even when you get it wrong.
Exam-style only. Instant feedback, shuffled each attempt, best score saved on this device.