CPSC 333 SENG 311: Foundations Principles of SE

1
CPSC 333 / SENG 311 Foundations / Principles
of SE

• Project Management

2
Agenda

• Overview
• Project management tasks
• Managing your team project

3
Software engineering versus software management

• Many problems in software development are
  management problems
• cost estimation
• time estimation
• scheduling
• change control
• version control

4
Goals of project management

• Project management planning, organizing,
  managing of tasks resources to accomplish a
  defined objective
• What, who, when, how much (i.e., costs)

5
Project management phases

• Planning the project
• Scheduling the tasks
• Tracking progress
• Communicating project information

6
Agenda

• Overview
• Project management tasks
• Managing your team project

7
Management tasks

• Task definition scheduling
• Resource management
• Risk management
• Configuration management
• Quality management

8
Scheduling

• Define what tasks need to be carried out
• Task schedule duration, priority, required
  skills
• Milestones significant events in the project
• Dependencies, e.g. Task precedence relationships
• People equipment
• Resource leveling is the process of ensuring that
  the schedule reflects adequate resource usage
• Do not over-subdivide tasks!

9
Tracking the schedule

• Conducting periodic project status meetings
• Evaluating the results of all reviews
• Determine whether formal project milestones have
  been accomplished
• Compare planned and actual end dates
• Talk with your people

10
Resource management

• Track the amount of work done by people and
  equipment
• Involvement in multiple projects?
• People/Equipment calendars
• Distribution of responsibilities
• Keep track of resource costs

11
Risk management

• Risk identification
• E.g. unknown technologies, tools, relationships
• Risk quantification
• How much can this risk cost us if it occurs?
• Risk resolution
• Reserve time for overcoming troubles
• Define tasks that reduce risks
• Contingency / Mitigation plan
• put some processes in place to handle risks when
  they do occur

12
Configuration Management

• Deals with products
• Configuration Management Plan (CMP)
• responsibilities
• versioning schema
• tasks required to produce a baseline
• tools being applied for CM
• Team assignment project manager responsible for
  project configuration in development environment

13
Quality management

• Quality improvement paradigm

14
Quality management plan

• Test plans
• Review plans
• Measurement plans
• Risk management addressing technical risks of the
  deliverable

15
Scheduling models

• Myth if we fall behind the schedule, we can
  always add more programmers and catch up later in
  the project
• PERT charts (Program Evaluation and Review
  Technique)
• Network diagram
• Gantt charts (bar charts, timeline charts)
• Critical path method

16
Network diagram (or task network)
17
Task Network

• Assist PM to schedule
• identify task dependencies
• schedule concurrent tasks
• identify the critical path, or those tasks that
  must be completed on time in order not to slow
  down the entire project

18
Timeline diagram
19
TimeLine Diagram (or Gantt Chart)

• project tasks listed on LHS of table
• horizontal bars indicate duration of each task
• multiple bars at same time indicate concurrent
  activities
• diamonds indicate milestones

20
Agenda

• Overview
• Project management tasks
• Managing your team project

21
Managing your team project (I)

• Development tasks
• Quality management tasks
• Review tasks
• Testing
• Analyze risks
• Configuration management tasks
• Change report strategy
• Versioning method

22
Managing your team project (II)

• Schedule the tasks
• Define milestones (project manager)
• Assign team members to tasks
• Regular meetings to
• Find ways out of (time) problems
• Check if deadlines are kept
• Discuss problems, etc.
• Report problems in advance

23
Summary

• Many problems in s/w development are management
  problems
• Time, resources, and tracking are big issues
• Management ideally identifies problems before
  they occur and fixes them
• You will need to apply many of the management
  tasks to your project

24
Were Available!

• Questions?
• if you have any questions about contents of this
  lecture or other course-related issues, please
  come by during our office hours, or send us email
• Dr. Joshua MTW, 12-1pm, ICT 548
• joshuar_at_cpsc.ucalgary.ca
• Dr. Walker WF, 1-2pm, ICT 546
• rwalker_at_cpsc.ucalgary.ca