Always consider realistic expectations (or realistic goals if you prefer) and also consider an improvement of the team performance.
How much can we improve?
You could consider that the team will deliver 10% of improvement per year or per month. 10% per year sounds reasonable, given that China has been growing at 10% per year for the past 10 years. 10% per month sounds like too much. But I've found that in practice that is not the case: you can't improve by 10% per year nor per month because performance doesn't improve cuadraticly but linearly.
I usually divide the teams in layers, one layer for the presentation, one for the business rules and another for persistence. Also there may be other teams for workflow or for whatever communication with other system is needed. This means that initially the team produces zero use cases per week, irrespective of their size, because of the communication problems. Some developer requests something to another developer, but they don't understand what it is. Even when they do understand each other, there are so many unkowns, that they simply fail to deliver a working system.
But eventually they learn and they deliver something usable.
Then each month the speed of the team is increased by 5 use cases per week.
Month Speed per week Done this month Total
Month 0 0 0 0
Month 1 5 20 20
Month 2 10 40 60
Month 3 15 60 120
Month 4 20 80 200
Month 5 25 100 300
Incredibly, our team is able to produce more and more per week, increasing the speed effortlessly each week. But the project is finished at 300 use cases (actually there was some duplication and some returned use cases, so finally only 250 use cases were in the system).
If we allowed other projects to enter our production system we could continue to produce more:
Month Speed per week Done this month Total
Month 6 30 120 420
Month 7 35 140 560
Month 8 40 160 720
Month 9 45 180 900
Month 10 50 200 1100
Month 11 55 220 1320
So in a year we could have finished 3 projects instead of just finishing one in 6 months.
Clear roadmap
Any project is doomed if it doesn't have a clear roadmap. A clear roadmap is a clear understanding of:
1. What has been done.
2. What needs to be done.
All the rest can be considered irrelevant "detail". It does not matter if you have the smarter developers working 25 hours per days, 8 days per week. It doesn't matter if they write clear code that anyone can read and modify, and it doesn't matter if they write a million use cases per day. If you don't know what has been already achieved and what has not been achieved, your project is doomed.
Even more important than that is that the whole team knows where the project stands. So ANYONE on the project can login into an staging machine at any time and test the system. this means the project is a 100% repro. You can repro any functionality and any bug.
Clear specs
Ok, let us suppose you already have all that. You really have a road map. You can repro everything on the staging machine. And you have unit tests and functional tests for every feature. And you do iterations and you demo the features at the end of every iteration, and you do pair programming, collective code ownership, etc.
But you don't have clear specs. So whenever you do the demo at the end of any iteration, you fail, because it is not what the user wanted.
Having clear specs is very important, the problem is that it doesn't matter how many times I tell you so, it doesn't matter that you remember it everyday, if you deliver software systems, by definition you know nothing about the business and everything about the past software project, and your users know nothing about writing documents for software developers and the project sucks.
So in the end, prototyping the user interface is the best way to deliver software that works.
We usually call it "user interface mockup" to distinguish this prototypes from the real prototypes, the kind of prototypes we use to figure out if we can deliver the functionality because it is technically feasible.
No hay comentarios:
Publicar un comentario