Stop Throwing Money Away In Your IT Department

ozeaylptqo

Companies continue throwing money at IT projects and accept a pathetic 30% success rate. The IT field is filled with complexity and the fast pace seems overwhelming at times, yet we as professionals should adapt to the changing environment and use available best practices to increase the success rate of IT projects. IT professionals need to understand best practice guidelines, processes, templates and how to deploy them in different situations.



  c: h7 b8 Y2 [+ f, N, fFollowing these best practices is not a silver bullet. They also will not guarantee success everytime. They will however, provide you with the necessary tools that provide you the greatest chance for success.

. n5 ]' \+ \5 r2 V! A7 y" Q, S# o( R

Today we will review a few best practice IT management techniques.
8 o) I, q" {+ f5 H
& G* Y8 q3 v5 q! w( y
5 N+ k6 X; m' k1 D# d7 l% H  O
Align IT and Business
( K% G8 t7 g. a7 n% b
  P( m6 q' v! O% x4 N3 f5 o& a, N# t
3 R1 a* a& U# S8 D& p6 D
: c+ J# M0 k$ x. y) pAlign IT projects to specific business strategy goals and objectives. Do not start or continue IT projects that are not aligned with the business strategy.

5 r. a2 u6 ?: I( ]

  Y7 {1 h9 {7 A: gQualified Leadership

7 `! R$ d  N& Y
& p! ?0 X, ]3 @7 O8 y
0 u7 ]* F: o( m# yMake sure that each project has a full time leader with overall responsibility and authority for the project. The project leader should be qualified to manage the project size and complexity.

0 R+ z$ S# S! Z9 M4 u7 j

9 g1 O0 W* H, L2 X. d4 jBe Competitive



3 C! p% F3 J% u! w# N4 c  YUse information technology to improve your business competitive advantage.



Define Metrics
8 k; B* X# a! B6 n+ J) }


7 h0 y/ m/ v* i3 g  F" V) nDefine and track measurable objectives that are necessary for the success of the project. Review these metrics monthly and adjust the project as needed.

0 w; z7 z$ l% v6 k6 i$ E. h3 V
, h! u! C. F' T5 w+ L3 F% Y4 c
Leverage Current Technology
( S+ X, I7 U2 L


Leverage the investment of your current systems when developing a new system.

  h. l0 }- p% [9 B7 v$ {

Project Organization


! D( |. l- U- Q" @- p
Project teams or sub-teams should contain 2 to 7 team members with a mix of technical and business specialists. Keep the project team organization small and agile.

$ q  r& F% H' i" \0 E+ H+ }# H
2 o! ~) k- w5 h7 H0 O+ T
& b, I+ A; Y3 G. o/ _  I  o7 o  p1 pKeep It Simple

: M% ]( b% b2 q0 s! ?' H( T# q8 T
7 t4 d0 l5 L5 c/ i! t& f
6 P" u% i- w4 b# y% l. K. E4 D9 cUse the simplest possible combination of business processes and technology to achieve your goals.
2 x1 u. g, d$ f  h


Work In Small Units
2 K$ @/ G. s$ q, h. T! ^5 _
) l# t3 i6 U6 \1 a! s! O

Project work should be broken down into small units. A task should not exceed 80 hours and should not be less than 8 hours. The project should produce workable systems every 30 to 90 days.
/ p  D4 T8 l% R9 ^: a- p+ ^


8 A2 N& h; B. M! t6 P* Z0 P! QKeep It Small



Break the development of big IT system projects into smaller functional projects to reduce the complexity and lower the overall risk of a big system project.
0 z5 j) b0 }# G; s

: M  J; H2 P* v* Z, W7 t5 x; ]
, f! G: L% c, GProject Administration
& }) L. _( u2 K' H* Z


Provide each project team with a coordinator or administrator that help project managers and leads keep project plans and budgets up to date and accurate.

. R4 `' \2 H$ }- I) u
, j; T. m3 G6 |+ {# v3 M: }. p
: K6 f9 l& n5 u9 {4 P* ?Understand Your Capabilities

0 K9 l  ^% N9 [
* s7 m$ v6 G; W* G) @
Don't take on an IT project when the complexity exceeds the companies capabilities.
6 J8 u( u$ R3 w: R/ B  h" D% V( Q


+ V* H9 L  o  A7 o) OStart From Scratch
) T8 |8 I/ Q6 {; D6 a- D
2 D/ _, v: y: a+ k

When restarting failed projects, start from scratch. Don't use the original design and project organization that failed the first time.
  Q. ?  [/ U2 o; x+ {* L

0 G* C/ O+ j' E  C4 g0 r3 v
Copyright (c) 2006 Dennis Sommer