It all starts with Quality
Testers do not just “do testing” in an Agile team and have many roles to play during the delivery of software. Testers are fully involved in the development lifecycle, meaning quality starts from day one. Although everyone in the team is responsible for quality, the test team tend to drive this and lead by example to promote good working practices, as well as being at the forefront when identifying product risks.
It all starts with Quality
Hiring a team that consists of qualified people that are well versed in Agile principles is extremely important for any software development team. But the task of interviewing and hiring good Agile testers often proves to be difficult. With that in mind, we've created a new white paper with 10 great questions you can ask when conducting interviews, and a guide to the kind of responses we would expect. You can download the full white paper here, with a sneak peak below.
As a multi-award winning software testing consultancy, nFocus live and breathe Agile. So much so that we decided to run our Marketing Team using Scrum. If you're interesting in learning about the benefits of adopting Agile from a testing perspective, check out this white paper instead.
In today's post I thought it would be useful to consider Agile Test Strategy and the quality challenges associated with implementing Agile and Scrum. If you have time, we would also recommend taking a read of the white paper - The quality challenges associated with implementing Agile and Scrum.
So by now you would have realised that projects run using waterfall methodologies are from the Triassic period and Agile is the new kid on the block and here to stay (well for the next six months at least..). And, the traditional role of a Test Manager seems no more, almost extinct like the Tyrannosaurs. But wait, just because testers are working in collaboration with the project teams and reporting, estimating and planning directly with them doesn’t mean the Test Management role is dead as a Dodo, no far from it.
So I get to see lots of different organisations all trying to implement Scrum to varying levels, several themes come out:
Welcome to the first in a series of bitesize articles we're writing on Agile and Testing.
Creating a robust and practical Agile Test Strategy should exist in all organisations that employ an Agile approach to delivering projects and programmes of work. Being ‘Ready’ to test is vital to the success, having just a set of requirements isn’t enough….
Agile Project Management is the focus on producing a quality product by the continuous improvement, project team support, and providing flexibility in the requirements and scope, not to mention ensuring testing is performed in the most dynamic and efficient way possible to produce the desired outcomes. Performing good Agile Project Management is very important, to embrace the main principals of Agile to ensure the customer satisfaction through early and continuous delivery and to provide the best chance of the customer's competitive advantage by being first to market with new and innovating products and services.
There have been challenges in the adoption of the Agile principles (an Agile Test Strategy) and Scrum Framework particularly with poor quality of the delivered software. This has resulted in delays and a mismatch of the expectations of stakeholders and delivery teams. There is no specific mention of testing or quality assurance in Agile or Scrum; it is implied as an integral part of the principles and framework. This has caused some confusion resulting in inconsistent approaches to quality management and testing. Often formal testing has been reduced to ad hoc ‘try it and see’ during a sprint. This loses the testing rigour that delivers quality by use of industry accepted full lifecycle testing.