Plug-n-Play ALM/Agile tools

Connect a variety of ALM/Agile tools. If you have your data spread across multiple tools, no problem, connect all of them. View26™ enables powerful aggregation and correlation across all the tools.

Instant Charts & KPIs

VIEW26 uses data from ALM/Agile Tools to help IT leaders move faster, optimize work patterns, and gain actionable insights with concrete data.

One click sharing of reports

Build report from standard templates or create your own. Add custom annotations where required. Share your report to any user with a single click. Access reports anywhere, anytime and on any device.

Watch demo video

Welcome to our blog!

We post about Software Engineering topics, insights and events, as well as updates of VIEW26.

Measuring Agile Maturity with Cycle Time

By Ajay Emmanuel on June 9, 2017

An efficient way to measure the maturity and performance of an agile team is by measuring cycle time. Cycle time is the time spent working on an issue — typically, the time taken from when work begins on an issue to when work is completed, but also includes any other time spent working on the issue. For example, if an issue is reopened, worked on, and completed again, then the time for this extra work is added to the cycle time.

Continue reading

Test Management and QA Tools for JIRA

By VIEW26 on May 11, 2017

Testing in an agile software development environment is an essential part of delivering requirements that provide a good experience for the end user while maintaining velocity.By integrating QA tracking, testing and analysis into each iteration to phase of the agile software development process, teams can move faster, identify blockers with more accuracy,and release updates more efficiently and effectively. While JIRA wasn’t designed to serve as a Test Case Management,it can be configured to support test case management in a couple of different ways.

Continue reading

Avoiding a cliff-hanger burndown chart in JIRA

By Ajay Emmanuel on May 5, 2017

The Burndown chart is very simple. It is easy to explain, easy to understand. But there are pitfalls observed in the way teams adopt and use the burn-down chart for tracking the Sprint progress. The most common issue is of the Cliff-hanger Burn-down chart. When we first started off using JIRA Agile, we used Epics to specify large feature-sets ,stories for the individual capabilities of the larger feature, and technical tasks (JIRA sub-tasks) for individual work items.

Continue reading

The 4 agile testing quadrants

By Guest Blog on May 3, 2017

A good agile product development manager knows that you can’t separate coding from testing. Because agile methodologies are iterative, testing and coding are done incrementally and interactively so that features can evolve in response to changing customer requirements. Agile testing comes in many shapes and sizes and covers all types of testing, including unit, functional, load, and performance tests. Depending on what type of agile testing you’d like to do: from automated, to manual, and everything in between, there are different test types you can choose from.

Continue reading