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.
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.
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.
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.
Introduction There’s no doubt that Excel is widely used as a tool for Software QA analysis and reporting. Whether one clamors to pivot tables,build macros or invoke the function wizard, the instinct to turn to Excel for analytical tasks is undeniable. At the same time there are 4 areas where Excel is inflexible, time consuming or just simply can’t get the job done. 4 capabilities you need in Excel for Software QA Professionals Flexible Charts - Sure Excel lets you create charts.
Background Last month I was invited as a speaker at Global Testing Retreat 2017(#ATAGTR2017) which is perhaps the greatest Agile testing conference in India. My talk Focusing Test Managers time on what matters focused on how digital transformational programs are putting pressure on QA & testing function and therefore the need to reinvent. The key theme of the conference revolved around the next wave of Quality Assurance,on how to evolve as test teams to deliver Quality@Speed, on how to accelerate test automation,and most of all moving from a IT focused test role to a business focused QA.