Manage & Control

You manage, monitor and document the iterative development process and apply standards to ensure quality and continuity. You use tools and a process-based approach. You work constructively and communicate proactively with stakeholders. You take responsibility for your own contribution in the collaboration and the final result.

Overview of Documentation Types

In your projects you will often create different kinds of documentation. Each type has its own purpose, audience, and level of detail. Understanding the differences helps you decide what to write down and how to present it.

---

Process Documentation

Purpose: Capture the raw progress of your work.
Audience: Mainly your project team.
Examples: Notes, sketches, test logs, photos of prototypes.
Tip: Be honest about failures, they are valuable learning points.

---

Design Documentation

Purpose: Present a curated version of the process and outcomes.
Audience: Clients, teachers, or external stakeholders.
Examples: Polished visuals, concept descriptions, key insights.
Tip: Keep it concise, clear, and tailored to your audience.

---

Technical Documentation

Purpose: Explain how a system, code, or prototype works.
Audience: Developers, engineers, or anyone who wants to build on your work.
Examples: README files, wiring diagrams, setup instructions, code comments.
Tip: Test your documentation by letting a peer follow it.