På konferensen Agila Sverige 2009 gjorde jag ett blixttal på temat lättrörlighet och lärande, med titeln “Att lära sig tillsammans”. Konferensarrangörerna filmade alla tal, och mitt har nyligen blivit publicerat. Bäddar in det här nedan.
Here’s a video of a talk by Jeff Sutherland at Öredev 2008. Although I still find all his numbers suspect, because I don’t understand what he does to actually measure productivity of the teams he works with - I still like to listen to him speak. His ambition to push the envelope and find new ways to look at the things we work with is what manages to inspire me, not all his numbers.
Three short clips featuring systems thinker Russell Ackoff have been made available on YouTube, and embedded below. Ackoff speaks plainly about profound things, so listen closely, and don’t mistake his plain words for a lack of depth. I’m not an expert, just an interested student, but it seems to be that Ackoff’s great contribution is a clear and understandable explanation of how systems concepts can be applied in organizational thinking. Here are a few key points about the nature of systems, presented by Ackoff in these clips:
Every system is defined by its function in the larger system which contains it
An essential property of a system is that it cannot be divided into independent parts
A system’s properties derive out of the interaction of its parts, and not the actions of its parts taken separately
As an example, here are a few quick thoughts on how our thinking about software development teams needs might change if we look at them through the systems thinker’s eyes.
To understand why a given software development team performs the way it does, we need to examine the organization in which the team exists. We can’t find the answers by analyzing the team in isolation.
The true team most likely differs from the team as defined on the org chart. The team on the org chart probably contains non-essential parts: that is, parts that cannot be said to be a part of the system, because they can be removed without impacting the output of the system. Also, the true team most likely contains people that are found in a totally different place in the formal organization.
We can’t split an effective team in two halves and expect each part to have fifty percent of the efficiency of the whole team. A team’s effectiveness derive out the interaction of its members, not the actions of the team members taken separately.
UPDATE, JAN 11, 2009 Three short clips with Russell Ackoff have been posted to YouTube.
UPDATE, OCT 26, 2008: Kevin, who first pointed out to me that the video links in this post were broken, have managed to get in touch with Chicago-Kent. He received the direct links to the missing Ackoff lectures, and passed them on to me. Here they are:
UPDATE: Russell Ackoff’s talks on Girls Link seem to have been taken down. Readers Kevin and Lennart have asked me if there is a way to get hold of them again. I have not yet found such a way. I have, though, tried to get some more info on this via email, but without luck so far. If I find out more about this, I’ll post about it here. Check back here or/and post a comment if you want to know if I find a way to see them again.
Oh my, oh my! Is this sweet or what? A full set of videos with systems thinker Russell Ackoff. Russell Ackoff can argue like no other for the idea that we are in the middle of a paradigm shift, in which we are moving away from the old Newtonian, or mechanistic, way of looking at the world, towards something else - something based on the realization of the importance of synthetic thinking.
Ackoff explains how analytical thinking can help us understand how something works, but it cannot help us understand why that same thing works the way it does. To understand the why, we need to look outside of that which we are inspecting - we need to look at its context.
Author, consultant and speaker Mike Cohn has a two-part video out on YouTube. In it, he talks about his area of expertise - the planning and estimation of agile projects.
Mike will be visiting Sweden this fall, and do a couple of his popular courses, hosted by Citerus. Don’t miss out on this opportunity to learn about Mike’s accessible methods of planning agile projects - they will be an excellent addition to your toolbox.
Around 25 minutes into the interview, the topic of RUP appears. Tom points out the amount of knowledge available in the RUP, but also how it has often been implemented with a focus on the specific practices, rather than on the principles that lie behind the RUP: iterative, incremental software development.
This problem is not entirely unexpected, since people who need the guidance provided by the RUP manuals are probably not yet at a skill level where they can work from principles. When learning something new, we need rules and practices. Unfortunately, in projects and management, the same rules and practices will not work for everyone. A skilled practitioner knows this, and works from the principles he believes in to deduce practices that are useful in the current context. When people “implement” the RUP by copying practices without knowing why, problems are likely.
At around 36 minutes, Mary discusses the difficulty of applying lean and agile over company borders. This is an interesting question, but one that needs some care. Any project run over company borders is challenging. Lean and agile have the nasty and necessary habit of talking openly about uncertainties and risk, and recommending transparency. Obviously, this will put a strain on any relationship between parties who are used to contracting defensively with each other.
I'm a consultant. I help other people succeed with software development. In my work, I help teams and organizations be more effective and ship software. I base a lot of my work on Scrum and teach Certified Scrum Master classes.
Twitter: tofo
CSM-kurser
Jag håller regelbundet kursen Certifierad Scrum Master, i Citerus regi. Det är en tvådagars workshop där den som deltar får lära sig om Scrums bakgrund och historia, vad en Scrum Master gör, hur ett team blir effektivt, om teknisk skuld och klarkriterier och hur man planerar ett Scrum-baserat projekt. Hundratals personer har gått kursen, och så gott som alla ger den ett betyg mellan sju och nio på en niogradig skala, och rapporterar att man fått med sig värdefulla lärdomar man kan tillämpa direkt i sina egna projekt.