A few weeks back, I blogged about a great series of posts on how NPR.org migrated from Bugzilla to JIRA. The first two posts covered much of their high-level reasoning for making the switch, but in the third and final post, Kim Bryant, gets her “geek on” by diving into the nitty gritty details of how NPR.org uses JIRA to manage daily activities.
Kim gets specific about the 5 different user roles NPR.org has defined and what types of activities each performs regularly. She explains how they use projects and components to organise tasks and activities for Digital Media projects and requests, software applications and system administration. She also covers how they user versions to triage incoming requests, manage a backlog and plan tasks for release.
NPR.org also uses GreenHopper for agile project management and relies on calendars, charts, time tracking, dashboards and more.
Automated issue creation
NPR have even setup a project to collect automatically-generated errors from their applications. Jason Grosman has written another great post about how they mine their server logs and push issues directly into JIRA. They even developed a way to capture client side errors without bothering their users:
It’s great to see NPR.org taking full advantage of JIRA’s flexibility to manage their daily project activities. They are constantly “tweaking” JIRA to improve the way it works with their processes, not the other way around. I can’t wait to hear from Kim once they actually move to JIRA 4!