Susan Worthy, my manager from a past job at ClearStory Systems, pinged me the other day regarding their development team’s switch to JIRA. Somehow, the switch to JIRA caught the attention of the CEO and, long story short, JIRA went from being just a bug tracker to an entire project management tool.
While Susan and I had discussed Confluence for knowledge management before, she had no idea that JIRA was an Atlassian product.
Here’s the kicker. I knew of the brand name “Confluence” from our conversations. I had no idea that JIRA = Atlassian.
So basically . . . again . . . YOU ROCK!
It’s not often that I rock, so I had share. 😉
I asked if I could quote her entire email about JIRA; she said yes, but then Hank Nelson, the CEO, decided to write a blurb himself. Thanks, Hank!
My development team selected JIRA to replace Bug Impact and to provide an increased level of management. We were severely struggling with a major product release and continually missing milestone dates and not completely understanding the ramifications of some our decisions on the ultimate release date. We were becoming demoralized and clients were banging at our door for the new modules that we had promised them.
I personally dove into the abilities of JIRA and very quickly realized that we had only touched on the product’s abilities. We focused our efforts for a few days on JIRA and were able to completely outline the remaining tasks and timelines. Using JIRA we were able to assess the inevitable trade offs in an effective, real time manner. Although we will be a few weeks late, using JIRA has allowed us to determine the realities of our project and set reasonable expectations.
We will be expanding JIRA’a capabilities to other aspects of product management and areas of the company.