|Door:||Harm Pauw, 22-11-2016|
|Onderwerp:||Development driven by tests|
|Door:||Pieter Versteijnen, 22-11-2016|
The first thing you need is knowledge about test automating. When you leave school or never invested time in learning how then start there. Attend a TDD training, watch videos, read blogs invest time to learn how unit testing works. But that’s not all, also invest time in stuff like clean coding and design patterns. At the end of this blog I will put in some links to books to read.
|Door:||Wiger Middelkamp, 22-11-2016|
|Door:||Pieter Versteijnen, 15-11-2016|
• Have you seen defects go back and forth between a test and development department?
• Have you seen a delivery go to production with lots of defects?
• Have you seen a delivery go to production with a lot of stress from the team or other departments?
• Have you experienced downtime during or after the release?
• Have you heard testers complain they cannot test everything on time?
|Door:||Guus Verweij, 07-11-2016|
Yesterday in our Agile Expert Program a colleague of my (Martijn Dehing) tripped over a post-it note with “Agile Scrum” written on it. I had not even noticed it anymore, so often I hear this two things glued together. But he was right to make a point of it. “Agile Scrum” doesn’t exist!
Agile is the container concept where a framework like Scrum is covered by. So Scrum is always an Agile practise, but Agile doesn’t mean that it necessarily is Scrum. It could be XP, TDD, or any other Agile framework. It’s like:
|Door:||Wilbert Seele, 05-10-2016|
Starting Fresh with Agile
I attended Scrum Day Europe 2016 last summer and had a great time. The talks were great and I was cured of a sudden case of the Zombie Scrum to boot! I began writing this article some time later, but due to circumstances it took me until now to finish.
Part of the program was an update from Scrum.org on what they’re working on, and a follow-up talk about Scrum Studio. This really resonated with me as it confirms something I’ve long suspected. Scrum Studio was born out of empirical observations of Agile transformations. The observation in question being that the transformation doesn’t happen. Of course, there’s always exceptions to the rule, but in general the finding has been that the running organization can’t change Larman’s Laws have been confirmed.
|Door:||Harm Pauw, 31-08-2016|
If a non-developer looks at some source code on the screen of a developer, that source code will look like some random characters in all kinds of funny colors. They think that this is what makes programming hard. I think that this is also one of the reason why time and time again attempts are being taken to create visual tools to avoid having to manually write source code, like UML tools that generate code for you.