Testing in an Agile Environment
"Adopting Agile can mean fewer defects, and projects going through User Acceptance Testing (UAT) more quickly."
Forum Practical Agile report, October 2011
Testing in an Agile environment involves testing as early as possible and testing often but what are the challenges affecting Agile testing, how is it different to other testing methodologies and what are the benefits?
To work correctly, Agile testing has to be run using proper processes and guidelines, and not as an excuse to get things done more quickly. Consistency in approach is critical and "'being' Agile, rather than 'doing' Agile", as one organisation coined it, will bring success.
Agile development also bends the traditional ideas of work roles: with Agile, people are expected to be able to perform each other's roles - developers will test, business analysts will develop, and testers and developers will do analysis. The test managers' and test analysts' job is then to implement changes on a sprint by sprint basis. But working this way raises further challenges, including the need to maintain control and communications between and within teams and stakeholders.
Who should attend
- Member Experience Report Presentation
- What do we mean by Agile?
- Choices (what project; which Agile)
- Organisational and people questions
- How to test in Agile
- Estimating, measuring and reporting
"The Corporate IT Forum is a fantastic level check, free of vendor sell and consultancy hype. I like the open sharing of experience…"
"We get valuable knowledge and experience from members of The Corporate IT Forum. This helps us to make better and informed decisions to reach our business goals…"
"The knowledge from other people on what they are doing/have done is invaluable to my team"
"The workshop validated the marketplace for supplier apps; participants were of a uniformly high standard; personally, I value highly the ethos of the Forum in the fact that it is supplier independent"