Discussion Locked

IT dept internals

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We need help in finding good resources on following.

We are an IT dept in a mid-size bank. Besides production site we feel need in R&D site(s) and maybe labs with different usage regulations.
Links to best practices and samples are needed.

What are the typical IT roles (CIO, architect, software developer, project manager etc) and their functions, requirements to the employees skills and preferred personality (pedantry, exactness, erudition etc) for the roles ?

Thank you in advance

16 replies

by manish_mohnot

I am not sure, whether I understood your question. I work with a large size credit card bank as a IT head of two business units. My 10 yrs of IT experience is with two of the largest Banks in world.

If you could explain your question in more detail, probably I could be helpful to you in the Banking environment.

by manish_mohnot

I am not sure, whether I understood your question. I work with a large size credit card bank as a IT head of two business units. My 10 yrs of IT experience is with two of the largest Banks in world.

If you could explain your question in more detail, probably I could be helpful to you in the Banking IT environment.

by moller

I am not sure what kind of help you're looking for.
As I read your question it is only a matter of titeles, not a matter of how the organisation i build.
My advise to you would be: draw up an organization where a person ONLY have 10 to 20 people direct below her/him.
When that is done, start at the top with the CIO, and go further down.
What titles - or roles - is best at your place? I can't say

by paul.jeanjr

I run a financial systems Application
Development shop. The following units are
identified:

1. Production Support - Maintenance
Team leader and programmers respond to
requests to fix damaged components.

2. User Acceptance Testing - Business staff
to test the system according to specifications.

3. Systems Testing - Team leader and testers
apply manual or automated testing scripts to
modules and conduct testing activities on new
changed or corrected code.

4. Development Team -Team leader, senior
analyst/technical code coach/reviewer,
programmers. Programmers do not test their
own code except for unit testing.

5. Business Analysts, System Architect,
Project manager, Project office, DBAs,
Infrastructure (hardware) technicians,
performance DBA's to optimize code and
environments, technical writer. R & D is
done here along with high level planning

6. Business staff to define requirements,
functionality, request changes, enhancements,
report bugs.

Do you need a CIO, CTO, both? Depends on
budget, management philosophy, corporate
culture and buy-in. Does the CIO/CIO sit on
the management board as an equal, reporting
to the CEO, or is it a subordinate position
reporting to the CFO?

Are you recruiting or building from internal
resources? Do you plan to outsource some or
most functions? To answer your last
paragraph would involve an analysis of your
environment to determine skillsets,
personality fits, environments, pay and
benefitpackages/plans, training and
retention strategies. Your HR group may have
some information, head-hunting firms may have
some examples and you can hire someone to
write job descriptions used to recruit,
assess and select candidates. Drop me a note
if you want to discuss further.

Paul Jean Jr.
Director, Application Development

by shanghai sam

I agree very much with Paul Jean Jr. It starts with a sense of the organizational structure needed to accomplish your goals. In starting departments, the hardest part is looking around and determining what roles you want to accept in your dept. or would be allowed to accept. Remember your dept interface with itself most of the time, but the rest of the company when things have gone very well or vey wrong.

As you already state, you have grown to have a production environment run one way, while you develop fully capable test and staging aeas, development servers, and a possible R&D function.

I praise you for taking personalities into account when managing an IT group. Ver few other managers may face the type of diersity of personalities and culltures you probably face.

Some developersfor example, really just want to be told what to code, given clear requiremets, and a due date. Then left alone. They have no interest in office politics, social events, or the applications they are even developing. Like each group, you'll develop a different managerial expectation and approach suitable for tem.

There is often another group not content to be robots of coding efficiency. They want to be on the cutting edge of code, languages, and equipment hitting the tech world daily. They can be very enthusiastic but often feel trapped by org restraints. Balancing this with the constraints of the business' current business priorities and prior architecture decisions. You don't want to discourage this group. They'll bring you new ideas, care about the business or at least view the business as a way of funding the acquisition of better toys.

Another group is the don't blame me crowd. Frankly, get rid of them. We ALL make mistakes. Anyone who spends so much time covering their ass as they do working their ass belongs elsewhere. That could be a function of an individual's fear to fail or obssesiveness to cl

by shanghai sam

I agree very much with Paul Jean Jr. It starts with a sense of the organizational structure needed to accomplish your goals. In starting departments, the hardest part is looking around and determining what roles you want to accept in your dept. or would be allowed to accept. Remember your dept interface with itself most of the time, but the rest of the company when things have gone very well or vey wrong.

As you already state, you have grown to have a production environment run one way, while you develop fully capable test and staging aeas, development servers, and a possible R&D function.

I praise you for taking personalities into account when managing an IT group. Ver few other managers may face the type of diersity of personalities and culltures you probably face.

Some developersfor example, really just want to be told what to code, given clear requiremets, and a due date. Then left alone. They have no interest in office politics, social events, or the applications they are even developing. Like each group, you'll develop a different managerial expectation and approach suitable for tem.

There is often another group not content to be robots of coding efficiency. They want to be on the cutting edge of code, languages, and equipment hitting the tech world daily. They can be very enthusiastic but often feel trapped by org restraints. Balancing this with the constraints of the business' current business priorities and prior architecture decisions. You don't want to discourage this group. They'll bring you new ideas, care about the business or at least view the business as a way of funding the acquisition of better toys.

Another group is the don't blame me crowd. Frankly, get rid of them. We ALL make mistakes. Anyone who spends so much time covering their ass as they do working their ass belongs elsewhere. That could be a function of an individual's fear to fail or obssesiveness to cl

by shanghai sam

I agree very much with Paul Jean Jr. It starts with a sense of the organizational structure needed to accomplish your goals. In starting departments, the hardest part is looking around and determining what roles you want to accept in your dept. or would be allowed to accept. Remember your dept interface with itself most of the time, but the rest of the company when things have gone very well or vey wrong.

As you already state, you have grown to have a production environment run one way, while you develop fully capable test and staging aeas, development servers, and a possible R&D function.

I praise you for taking personalities into account when managing an IT group. Ver few other managers may face the type of diersity of personalities and culltures you probably face.

Some developersfor example, really just want to be told what to code, given clear requiremets, and a due date. Then left alone. They have no interest in office politics, social events, or the applications they are even developing. Like each group, you'll develop a different managerial expectation and approach suitable for tem.

There is often another group not content to be robots of coding efficiency. They want to be on the cutting edge of code, languages, and equipment hitting the tech world daily. They can be very enthusiastic but often feel trapped by org restraints. Balancing this with the constraints of the business' current business priorities and prior architecture decisions. You don't want to discourage this group. They'll bring you new ideas, care about the business or at least view the business as a way of funding the acquisition of better toys.

Another group is the don't blame me crowd. Frankly, get rid of them. We ALL make mistakes. Anyone who spends so much time covering their ass as they do working their ass belongs elsewhere. That could be a function of an individual's fear to fail or obssesiveness to cl

by mindbump

I agree very much with Paul Jean Jr. It starts with a sense of the organizational structure needed to accomplish your goals. In starting departments, the hardest part is looking around and determining what roles you want to accept in your dept. or would be allowed to accept. Remember your dept interface with itself most of the time, but the rest of the company when things have gone very well or vey wrong.

As you already state, you have grown to have a production environment run one way, while you develop fully capable test and staging aeas, development servers, and a possible R&D function.

I praise you for taking personalities into account when managing an IT group. Ver few other managers may face the type of diersity of personalities and culltures you probably face.

Some developersfor example, really just want to be told what to code, given clear requiremets, and a due date. Then left alone. They have no interest in office politics, social events, or the applications they are even developing. Like each group, you'll develop a different managerial expectation and approach suitable for tem.

There is often another group not content to be robots of coding efficiency. They want to be on the cutting edge of code, languages, and equipment hitting the tech world daily. They can be very enthusiastic but often feel trapped by org restraints. Balancing this with the constraints of the business' current business priorities and prior architecture decisions. You don't want to discourage this group. They'll bring you new ideas, care about the business or at least view the business as a way of funding the acquisition of better toys.

Another group is the don't blame me crowd. Frankly, get rid of them. We ALL make mistakes. Anyone who spends so much time covering their ass as they do working their ass belongs elsewhere. That could be a function of an individual's fear to fail or obssesiveness to cl

This discussion is closed to new replies.