Consider the process of weekly control over the timing of a project or project stage (in this article, these will be synonyms). The novelty of the approach will consist in the fact that it will be necessary to automatically "compress" the already prepared project schedule.
Concept Fact + Expectation + Forecast
As a basis, I took the budgeting model I saw at Norilsk Nickel and imposed it on the deadline control process.
Fact is how many hours per hour were spent on a task
Waiting is how many h / h is left to complete the task.
The forecast is how many days (we are already interested in the duration) is required for future tasks. First, it is taken from the approved plan, nothing changes.
In this way we can draw up a model of the end of the project.
Deviation is the difference between the approved deadline and the end in the Fact + Expect + Forecast model.
The baseline is the approved plan against which we will compare.
Process task
I see the main task in fulfilling the remaining scope of work (Expected + Forecast) in the remaining period according to the Baseline (approved) plan. We can no longer control the past (fact), but from it we can extract reasons. More on that later.
Collecting Fact + Expectation
- /
/ .
- + MS Project. , 2 , .
Task Manager |
MS Project |
|
. |
- |
|
|
- |
|
|
- |
, - . + |
- |
|
1. MS Project
|
- |
|
|
, , . !
, ( ), , / .
, :
- + + .
, - , . , .
, .
|
|
, . |
1 |
-5 |
8 |
-9 |
. . . |
|
9 |
-20 ( ) |
. , .
. ?
. , ? - . , .
( , ). , .
?
?
, :
- - ( ).
?
.
,
, 20 , 30 (6 ).
|
|
|
|
|
|
0 |
10 |
|
|
20 |
20 |
|
|
20 |
30 |
20 / 30 = 0,67
.
|
|
|
|
|
|
6,7 |
6,5 |
|
|
13,3 |
13 |
|
|
20 |
19,5 |
,
5 , 20 / (30-5) = 0,8
MS Project
MS Project .
.
, :
< ,
1 = ( - ) * /*
1 = * /*
1 2 .
, - . . 6,666 , 10 .
PMBoK 4 . , .
"" .
, .
-
,
, ,
- ,
, 80% , 20% . .
.
.
:
( , , )
( ).