There has been a lot of discussion about the What’s and Whys of Behavior Driven Development and I would like to offer my take on this subject. Why Behavior Driven Development? The term “Behavior Driven Development” aka BDD was first
100% Code Coverage
Introduction The focus of this writing is on the appropriate amount of unit test coverage in legacy code. As a definition of legacy code, I defer to Michael Feathers’ description: code without tests. Common questions about code coverage are how much is
Elastic Beanstalk and Visual Studio in Action
Elastic Beanstalk is AWS’s simplified application deployment and management platform. It allows developers to focus on building applications instead of some of the tedium associated with deploying it to a robust production environment and much of the care and feeding once they are deployed. When working with Elastic Beanstalk, you can limit your scope of… Continue reading →
Dan Ariely: What makes us feel good about our work?
This is a great TED video from Dan Ariely that discusses motivation in the knowledge economy.
Agile Testing–Common Myths and Truths
I recently presented on Enterprise Level Integration and System Testing in an Agile Environment at few locations. Whenever I discuss agile testing, I am asked several questions that expose various misunderstandings about agile testing. Myth–Testers may not get detailed requirement documentation
Is Your Scrum Master a Servant Leader?
If your organization is using the Scrum process, you may be familiar with the role Scrum Master aka “scrummee” in my team. If you attended any Scrum training or have been coached in Scrum, you would have definitely come across
Thoughts on Training and Coaching
I recently attended a talk by a well-known agile coach and author where he stated “training without coaching is irresponsible, and vice-versa.” This statement got me thinking about how we transform companies and the approach to training we take. I
Trust the Team!
One of the Agile Manifesto principles says we should “build projects around motivated individuals – give them the environment and support they need – and trust them to get the job done.” Recently I was reminded of how powerful a
PRODUCT OWNER: Beyond the Scrum Guide
The Scrum Guide presents the framework for Scrum and high-level details about each role. For role-specific details, there is purposefully no prescription in the Scrum Guide that defines how a developer, a tester, or a Product Owner (PO) works. Specifically, the PO is
Agile Contracts
There seems to be a ton of willingness today for companies to modify their legal relationship with their clients. Maybe we are finally at a point where we realize that holding people’s feet to the fire doesn’t produce the kind



