Showing posts with label scrum. Show all posts
Showing posts with label scrum. Show all posts

Tuesday, July 26, 2011

Impact of visualization on the self-organizing system

In self-organization systems/teams, visualization plays an important role. Consider next graphic expressing the definition of project structure.
 
In the project organization structure two extremes can be observed: chaos or command and control.
Chaos in project can be seen, e.g. if team structure is not clear, every co-worker is (maybe) working on topics he founds important. This leads to local optimizations on different levels. The probability to succeed in this structure is very low as can be often seen already by first integration of outputs.

The other extreme is the “Command and control” approach were single person – typically technically very strong – is driving every single change personally. He gives orders and on regular manner checks the progress, takes countermeasures if necessary, etc.

Within scrum – what we want to achieve – is such level of self-organization, that pros from both extremes are in place and if possible cons are eliminated. Visualization can help establish so-called center of gravity – a motivation point – attracting people and driving them as a team towards common goal. It is the common goal that drives self-organizing group to the right direction and help them consistently work to achieve results.
As only very small portion of  available information can be physically visualized, people are very instinctively attracted.
Similar effect can be caused or is supported by good vision.

On the other side it could be also dangerous tool. As only small portion of knowledge is visualized, it is important to show correct part of it. However, I believe in healthy and critic environment - folks discovers “side ambitions” very quickly and pushes company towards open and transparent culture.

Friday, May 27, 2011

Role of visualization in SW development


Development department can be seen as a system with certain inputs and outputs. As input we could consider market needs, or product specification, depends on abstraction level to be considered. The output is then either profit or product with certain attributes.

Nowadays, nobody would question that this system is very complex, processes running inside it are stochastic and exact description is impossible to achieve.
Independently on the system complexity, control theory points to a feedback as to the central role in order to achieve good and fast results. The output of process step is sampled and summed with required value. It is then put back to the system so behavior can be adapted to reach required value – in our case faster.



In product and especially in software development process the output is often information – market needs, requirement specification, test specification, architecture, and SW modules.

Such output is not visible per default and if visible, then only to small number of people – actuators cannot access it in a non limited way. Same is valid for intermediate information created within the process. This fact causes that feedback signal is either not in place at all, is very low or noisy.

From this point of view any attempt to visualize information has dramatic positive impact on the system – development process.And not to forget: missing feedback loop - lost opportunities for learning.

Wednesday, November 17, 2010

Decide only if you bear consequences

Yes, it could be that I am too young for giving organizational hints, but this rule I have to say anyway:
I am sure that there are good exceptions - nevertheless generally everybody going to make a decision in the organization should follow this rule:

Decide only if you bear the consequences

Meaning that if you are deciding on something, but you are not directly influenced by this decision, don't do it. You see probably a problem, so search for people that would be most affected by this decision, and ask them to make it. It can be that these people are too focused and concentrated on solving their daily business - thus they may not see the problem. Or it may be that situation what you consider as a problem is not a problem at all. At least not for people involved.
Following this rule we would avoid poor decision, e.g. from project management, CM responsible, architects, testers, etc...

Once I got a question how have I setup teams and what needs to be taken into account by putting teams together when trying to reorganize teams towards scrum. Answer is simple: ask people, let them organize themselves. Thus, this concept of taking decisions supports in nice way so heavily discussed self-organization of scrum projects.

Wednesday, October 27, 2010

Source of resistance

Last week we discussed interesting topic in the team: how long does it take to start live the real scrum. At least inside the team.
The result of discussion was few interesting points, perhaps you have similar experience from your company:

* Bonus system: The whole bonus system is strongly oriented to individuals. Personal success is promoted by money - team success is promoted by email. This way team members will not per default try to reach common success, but they want to be better than others in the team.

* Lost of power: With introduction of scrum, the transparency is so significantly improved. Thus, sooner or later teams will be empowered and able to decide how to fulfill product owner's wishes. This brings the change from serious position in society to situation similar to playground: "let's play some roles at work". Some people can cope with it some not.

* Company training aka propaganda: There are plenty of different communication ways. Starting by emails from CEO, corporate magazines, all stuff meetings or standard process training - if the environment follows old practices, your scrum team will face pressure every day from different corner.


* Experience from the past: Every team willing to change basic principles and values of the development is surrounded with people already having great experience. Starting by HR, boss, other teams, experiences architects, etc. And this is another strong source of resistance where young team has to bear a test. Every person leveling himself as experienced is willing to give advice. If principles and values are different such advice will never go same direction as team transforming its work art.

* Domain specifics: In come cases it is even the domain what is used as argument in order not to change status quo. However, this is nothing else as point discussed before - however presented in a different way.

* Risk: Big companies certainly have strong controlled and structured environment (exception proves the rule: there are always crucial and structurally bad handled areas in big companies => that's why small companies still have a chance on the market).
To trigger change typically means to convince first of all the team itself, and then step-by-step get either GO or approval or at least inform all the other stakeholders. This of course costs a lot of energy and cannot be done within few hours. So as a consequence certain step needs to be taken even before you get GO from all stakeholders. Your boss perhaps does not know that you are going to organize HOW planning meeting. Will you take the risk?