With a growing number of tools involved in software development, it becomes more difficult to pinpoint which tool should be used when, and for what. We set out here why and how you would use ScopeMaster as well as Jira.
We Use Jira Server
If your stories are already in Jira Server, export them (via CSV), put them into ScopeMaster, refine them then transfer them back into Jira either one by one or by importing the CSV.
We Use Jira Cloud
You have a choice, you can do the same as above or you can add the Jira Plugin to your Jira Cloud Instance and then maintain your stories in Jira. From within the plugin, you can see the analysis and sizing information. You can also purchase a subscription to ScopeMaster and benefit from the extra insight on user story quality.
Jira Software is a very popular platform for collaboration, its principal function is to provide a shared repository for content and team activities for the development of software. Unlike ScopeMaster, Jira does not analyse your user stories, it does not identify potential defects and it does not perform estimation on them, whereas ScopeMaster does. They are complementary tools.
Introducing ScopeMaster into your software development process, brings significant value that compensates for the extra effort involved in ensuring effective user adoption. With better quality requirements earl on, you project will have less rework and project risks are reduced because of increased certainty of scope, early on.
Integration with your current processes is a key issue to give thought to when you’re considering introducing a new tool, but another important consideration is whether the value delivered by the potential new tool outweighs disruption that could be caused by the adoption of new software.
Remember, the value of using ScopeMaster far outweighs the effort of introducing it into the process.
Recommended: ScopeMaster then Jira
Stories that are first analysed and improved within ScopeMaster and then moved to Jira once development starts. The quick way to move content from one system to the other, without re-keying, is via CSV format. You can easily create a new project space in Jira with user stories imported from ScopeMaster.
Early Quality, means less Change
You should find that using ScopeMaster first, your stories will remain fairly static thereafter. The acceptance tests may evolve, but the stories themselves will not.
Easy Bi-directional transfer
Both Jira and ScopeMaster allow stories to be moved in either direction via CSV without the need to rekey.
Already have Stories in Jira?
ScopeMaster directly supports importing stories from Jira (via the API).
Your primary requirements repository and collaboration tool is Atlassian’s Jira. Adding another tool to your software development project might be a concern. But wait! The value that any tool delivers should be your number one consideration. We have already shown that the value of ScopeMaster is very significant – as much as 30% of your project cost. The next consideration is can you slot it conveniently into the development process, and the answer is yes.
ScopeMaster provides best value early on during the software lifecycle. We find that most customers are happiest by using ScopeMaster as the initial place where they create and refine requirements. Once refined, they are then exported into Jira (or your normal collaboration repository).
Using ScopeMaster alongside Jira (or similar tools) is both straightforward and easy.