Comprehensive software reviews to make better IT decisions
Zephyr Extends Jira Cloud With Test Management Capabilities
Atlassian’s Jira remains a popular collaboration tool for teams looking to better coordinate work. However, it requires third-party add-ons and integrations to support end-to-end artifact traceability and product delivery. SmartBear Zephyr fills Jira’s test management capability gap.
The test management landscape is still dominated by the big names in the industry, such as HP (software delivery products acquired by Micro Focus), Microsoft, and IBM. The market is now changing with the emergence of more open source options and small, tactical solutions, such as Zephyr, which offers specific testing capabilities without the added bells and whistles found in comprehensive suites. Zephyr gives organizations essential test management features, such as:
- Create, store, and categorize test artifacts
- Manage, launch, and report automated testing
- Enable traceability between test cases and requirements
- Track and analyze defects
SmartBear’s 2018 acquisition of Zephyr extends its test design and execution capabilities through its integration with SmartBear’s portfolio, such as SwaggerHub, HipTest, CrossBrowserTestin, and SoapUI Pro. The recent release of Zephyr for Jira Cloud, a subscription-based add-on, further expands Jira Cloud to include testing in its workflow and enhances the visibility into testing practices and progress.
Source: Atlassian Jira, product report, SoftwareReviews
Jira acts as a centralized platform to coordinate and orchestrate testing activities using the Zephyr add-on according to quality, feature, delivery, and collaboration requirements defined in the tailored Jira workflow.
Zephyr for Jira Cloud is a much-needed capability to expand work management visibility and traceability into the testing lifecycle. Zephyr improves the management of tests in the Jira environment, but it does not execute them, so additional tooling or integration costs may be required. Nonetheless, this add-on should motivate the evaluation of your application lifecycle management architecture, particularly the integration of your tools and the relationship among all of your artifacts, in order to get the most value from your tools.
Want to Know More?
Traditional accounting practices are tailor made for waterfall project management. Organizations that have transitioned to the use of standing product teams using Agile and DevOps need to transform their accounting practices as well or they will leave valuable capital expenditure dollars on the table.
IBM is changing the terms of its ubiquitous Passport Advantage agreement to remove entitled discounts on over 5,000 on-premises software products, resulting in an immediate price increase for IBM Software & Support (S&S) across its vast customer landscape.
So you’ve gone Agile. You do daily scrums, retrospectives, and all the “right” Agile ceremonies. But still your organization isn’t quite convinced. It is now critical to balance the drivers and goals of both Agile and traditional thinking in order to achieve organizational success.
Do you feel like your Agile teams are treading water – going through the motions but never going anywhere? It’s a risk, and practices such as daily standups, retrospectives, and demonstrations need to be used wisely or you risk losing discipline to meeting fatigue.
Stakeholders expect the speed and responsiveness of product delivery does not come at the expense of quality. QA tools offer retailers the ability to continuously ensure both business and technical quality standards are upheld, but these tools should not be viewed as a silver bullet.
No matter how good your product roadmap and backlog are, they are only as good as your audience’s ability to understand your vision and priority.
The scrum master is like the conductor of an orchestra, ensuring that every piece fits together at the right time to create something greater than the sum of the parts. You don’t have to know how to play each instrument, but you do have to understand what each part contributes to the overall masterpiece.
Tools are important to product teams, but only when they support solid people and processes.
Aha! introduces scenario planning to give product owners the ability to create and compare multiple release approaches based on team capacity and backlog priority.