Member Login

Lost your password?

Registration is closed

Sorry, you are not allowed to register by yourself on this site!


Posts Tagged ‘feedback’

Do you really know what’s happening around you?

Thursday, March 22nd, 2012

The interesting thing about reality is that we don’t notice it until after it has happened, if we notice it at all. At a fundamental level we are experiencing the world as a flow of environmental data; things happen and register with our nervous system through our senses. And, we notice.

Or do we?

The interesting thing about reality is that we don’t notice it until after it has happened. Each sense is processing a constant stream of stimulus, whether we notice it or not. And, it’s all competing to be noticed by our consciousness. Most of it simply passes us by, as if it didn’t happen, but a small amount of it bubbles through our thoughts and awarenesses to cause us to direct our attention. By the time we do, the original event registered by our senses has gone, and been replaced by whatever is happening now.

The interesting thing about reality is that we sometimes don’t notice it at all. A sensation bubbles through our nervous system and we become conscious of it, and then we notice what it means; a sound becomes a plane passing overhead, and we no longer notice the sound just the plane; the sensation in our stomach becomes our hunger, and we only notice the hunger not the muscular tension. The colour, texture and sound in front of me becomes you, and I no longer notice the individual sense data that makes you up, I just notice something that I call you. I stop paying attention to what is going on, and instead pay attention to the abstraction of it, and in that moment I can cease to notice when you do something subtly different from what I expected you to do.

We mostly don’t notice what’s going on in the world, instead we notice what we notice about what’s going on, and then act as if that is what is going on. We replace reality with our model of reality, and reality as it is actually happening fades into the background. Once something has a meaning, that meaning replaces the something, and the raw something ceases to exist.

This has a profound impact on the way that we respond to each other in environments where feedback defines how we work and what are are doing.  Are we responding to what is actually happening, or what we think is happening? How does someone respond to our response, do they respond to what we are doing, or what they think that we are doing?

How often do you notice that the person talking to you was actually talking about something other than what you thought they were? If the answer is rarely, then I suggest you stop and actually pay attention to what’s really going on around you. Do you notice reality as it actually is, or could be that you’ve been paying attention to your imagination instead?

(Image: Idea go / FreeDigitalPhotos.net)

Can you write software by planning everything up front?

Tuesday, March 13th, 2012

Image: nuttakit / FreeDigitalPhotos.net

Traditionally software was designed as a large up-front planning task, using techniques such as the water fall model of software development. In these approaches the entire system was analysed and the software and hardware components architected up front, culminating in a complete design that just needed to be acted on by programmers to delivery the entire working system.

This is actually the way that most projects are planned in the non-software world, for example, when a building is constructed the plans are approved up front, the materials are calculated and plan for the construction is produced. Then it is just a matter of following the plan, with the right individuals for the job, with the right materials, in the right order, and the building gets built.

Of course, inevitably problems that occur in the delivery phase; something wasn’t thought through properly, some materials don’t perform as planned, the environment doesn’t behave as expected, the external dependencies don’t come in on time. This means that even when all the planning has been done in advance, even to a high quality, there is still a large uncertainty around delivery dates, and overall cost of the project. It is rare that a project can be delivered without some form of re-evaluation of the design axioms emerging from knowledge encountered during delivery.

Things get interesting when you begin to really take on board that however much you believe it can all be planned in advance, the reality is that you moment you make any changes to the system, new information emerges that wasn’t present when the original plan was made.

I challenge you to recall any circumstance in which you planned everything first, and then implemented the entire project without making any changes to that plan on the way. I bet you can’t!

Beginning to think about feedback in agile software development

Thursday, February 23rd, 2012
Image: Stuart Miles / FreeDigitalPhotos.net

Image: Stuart Miles / FreeDigitalPhotos.net

I thought that as an exercise it would be interesting to explore in a series of small blog entries the nature of feedback in dynamical systems, and the implications that that has for an agile delivery methodology. So, stay tuned if you’re interested, as that’s what I’ll attempt to do over the next few days and weeks. Feel free to chime in, so I’m not just talking to myself :).