In the beginning of the project, everyone will be working together to create deliverables that fall under the following categories:
- Minor: A task that should take less than 2 hours.
- Major: A task that should take less than 8 hours.
- Epic: A task that should take less than 40 hours.
In addition to this, these tasks should have tags added to them. Tags will be more solidly established during this beginning-process, but some foundational ones are:
- Progress Halted
- To-Do
- In-Progress
- Completed
Lastly, tasks should have categories. Categories will exist depending upon if someone exists in the team to support a particular category (if there aren’t any website designers, there’s no need for that category). Here are what they may look like:
- Back-end
- Front-end
- Design
- SA
An example ticket, visible on Notion, may look like:
You can in the ticket title: there’s some information regarding what should be done, and there’s the ticket-id. Since this is a style-based ticket, this would be created by a website designer (if we get one), or by a front-end developer. You assign yourself tickets as you can, but by the end of the project, the development effort should be evenly spread. This identification is necessary, even if it’s not created yet. If you take on this ticket, but don’t want to start development immediately, copy the ticket id and paste it in as a comment where it would be created in the project. This is critical for speeding up development and issue-fixing.
There is a ticket-id naming scheme. It goes as follows (and must be followed): [yourInitials-functionOrElementName:filename]. I chose [lp-div.resourceWrapper:resource.css], as:
- lp: my initials
- -div: the element name
- .resourceWrapper: optional additional information about the function or element
- :resource.css: the name of the file. If there are multiple files this needs to be done for, or multiple elements, then use a semi-colon. For example: [lp-p;span;a.animatedUnderline:resource.css;survey.css]
