Approaches of Project Allocation

Hi,

Every IT project has set of requirements. Every IT project has set of people to deliver those requirements. Now, typically, when a lead starts with the project, he/she has 2 basic options to assign the work.

1. Use Case approach -- Create use cases from functional requirements. Assign use cases to developers. Agile developers may call it Story approach as well.
...a) This approach will work well if you are sure that developers are good in translating the functional requirements to technical requirements, technical requirements to code with modularity, reusability, scalability, maintainability etc..
...b) This approach will also work if the project is small scale project.
...c) Use this if you wish your developers to grow as functional/domain consultants.

2. Layered approach -- Design detailed architecture layers. Split the project into layers - presentation, business, data..add more if you wish to make it more complex like service, common etc.
...a) Most commonly used in large scale projects.
...b) Can be very effective when you have developers having expertise in different layers like data, business and presentation. Well, not all people are good in writing stored procedures.
...c) Use this if you wish to train people in different layers / technology sets. May be, I wish to grow some people as DBAs.

~ Navjot Singh Sohanpal