Professional Documents
Culture Documents
Definitions:
Each event is always in a specific state at any given time of a project. At project start,
all events are at the same state. This initial state is stateless, meaning that time has not
altered any task value.
Event state = TASK Evaluation. A Function that is fully documented, described by its
boundaries, is known to be of a very high degree of confirmation, can be said to exist (in
time), can be tested.
In order to assess an event state:
Consider: Task Evaluation = Feasibility (can it be done and how?)
The highest degree of confirmation of the above statement determines the validity and
purpose of a task, therefore of the event of which it is a subset.
For each state at time t there is a another state (tn) state which is a risk evaluation
factor
All states at any time
Example
Task 2 depends on 1
Task 3 depends on 2
Task4 depends on 1
Page 1 of 3
Task 4 depends on task 1, 4
Task 5 depends on 1, 2, 4
So at time x
List A:
- Task
- Resource
- Time allocated
LIST B
- Task Status Flag = status defined by level 0 – 5 (critical levels factors) ->
sends status code for evaluation to dependency tracker module
- Dependency list (check list) => Takes input from current Task status level ->
measures against all dependant task EX - Say this is task 6 dependants on task 1,
2, 4
LIST C
-
- Flags / Alerts
- Percent complete in % and Pb()
- Status
Task 1 = Status = Delay -> Time due = 2 weeks – (7 oct 2008 ) -> diff of task time 6 –
time 1 = SHOULB be x BUT is … XX ), comparison to schedule –> assign a temp status
Level to task 6 (delay of this magnitude is critical) HOW do I know that? Lookup next
dependency - …. Task 2 = Status = hold, delay -> Time due = ‘ ‘ -> diff of task time 6 –
time 1 = x ), comparison to schedule – assign temp NEW –(X by status of task 4) lookup
next dependency-> Task 4 = Status = in progress, -> status is 4 (75% complete)
PM
In optimal conditions:
Meaning for each state there is a counter state which is a risk evaluation factor
Such as
Start -> Stop
Fast - > Slow
Forward -> Backwards
Cancel
Delay
Hold
Derivative of x -> Deviation
Obtain the Minimum of the Maximum (minimax) of set of condition where ‘winning’ is
less the object as not loosing. The strategy being having as much data as possible as to
always be in a situation where the optimal is achieved within the available Max /
minimum amount of variables:
Space
Time
Conditions
Available stats
Example
Task 2 depends on 1
Task 3 depends on 2
Task4 depends on 1
Task 4 depends on task 1, 4
Task 5 depends on 1, 2, 4
So at time x
Page 3 of 3