Two folks asked me to write a bit more about the afternoon sessions, especially about the estimation one and here I go, I will resume what we talk in that session.
The format of the session was open, there were more that 20 people and each talk about the way he uses to estimate.
In may opinion the natural process is to first estimate the size, then the effort, and finally considering a certain team you can deduce duration and cost, but not everybody uses this process (or unless not explicitly), some stated to estimate duration at once.
In few words, the following methods were mentioned:
- Parametric methods (or magic formula-based methods that is the way I like to call them), basically this methods propose to analize your requirements and count points to determinate the size. Then you use that points in a formula that adds some variables to adjust the estimation based on particular information of the project (programming language, experience in similar projects, etc). In this category are Cocomo methods.
- Expert opinion and manager manipulation methods (this original name is mine): maybe this is one of the most commonly used methods. Several people in the session told to used it and I know that some colleagues in my company use it all the time. It is very simple, a manager (boss, project leader, project manager or whatever you call it) ask an expert (some time not so expert) to estimate certain items. Then the manager adds some buffer and that’s it. Not very formal, not very precise but fast and easy.
- Several-experts-based methods: I know this is a very ambiguous name, but that is the idea, I want to use this name to refer several different methods that include Delphi methods and planning poker (I think that planning poker is a Delphi variant). In these methods you have a team of experts (when I say experts I am just referring to people that is capable of give a realistic estimation because of his experience). Something very interesting of these methods is that under certain conditions these methods get a probabilistic support: if there are 4 or more experts and each expert opinion is independent, then we can apply the central limit theorem and get an confidence interval.
In my case I always try to use methods in the third group, in particular to estimate the complete product backlog at the start of a project I prefer to use Wideband delphi and then when estimating tasks at the begining of an iteration I prefer planning poker. During the session I mention a spreadsheet I use for Wideband-Delphi and after the session some people asked me to share the spreadsheet, so I published it here.
When I started writing this post I get the idea of preparing an estimation workshop, I think it could be an interesting activity, well I will analyze it.
That ‘s all, see you.
Well, finally I get some time to write about it. The meeting took place at the Unicen building in the center of the city.
We started about 8 in the morning setting up the place. During the morning we had only one session:”Scrum bird game”, 4 product owners (jgabadini, dfondevila, mbelnicoff and me), and about 60 participants divided into 8 teams. I took us about 2 hours. Some retrospective items after the game:
- Several teams try to build the birds assuming things about the requirements without asking the product owners
- After the chaos of first iteration most teams improved their organization and that allow them to improved their performance.
- It was not a good experience to have one product owner for two teams at the same time. The product should be always available.
- The products should be full tested by the product owner, I let the team to test the flexibility of the bird :(.
After the lunch break there were three slots of 4 sessions each. I took part of the following:
- How to work less: the idea was to debate about how collaboration with the customers can make us work less as a result of delegating some task on the customers/users. I gave the example of UAT written and executed by the user.
- Estimation methods: it was an open session were each talk about the way that use to estimate.
- Tools for agile development: after talking about different tools, we agreed that in every project is necessary to have certain tools: a source code repository (svn, cvs, whatever), a tracking tool to manage issues, risks defects, etc, and a wiki to use as a knowledge base.
I am very satisfied with the results and I hope to see some folks from Tandil next month in the La Plata.
That is all, see you.
We have just finished the retrospective and these are the main items we got:
- Organize some agile activities in Bahia Blanca
- Organize monthly meetings in for the agile community in Tandil
- Organize some workshops about agile implementation
- Document a real case on agile implementation by the Tandil ‘s community
- Promote integration activities between the different agile communities in Argentina.
I am here at Tandil having lunch in the middle of the journey. During the morning we played ” the scrum bird game”. It was a really interesting experience; we built eight teams (about 8 people each). Well I will continue later because the afternoon sessions are starting right now.
Well, I must say that I am pretty happy with it. I think this RC is much more stable than the Vista RC that I tried some years ago.
I have installed and run successfully some more software: Visual Studio 2008, Smart SVN, OneNote, Foxit Reader and Ant.
At the same time I have some minor issues to report:
- In some cases when using winamp, my screen starts flicking when winamp has the focus.
- Occasionally when I typing the cursor literally jumps to another position.
During next week I will try some more programs like Skype, Autocad and Paint.Net
Last Thursday I offer a class at university titled “Code Design”. Maybe the name was not the best, the idea of the class was to review and discuss good coding practices. The slide deck of the class is available for download here.
The next stop in the Agile Open Tour is Tandil, on May 16. Yesterday I wrote my position paper to complete my inscription and now I invite you to write yours. Here is the registration page: http://www.agiles.org/agile-open-tandil-2009.
See you in Tandil!