Redirects to legacy blog post.
Is your organisation:
* Wanting to get more out of your Software Developers?
* Wanting to increase RoI?
* Spending too much money fixing bugs?
* Development team not releasing business value fast enough?
* Maybe your a software developer and you want to lift your game to the next level?
If any of these points are of concern to you… read on.
Redirects to legacy blog post.
The first thing to clear up is that TDD is not primarily about testing, but rather it forces the developer to write code that is testable (the fact the code has tests written for it and running regularly is a side effect, albeit a very positive one).
Redirects to legacy blog post.
Following is the five steps we use to run our Retrospectives. I’ve purposely made these as terse as possible, so it can be used as a check list as the retrospective progresses. Below the five steps I’ve added some extra info and tips.
Redirects to legacy blog post.
I recently wrote a post for the company I currently work for around the joys of doing TDD. What is your current approach to testing? How can you spend the little time you have on the most important areas? I thought I’d share some thoughts around where I see the optimal areas to invest your test effort.
Redirects to legacy blog post.
In this post, it’s my intention to bring some clarity to the following question. Why does a business decide to employ Scrum as the chosen framework that their development team/s use for managing the business’s projects / work items?