0% found this document useful (0 votes)
2 views4 pages

02 Project Management Field Notes

This document serves as a compact guide for small teams managing projects, emphasizing the importance of defining objectives, success criteria, and scope before task planning. It covers essential project management components such as scheduling, risk assessment, and communication strategies to ensure effective project execution. The guide also highlights the significance of maintaining a decision log and clear communication to avoid costly surprises.

Uploaded by

kaisinux
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
2 views4 pages

02 Project Management Field Notes

This document serves as a compact guide for small teams managing projects, emphasizing the importance of defining objectives, success criteria, and scope before task planning. It covers essential project management components such as scheduling, risk assessment, and communication strategies to ensure effective project execution. The guide also highlights the significance of maintaining a decision log and clear communication to avoid costly surprises.

Uploaded by

kaisinux
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Project Management Field Notes

Scope, schedules, risk and communication

Purpose
A compact guide for small teams managing practical projects without relying on a heavyweight
methodology.

Independent learning notes | General educational use

Original educational sample Page 1


1. Turning an Idea into a Manageable Project
A project is temporary work undertaken to produce a defined result. The most common planning failure is
starting with a list of tasks before defining the result. Good project management begins by clarifying the
objective, the success criteria and the boundaries of the work.

A simple project charter


Element Example

Objective Launch a customer self-service portal

Success metric 80% of common requests can be completed online

Deadline End of Q4

Constraints Existing identity platform and fixed budget

Out of scope Replacing the billing system

Scope is a decision tool


A clear scope does not merely describe what will be built. It also helps the team reject attractive but
distracting additions. Whenever a new request appears, ask whether it directly advances the agreed
objective, whether it changes cost or schedule, and who is authorized to accept that change.

Work breakdown
- Break the deliverable into major workstreams.

- Split each workstream into outcomes that can be assigned and verified.

- Only then create detailed tasks, estimates and dependencies.

A task list is useful only when each task has an owner, a definition of done and a clear relationship to the
project outcome.

Original educational sample Page 2


2. Scheduling, Dependencies and Critical Work
Scheduling is not simply placing dates beside tasks. A realistic schedule models dependencies, resource
limits and uncertainty. Some tasks may run in parallel; others cannot start until a predecessor is finished.

Dependency types in plain language


- Finish-to-start: testing starts after implementation finishes.

- Start-to-start: training preparation can begin when documentation work begins.

- Finish-to-finish: final reporting cannot finish before final validation finishes.

Critical path concept


The critical path is the chain of dependent activities that determines the earliest possible finish date. A
delay on a critical-path activity, without compensating action, delays the project. Activities outside the
path may have schedule flexibility, often called float or slack.

Task Duration Depends on

Requirements 5 days -

Design 4 days Requirements

Build 10 days Design

Test 5 days Build

Training material 6 days Design

Go-live 1 day Test + Training

Estimating with ranges


Single-number estimates create false confidence. For uncertain work, record an optimistic, likely and
pessimistic duration. The range itself is information: a wide range signals that discovery, prototyping or
risk reduction may be valuable before committing to a date.

Original educational sample Page 3


3. Risk, Communication and Decision Logs
A risk is an uncertain event that could affect objectives. A useful risk register is short enough to be
reviewed frequently and specific enough to trigger action. Vague entries such as "technical issues" are
less useful than statements that include cause, event and consequence.

Risk Probability Impact Response

Vendor API delay Medium High Prototype early; maintain fallback import

Key expert unavailable Low High Document design; identify backup

Scope growth High Medium Use change approval rule

Status communication
A good project update answers four questions: What changed since the last update? Are the objectives
still achievable? What decisions are needed? What should stakeholders expect next? A dashboard full of
green indicators is less useful than a short explanation of the few items that may alter the outcome.

Decision log
- Record the decision, not just the meeting discussion.

- Capture date, decision owner and the reason.

- Link the decision to requirements, risks or architecture when relevant.

- Revisit old decisions only when the underlying assumptions have changed.

The goal of project governance is not paperwork. It is to make important assumptions, responsibilities
and trade-offs visible before they become expensive surprises.

Original educational sample Page 4

You might also like