[Recording broken into three parts…sorry about that.
ZIP file Ch23ProjectManagement]

Break into parts
Assign
Anticipate problems
23 Project Planning
proposal
	Estimate work, schedule, cost, scope, quality, etc.
Startup
	Organize into parts and phases
Update
	Review, work, schedule, cost, scope, quality, etc.
Bidding
	Work out price, terms
	Contingency funds, slack time, etc
	Effort costs (salary) hardware and software, travel/training,
		profit
	As plans change, requirements change, technology,
development problems

23.1 software pricing
	Might bid to lose money
		Gain status
		Gain market share
		Keep employees busy
		“pricing to win”

23.2 plan driven development
	Plan in advance, use plan as guide
	Revisions often need to be made
	Discover problems before getting in too deep
	Easier when you see problems in advance
	Large, and very secure projects need better plans
	Small systems in changing environments , more agile

   Project plans
	Introduction
	Organization
	Risk analysis
	Hardware and software requirements
	Schedule
	Monitor
   Planning process
	Iterative
	As information is included, revise
		Requirements, budget, schedule, risk, etc
	Constraints
		Delivery
		Staff
		Budget
		Tools, etc
	Milestones
		Point naturally evaluate progress
		Deliverables
		(COULD END UP CANCELLING THE PROJECT)

23.3 scheduling
	Even agile needs a schedule
	Tasks (week to months)
	Prerequisites
	Parallelism
	Contingency (30% to 50%)
	Gant charts (emphasize time schedule)
	Pert charts (emphasize pre-requisites)
	Don’t be too optimistic; allow for things to go wrong
23.4 agile
	Iterative and flexible
	Release planning
	Can use user stories
	Velocity—how fast are you adding features
23.5 estimation
	Experienced based
		(but is your experience relevant to this project)
		Algorithmic cost modelling
		Effort = A * size^B * M
		B complexity M rigor
	How long did you think it would take?
		Estimate how long it would take if NO difficulties
		Overestimate hours by a factor of 4	
	Optimistic time, pessimistic time, expected time
		(O +  4* E + P)/6
23.6 COCOMO
	Software from reusable components
	Early design
	Estimate effort to reuse code
	Architecture
	Project duration
	Staffing