Discussion:
Use Jira to replace the RAID log
f***@atlassian.com
2009-10-13 21:17:00 UTC
Permalink
Hello All,

I'm being asked to use Jira to replace the project manager's RAID log. Tracking Issues are straight forward. It is the Risks, Assumptions, and Dependencies I'm not so certain about. Has anyone used Jira to track risks, assumptions, and dependencies? What is the best workflow for this etc...? Thanks, David
--
Post by daw13 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=37884
f***@atlassian.com
2009-10-15 09:08:46 UTC
Permalink
Yes, I've done this for several teams in the past.

The first team needed a simple Risks and Issues register. The basic setup of fields for summary/description/due-date were the three they really needed, and the other standard fields (assignee, reporter etc) delighted them. We mapped "components" onto "business unit affected", ignored versions, and a handful of other custom fields fell out naturally. The project had two main issue types (Risks and Issues, as you could probably guess), but the thing that worked best for them was a stack of sub-task types - meetings, follow-ups, notes, process change, software change and so on. We used the "if any sub-tasks are open" condition to stop closure of the top level issues. The workflow was very simple for most things - "needs assessment (open)", "in progress" "ameliorated" (yeah, I know) and
"closed". Most of the sub-tasks had their own workflows as well.

The main reason for using Jira for this was simple - it tracks every change to an item. Even the basic reporting was enough to work for the risk teams.


I never got to grips with the Assumptions - the team couldn't really decide on a process that I could translate into Jira, beyond a simple checklist. It was important to get it into Jira though - they loved the ability to link other items to Assumptions. They ended up in a separate project, with no real workflow (but lots and lots of comments!)

Dependencies sort of fell out later - the team had a couple of meetings about it, then the team lead said to add it as a new issue type. Six months later, we had 2 items raised, but the team were reporting hundreds of them. A quick look round showed that they were effectively using the sub-tasks as dependencies as the "can't close if sub-task open" dealt with the process automatically. We killed the main issue-type, and put a simple "dependency" tick-box custom field as a flag on some of the sub-task types.

One more layer of sub-tasks would have been rather useful, and some of the reporting was a bit of a cludge, but it ended up working very well.
--
Post by broughn2 - online at:
http://forums.atlassian.com/thread.jspa?forumID=46&threadID=37884
Loading...