Why?Back in 2008 i was working as the lead test analyst on the autotrader.co.uk search platform, and I was informed by the delivery manager that we would be running a very large project, and we would be using Agile methodologies. But why Agile?
Ok, so we want to do thing thing called Agile.And we identified some benefits. 1 Improved quality2 Improve response3 negotiate a delivery schedule.But how did we do it? How to become Agile?
How?I’ve often described the “how” of our Agile baptism as a paradigm shift. That’s because none of the practices are difficult, in fact we deliberately keep them simple, and try and reduce the overhead of process and organisational minutiae.So it’s a culmination of lots of subtle practices that make the whole.
In SummarySo our move to agile was a real shift, in terms of where we live within a project and within the team (in terms of responsibility) .We had to invest in automation (I'm talking time investment, not just monetary, and it has to be sustained).Automation using Twist allowed us to focus our manual efforts, use our skill to determine the edge cases. (developers think in happy path terms).
So our move to agile was a real shift, in terms of where we live within a project and within the team (in terms of responsibility) .We had to invest in automation (I'm talking time investment, not just monetary, and it has to be sustained).Test automation allowed us to focus our manual efforts, use our skill to determine the edge cases. (developers think in happy path terms).
