aprile 2011 Blog Posts

Nowadays Agile Coach challenge (here, now, at present moment, in this organization unique contex)

The Agile Coach facilitate the dev team and management to reach the full potential of the organization in software development. Given the time, energy, passion and effort we put in our job, why not to do it alright ? Improvement requires change. Sooner or later an Agile Coach face obstacles and resistance to change, in his area of influence and outside that area. When the Agile Coach is sponsored by the management then he could face resistance to change from the dev team. And when the Agile Coach is sponsored by the dev team it could be the other way around. Ten...

posted @ venerdì 22 aprile 2011 14:35

Coaching Self-Organising Teams

This April in Helsinki I have attended the course Coaching Self-Organizing Teams by Joseph Pelrine. During the course I've been able to find the answers for many practical questions : what really is serf-organization and what is not ? what is the 'self' in a self-organising system, and for a team ? beyond mathematical and biological models (people are not ants: have intelligence, awareness, free will and purposes) what can explain social complex systems like teams...

posted @ lunedì 11 aprile 2011 23:20 | Feedback (0)

The redpill and the bluepill of sw development

The   bluepill   of software development: defined process outdated Gant charts procrastination of reality check The   redpill   of software development: empirical process inspect-adapt feedback/control loops continuous reality-checks Choose: http://en.wikipedia.org/wiki/Bluepill or http://en.wikipedia.org/wiki/Redpill Tags :  Team Work | Agile | Lean Agile | Leadership | Team | Progettazione Software | Traduci al ITALIANO >>>

posted @ sabato 2 aprile 2011 20:46 | Feedback (0)

Traditional/Modern Management

Some thoughts about differences I noticed between traditional management and modern software project management. In traditional management a manager can define and be responsible for the deadline and the scope of a project (i.e. fixed scope, fixed price, fixed deadline contracts). Often with the assumptions that : the customer knows all what he wants (before the project start) the developers know how to build it (before the requirements are known and understood and the used technology is proven and well known) nothing will change along the way, unforseen events will not...

posted @ sabato 2 aprile 2011 20:20 | Feedback (0)