IT 3301

Review for the Final

This session

Project presentations

Review for the Final

What have we covered so far...

What is a Project?
Sequence of activities
Unique Activities
Complex Activities
Connected Activities
One Goal
Specified Time Within Budget According to specification

What have we covered so far...

The scope triangle (Scope, Cost, Time):

Scope: Functional specification; statement of work;
Cost: Total cost of resources, including human effort;
Time: Based on time required to do the work as well as imposed limits
Based on a defined level of quality and available resources

What have we covered so far...

Project Objective/Overview Statement

Problem / Opportunity
Goal
Objectives
Success criteria
Assumptions, risks, obstacles

Also,

make sure youve got your stakeholders

identified
make sure youve got all their input
prioritized
negotiate bounding limits

WBS Review

Review - Network Diagram (Precedence Diagramming Method)

A

3
ES
F

LS

EF
S

2
LF

ES - Early start
EF - Early Finish
LS - Late Start
LF - Late Finish
S - Slack or float

Extra credit - calculate the duration and critical path

A

F
B

Review - Network Diagram (Precedence Diagramming Method)

1

Example - lets calculate the forward pass

Review - Network Diagram (Precedence Diagramming Method)

1

Example - lets calculate the backward pass

Review - Network Diagram (Precedence Diagramming Method)

1

Example - lets calculate the backward pass

Review - Network Diagram (Precedence Diagramming Method)

1

Example - lets calculate the backward pass

Review - Network Diagram (Precedence Diagramming Method)

1

1
A

3
1
B

C
2

6
0

3
7

3
6

2
3

Example - lets calculate the slack (which is the critical path?)

F
7

8
0

2
8

Chapter 7 - Finalizing the schedule and cost based on

resource availability
Chapter 7 objectives

(* note - good source for study guide ;-)

1.

understanding why resources should be leveled

2.

Understanding the various approaches to leveling resources.

3.

Determine the appropriate use of substitute resources.

4.

Understand a work package and its purposes.

5.

Describe the format and explain the contents of work package.

6.

Know when to require a work package description.

Work package

Work package

Monitoring and controlling progress.

Five reasons you want to measure duration and cost variances.

1. Catch deviations from the plan early.

2. Damping oscillation.

3. Allow early corrective action.

4. Determine weekly schedule variance.

5. Determine weekly effort variance.

Monitoring and controlling progress.

Graphical reporting tools: Gantt charts. Milestone reports.

Monitoring and controlling progress.

Change requests can result in one of the following 6 possible outcomes.
1. The change can be accommodated within project resources and timelines.
2. The change to be accommodated but will require an extension to the delivery schedule.
3. The change can be accommodated within the current delivery schedule but additional resources will be
needed.
4. The change can be accommodated with additional resources and extension of the delivery schedule will be
required.
5. The change can be accommodated with a multiple release strategy for prioritizing deliverables across the
release dates.
6. The change cannot be accommodated without significant change to the project.

Agile Development - SCRUM

Key Roles
Product owner - embedded business side customer
Development team - small group, self organizing / flat governance
Scrum master - coach, not a dictator
Key Events
Sprint planning - Time boxed objectives (Epics, User Stories)
Daily scrum - Reduce the cost / time of communicating
Sprint review / sprint retrospective - continuously re-plan
Key Artifacts
Product backlog - All the work left to complete
A scrum task board - simple view of activities
Product increment - always improving a working product
Sprint burndown chart - need to understand the teams velocity

Agile Development - SCRUM

Risk Management Planning

Risk Management Plan
Methodology defines approaches, tools, and data sources that
might be used to perform risk management on the project
Roles & Responsibilities defines the lead, support, and risk
management team membership for each type of action in the plan
Budget - $
Timing Describes how often the risk management process will be
performed throughout the project life cycle.
Scoring and interpretation methods used for performing qualitative
and quantitative risk analysis
Thresholds the target against which the project team measures the
effectiveness of the the risk response plan execution
Reporting formats - defines how the results of the risk management
processes will be documented, analyzed, and communicated to the
project team and stakeholders
Tracking Documents all facets of risk activities and how the risk
process will be audited

Risk Management
Risk Events or consequences that have the
probability of occurring during a project and that
are measured by their impacts on the project
Components
Risk event
Risk event probability
Risk outcome or consequence (Amount at stake)
Risk event status (Probability x amount at stake)

Risk Identification
Determining which risks are likely to affect the
project and documenting the characteristics
of each

Internal risks Things that the project team can

control or influence
External risks Things beyond the control or
influence of the project team

Risk identification is concerned with opportunities

(positive outcomes), as well as with threats

Risk Identification
Types

Business (profit or loss) and insurable (loss)

Known known Total certainty

Known unknown Degree of uncertainty
Unknown unknown
Total uncertainty

Categories

External, unpredictable
Regulatory, etc.
External, predictable Market risks

Evaluating Risk

Evaluating Risk