Slashdot Mirror
Ask Slashdot: Issue Tracker For Non-Engineers?
purplie writes My non-technical spouse is an analyst in a small county government department, a handful of people plus some contractors for projects. Their project/task management is mouth-to-mouth, sticky notes, and emails, and it's driving them crazy. I want to suggest something like an issue tracker. It would have to work for tasks both large (year-long investigations) and small (arranging catering for a meeting). The issue trackers I'm familiar with are too software-development-oriented, or make too many assumptions about your 'agile' religion. Are there any good options for non-engineers? They use mainly Windows and have iPads. I don't like web-based tools, but that might work better for them because they don't have administrative privs on their machines. Something that also incorporates a wiki might be nice. There will be resistance if it's not really easy to use.
Redmine is pretty flexible and has worked for us across multiple disciplines.
Consider Trello. It's not strictly an issue tracker, but it's very good for this sort of thing and already popular outside of software circles.
You don't want issue tracking - you want task scheduling and task completion methodologies. The non-engineer have schedules to fulfill which are usually not associated with a deliverable but a task. If there's no deliverable, there's no bug, no feature, i.e. no ISSUE. So tracking issues loses the focus. Issues aren't always tasks in trackers and that's why those are so tied to code, since they mold issues to whatever a release date/agile software development needs.
Unlike issues, tasks always translate to effective actions to undertake someplace, sometime, with someone, for whatever reason.
Post-its are still used nowadays because they do their job representing tasks, and their physical form, order or the fact it is in the trash can imply its relevance, priority, date/time-frame and status. Tell her to keep using tools she's comfortable with, but customize a variation of KANBAN for her team's specific needs. And then maybe decide if a web platform or a physical board make more sense in her context, and the learning curve is acceptable. Post-its + a board or Trello are a good place to start.
I've successfully managed to trick a bunch of psychologists into using redmine for issues management. These guys are the epitome of non-techies.