Divengine StudioPlan the work next to the reasons for it
Tasks in Studio live next to the requirements, diagrams and tests they are about. Boards for the day to day, timesheets for the honest numbers.
Coordination is not accountability
A board tells you who is doing what this week. It does not tell you why the system is built the way it is. Studio keeps both, and keeps them apart.
Coordination: projects & tasks
- Who works on what, by when, at which stage
- Boards, subtasks, priorities and time spent
- Short-lived: a task is done and closed
Engineering accountability: records & traces
- What the system must do, why, and how it is proven
- Requirements, decisions, change requests, evidence and baselines
- Long-lived: kept, revised and baselined
A task links to the diagrams and records it works on, so closing it never erases the reason it existed. Engineering decisions belong in change requests and decision records, where they are kept and baselined.
Kanban boards for every project
Projects and subprojects hold tasks of different types (stories, features, bugs, epics), with priorities, deadlines, assignees and stages. Drag cards across the board, split them into subtasks, relate them to each other.
- Codes for every task (
BILL-0001), linkable anywhere - Members per project, inherited by subprojects
- Comments and attachments on every task
Time where it was spent
Start a timer on a task or fill your weekly grid. Allocated time versus time spent is visible on each task, and reports group hours by person, project or task for any period.
- Everyone logs their own time
- Project managers see everyone's time on their projects
Projects that belong to Developments
A project overview shows open, in-progress, done and overdue work, its subprojects and the time spent. Tasks link to the diagrams and artifacts they are about, so project work and engineering records stay connected.
