To date, tons of excellent textbooks, manuals and articles have been written on the topic of project management, millions of hours of training videos have been shot, millions of trainings have been conducted, and millions of specialists have been trained. Despite this, attempts to βmake the complex simpleβ do not stop.
This material examines a qualitative model of the impact of some project parameters on its duration, as well as a list of βgoodβ and βbadβ measures to accelerate projects.
The approach under consideration can be used as an additional educational material when training project managers, as well as a checklist when assessing the completeness and validity of the project manager's actions when solving problems in the project.
The considered project acceleration measures are in addition to other important aspects of IT projects, such as the quality of collecting and analyzing requirements, the quality of the solution, the quality of code production, etc.
The model of the influence of project parameters on its duration is considered in relation to the "average" IT project, which is characterized by the following parameters:
duration - from 6 months;
the number of project team members - from 7-8 people. with an average level of involvement in the project of 50% (project team members can be involved in other βcompetingβ activities);
the number of project participants from the customer's side - from 2-3 people;
the project implies some flexibility in the content (for example, the ability to adjust the priorities and timing of the implementation of functions or the possibility of changing the detailed requirements for functions).
A qualitative model of the influence of project parameters on its duration can be presented as follows:
,
Where
T is the duration of the project;
S - the content (scope) of the project, the scope of implemented functions (features) and work performed;
L - losses of various kinds that can be identified and eliminated;
C β , ;
W β , ;
E β ;
O β β β.
, ( T), S (), L ( ), C ( ) W ( ), E ( ), O ( ).
:
|
|
|
|
|
S () |
||||
S.1. |
, |
|
, |
|
S.2. |
, |
|
, |
|
S.3. |
, ββ, ββ, ββ |
|
|
.
|
L ( ) |
||||
L.1. |
( , , ..). . |
|
|
|
L.2. |
, (), |
|
, .
|
|
L.3. |
|
|
|
.
|
L.4. |
, (2-3 .). |
|
.
|
|
L.5. |
, . , .
|
|
ββ , |
.
|
L.6. |
(>>50%). |
|
|
|
L.7. |
( FixPrice-> β β Time & Material -> agile ..) |
|
.
|
. -. . |
L.8. |
ββ ( , ) |
|
. ββ |
|
C ( ) |
||||
C.1. = S.3 |
, ββ, ββ, ββ |
|
-
|
.
|
C.2. |
( ) |
|
|
. , , |
C.3. |
( ) ( ) . ( ) ( ) . |
|
|
.
|
W ( ) |
||||
W.1. |
|
|
. .
|
. .
|
W.2. = L.6. |
(>>50%). |
|
|
|
W.3. |
|
|
.
|
.
|
W.4. |
. ( , ) . |
|
, |
, .
|
E ( ) |
||||
E.1. / |
() |
|
. .
|
(, ). , .
|
E.2. = L.8. |
ββ ( , ) |
|
. ββ |
|
E.3. |
(ββ) |
|
.
|
(, ). - |
E.4. |
( ββ ). ββ ( ) |
|
. β β .
|
(, ).
|
E.5. |
, β β, |
|
β β |
, .
|
O ( ) |
||||
O.1. () |
( β β). . |
|
|
, |
.
ββ ββ. ββ () ( ):
S.1.
S.2.
L.1.
S.3.
L.8.
L.2.
L.3.
L.4.
L.5.
O.1. ()
L.6.
L.7.
C.2.
W.1.
C.3.
W.3. Increase resources through paid overtime
E.1. Attract a highly qualified expert / coach