Tags

, , , , , , , , ,

Hi all,

My latest rounds of training being done, I noticed a trend emerging from these sessions. The impending desire for people to be told what to do is imprinted really deeply in all of us. One thing that is fundamental in the course we give is to destabilize to root knowledge of how software development should done. For too many years we have built a notion that software can be, somehow, scalpeled or boxed in order to fit into a well oiled defined process. For those of you who have taken the time to read my previous posts, in most of them I mention the fact that it is important to remember that software requires complex cognitive work, which implies creative work. This work cannot be mapped to a predictive pattern. Scrum works well, if you haven’t guess it yet, because it is rooted in an Empirical process. Empiricism is what leads us to understand something by acknowledging that we must first try something and then adapt to better suit our context. This context, especially in software development, is ever changing and therefore not suited for defined thinking.

It would be like trying to fit the square peg you have on your right into a round hole over and over again. You all know, as well as I do, knowledge is power. Simply applying that knowledge is wasted if not well adapted. This is where Scrum comes in and why it is perfectly suited for our industry.

Now, in order for that to happen we must first be willing to fail, therefore let people work out their own problems (source of motivation) in order to achieve higher efficiency and for people to understand the foundation of why we do certain things (within Scrum). Alot of people have a hard time grasping this fact, mostly because it is so much outside their comfort zone.

Feel free to share your ideas, comments. Scrum on!

Thanks, PS 🙂

Advertisements