We user JIRA for bug tracking and release management and we have started using greenhopper for project management inside of JIRA but one thing that it lacks is the idea of user stories versus tasks in those users stories. Does anyone recommend other task board like agile project management tools that fully support users stories and tasks as well as being fast and simple to user. I started looking at targetprocess so if anyone has feedback on that specifically it would be great as well.
问题:
回答1:
TargetProcess is the least intrusive project mgmt tool I've used.
回答2:
A common anti-pattern for Scrum and XP teams is to break stories down into tasks, track those tasks, and at the end of the iteration notice that all tasks are done, but the user stories aren't (because they are more than just the sum of their tasks).
I highly recommend not tracking tasks at all. Brainstorm them for estimation, if you like, but always estimate and track whole stories. If a story is to big, break it down into smaller stories - that sometimes takes some creativity, but it's almost always possible.
You can use sub-issues in Jira to aggregate stories into bigger stories, although this isn't very well supported by greenhopper, as far as I remember. If your team is colocated, I would very highly recommend index cards on a white board, anyway - even additionally to Jira, if you have to (that's how we currently work).
回答3:
Whiteboard and sticky notes or note cards.
I know you asked for software, but depending on your environment it might be hard to beat the communication value of a publicly visible task chart.
But if you must have software there's also Rally and VersionOne.
回答4:
My company have been using TargetProcess for a while and we are very pleased with the product. Whenever we have experienced problems or bugs, we have reported it to them and the problem or bug is solved really fast. It's a great tool that worked well with SCRUM. I really recommend it.
回答5:
Acunote is the best one I've found to-date. Really easy, simple and quick to use.
回答6:
We use Jira with GreenHopper with no problems. If you have control over the configuration of your Jira instance, you can easily create a story issue type that allows having sub-tasks. During the planning phase, we drop the stories onto the next version, and split them into sub-tasks, estimated in more precise time and assigned to team members. If those tasks are separate you can also convert them into sub-tasks of a specific story.
回答7:
Thoughtworks would be happy to sell you Mingle
回答8:
Take a look at http://AgileZen.com/
回答9:
take a look at jazz: http://www.theserverside.com/news/thread.tss?thread_id=44577, http://jazz.net/pub/index.jsp
回答10:
We've just released a brand-new tool called Crew which might work for you. It's very flexible and allows you to set up a project structure and workflow that fits your process.
http://www.devmynd.com/crew