Continuous delivery, test automation and UA(T)
Everyone talks about UAT, but having a UAT phase is in many ways failure of your development model. Why should a user have to run testing if the requirements were captured correctly through continued engagement throughout the development (using sprint showcase)? Why does a user need to test the software when your automated test coverage should be 100% (unit, functional, GUI, performance, etc..)? Are you building total product or developing against features? Spending hours / days on devising a UAT checklist or strategy?
I have put the (T) of UAT in brackets as part of your continuous delivery model should incorporate the concept of omitting the testing element and instead the user should just be signing off against a deployment to a staging environment.
User Acceptance is an improved model on User Acceptance Testing, it'll minimise the need for User Acceptance and stop you from having to put together a user testing strategy.
I specialise in all things Agile (XP, Kanban, Lean), in particular Scrum. I have a passion for taking on 'problem' projects / teams and turning them into a sucess as well as promoting automated test driven practices.




