Your Software Process Sucks : The PreludeFiled Under Human Factors, Software Process
Picture this. You are sitting in a job interview with your next potential boss. Being a TDD/Agile/Scrum zealot you proudly declare:
“A strong skill of mine is software process, I really think I could be an asset to your team.”
Should the correct answer of the potential boss be:
- A. That’s great! We could always use people willing to improve the process.
- B. What do you have in mind?
- C. Our waterfall process has worked for 5 years. We will not change it for anything.
Recently, I was blown back when I heard the answer C come out of the mouth of a Sr. Architect. The interviewer could tell that I was sincerely disappointed by this answer and asked if I wished to continue. I agreed out of curiosity of what other nonsense he might say.
Choking on my bottled water was probably not the best show of face, but seriously? You don’t want to improve your process? You don’t want to work faster, smarter, and more efficient? Do you not like money?
Unfortunately, this is a resistance to change seen in a lot of organizations. Why does this occur? How can we fix it? Stay tuned, as the next couple of posts I will be exploring these questions under the series title “Your Software Process Sucks”.