“IT’S ALIVE!” Are you turning Jira into Frankenstein’s monster?

Patrick AndersonPosted by

“The beauty of the dream vanished, and breathless horror and disgust filled my heart.” – Victor Frankenstein, Frankenstein, Mary Shelley

When Victor Frankenstein set out to create human life from non-living matter, he had a clear vision: to better mankind. He wanted to do this by creating a beautiful creature with “lustrous black hair”, “teeth of pearly whiteness” and “watery eyes”. Yet despite Frankenstein’s best intentions, his fiddling and tinkering created a hideous eight-foot monster that reaped havoc on the brilliant scientist’s life. Why am I regaling Shelley’s classic? Because many organizations are in danger of turning Jira into their own monster.

Atlassian’s Jira is very effective at helping developers to manage their backlog, track work progress, and monitor issues. Its success in the Agile Development space has been profound and far-reaching, and most Jira users would argue its beauty lies in its simplicity. At the same time, another key benefit is the tool’s ability to be customized to meet individual/team workflow needs. This functionality is both a blessing and a curse because it allows IT teams to fiddle and tinker with customizable fields and plug-ins to incorporate as much of the software delivery process, from ideation to delivery, as possible – turning Jira into something that it’s not.

There is the misguided notion that all stages of the software delivery value stream can be successfully migrated into one system, despite no evidence to support the theory (remember when we overloaded poor Rational Team Concert (RTC)?). Having one end-to-end platform is naturally appealing in terms of perceived simplicity and cost benefits. The idea, however, is inherently flawed. History speaks for itself; any tool that has attempted to be ‘everything for everyone’ has failed miserably. There’s just too many nuances within the different workflows across the various specialty teams that plan, build and deliver software at scale.

When you plug too much workflow into Jira (or any one tool), you will inevitably flood the tool and hit a wall, undoing all the productivity achievements that Jira and other leading development and delivery tools have brought to the software delivery process. It won’t take long before your own monster begins to wreak havoc on your organization’s ability to accelerate the value delivery of your software products, and that you too will have breathless horror and disgust fill your heart. 

And we don’t want that, do we? Sounds far too dramatic. Fortunately we have own brilliant scientist in Craig Gorveatt – a Pre-sales Engineer at Tasktop – who in the below webinar explains how to unburden Jira to optimize your end-to-end software delivery value stream (and ensure the beauty of your dream, whatever that may be, doesn’t vanish!):

Are you drowning Jira and the rest of the software delivery value stream? Download the white paper!

Click image to download white paper