This is probably one of the stranger questions that one could pose here, but I'm curious to know what others think.

Situation: VFP thick-client app, using roughly 100 VFP tables. A payment/deduction system. (2 primary modules that have a certain level of integration). Highly configurable by client. Altogether, about 35 forms (ranging from a big three-tab entry form to a bunch of modal 'option' forms). Good amount of business logic. Several complex queries to pull historical data. Requirement for multiple update triggers to ensure data integrity. Potential for over 100 users hitting it daily. (basically, your standard VFP app after about 2 years of every enhancement but the kitchen sink). Several reports using Crystal.

Goal: Web-based and SQL Server using .NET, must deliver to QA by end of September/early October, must be in production by around Jan 1, 2003.

Team:
Person 'A' - many years VFP/crystal background, intimately involved with all aspects of existing product, both technical (program code, databases) as well as business application, UI layer, etc.. Knowledgeable in SQL Server, has been working with .NET to get a 'head start'.

Person 'B' - equally knowledgeable of business application, intimately involved with database and business rules, somewhat less familiar with all the inner workings of the app

Person 'C' - Good VFP Coder, good knowledge of ASP and Java, intelligent, but far less experienced in the app. Very weak on UI, but pretty good with logic and relationships.

All people will need .NET training very soon. Person 'A' has somewhat of a headstart, but all three need training on architecture.

Objective: Person 'A' has been carrying far too much of the weight. Must distribute workload - a key company objective. However, current app is not well documented, and the business layer and database rules must be identified. Also, application must be delivered on time - it is make or break.

Problem: how to distribute the workload...by tier, or by function?

Here was my proposal. I'm seeking feedback to see if others view this as optimal (given the VERY short timeframe, and the need to get workload off of person 'A').

1) Person 'A' and Person 'B' document the business logic, stored procs, and update triggers required.

2) Person 'A' focuses on developing/coding the UI, and on the integration with Crystal.

3) Person 'C' develops the bulk of the middle tier using VFP 7, with assistance/mentoring from person 'A' and person 'B'

4) Person 'B' develops most of the stored procs and update triggers, with help from person 'A' (and maybe 'C', if he isn't totally overwhelmed).

This 'seems' to be the only way I know to utilize existing skills to break the work out. (By the way, I am person 'A', our database/back-end guy is person 'B', and an additional programmer is person 'C'). If the timeframe were far less aggressive, I'm sure it might give us more options.

Does this sound like (and I realize this is very high level) a good direction, or are there more optimal ways to slice this?

Thanks in advance to anyone who actually had the patience to read through this!!!

Kevin