#fogbugz

[infobotbiz-blog]

Resolved: What web-based software combines bug tracking, agile project management and client collaboration? #fix #development #computers

Resolved: What web-based software combines bug tracking, agile project management and client collaboration? #fix #development #computers

What web-based software combines bug tracking, agile project management and client collaboration?

Possible Duplicate: What are project managing, task/issue/time tracking web apps are available for free or at least cheap enough?

I’m aware of really good packages that handle each one individually: 1. Bug tracking: Trac, Mantis, JIRA, FogBugz 2. Agile Project Management: Version One, Pivotal…

View On WordPress

[infobotbiz-blog]

Fixed: How does Trello store my information? #dev #solution #answer

Fixed: How does Trello store my information? #dev #solution #answer

How does Trello store my information?

I started using Trello at work to manage my team and liked it, but then my my VP Dev told me we can’t store any company information offsite because of regulations (we’re working with the finance industry). Trello is not hostable locally, so I’m out of options.

If I’m going to try and work around this, I need to at least know that all the data is encrypted…

View On WordPress

[anglee-blog]

[aridavidow]

In talking with other developers who are doing Scrum (vs. other forms of Agile development) the couple who seem to be happy with their tools are using Jira (which really means Jira, a bug-tracking application, with a plug-in for Scrum called Green Hopper, and maybe other plug-ins). That is a very, very small sample size and none of the users that I know really knows Jira or Scrum.

Where I work, we use Fogbugz, which I generally like (and love relative to the open source bug trackers to which I have been exposed). I don't find Fogbugz a great tool for Project Management, but several of the issues that bother me might work much better in Scrum development compared to trying to shoehorn traditional Waterfall into Fogbugz.

This link outlines a scrum process that is not so scrum-ish (it assumes pre-planning all sprints in a project, for instance, instead of maintaining a backlog, grooming stories and epics, and then promoting things as part of planning for each "next" sprint after the review of the sprint-just-ended. It does, however, map reasonably well to outline planning as we have done successfully on our hybrid in-house Agile style.

Worth thinking about as we look at ways to do better project management (which we currently think means "more Scrum-like").