docs: new terminology for roadmap #343
Open
+128
−59
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Propose new Terminology for roadmap
I wasn't asked, but... as a new user of roadmap, it was very unobvious to me why "Milestone" is not a point in time, but rather a group of deliverables, so I came up with this proposal. I don't want to introduce yet another solution, instead I propose to follow common PM practices.
I've kept the changes straightforward. I think this is a good timing for such a change, as it will help to coordinate between components roadmaps and Logos Testnets.
Motivation
Changes
Key Terminology Updates
graph LR I["Initiative"] D["Deliverable"] E["Epic"] Is["Issue"] R["Release"] M["Milestone"] I -->|contains| D D -->|contains| E E -->|contains| Is I -->|included in| R R -->|split by| MNew Fields Introduced
Initiative fields:
Release fields:
Impact
Next Steps