Fundamentals of Project Managementwebdocs.cs.ualberta.ca/~games/299/Lecture5.pdf · Fundamentals of...
16
1 Fundamentals of Project Management Fundamentals of Project Management CMPUT 299 H. James Hoover Fall 2005 2005-09-22 Version 1.1 CMPUT 299 H. James Hoover Fall 2005 2005-09-22 Version 1.1
Transcript of Fundamentals of Project Managementwebdocs.cs.ualberta.ca/~games/299/Lecture5.pdf · Fundamentals of...
1
Fundamentals of ProjectManagement
Fundamentals of ProjectManagement
CMPUT 299
H. James Hoover
Fall 2005 2005-09-22
Version 1.1
CMPUT 299
H. James Hoover
Fall 2005 2005-09-22
Version 1.1
CMPUT 299 - Fall 2005Project Management
2
Management isManagement is
♣People
♣Problem Solving
♣Process
♣People
♣Problem Solving
♣Process
CMPUT 299 - Fall 2005Project Management
3
PeoplePeople
♣Identify skills - have and missing
♣Identify personalities
♣Match skills and tasks with people
♣Run effective meetings
♣Identify skills - have and missing
♣Identify personalities
♣Match skills and tasks with people
♣Run effective meetings
CMPUT 299 - Fall 2005Project Management
4
Process = Planning + ExecutionProcess = Planning + Execution
♣ Problem solving generates tasks♣ Planning organizes tasks♣ Planning is continuous:
♣Maintain a task queue♣Assign priority to tasks♣Assign tasks to people♣Monitor status to maintain situation awareness♣Re-evaluate tasks, priorities, assignments
♣ Problem solving generates tasks♣ Planning organizes tasks♣ Planning is continuous:
♣Maintain a task queue♣Assign priority to tasks♣Assign tasks to people♣Monitor status to maintain situation awareness♣Re-evaluate tasks, priorities, assignments
CMPUT 299 - Fall 2005Project Management
5
PlanningPlanning
Meetings+
Task Queue+
Repository
Meetings+
Task Queue+
Repository
CMPUT 299 - Fall 2005Project Management
6
Task QueueTask Queue
♣What - name and short title
♣Who - who monitors, who acts, who helps
♣Priority and timing
♣Current status
♣Details and links to other tasks
♣What - name and short title
♣Who - who monitors, who acts, who helps
♣Priority and timing
♣Current status
♣Details and links to other tasks
CMPUT 299 - Fall 2005Project Management
7
Task QueueTask Queue
♣The task queue is the key management tool
♣Keep it current!
♣Review it often!
♣The task queue is the key management tool
♣Keep it current!
♣Review it often!
CMPUT 299 - Fall 2005Project Management
8
RepositoryRepository
♣Keep everything in a repository
♣Keep under version control
♣Maybe keep under access control
♣Keep a history
♣Backup the repository!
♣Keep everything in a repository
♣Keep under version control
♣Maybe keep under access control
♣Keep a history
♣Backup the repository!
CMPUT 299 - Fall 2005Project Management
9
Problem SolvingProblem Solving
♣There is a general problem solving process
♣Works for all domains
♣Iterative and Incremental
♣Fractal Spiral Model
♣There is a general problem solving process
♣Works for all domains
♣Iterative and Incremental
♣Fractal Spiral Model
CMPUT 299 - Fall 2005Project Management
10
CMPUT 299 - Fall 2005Project Management
11
Steps of the SpiralSteps of the Spiral♣ Strategy -
♣What are we trying to do?♣Does it make business sense?♣How do we measure success?
♣ Analyze - what do we want to do?♣ Design - how are we going to do it?♣ Implement - do it♣ Test - did we do what we intended?♣ Deploy - evaluate and release results to next spiral
♣ Strategy -♣What are we trying to do?♣Does it make business sense?♣How do we measure success?
♣ Analyze - what do we want to do?♣ Design - how are we going to do it?♣ Implement - do it♣ Test - did we do what we intended?♣ Deploy - evaluate and release results to next spiral
CMPUT 299 - Fall 2005Project Management
12
Recursive Spiral ModelRecursive Spiral Model
♣It is self-similar. Each step is executed via asub-spiral.
♣Deployment in a sub-spiral transitions to thenext step in the larger spiral.
♣Recursion into sub-spirals stops on reachinga step with an obvious well-understoodsolution.
♣It is self-similar. Each step is executed via asub-spiral.
♣Deployment in a sub-spiral transitions to thenext step in the larger spiral.
♣Recursion into sub-spirals stops on reachinga step with an obvious well-understoodsolution.
CMPUT 299 - Fall 2005Project Management
13
ExampleExample
♣ Writing a paper for a course♣ Strategy: time lines, resources, cost/benefit,
domain, evaluation mechanism♣ Analyze: topic (sprial to choose one?), research?♣ Design: research?, outline♣ Implement:♣ Test:♣ Deploy:
♣ Writing a paper for a course♣ Strategy: time lines, resources, cost/benefit,
domain, evaluation mechanism♣ Analyze: topic (sprial to choose one?), research?♣ Design: research?, outline♣ Implement:♣ Test:♣ Deploy:
CMPUT 299 - Fall 2005Project Management
14
Project SpiralsProject Spirals
♣Project spirals from inside out.
♣Each spiral achieves an increment in theproject.
♣A spiral will have a mix of increment stylesas determined by the strategy step of thespiral.
♣Project spirals from inside out.
♣Each spiral achieves an increment in theproject.
♣A spiral will have a mix of increment stylesas determined by the strategy step of thespiral.
CMPUT 299 - Fall 2005Project Management
15
Spiral Increment GoalsSpiral Increment Goals♣ Broad and shallow - covers every subsystem
from the outset, but only with limitedfunctionality. Works well for generallyunderstood domains.
♣ Narrow and deep - focuses on substantiallyimplementing a small but problematic subset ofthe system. Works well with risky parts of thesystem. Risks are addressed first and can beevaluated before heavy investment in the rest ofthe system.
♣ Broad and shallow - covers every subsystemfrom the outset, but only with limitedfunctionality. Works well for generallyunderstood domains.
♣ Narrow and deep - focuses on substantiallyimplementing a small but problematic subset ofthe system. Works well with risky parts of thesystem. Risks are addressed first and can beevaluated before heavy investment in the rest ofthe system.
CMPUT 299 - Fall 2005Project Management
16
Spiral Increment ResultsSpiral Increment Results♣ Evolutionary iteration - builds on the previous
ones, discards or modifies very little of theprevious effort.
♣ Prototyping iteration - produces an artifact thatresolves some issue, or demonstrates somecapability. Used to evaluate and manage risk, andare intended to be discarded.
♣ Evolutionary iteration - builds on the previousones, discards or modifies very little of theprevious effort.
♣ Prototyping iteration - produces an artifact thatresolves some issue, or demonstrates somecapability. Used to evaluate and manage risk, andare intended to be discarded.
