Lesson 0 · Why GitHub inside PORTWARE?

Why code, work and requirements belong in one place; who sees what.

Goal of this lessonTo see why the code, the work and the requirements of a software product belong in one place.

How it is today

The code lives on GitHub, the task in a project tool, the requirement in a Word file, the release note in an e-mail. Sales and support cannot open GitHub; developers update task status by hand; in an audit, "which change met this requirement?" takes days to answer.

The trace chain

The trace chain from requirement to productRequirementREQ-0012TaskT163Codebranch · commit · PRReleasev2.0.1ProductPW-SD-750PORTWARE builds the links itself: the key appears in the text, the record is linked.The matrix counts every link; a broken one shows as a 'Gap'.
The five links of a piece of software work. Before PORTWARE the chain was spread over four tools; now it reads on one screen.
WhoWhat they see in PORTWARE
Project managerThe task's code, PR state and the task's stage, current by itself.
DeveloperThe branch name is ready; the commit message links and closes the task.
Sales and supportThe product's software version and release notes, without GitHub.
Quality and auditEvery requirement's evidence: task, merged change, verification.
What does not change
Developers keep working on GitHub. PORTWARE only reads and links; it never changes code. The one exception is opening a task's branch, on your approval.

Check yourself

Does PORTWARE change code on GitHub?
No. It reads and links; it only opens a task's branch, when approved.
Where does the sales team see a release note?
On the product form's GitHub button and Software tab.