Github Project Management
Here is the best example I can find of how to use github project kanban to organize a team.
https://youtu.be/wj_4KV3r1GI?si=DJXdlTCsf4izuxDP
Here is an updated version that is more of a how to get started:
https://www.youtube.com/watch?v=oPQgFxHcjAw
Quick details:
- The first 26 minutes are the most valuable
- you can watch at 2x speed
- Issue: this is a call to action (todo, corrective action, preventative action, etc…)
- Do not worry about the concept of a "pull request" yet
Important observations:
- the concept of using kanban boards to manage issues (tasks) is common to many/most projects (not just software development)
- most of what we do is related to software
- the ability to have tasks appear on multiple boards (said another way: have boards created for specific audiences) is an important feature.
- continued… what you want your boss and/or your peers to see might be different than what you want your direct reports to see and action.
The fact that we have our own technical teams means that we can create automation around our project management.
I believe you will need the team edition at about $4 per user per month if/when we go into production with a team. We can use free tools while we confirm it works for us.
The above details combined with obsidian as a front end for writing the ops manual should make for a smooth and friction-less organization.
I hope this helps!