Uncle Bob Martin recently blogged about the hordes of untrained developers coming into the industry, which eventually leads to some huge software disasters. James Bach wrote about the failures of HealthCare.gov that stemmed from incompetence in software management. These are very good articles, that make you think: Should software professionals (developers, testers, managers) be regulated?
Last week I went to a presentation about Scaled Agile Framework – SAFe. I’ve read a bit about it before, but this was a more broad introduction to the topic. It’s going to be a success. When I talk about why scrum succeeded in crossing the chasms from developer world to business world, the main
A recent comment on (the now legacy) “4 signs that agile is declining”: “Let me be clear: Every single failing or failed project I have seen in the last 35 years, regardless of development process, has had self-inflicted mortal wounds from execrable language skills and the resulting breakdown of communication. People nod their heads up
Because we know what it is like to read and debug a 500 lines method . And we don’t want to go through it again. Because we’re sure the other guys’ code can use improvement. Even if they thought otherwise. Because we can’t think at the same time about both the solution and its readability.
It’s been more than two years since I’ve wrote “4 signs that agile is declining”. I gave a talk at Agile Eastern Europe (which hopefully will be up soon) that revisited this topic. I went over things I see today that help agile lose. Not because it’s bad, but the way it seems from business
An interview with me appeared on DevPro Connections. Well, not appeared, more like published. Yes, much more like published.
As I was tinkering with my new CI toy, I became aware of a difference between light CI tools, and the feature heavy ALM tools: Permissions. I always I knew it was there, the ability to restrict all kinds of stuff. From adding work items, to deleting files from source control and to view comments.
Read about it on the Typemock blog. It’s D-licious.
Once you start to deliver software, you build trust. Once you have trust, people around you get more patient, and give you more leeway. Once people are patient, you get opportunities to experiment, and yes, even fail sometimes. Once you experiment, you learn from both success and failure. Once you learn, you get more ideas
My new article on Agile Connection is live. It’s about co-location, which is a basic agile premise. And how it can be broken and mended very easily. Read it here.