Documents
The documents a project generates from the record its team wrote once: the business requirements document the client signs and the software requirements specification the team builds against, each rendered, reviewed, approved and shared from one page.
A project writes its documents rather than having them typed. The planning record the business analyst keeps, the epics and stories, the requirements, the business rules, the use cases, the people and the dictionary, is the source; a document is a kind, a title, a file format and a scope (the record as it stands, with or without drafts, or a frozen baseline), rendered as a PDF or an HTML page that reads the record through the same permissions as the person who asked for it. Heimdall drafts the opening page, the author edits it, and the project manager's approval makes a copy final: the one the client receives, superseding the kind's earlier final copy.
Two kinds are open today. The business requirements document is the client's: what they need and why, the people, the scope as epics and stories, the rules, the glossary, the risks and the decisions, ending on a sign-off table. The software requirements specification is the team's: every functional and non-functional requirement, the rules, the use cases step by step, the data dictionary and where each requirement is built. The other kinds the application declares (sprint reports, release notes, UAT sign-off sheets, test summaries, post-mortems, status reports, the traceability matrix and timesheets) are refused until the modules that write them land, and each gets its own page here when it does.
Generated documents
The Documents page: generate, read, edit the opening page, render again, put a draft to the project manager, share the final copy, supersede and delete.
Business requirements document
What the BRD prints, section by section, who reads it and what the sign-off page asks of the sponsor.
Software requirements specification
What the SRS prints, section by section, and how the team builds and tests against it.
Documents shared with you
The client's view: the final copies, where they appear and what a client never sees.
How is this guide?
Last updated on
Sprints
Plan a sprint with its dates, goal and capacity, pull its scope from the backlog, put it to the team for the commitment that starts it, follow it while it runs, close it with its velocity and carry the unfinished work on.
Generated Documents
Generate a business requirements document or a software requirements specification from the project's own record, edit the opening page Heimdall drafts, render it again, put it to the project manager, and share the final copy with the client.