Your New Process (Some Assembly Required)Filed Under Software Process
Software teams are continually looking to adopt and mutate their processes to help counteract their immediate needs and weaknesses. And I think we can all agree that different software processes have their strengths and weaknesses.
Therefore, it is only logical to say that the this equation holds true:
Process Strengths + Current Team Weaknesses = Process Adoption and Success
The #1 failure of newly adopted software processes is effort.
I have watched numerous teams time and time again throw away software processes (that could have solved all of their problems) because they never gave any effort to truly adopting them.
You see your egg and expect it to crow – Chuang Tzu
Just because you “label” yourself as an Agile team – does it mean you are actually using Agile? Seriously…be brutally honest…does it?
It pisses me off to no end when a poorly executed project is blamed on the process. What a bunch of bullshit! It isn’t the poor process’s fault – it is the crap job of the people executing it.
I sincerely believe that regardless of the process – if you give real effort your project will be a success. After that, permanent adoption of new processes is if the new processes give you better success on a relative scale.
Without true effort, no process will work.
Without true effort, no project will be a success.
Without true effort, you are wasting your time.