4 micro-topics in Engineering Practice, each with the evidence that proves you have it and the written reason behind every link. Nothing outside this domain sits under it — you can start here. Downstream, it holds up 2 domains.
4 topics · depth 0–2 of 16 · 3 internal links · 0 in · 2 out
Load-bearing links first. Each one says what in this domain rests on what outside it, and why.
Nothing outside this domain sits under it. It is an entry point — you can start here.
In prerequisite order. Each idea names the artifact that closes it, the market demand that put it on the map, and what it stands on.
Depth 0 · representational · unassisted · M07 §7.1
States who, what and how it will be judged
Depth 0 · meta · scaffolded · M07 §7.1
Translates technical constraints into business terms
Scope conversations are easier with a prioritized list in hand.
Depth 1 · meta · scaffolded · M07 §7.1
Splits work into shippable increments
Write user stories with acceptance criteria
You split stories into stories.
Depth 2 · meta · scaffolded · M07 §7.1
Applies a method like MoSCoW to cut to an MVP
Decompose an epic into stories
Prioritization operates on a decomposed backlog.
Everything downstream that names an idea here as a prerequisite, grouped by where it lives.
1 link
Explain agile principles rests on Write user stories with acceptance criteria
The practices make sense once you have written the artifact they produce.
1 link
Diagram a system before building it rests on Write user stories with acceptance criteria
A diagram is easier to draw once the requirement is stated.
Retool. Retrain. Relaunch.
375 ideas. 17 weeks. No tuition, ever.
Vets Who Code is a veteran-run 501(c)(3). The accelerator is free, remote, and we don’t take a share of your first paycheck.
Free · Remote · 17 weeks · EIN 86-2122804