4 ms·
Nope. Having worked in a shop that used GitLab issues for project management, I've come to realize GitHub-style issue trackers work if all your project managem
by TeMPOraL 5y ago
Nope.
Having worked in a shop that used GitLab issues for project management, I've come to realize GitHub-style issue trackers work if all your project management boils down to creating and tracking bite-sized blobs of work. It stops being sufficient when you need to actually plan ahead. FWIW, so does Trello. Couple reasons why:
- Issues are flat. Work breaks down into a tree. And no, "epic / ticket / checkboxes in task" is not enough, that's barely two and a half levels. Compare with https://en.wikipedia.org/wiki/Work_breakdown_structure https://en.wikipedia.org/wiki/Work_breakdown_structure [0].
- Issues are independent. Properly broken down, work in a project has dependencies. That turns a tree of tasks into a directed acyclic graph of tasks - work items depend on other items, often items from different areas in the WBS.
- Issues don't schedule well. Most issue trackers I've seen don't support simultaneously entering planned start/end dates, actual start/end dates, and actual work being done. This means they can't be effectively used to estimate the length of the project, and update that estimate as the project progresses. Forget about any auto-scheduling.
There's a reason why old-school PMs love their Gantt charts so much - they properly reflect the graph-like nature of work, and they let you see the information crucial for planning at a glance.
In my opinion, any system that doesn't support entering DAGs of tasks with planned manual and automatic dates (e.g. "this task will take ~5 days, and starts when that other task ends"), and doesn't allow you to compute the critical path, is not a project management tool, but a glorified TODO list. A good PM tool does what I've outlined above, plus it lets you easily run what-if analysis - that is, play around with estimates, resource availability, task ordering, to explore the space of possible project plans and possible failure modes.
So, in my opinion, neither GitHub/GitLab issues, nor Trello or other Kanban boards, are useful for PM work. I've heard that properly configured Jira just might be. MS Project is a good one, if you ignore its clunky UI and propensity to randomly lock up for no reason.
--
[0] - Even where the Wiki says "For most projects a hierarchy of two to four levels will suffice.", this is in context of "lowest level of detail of the WBS should be longer than a single reporting period", which would be typically a month or more. Tickets in the issue tracker are thus a level below that. So, to properly break a project down, you need ~2-4 levels of structure above your tickets.
- simonw 5y ago"Issues are independent. Properly broken down, work in a project has dependencies" A trick I use a lot is to open a "tracking issue" and then link to it from other dependent issues by mentioning its #ID in those issue's descriptions. The tracking issue automatically shows the open/close status of those other issues, which means I can see at a glance if all of the dependent issues have been completed. Here's an example: https://github.com/simonw/datasette/issues/1105 https://github.com/simonw/datasette/issues/1105 It's not nearly as sophisticated as what you're looking for in terms of date estimates and critical paths, but it does work well for light-weight dependency tracking.
- TeMPOraL 5y agoWe've done something like this too. It worked well to keep track of related issues, particularly during regular reviews. It turned out insufficient when we had to plan ahead for ~6-12 months of work on polishing "version 1.0" (~300 existing tickets that needed to be pruned, reprioritized and otherwise rearranged) and building "version 2.0" (proper work-breakdown task of a complex project). Our PM tried to handle this challenge for a while, by writing scripts against GitLab API. This eventually turned out insufficient, so the PM, myself and another coworker set out to find a project management tool that actually does project management. It's after extensive discussions and search that we figured out none of the well-known work tracking products in software development fit the bill. Best easily-accessible options we've found were: MS Project (if you're on Windows, which we weren't), Jira (if you hire a person full-time just to manage it) and YouTrack from JetBrains (if you hire a person full-time just to script it). There are other options in the corporate PM space, but we didn't get to explore those as a startup (and eventually we've all left the company).
- eezing 5y agoSounds like you spend a lot of time managing your PM tool.
- TeMPOraL 5y agoNah. There's not much to manage in a proper PM tool itself. But you have to know the basic concepts (like critical path) and understand the problem space (e.g. tasks form DAGs, not sequences). Also, project management is in big part planning the work, not doing the work. Issue trackers help with the latter, not the former.