It is not Agile's fault, it is your fault - Are you fed up with such statements? This article tries to provide a more constructive answer on how to make Agile successful. It first shows how Scrum can be harmful, then argues how Agile requires different skills on both product and delivery levels. It suggests to use CICD to counteract Scrum's traps and stresses the importance of systems thinking.
Automated acceptance testing reduces time wasted in manual testing and bug fixing, and when combined with Behaviour-Driven Development, can guide development effort. But it requires skill, practice and discipline. The Screenplay Pattern helps teams address these difficulties and is where you may end up by mercilessly refactoring Page Objects using SOLID design principles.
In a team doing TDD there is no need for testers that do manual checking. This gives testers the opportunity to focus on test automation and exploratory testing, but these require technical skills. 3
James Grenning talks about why people are not doing technical practices sufficiently or well enough, TDD and unit tests, and on becoming better in discovering "bad code”.
There’s no reward for being a Scrum or kanban shop if we are not delivering value to customers. We need to change our mindset, and focus on the principles that people follow and values they share.
"BDD In Action" is a book that aims to cover the full spectrum of BDD practices from requirements through to the development of production code backed by executable specifications and automated tests. 4
Developers across the globe attend coderetreats to learn from each other and refine their software design skills, but how do they work? What do people say about them? How can we make them even better? 3
A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around or through the challenge of doing fast iterations.
At then recent Agile Singapore conference James Grenning presented two technically focused talks - one on the importance of technical excellence and the other teaching test driven development. 3
Common System and Software Testing Pitfalls provides 92 pitfalls that make testing less efficient and effective. It aims to help you to avoid falling into pitfalls or dealing with the consequences.