|
|
|
|
|
|
by tonyarkles
4148 days ago
|
|
|
Not to criticize those who have worked on project management systems in the past, but I've found that most systems are generally pretty painful for me. Generally the project management "systems" that work best for me is something like a shared Evernote checklist or org-mode, but those aren't nearly as good for clients/teams to use. One of the things that I've often encountered is a granularity/association problem: tasks often become either Omnibus tasks where there's a shitload of stuff jammed into a single task, or a spread out mishmash of related tasks that don't have very good linking between them. A good example would be a web development feature. I'm going to do the backend, someone else is going to do the frontend. Those are two pretty distinct tasks, but there's a lot of shared communication there. And most PM systems I've used don't have a (good) way to link those together. Mostly in my experience, 3rd party tools end up getting used, with links to shared wiki/moqups/google docs/dropbox whatever. If I need to have 7 tabs open (email, slack, trello, moqups, google docs...) to get all the information I need to figure out what I need to work on next, my PM system isn't serving me very well. |
|
|
The biggest issue we had in our team was that some team members are just slowed down by having to use a project management tool and would much prefer to just have a written checklist on their desk, but obviously this causes a lot of issues when you're trying to keep track of what's been done and what hasn't. The planner was created to help circumvent this issue, when tickets are assigned to a user and planned for a certain date they become a checklist on that user's dashboard. This way we were able to let checklisters do their thing uninterrupted and still have their progress tracked on the board and the general product overview.
Tasks becoming either omnibus or overly fragmented is familiar to us too. Matterhorn has a feature grouping system that can help but it always comes down to how you use them. It might be an interesting problem to solve for the future.