3 ms·
In an early startup, where developers are also doing ops, and there are periodic manual tasks (like daily/weekly/monthly running certain kinds of backups, eyeba
by neilv 4y ago
In an early startup, where developers are also doing ops, and there are periodic manual tasks (like daily/weekly/monthly running certain kinds of backups, eyeballing AWS dashboards and logs to check for anything alerts missed, etc.), using the same board and issue-tracker you use for development tasks helps.
In one company, I used GitLab Board, and had special tags for the recurring and background tasks, which were sticky in Kanban columns right below the generally one-time development tasks. The deadline dates for recurring tasks kept changing to the next time the task had to be done. The Issue description had the concise immediate instructions for the steps of the task (with a link to the wiki for related and background info). And every time you did the task, you added a very quick Comment with any notes, and bumped the due date.
It was very lightweight, and fit the simplicity I was advocating (e.g., the GitLab Kanban board says what everyone is doing, all info goes into GitLab in one form or another, minimal other tools and silos to juggle, etc.).
- thrdbndndn 4y ago> Kanban board Does it have specific meaning in software engineering? Isn't Kanban just billboard in Japanese?
- SahAssar 4y agoYes, it's usually a column-based system for tracking progress of tasks that move through various stages (eg. planning, development, testing, rollout, evaluation). See here: https://en.wikipedia.org/wiki/Kanban_board https://en.wikipedia.org/wiki/Kanban_board
- neilv 4y agoExactly. Sometimes my columns aren't waterfall phases, but more: Backlog, Blocked, Active, Done, Abandoned. The "Blocked" is important to highlight on the board: when someone can't do their thing, no sense floundering quietly -- highlight that, see who can unblock it, and what anyone else can do in the meantime. "Abandoned" is another one that I think is important, but might be unusual. If the task no longer makes sense, stop immediately, move it to Abandoned, and move on to a more worthwhile task. Just don't abandon anything quietly; acknowledge it on the board, communicating to everyone immediately we're not doing that anymore. Later, we can reflect on what info we had, when, and what we can learn from that. (I usually really-really want a Gantt model as well, on the same database that the board view is coming from, but the tools aren't quite there yet.)
- SahAssar 4y ago> Just don't abandon anything quietly; acknowledge it on the board, communicating to everyone immediately we're not doing that anymore. Even on personal projects I try to not remove TODO's or tasks without writing why it is no longer a goal. The amount of knowledge that is thrown away in many organizations or by people by discarding tasks without saying why is astounding, the why for discarding it can be as productive as a task completed.
- 015a 4y agoWe use Google Calendar, and it is generally the best solution in my experience. But not just a daily event; an actual time, with a meeting invite that anyone relevant joins, to run each task together. It helps knowledge transfer and helps guarantee that it happens. Documentation, like with most meetings, is thrown into Notion or whatever; just quick and dirty. Example: test our database backup restore process. Everyone hops on; leader logs into the cloud provider; confirms that the backup strategy is what we expect (which is documented in the description of the meeting invite); confirms that database backups exist in line with that policy; confirms they're of a reasonably expected size; we click one for staging -> restore to a new deployment -> wait for the cloud provider to set everything up, use that 5 minutes to talk with one another about stuff -> set up the database username/password; log in to AWS Secrets Manager -> update credentials -> roll the deployment to pull in the new credentials; confirm everything looks good; and tear the old (again: staging) deployment down. A second person on the call is tasked with documenting everything we did, taking screenshots of the screen share, and getting it all into a wiki. For us, it takes less than a half hour, do it every quarter or so, usually scheduled for a Friday afternoon where we can also talk about weekend plans and enjoy some drinks. Eyeballing dashboards is a harder one; a similar thing we do, similar to the last example, is more of a Performance Review, which is bi-weekly. We've got a collection of dashboards, database index metrics, etc; we all get together for a half hour and review all of them similarly. If anything looks unacceptable, we generally backlog two tickets: one to adjust our Slack/Datadog alerts for it so the next time we don't find out during the review, and another to remediate.