Intro to Unit Testing, TDD and BDD from QAGeekWeek
Had a swell time at QAGeekWeek. Here are the slides.
Had a swell time at QAGeekWeek. Here are the slides.
Why do we do the things we do? When we can explain why we d: practice, decide to keep or change the way we do things, we should have better excuses than “that’s the way we’ve always done it” or “it is considered a best practice”. If these are the only answers we have, we’re in a
A great time at BTD 2016. Here are the slides.
In the agile world, we’re told to “embrace change”. As we can see in the picture on the right, change can embrace you back, and it can hurt. But what is the cost of change? And how does agile affect it? Economically speaking, change has both reasons and affects, and both have economic consequences. In
Here’s the recording of the “Simple” talk, memes and all. It was recorded at Agile Eastern Europe, 2016 in Kiev.
When we started talking about scaling, we said that organizations are looking for a cure. The pain is slow delivery. That cure seems to be taking the success agility brought the team and scale it to a group, organization or the entire company. We know that small organizations (agile or not) generally have better delivery capabilities
Concluding the first part on “Everyday Unit Testing”, here’s the 2nd. Check it out!
My interview about unit testing is up on the A1QA blog. Check it out!
It’s a new series on Everyday Unit Testing, but I’ve got quite a set of ideas. Check out the first one.
What exactly do we want to scale in agile? As we discussed last time, we want to scale because of the perception that agile “works”, and therefore can relieve the growing pains. Let’s say it does work at the team level. It eradicates all the communication problems and the team is working at top speed.