Short video introduction to my sessions at Agile Eastern Europe 2010

In about 3 weeks I'll be flying to Kiev and meeting some of the best Agilists in the planet. But it won't be just fun and games for me. I'm already stressing about my sessions.

Check out the video introduction of my sessions at Agile Eastern Europe and, while you are at it why not book your flights and hotel and joining us there?

See you at Agile Eastern Europe in Kiev!

Introduction to my sessions at Agile Eastern Europe 2010 from Vasco Duarte on Vimeo.

Don't just plan, plan to be surprised!

Walking a tightrope without a net maybe good entertainment, but it's hardly what project teams enjoy the most. 

When the deadline comes and your team is late, you know why that is. No matter how well you plan (and you must) there will always be a volcano or a flood or simpler things like changing requirements or power-outages that will delay the project.

Delays are inevitable, we plan to get rid of the obvious ones, we do creative risk management to get rid of the less obvious ones, but ultimately it is impossible to avoid problems! It is smarter to be ready to deal with problems when they do happen.

This is why I liked this post by Dave Snowden about two seemingly contradictory strategies to deal with environmental disasters (or project problems, which ever applies to you). In the post he states:

They did recognise that some failures were inevitable, so they focused on speedy detection and fast recovery. In other words they adopted a strategy of resilience rather than one of robustness.  

There's no reason why you should use only one of these strategies in your projects, in fact they are complementary. Investing in planning is about implementing a "robust" strategy. Investing in adaptation mechanisms (like iterations, re-planning, demo with retrospectives, etc.) is about implementing a "resilient" strategy.

It is insane to think that a single-minded focus on "resilience" is a good idea, but so is a single-minded focus on "robustness"! Why do so many projects prefer either over the other? 

Photo credit: wollbinho @ flickr

Agile is easy! It's making it work with your business that is hard!

Last week I gave a talk at Turku Agile Day. The premise of the talk was simple: adoption Agile in R&D only is not enough. The goal was to create simple model to guide us through Agile adoption in a company (as opposed to a team).

I came up with a model that included 3 steps and 15 lessons learnt. How have your experiences been? Have you faced similar or different issues?

Check out the slides for the adoption steps and the lessons learned in the context of each step.

Check out the slideshare page for the notes on the slides that explain a bit more of the content for each of the slides.

Agile is easy! It's making it work with your business that is hard

View more presentations from Vasco Duarte.