>I'd like to share some experience with people working in a big VFP team like us. Is there someone that can share some experience with me?

I never understood a big VFP team. One guy to design and develop. One DBA - if needed and one Network guy - if needed.

Everybody else should be a salesman!

A software company would be better served to hire one developer with full cycle project deliveries on his CV. Use the rest of the money for a sales/support staff. After all - software development is not about spending money - it's about making money.

Teams slow stuff down - low skills - and weak communication - if the shop is selling hours - then, for sure, it has more to potentially bill. That's a shameful scam - but it's done all the time. You can pay a good developer 100K or 200K for a super project - or you can pay 20 developers 2 Million dollars for a confusing, demanding and sloppy project.

VFP does not need teams. But Microsoft needs teams in it's consumer base. Otherwise, the Redmond Shrimp Vendors would be out of work. The boss's insecutities about the team assures his team will be burping Redmond Shrimp and that he will be buying new product releases to test for MicroSoft - ad infinitum (ad nausium?)

It's a scam - an experienced developer and blow away a team of a 1000 inexperienced developers.

All a Team really does is make the Team Leaders feel important and make the boss feel insecure.

The game then is to argue that problems are not due to a lack of skills or experience of the team - but that they are due to not enough people on the team or because the team has not persuaded the boss to buy whatever logo MS put on the napkins the last Redmond Shrimp were wrapped in!

It only takes one guy (or girl) to write any VFP app. The issue is understanding the requirement, design skills and having enough experience to develop and work towards a delivery schedule.

Here's the false logic to team development. A team of 20 developers with one year of experience each does not equal ONE developer with 10 years of experience. Even ONE developer with 2 years of experience.

Teams attempt to do the impossible - that numbers will somehow trump skills.

Teams are about selling the latest MS "whatever", MS Seminars, trips to listen to the latest "guru" or buy his books and assuring the boss (the owner of the company that pays for those trips to the shrimp buffet) remains insecure.

Teams have nothing to do with project develpment and everything to do with MS Marketing Strategies and hiding project failures behind team size or false MS tool issues.

There - I said it!:-)

>
>Regards,