51–60 of 78 posts
I'm a long-term JIRA user (and even somewhat evangelist). There are probably many much more "modern" issue trackers over there, but JIRA worked extremely well for me for many years. There are a few big problems with JIRA, though (field-level security and limited issue hierarchy).
For my OS-projects I've found GitHub issues to be more than sufficient. That's what I'd call clean and simple.
We've been using Phabricator[1], a spin-out of Facebook, and love it. It's perfect for technical teams, and usable enough for the rest of the company. [1] http://phabricator.org/
More details in http://xn.pinkhamster.net/download/New_Process_and_Tools.pdf
Something simple like Wunderlist or Asana is a good choice, IMO. The less time you spend dealing with your PM tool, the more time you can spend on actually doing important things. I've also heard this argument if you're running a product, though I'm not sure how on board I am with it: don't record user requests. The important ones will be requested enough that you'll remember it.
I direct all feature requests go on a list that CS owns and we review it with our customer team, vp eng, myself and qa in a weekly meeting. We talk about the problems, get shared understanding and we collectively agree if we can say "not now". "Worth looking into". "This is easy let's do it now". "This could be tough or easy - needs more info". This is basically what partly feeds a short backlog (~20 items) that gets prioritized during sprint planning. Plus longer term roadmap stories.
Roadmap - a ppt with: Next 3 months (most detail) Next quarter (high level, use cases identified) Next Half (broad themes)
Looking at some of those 'complex' management tasks it seems like a missing feature would be to poll your repositories to look for TODO: 's and list them. For instance, I'm the sole developer of my web backend, iOS and android platformy thing and while android studio has good TODO: Integration sublime and Xcode require plugins, it would be awesome to have something that looks at all three repositories and tells me wh…
What does grep or a couple lines of Perl with a clever-ish Regex not do that you need them to, for the TODO finding thing?
Also, whilst I could do it on the command line, or can do it in each particular development environment (with the right plugins), I want some global overview of the whole shebang
Looking at some of those 'complex' management tasks it seems like a missing feature would be to poll your repositories to look for TODO: 's and list them. For instance, I'm the sole developer of my web backend, iOS and android platformy thing and while android studio has good TODO: Integration sublime and Xcode require plugins, it would be awesome to have something that looks at all three repositories and tells me wh…
Might not work for your development needs, but such a feature exists in PHPStorm/Webstorm, and I'm guessing probably all of the other IntelliJ products. There is a 'TODO' tab that shows you all 'TODO's in your project directory. Like so: http://i.imgur.com/TW4jXN8.png
For short term, post-it notes and legal pads. There's something for me about having those TODO's constantly in my face. I always get them done. And it feels so good to crumple that ball of paper and throw it into the bin. Each sticky is 5-30 minutes of work.
For longer term/planning: Trello. When I'm ready to tackle something, I convert the Trello card into a sticky note, archive the card, and get to work!
Sometimes when I am feeling super unproductive/lazy, and have a buildup of sticky notes, I'll convert all those sticky notes into a neat 1 page legal pad page - handwritten, with checkboxes. By the time I'm done doing converting (and crumpling up all those sticky notes!) I feel rejuvenated enough to work on that second pass.
I love throwing stuff away. When I am SUPER unproductive, I'll tear away the blank part of the sticky note and throw that away.
It's got a good command line interface, a built-in web interface, it's self-contained, and the model is easy to understand. It's simple enough that I can use it as a replacement for RCS for personal stuff (like a LaTeX document) but it scales to large projects too (it's used by SQLite and Tcl/Tk, for example).
It's also trustworthy, with a solid, portable, and well-tested code base—not a surprise since it was originally authored by D. Richard Hipp. I have no clue why it isn't more popular.
has just enough fields, features, and customization to be useful but not overwhelming.