 |
|
I WANT TO SUBMIT A CUSTOMER ENQUIRY REQUEST
|
|
|
 |
|
 |
|
Why Teams Not Departments
|
|
It is so simple and so obvious that you would think everyone was doing it. It's
like this. When you run a software house in departments, the model is not scalable.
What happens is that the more projects that go backwards and forwards from Development
to Testing and testing to development; from Testing to the technical writers and
back again. And then from QA back to development and so on, the more the blame culture
starts to grow. Nothing ever gets done. Nothing ever gets finished properly. And
it's always the next man's fault. Now, in teams, you put a project in, you get a
shrink-wrapped product out. All nicely tested and documented. If the work increases
then the numbers of teams increase commensurately. |
|
|
|
|
|
|
A skeleton team is a Team Leader, two developers, a tester and a documenter. It
never falls below this. But, if the project is big and multi-faceted, its easy to
increase the size of the team by adding more people. But its always this. One project
- One team!
More about ghost:
What is Ghost?
|
|
 |
|