I hope this helps:
A very very brief team layout for small centralized development projects:
- The Application development manager gets a request , individual service
requests (ISR), from
a user division signed by the division director. The Application
development manager
assigns the project to a responsible analyst.
- The responsible analyst determines the users requirements, does a cost
/benefit and estimates
resource cost and requirements. Reviews the finding with the
Application development manager and
end user. If OK with all, the project is given a priority. If not
OK it is killed.
- If OK the responsible analyst is the owner of the new system and is
responsible for team
management and security in the TEST environment. The responsible
analyst goes to the following
people for resources:
- DBA for database resources.
This includes the all important "owner/user" Oracle id.
This id owns all database object for that specific
application and is the
responsibility of the responsible analyst . --- etc.
- System administrator and network manager for tool access
and os logons.
- Programmers to build the system.
- The programmers and the responsible analyst get together almost
daily to go through
problem review, testing ,comparing notes and read Delbert.
- Once the system is built and TESTED the system is move to production
by
a "gate keeper" such as the system administrator. The DBA sets up
production
environment and a user review is done.
- If application system OK user signs off and on to the next project.
I believe no matter if you have a small shop of 2 or a large shop of 200,
at minimum, the
tasks I described above must be performed in some form or another.
The above is very brief and does not cover large projects or application
system maintenance.
If you give a damn about building good systems or making money you will
hire good people, treat them with respect, pay them well, train them and
work them hard.
Received on Tue Sep 09 1997 - 00:00:00 CDT
