Please enable JavaScript.
Coggle requires JavaScript to display documents.
Specification 2.0 - Coggle Diagram
Specification 2.0
What do we NOT want
Tickets
-
-
-
Scope change or acceptance criteria in the comments only (i.e. not also part of the task description)
-
-
Tickets that contain scope that is beyond the limitation of our tech stack - i.e. our tech cannot even deliver this :warning:
-
-
-
-
links to a lot of different projects/tickets without summary of what was previously implemented and only link to other tickets
super old Tickets created by people who are no longer in the company and we need to figure out what was meant by them
reopen or update done/archived tickets if there is a need to continue working on the same context of the archived/done ticket
-
-
discussions about tickets that happen outside the ticket are not written/summarized in the ticket (as a comment or in the description)
No structured body of tickets, just plain description
-
-
to have to make assumptions about systems that I do not know, i.e. I do not want to have to guess how the tech works on my own as a PM
-
-
parallel communication with stakeholders by different people who are working on the same project which creates confusion & different requirements
Devs asking requirements from non-tech stakeholders or trying to explain requirements without PM presence :warning:
Having too many endless discussions and asking permission to speak with Devs of other teams regarding scope
-
create endless documents to explain the scope needed to be done (i.e. create 5 different documents just to explain the scope of the functionality)
-
-
-