| ▲ | cmrdporcupine 12 hours ago | ||||||||||||||||
This is all a bit messy to read, but seems TFA recommends against 1:1s and any kind of ticket management or any eng. management all when you have 5-6 engineers and this ... insane. People need to get on the same page. You don't need to be (shouldn't be) process insane or go SCRUM or whatever to do that. But having regular organized interactions and task definitions is absolutely imperative even early on when you don't know for sure what you'll be doing. | |||||||||||||||||
| ▲ | Terretta 6 hours ago | parent | next [-] | ||||||||||||||||
Even works just doing it for yourself, Personal Kanban style: https://www.personalkanban.com/pk/personal-kanban-101/ I recommend Sunsama: | |||||||||||||||||
| ▲ | OhMeadhbh 11 hours ago | parent | prev [-] | ||||||||||||||||
yeah. i think you can get away with no 1-on-1's for small teams (like 4 people) but by the time you're at 6 or 8, it's probably a good idea. i suspect the OP has reason for believing this, so rather than say "they're wrong," i would say "i'm not sure they explained their environment sufficiently to explain their conclusion." as for ticket management. JIRA is not your friend. i would rather go with a stack of post-its than JIRA. JIRA does not help you understand what you are trying to do (in my experience.) once you've figured out specific tasks, JIRA can track those tasks, but so can BugZilla or (as my teams are using increasingly) text files checked into the repo. people often confuse the tool with the process and confuse following the process with making progress. the first rule of issue tracking systems is they should not get in the way of making tasks you need to do visible. JIRA routinely violates this rule. hmm... maybe i should write my own blog post. | |||||||||||||||||
| |||||||||||||||||