June 2011 Blog Posts

Theory X management style in IT ? Mmmmmmh

In short Theory X management style is based on the assumption that workers:       dislike work and will avoid it when possible; need to be forced with the threat of punishment to work towards organisational objectives. Prefer to be directed; to avoid responsibility; are relatively unambitious, and want security above all else.        While most hackers and computer programmers enjoy to use their intellectual potential to solve challenging problems (mastery) in their work, are proud to contribute substantially to the company success (purpose) and are keen on taking responsibility for their work (autonomy). This is a scientific finding. Theory Y management...

Consistency & Change

It is possible to pursue Consistency through  simplification of unnecessary complexity and emergence of useful order and at the same time pursue Change subverting established order even exploiting doubt and paradoxes and unintended details to create high value Consistency can enable change as well as change can increase consistency. When you explore and discovery what to keep and what to change and how. Instead bad Consistency  preserve the status quo obstructing both change, emergence of useful order and simplifications while bad Change add complexity and variations and disrupt existing order without creating high value This is the easy part. The difficult one is the willingness to change :) ...

More on traditional and modern management

Traditional management often strive to explain and predict with the aim to anticipate the future. Modern management often strive also to interpret the present and react to events with the aim to adapt and invent the future. The paradox here is that the effort to predict the future make it harder to control the future. While the effort to recognize and interpret the present reality and adapt to it can enable to control the future inventing it : We can't control systems or figure them out. But we can dance with them. - Donella H. Meadows Other curios paradoxes that...

Small steps Vs ongoing big changes

Scrum says: time-box & prioritize items to maximize value. In the release planning meeting, in the sprint planning meeting, at the stand-up meeting, every day during the sprint Startup and Open source lessons and Agile Software Development suggest: release early, release often, and listen to your customers eXtreme Programming principles: Baby Steps (to reduce risks and get early frequent feedback)  and Improvements (don't wait for perfection,don't leave behind you a mess) Complexity Science suggests: strive for safe-fail experiments whose success can be highly valuable and whose failure can be very informative Lean software development principles: Amplify Learning (with rapid try-it, test-it, fix-it feedback ...