Dr. Sheela Ramanna

Applied Computer Science

University of Winnipeg

Welcome to ACS-3901-001Principles of Software Project

Management

Instructor Information

My coordinates

e-mail: s.ramanna@uwinnipeg.ca

office hours: Tuesday: 2:30 - 3:30 (via Zoom)

Course webpage

http://www.acs.uwinnipeg.ca/3901

Access and sign in details (next week)

Other Information

Text book: Quality Software Project Management by Futrell, Shafer, and Shafer, Prentice Hall, 2002, ISBN: 0-13-091297-2 .

Prescribed reading will be assigned from this textbook.

Class Notes

Quiz 1: January 28, 2021

Quiz 2: February 25, 2021

Final Withdrawal Date: March 16

Reading Week: Feb 14-20 (No classes)

Last Class: April 6

Final Exam (Comprehensive – 2.5hours)

Exam Information

Quiz 1 : 20%

Quiz 2 : 30%

Final Exam : 50%

Evaluation Criteria(1)

There will be no assignments

Students who wish to gain experience in practicalsoftware project management are strongly advised totake the ACS-4901 course

All quizzes are in class and closed-book

There will be no make-up quiz. If you miss a quiz, asecond quiz will be worth 50%.

Exam and Quiz Requirements

Photo ID is required for quizzes and the final exam. Quizzes and the final exam will be delivered via Nexus and

proctored via Zoom. Students must have video capability, and video must be

TURNED ON for the duration of the exam for proctoring. Students may contact the instructor to ask questions External resources (or any material not listed above) are NOT

PERMITTED Communication with others (except the instructor) is NOT

PERMITTED

All course material will be available on the course website.

Lectures will be delivered live during the scheduled timesvia Zoom. RECORDING IS NOT PERMITTED. Videoof lectures WILL NOT BE POSTED. Students must beavailable via Zoom during scheduled class meeting times.

Students must DISPLAY their real/full name. Use of Video is OPTIONAL. Participants must be MUTED when not speaking. Students may interact via CHAT.

Remote Learning

Students can find answers to frequently askedquestions related to remote learning here:https://www.uwinnipeg.ca/covid-19/remote-learning-faq.html.

Note: A permitted or necessary change in modeof delivery may require adjustments to importantaspects of course outlines, like content, classschedule and the number, nature, and weighting ofquizzes.

Remote Learning - contd

There will be a 5-10 min recap of the previouslecture All questions submitted via Chat during the classwill be answered at the END of the lectureThere will be in-class problem solving sessions forquantitative aspects of this course.The schedule and other details for these sessionswill be announced on the first day of class

Lecture Format

New Misconduct Information

Avoiding Academic and Non-academic Misconduct. Students are encouraged to familiarize themselves with the Academic Regulations and Policies found in the University Academic Calendar at: https://uwinnipeg.ca/academics/calendar/docs/regulationsandpolicies.pdf . Particular attention should be given to subsections 8 (Student Discipline), 9 (Senate Appeals), and 10 (Grade Appeals). Please note, in particular, the subsection of Student Discipline pertaining to plagiarism and other forms of cheating.

New Misconduct Information

Avoiding Copyright Violation. Course materials are owned by the instructor who developed them. Examples of such materials are course outlines, assignment descriptions, lecture notes, test questions, and presentation slides. Students who upload these materials to filesharing sites, or in any other way share these materials with others outside the class without prior permission of the instructor/presenter, are in violation of copyright law and University policy. Students must also seek prior permission of the instructor /presenter before photographing or recording slides, presentations, lectures, and notes on the board.

New Misconduct Information

Detailed information can be found at the following:Academic Misconduct Policy and Procedures:https://www.uwinnipeg.ca/institutional-analysis/docs/policies/academic-misconduct-policy.pdf and https://www.uwinnipeg.ca/institutional-analysis/docs/policies/academic-misconduct-procedures.pdfNon-Academic Misconduct Policy and Procedures: https://www.uwinnipeg.ca/institutional-analysis/docs/student-non-academic-misconduct-policy.pdf and https://www.uwinnipeg.ca/institutional-analysis/docs/student-non-academic-misconduct-procedures.pdf

Introduction and TerminologyCompetencies and Definitions, SDLC Chap.1 and 3 Jan 7 Selecting SDLC -- Review of Process Models Chap. 4 Jan 12 Process Models Jan 14

Planning and OrganizationProject Teams and Roles --Team Selection Chap.6, 12, 29 Jan. 19 Project Planning and WBS – Proj.Proposal/Charter Chap.7 and 8 Jan. 21 Tasks, Activities -- Project Plan Creation +Review Chap. 9 Jan. 26

Quiz 1 Jan. 28 Software Sizing – Size Estimation Models Chap.10 Feb. 2

Software Sizing – Size Estimation Models Feb 4 Estimating Duration and Cost Chap. 11 Feb 9

Estimating Duration and Cost Feb.11

Reading Week Break Feb. 14-20

Problem Solving Class – Sizing and Estimation Feb. 23

Quiz 2 Feb. 25

Scheduling – PERT/CPM Scheduling Models Chap. 14 and 15 Mar. 2

Requirements Specification—Creating SSR Chap. 16 and 17 Mar. 4 Problem Solving Class -PERT Mar. 9

Risk Management – Quantitative Risk Assessment Chap. 18 Mar. 11 Software Metrics –Product and Process Metrics Chap. 21 Mar.16 Software Metrics Metrics Continued Chap. 21 Mar. 18 Problem Solving Class -Metrics Mar. 23

V&V- Testing strategies, test coverage and path measures

Chap. 23 Mar. 25

Monitoring and ControlProject Tracking and Control Chap. 25 Mar. 30

SQA and SCM Chap. 30, 31 April 1 Problem Solving (V&V) + Review April 6

It is qualitative•Selecting Software Development Lifecycles •Project Teams and Roles --Team Selection •Preparing Project Plans, Proposal and SSR

It is quantitative•Software Sizing and Cost Estimation Models•Scheduling with PERT/CPM•Risk Management Model•Software Metrics•Project Tracking and Control

About the course

It is NOT about Programming It is NOT about designing systems!Preparation for 4901 Project CourseProcess of executing a “real” project

with a “real” customer

About the course

ProsIt is very comprehensiveWritten for Industry Professionals/Standards

ConsSometimes has too much informationToo many definitions for the same termRepetitions

Use the materials in the notes Specific instructions will be given

About the text book

Text Book ( Volume 1) has only 21 chapters! The following topics are missing. Verification and Validation (Reviews, White and Black Box testing) Project Tracking and Control Quality Assurance and Configuration Management

Preliminaries

1. What is Software Project Management

- Leads to its definition

2. Why Software Project Management

- Justification3. How is Software Project

ManagementAccomplished?

- Methods and Tools

Definition: Software Project (Q1)

Example: Build a help desk (automated trouble-shooting/tracking) system for a client.

Characteristics:

• Reasonable size

• Limited duration

• Involves a team of people

• End-user or sponsor

Scope

Schedule

Quality

A project strives to deliver a product of a given scope, within a given cost and schedule, with a certain degree of quality

Why Software Project Management (Q2)

If Quality is low

Users will not use the software

If Scope is too large

Project team will be unable to meet expectations

If Schedule is too tight

Project team will not be able to complete the project

If Cost is exceeds estimates

Project will have to be cancelled

PM Triangle (Fig. 1-4)

scop

e

schedule

Cost

Resources

Perfo

rman

ce

Time

QualityCenter piece

= People/Tools

=size of the problem =Start/end dates

Balancing

How is SPM it done (Q3)

Good Planning and Organization

Selecting the Appropriate life cycle

Selecting appropriate team members

Careful Monitoring and Control

process, product and human resources

Two key concepts

1. Process

Sequence of actions performed for a given purpose

Example

Conducting systematic technical reviewsof all requirements, design and source code

2. Product

Example: Source code, Technical and user manuals, APP (code)

Example -Process

http://www.ics.uci.edu/~redmiles/papers/cscw96/final.html

Team Survival !

Well-defined processes are key to survival Teams can spend “most” of their time in a productive fashion

Poorly planned processes Teams spend a lot of their time correcting mistakes

Question –Process that is removed?

http://www.ics.uci.edu/~redmiles/papers/cscw96/final.html

Competencies necessary for a Project Manager

Product Competencies Example: managing requirements, selecting methods and tools

Project Competencies Example: documenting plans, estimating costs and effort

People Competencies Example: leadership, conducting effective meetings, selecting teams,

team building

The factors that make a software project successful are not especially technical!

NOTE: Pages 17-51 Details of each competency can be ignored

ACS3901 and ACS4901

Sample 4901 Industry Projects in 2020

Cosmic Debuggers;

Sponsor: UW ACS Dept.

Room View;

Sponsor: UW Faculty of Science

Well Made;

Sponsor: Tundra Oil and Gas

Evangelium 2020;

Sponsor: UW, Department of English

Start reading course notes on DAY ONEThere is a lot of material that will be coveredTerminology, definitions and so on

Use office hours and end of class lectures to askquestionsTake advantage of problem-solving sessions Do not flood my mailer with questions the day

before examAll quiz and exam dates are published!

Preparing for Quizzes

Lecture notes will be published at the end of the dayeach class (on the course webpage)Download the lecture notes each classDO NOT WAIT till the day or week before

examsServers can go down It is YOUR responsibility to backup and keep

course notes

Important

Final Grade distribution for 2019 (35 students)

1 (A+), 2 (A), 3( A-), 3 (B+), 2 (B), 4 (C+), 5 (C) , 13(D) and 2 (F)

Midterm Grade distribution for 2020 (49 students)

A+ (3), A(1), A-(3), B+ (4), B(5), C+(8)

C (10), D(3), F(12)

Challenges

Webpage Access

Ferdinand Borillo– ACS Tech Support

f.borillo@uwinnipeg.ca

Important: Mention course name (ACS-3901-001) in your email

32