DEVREVU · BUILD · PART 3 OF 3 · BEGINNER

Build · Part 3 — Roadmaps, Enhancements & Team Health

Zoom out from the daily sprint. See how your work ladders up to the product's direction — through parts, enhancements, roadmaps, and milestones — and how your whole team is really doing. This final part connects a single issue all the way up to the product roadmap.

From one issue to the whole roadmap

In Parts 1 and 2 you captured issues and ran them in sprints — issues are the "how". An enhancement is the "why" and "what" that gives them meaning: a unit of product upgrade that decomposes into issues and makes up your roadmap. Parts are the components almost everything links to, mapped visually in Trails.

This part connects the pieces. You map the product with Parts and Trails, create enhancements and place them on a Now / Next / Later roadmap, track delivery with Gantt and the Release Tracker, break big work into milestones, read Team Health, and extend DevRev with custom fields — closing with the builder best practices that tie all three parts together.

The eight sections of Part 3

WHAT'S INSIDE

Zooming out, three levels up

Parts & enhancements

Give work meaning.

Map your product with Parts and Trails, then create enhancements — the "why" behind your issues — scored by Customer Impact so you prioritise on real demand, not gut feel.

Roadmap & delivery

See the bigger picture.

Organise enhancements across Now / Next / Later, read planned-vs-actual on the Gantt, coordinate launches with the Release Tracker, and break big work into milestones you can report against.

Team health & habits

See how the team is doing.

Read aggregated delivery metrics in Team Health, extend DevRev with custom fields and subtypes, and apply the builder best practices that tie setup, work, planning, and release together.

The roadmap: Now / Next / Later

From one issue to the whole roadmap. Now go run it for real.