Open ghost opened 4 years ago
https://github.com/blockstack/blockstack/blob/master/engineering/README.md
This document is far too large and contains manual steps (error-prone, must be remembered).
The process should be "build-in" to tools. As an example, the github-issue-tracker is not capable to model a more complex workflow.
If you favor "Sprints", use a tool where you can file the sprints.
If you favor "User Stories", use a tool where you can file the user-stories.
Describing "engineering" within a document is not engineering at all. You need to evolve.
https://github.com/marketplace/zenhub
ghost
commented
4 years ago ghost
commented
4 years ago
Problem
https://github.com/blockstack/blockstack/blob/master/engineering/README.md
This document is far too large and contains manual steps (error-prone, must be remembered).
The process should be "build-in" to tools. As an example, the github-issue-tracker is not capable to model a more complex workflow.
If you favor "Sprints", use a tool where you can file the sprints.
If you favor "User Stories", use a tool where you can file the user-stories.
Describing "engineering" within a document is not engineering at all. You need to evolve.
Possible Solutions