Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality. Without standardizing, the project may suffer. Standardizing requirements descriptions provides a minimum of eight benefits from requirements descriptions unification, which in turn positively affects testing and makes management of ongoing changes in requirements easier with the help of tools.
Software technical practices are usually adopted as a means of creating better products. These practices can create and maintain a healthy human system. Technical practices raise the consciousness of individuals and the team as a whole. Technical practices hack consciousness giving us a quick, deep chute into depths of connection that improve our selves, our products, and our world.
The book Effective Debugging by Diomidis Spinellis describes 66 different approaches for effective debugging of applications and systems. It provides methods, strategies, techniques, and tools for finding and removing faults, and gives examples for using them in different settings.
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. 13
JUnit 5 is coming! In part 1 of our JUnit 5 coverage we wrote some preliminary tests. In part 2, we take a closer look at how to run tests, and some of the cool features JUnit 5 brings to the table. 6
We review the book Infrastructure as Code by Kief Morris, who lays down the foundation for Infrastructure as Code and outlines the main patterns and practices recommended for building it.
JUnit 5 is coming! It thoughtfully improves the JUnit API, has a great extension model, and a revolutionary architecture, which might very well redefine the future of testing on the JVM. 4
With over a decade of experience immersed in development and championing agile practices, Wendy Closson coaches technology leaders to manage effectively and navigate the choppy waters of business.
In this week's podcast Richard Seroter talks to James Shore, Llewellyn Falco, and Rebecca Wirfs-Brock on TDD and Incremental Architecture. 1
Richard Seroter talks to Lisa Crispin, who works on the tracker team at Pivotal Labs, and Justin Searls, software craftsman and presenter of How to Stop Hating Your Tests.
Today we'll get tactical, and talk about how the delivery team can acquire all the skills it needs to deliver software when the number of testers are low and specialization is a reality.
How do you handle a long list of defects in your project? You don't. Kirill Klimov explains why you should solve defects right away, or state that you will not solve them. 2