almost anything can be a github issue
what are issues, even?
i think i have historically been resistant around putting work items that aren't code into issues. Like, "book a meeting with stakeholder X" seems silly to put in a backlog. Just do it and be over with it, i have thinked many times.
working the hardest you can, without looking up, will lead you wrong
The mindset of just doing everything right away changed when my backlog went from 10 items, to 100 items, to 250 open items. Then, an hour of my focused time being spent in a meeting may not be the most valuable use of my focused time (around 2 hours maximum each day).
If all tasks that I can possibly do are tracked in the backlog, i have all possible input to make the most value out of my time.
my issue template
i currently use the following types of issues:
- investigations. "investigate how we can do it"
- actions. "implement it according to what what we investigated"
- tasks. "book a meeting with department"
- features. "payment integration with klarna"
i have this simplified issue template. maybe i should start doing acceptance criteria and definition of dones, but i dislike those. they feel overly technical in nature.
# Mission
The department knows something we don't know regarding this feature.
# Outcome
We will have clearer picture around what the department thinks
# Deliverable
`meetings/meeting-notes.md`