Archive for the 'people & systems' Category

How to destroy your corporation in 1024 easy steps

Friday, September 14th, 2007

My take on projects in ye average bigge organisation has been: the price of a project depends only on the position on the corporate ladder of the manager who starts the project. The lower the level of the manager, the cheaper the project.

Please note that delivered functionality or business value is not part of the ‘project cost’ equasion

I have often wondered about, and looked in amazement at these large projects that seem to go on forever. I believe that most projects can be done with less people in less time, and many projects are not worth doing at all.

Maybe someone at <insert large ‘consultancy’ company here> did actually invent a working perpetuum mobile…

Read what a (former) big shot in a large company writes on how this mechanism works in practice, and what it feels like to be on the receiving end. How to destroy your company by packages, outsourcing and ‘consulting’ companies (and not paying attention to your users and customers)….

“Outsourcing is a brilliant trick of the managers. The responsibility for the failing project is moved to an outside vendor. They are now the object of aggression.

The real customers don’t talk with the programmers. They talk with the managers that are talking to managers that are talking to managers. Somewhere in the chain of communication all the meaning is lost. The result is something they don’t want, the users don’t want and the customers don’t want. Last but not least the process took so long that the market has changed. They have to start all over again.

Do you now understand why we there is such a shortage in IT specialists? About 30% of IT-projects is succesful. This means that 70% of the IT-specialists are working for nothing.

My advice

Adapt what is working as long as possible.

A team of 15 people is capable of doing more than a team of 1000.

Do it yourself.

Hans describes a full circle process of what happens before a project is outsourced. I call it the “Shit” cycle I couldn’t resist making a drawing of it:

the shit cycle

I missed one phase in the process: the pre-project phase, which consists of a sales rep of <insert large ‘consultancy’ company here> taking the high-level manager to the golf course…

What I don’t know is, each time the project goes through the cycle again whether golfing is required (Hans writes about one project that cycled for ten years…).

eXtreme Customer Collaboration

Saturday, September 8th, 2007

Making someone responsible to be a product owner, might make a development team feel absolved for ‘customery’ things. For a long time my gut feeling has been that the whole team (product owner, developers etcetera) should place themselves in the customers’ shoes. Attending presentations on product ownership in the eXPerience reports track at Agile 2007 confirmed that feeling.

Getting everyone to ‘crawl in the skin of’ their users creates simple to use products that do what they must and no more. Sometimes with amazing, simply beautiful interfaces.

There were presentations by:

The BBC story was on using the time of product owners wisely, I hope to write about that in a separate post.Yahoo’s and Oxygen’s stories are both about strong product ownership, focus on essentials, and last but not least: crawling under the skin of users. In the case of yahoo those were college students, in the case of oxygen women who are planning something, e.g. a home (re-)decoration or a wedding.

Both stories reminded me of ‘The Knowledge Creating Company’ by takeuchi and nonaka (1995). There is a chapter on how Panasonic created the first bread-baking machine. The chief engineer on that project had tried to understand bread baking from reading a book, and failed. Then he went to take lessons with a master baker in an Osaka hotel. He then tried to explain the bread-making and -baking process to his colleagues, and failed. Eventually groups of engineers would do internships with the master baker to get a ‘gut feel’ for breadmaking – this eventually helped them to resolve the myriad of constraints on a breadmaking machine.

Looking through the agile2007 proceedings, the written version of oxygen’s experience report actually mentions the knowledge creating company, I did not see that in the presentation.

If you are interested in product development, and haven’t read the knowledge creating company yet, I strongly recommend you do so. It is not an easy read (quite thorough), but you’ll come back with a more thorough understanding of product development.

The book also has good tips on how to collect knowledge and share it from one project to the next (or at the same time) – collecting and condensing knowledge takes time and concentrated effort – this gives project managers something to do with the spare time they get once their teams start to self-organise… ;)

eXperience more Agile

Monday, August 20th, 2007

I’ve just (nog quite) returned from the agile2007 conference. I’ll be in the New York / Philadelphia area for another week – in case you’d like to meet up… I hope to write up some of the things that struck me at agile2007 soon-ish…

In the meantime I would like to announce the fourteenth edition of the eXperience Agile course – One of the few courses that goes in-depth in both Agile planning and test-driven development. It will be held from October 9 through 10, near Eindhoven, the Netherlands. Come join us for three days of fun learning and experiencing Agile Software Development :) .

Agile Open Proceedings

Tuesday, June 19th, 2007

The Agile Open 2007 Europe Book of Proceedings is out now!

img_3580.jpg

Monday planning session

It contains photos as well as results of individual sessions. We asked the session conveners to provide (handwritten) notes of each session. Raphael Pierquin scanned the session notes, and combined them with photos of flipcharts and people in the session to PDF documents.

img_3623.jpg

Diana, Stephan, Bernard Zero and Rachel have Fun with Agile 

We ran this as an expiriment to see if we could have an in-between form from open space by-the-book (handwritten proceedings copied to paper – is timely, but costs lots of paper and is not searchable ) and a wiki (does not need paper, is searchable, but participants often leave writing down the results for ‘later’ ).

The book of proceedings is not yet complete, published in the ‘release early, release often’ spirit. The PDF’s are attached to an an individual results page for the session – we hope participants will transcribe some of the  results, so we have both timely as well as searchable results.

img_3629.jpg

 Jan, Nynke, Robert and Erik enjoy the scenery

Guerilla Open Space @ XP 2007

Thursday, June 14th, 2007

At Agile Open, I have heard rumours that there is going to be a Guerilla Open Space @ XP 2007. Today I have heard a rumour that the Agile Alliance is going to sponsor it.

I heard good stories on the Open Space being run last year at XP 2006 in Finland – Many attendees, extra rooms needed etc…

This year, the conference organisers decided not to have an Open Space. Charlie Poole, who facilitated it last year, offered to organise it again this year. He heard nothing from the organisers for a long time. At the last moment they said they are not going to have an Open Space. Does the word ‘stonewalling’ sound familiar?

Question: Why would a conference organisation not support a part of the conference that was highly succesful last year??

So, if you are in Como for XP 2007 or otherwise (for the guerilla open space you probably will not have to register), I recommend you check out whether this Guerrilla Open Space rumour is actually true. Quality is guarenteed by the passion of the people who choose to be there ;) .

(Answer: the ‘acadamic paper’ programme at xp200* is weak and people spontaneously apply ‘the law of two feet’ – they go if they can learn or contribute more somewhere else).

Agile Open @ the IAF Benelux conference

Thursday, May 31st, 2007

I hope to write something substantial again, soonish :) . Meanwhile some announcements you might be interested in.

On June 15 Marc Evers and yours truly are hosting  Agile Open @ the International Association of Facilitators Benelux conference (In De Bovendonk, Hoeven, Noord-Brabant, Netherlands) . This year we are taking our eXPerience with open spaces on the road, and do open space related workshops inside other conferences. The one @ the IAF conference is more meta – a small experience of Open Space followed by reflective practitioners :) And then some more practice in the Open Space that afternoon, facilitated by Nynke Fokma an participants in the morning workshop.

I have heard registration for the IAF conference is going well (around a hundred registrants), and there are still some places available. The event is partially in Dutch, but I’m sure the Open Space will adapt to the right people :) .  And the Appreciative Inquiry workshop by Andrew Ballance (parrallel with Agile Open @ IAF) will be in English for sure.  Hope to see you there!

next eXperience Agile Training June 27-29, Eindhoven, NL

Friday, May 25th, 2007

I’m glad to announce the thirteenth instance of the highly succesful eXperience Agile course, thee days of fun learning and experiencing Agile Software Development. The course goes in-depth in both Agile planning and technical practices.

This course will take place on June 27 to 29 in Eindhoven, the Netherlands, and will most likely be taught in English. We still have a few open places. See the course page if you wish to read a full description.

Small Change

Monday, May 7th, 2007

I prefer small change over big change. I’m talking about transformations, of course :) . Small transformations make it easy to check if what we want to happen actually happens, and how far of we are. If you’re reading this blog there is a fair chance you are familiar with growing software in small steps – I apply the same principles when working on myself or helping others to improve their (development) performance.

(more…)

Agile Open Europe, Summer 2007 Edition

Thursday, May 3rd, 2007

smiling faceAgile Open Europe, the Summer 2007 edition is coming up soon (June 11 and 12, Hilversum, the Netherlands). So far we have eleven registrants from five different countries: France, Poland, United States, Great Britain and, last but not least, The Netherlands – host country :) . That means that we have about nineteen places left. They are going moderately fast. If you are thinking about joining us, please register soon-ish, so we can keep all the rooms we booked.

More about the location

Diana Larsen asked us whether the location was easy to reach from Schiphol/Amsterdam Airport.

We chose Hilversum specifically, because it is not far from Schiphol Airport (www.schiphol.nl) (the main airport, near Amsterdam), hoping to attract people from the US who would be ‘around’ in that time of year anyway… :)

There is a direct train connection from Schiphol to Hilversum (takes bout 40 minutes, connection about every 15 minutes), and then it is about 10 minutes by Taxi to the conference location. ( train connections are at http://www.ns.nl/ – the ‘english’ switch is on top right of the page). Train stations are called ‘schiphol’ and ‘hilversum’.

I mentioned a Taxi ride, since the location is surrounded by heath with patches of forest, and walking from the bus stop down the entry lane would take you about ten, fifteen minutes maybe…

agile open logo

If we fill up, it will be a very nice location indeed – the conference location is on fairly large grounds, with only a few buildings on it, one will be dedicated to Agile Open. We hope to see you there :)

The shortest open space how-to that could possibly work

Wednesday, February 28th, 2007

A friend of a friend asked me: How do I prepare for my first open space event?.

surprised to prepared be...

Here is my zeroth draft answer to her:

Short answer: Decide what the theme for your meeting is, book a room and invite participants. Then create a context that gets everyone into creative flow, and at the start of the meeting explain the mechanics of open space. This way, your meeting is very likely to generate useful results for everyone and … be a lot of fun.

Open space is the simplest meeting format that could possibly work.

It is based on (un)common sense of what people do naturally in productive meetings.

Long answer:

A clear theme is important, as are the principles. For me the principles are the most important, I’ll explain the open space conference format ‘by the book’ after the principles. If you understand the principles and have some experience running open space, you can adapt the format to fit more situations.

Principles (from Wikipedia on Open_Space_Technology):

While the mechanics of Open Space provide a simple means to self-organize, it is the underlying principles that make it effective both for meetings and as a guidepost for individual and collectiveeffectiveness.

The Law of Two Feet — a foot of passion and a foot of responsibility — expresses the core idea of taking responsibility for what you love. In practical terms, the law says that if you’re neither contributing nor getting value where you are, use your two feet (or available form of mobility) and go somewhere where you can. It is also a reminder to stand up for your passion.

From the law flow four principles:

  • Whoever comes is the right people
  • Whatever happens is the only thing that could have
  • Whenever it starts is the right time
  • When it’s over, it’s over

And finally, the open space rallying cry:

prepare to be surprised

Mechanics:
Since the meeting is supposed to be self-organising, the conveners put their energy _not in running the meeting_ but creating a setting that gets everyone’s creative energy flowing.

Stages:
before-meeting preparation, on-site preparation, Opening, marketplace of ideas, break-out sessions, closing, (optional action planning session).

Before-meeting preparation:
Decide on the theme. Possibly appoint someone to be a sponsor (the person that introduces the theme of the meeting) and facilitator(s) – the people who create the context before and guide participants during the meeting. Book a suitable venue, decide on size etc. (room/rooms). Invite people. You may or may not have formal registration, sometimes having people sign up on a wiki can be enough.

Preparation on the (first) day:

Put chairs in a circle for the start of the meeting. If you have more than seven participants, make a big circle for the start and create circles of chairs elsewhere for the break-out spaces.
Break-out-spaces are where the bulk of the meeting, after the theme setting and creation of the agenda takes place.

 

Have bold markers and pieces of paper ready. Prepare a wall where people can post their issues for break-out-sessions. Divide the wall into a matrix of timeslots and break-out spaces.

 

If possible, have food and drinks on-site, so that people don’t have to wait or go elsewhere for that. This helps the attendees gel more. Also, try to have a space for your group only.

Opening:

  1. Show the timeline, how the event breaks down into Opening, Marketplace of ideas, break-out-session, closing.
  2. Sponsor introduces the theme. Briefly. One or two minutes max. Long openings drain the energy of the meeting quickly. Get participants to work ASAP.
  3. Facilitators introduce the principles and the format. Explain how the marketplace of ideas works.

Marketplace of ideas:

  1. Participants write ‘issues’ on pieces of paper. Preferably with bold markers, so they are easy to read from a distance.
  2. Participants choose a timeslot for their topic on the agenda wall.
  3. One by one, participants explain their issue to the others, with the aim of drawing the right people to their break-out-session.

Break-out sessions:
Once people do not come up with new issues (wait a little bit, and ask ‘are we done?’. I find the silence that often happens at the beginning and end of the marketplace the scariest. However, this silence seems to be very productive.
You may ask people to put their name on sessions they want to attend. More than one session per slot is OK… (law of two feet :) ). This gives conveners an idea of how busy their session is going to be. It gives participants an image of how the break-out session is going.

People may shuffle sessions around, or merge sessions as they are deciding where to go.
Have a wiki where people can record outcomes of sessions, or provide paper forms for note-taking during sessions (recording who attended, a summary of the session and outcomes/questions for further work) that you
can collect into a ‘book of proceedings’.

The facilitators’ role in this bit of the conference is to answer questions, and make sure everyone has the materials they need to run their break-out session. They do not (in principle) intervene in the sessions – the participants are supposed to self-organize.

Closing:
Have everyone back in the circle. A simple and effective way to close is to have the participants pass a ‘talking stick’ around, and let them (briefly, e.g. in a sentence or a word) say what they feel about the day.

Optional: action planning.
Have a bit where people can convene around flipcharts to plan actions for things that came out of the break-out sessions. This uses a mini-marketplace (since there is just one timeslot). I’m not entirely convinced this works wel, although I’ve seen it work well recently at Agile Open Northwest. Maybe more on this later.

More…

The book Open Space Technology by Harrison Owen uses more text to explain open space. I’ve left some things out, to make this howto short – some people may feel that this is stripped beyond the bare necessities… :) Oh well, I believe this is enough to get started. I may pontificate on subtleties and my experiences later… Or I may find a way to make the how-to even shorter.

surprised, prepare to be...

Is this helpful?