THE UNIVERSITY OF LAHORE
Course Outline
FALL 2015
Session 2015-16
CS-5310
Effective Date: 29 September, 2015
SCU 3 credits
Co-requisite (s)
-Pre-requisite(s) Introduction to Software Engineering (CS4347)
Weekly tuition pattern 2 classes (90 min each)
Teaching Team
Syeda Synnia Tanveer
Synnia.tanveer@cs.uol.edu.pk Atif Ikram
Atif.ikram@cs.uol.edu.pk
1-
Course Description
To develop ability to plan and manage software development projects successfully, maximizing the return from each stage of the software development life cycle.
2-Objectives
The course mainly aims to achieve the following objectives:
1. Equips the students with the tools and techniques required for the effective end-to-end management of software projects.
2. Offers practical advice from real examples to facilitate the selection of the right technique for a particular project. Instead of focusing solely on the technical problems.
3. Addresses the social and the organizational concerns that are frequently responsible for project failure.
4. Defines the topics relevant to the local software development industry (e.g. management of outsourced projects, software process improvement, etc.)
3-Outcomes
By the completion of this course, the students should able to:
1. Know the tools and techniques to practice the effective end-to-end management of software projects.
2. Able to select the right technique for a particular project, instead of focusing solely on the technical problems.
3. Know the social and the organizational concerns that can cause a project failure. 4. Have awareness about local software development industry concepts like how to efficiently manage the outsourced projects etc.
4-Course Structure
1. Presentation by lecturer 2. Group Discussions 3. Discussing Case studies 4. Assignments
5. Quizzes
5-
Course Duration
This course will be held twice a week of 90 min each class duration (lecture)
6-
Course style
The course will be delivered in a classroom environment.
7-
Additional Course Requirement
limited to: Writing, Presentation, Decision Making and Teamwork.
8-
Text and Other Resources
8.1 Text
1. Bob Hughes and Mike Cotterell , Software Project Management, 2005, McGraw Hill Higher Education
8.2 Other Resources
9-
Course Outline
The lecturers are supposed to complete the following topics/sub-topics before the mid/final term examination as prescribed in the course outline below:
Week Lecture Topics/Sub-Topics MaterialReading
1
1 Software CrisisWhy do software projects fail?
How can we make our project succeed?
Software crisis.ppt
2
Introduction, Fundamentals
Basics, The filed, Job Fundamentals, Project Management Skills. Project Management Skills, Project Management Positions, PM History, Project vs Program Management, Interactions/Stakeholders, PM Tools: Low-end, Mid-market, High-end, Gantt chart, Network Diagram.
Session 1 (Lecture1).ppt
2
1
Introduction, Fundamentals
PMI’s 9 Knowledge areas, PM Strategies: Classic Mistake Avoidance, Development Fundamentals, Risk Management, Schedule-Oriented Practices. Project Dimensions: People, Process, Product, Technology, Planning, Tracking, Measurement, Trade off Triangle, Technical Fundamentals.
Session 1 (Lecture 2).ppt
2
Introduction, Fundamentals
Project Phases, Seven core project Phases: SDLC Life Cycle, Life Cycle relationship, 36 Classic mistakes: People-related, Process-related, Product related, Technology related. Session 1 (Lecture 3).ppt 3 1 Processes, Organization
Project Success Rate, Project Metrics: Project size, duration, team, Stakeholder Triad: Function
representative, Executive sponsor, Project manager, 15 PM Job Functions, PMI Framework, The 5 PMI Process group: Initiating, Planning, Executing, Controlling, Closing, PMI Process links, PMI Phase Interaction, Importance of Phases.
Session 2 (Lecture1).ppt
2
Processes, Organization
Understanding Organizations: Structural frame, Human Resource frame, Political frame, Symbolic frame, Organizational Structure: Functional, Project, Matrix, Pros & Cons of each Organizational Structure, Organizational Structure Influences on Projects, Organizational Impact,
Session 2 (Lecture2).ppt
4 1 Processes, Organization
Why Firms Invest in IT, IT Planning Process, Methods for selecting projects, Board Organizational needs, Categorizing IT Projects: Problem, Opportunity,
Directive, Project Portfolio Management: 5 level approach
2
Processes, Organization
Procurement Management: Why outsource, Project Procurement Management Processes and Key outputs, Procurement Tools & Techniques: Make or Buy analysis, Types of Contracts: Fixed Price or lump sum contracts, Cost reimbursable contracts, Time and Material Contracts, Unit Price Contracts, Contract Types Vs Risks, Statement of Work (SOW), SOW Template
Session 2 (Lecture 4).ppt
5
1
Planning
Time allocation by phase: 40-20-40 rule, Potential deliverable by phases , Concept exploration, Requirements, Why requirements are important,
Analysis and Design, Development, Integration & Test, Deployment and Maintenance, Lifecycle planning, Selecting for Software developmental approach: Plan driven, Incremental , Re-use oriented Software Engineering, Choosing your Life Cycle
Session 3 (Lecture 1).ppt
2
Planning
Preliminary planning parts, Your PM Process, Primary Planning Steps, Planning basics: Scoping, Estimation, Risk, Schedule, Control Strategy, Planning Documents: Software Development Plan, Risk
Management Plan, Software Quality Assurance Plan, Software Configuration Management Plan, Project ROI Analysis, SOW, Project Charter, SPMP, Budget plan, Responsibility Assignment Matrix (RAM),
Session 3 (Lecture 2).ppt
6
1
WBS, Estimation and Scheduling
Project Planning: A 12 set program, How to schedule, Partitioning your project, Project Elements, Work breakdown Structure (WBS), A full WBS Structure, WBS Types: Process, Product, Hybrid
Session 4 (Lecture 1).ppt
2
WBS, Estimation and Scheduling
WBS & Methodology, WBS Techniques: Top-down, Bottom-Up, Analogy, Rolling Wave, Post-its on a wall, WBS Guidelines.
Session 4 (Lecture 2).ppt
7
1
Estimation and Scheduling
Estimations, Estimation Methodologies: Top-down, Bottom-Up, Analogy, Expert Judgement, Priced to Win, Parametric or Algorithmic Method
Session 4 (Lecture 3).ppt
2
WBS, Estimation and Scheduling
Wideband Delphi Process of Estimation, Other Estimation factors
Quiz 1
8 1
MID TERMS
29
1
Scheduling Diagrams
Project network diagram fundamentals, CPM, PERT
Scheduling Diagrams (Lecture 1). ppt
2 Scheduling DiagramsGantt charts, Critical chain scheduling, Scheduling(Lecture 2). ppt Diagrams
10
1 Using MS-ProjectAssigning Resources, Resource leveling, 2
Using MS-Project
Team models, Managing conflict and motivating
Assignment
11
1 Controllingreporting( status reporting)process Performance Ref.[2] page 140
2 Project metricsOriented Metrics, Function-Oriented Metrics, : Software Measurement, Size- Ref.[2] with file namemetrics.docx
12
1 Reconciling LOC and FP Metrics, all metrics with examples Ref.[2] with file name metrics.docx
2 MS project, Status Reporting, Performance etc , Assignment
13
1 Earned Value Analysis Ref.[1] Page 186
2
Communication Techniques or approaches: Formal, impersonal approaches, Formal, interpersonal procedures, Informal, interpersonal procedures, Electronic communication, Interpersonal networking
Ref.[2] page 65,66
14
1 Project Recovery: 5 actions
Ref.[3] reading material attached, with file name as, Project Recovery Strategies.pdf
2 Risk management:analysis, Risk mitigation Risk identification, Risk Ref.[2] page 308,309
15
1
Change control: software configuration, controlling versions, controlling changes, Auditing, communication changes, Guidelines for effective configuration management
Ref.[2] page 112-116
2
Migration: Software implementation, implementation prerequisite, key
implementation plan, implementation activities, Ref.[2] page 404-409
16
1 Post project Review: Post mortem Ref.[2] page 411
2 Closing: project wind-Up
17 1
FINAL TERM EXAMINATION
210-
Assessment Criteria
No. Assessment Percentage
1. Mid Exam 25%
2. Final Exam 50%
4. Quiz 10%
5. Project 15%
Total 100%
11-
Attendance Requirements
You are expected to attend all lectures, seminars, tutorials, and lab sessions or any other classroom activity. Where you fail to attend classes, you cannot expect the lecturer to brief you on what you have missed. You are responsible for your attendance, not the academic staff. Attendance at tutorials and lab sessions will be strictly monitored, and failure to attend will be taken into account.
12- Submission and Collection of Assignment
All assignments should be handed in at the beginning of the class sessions when they are due. All assignments may be handed back during scheduled classes.
13-
General Information
Students are required to be familiar with the university code Conduct, and to abide by its terms and conditions.
13.1 Copying of Copyright Material By Student
A condition of acceptance as a student is the obligation to abide by the University’s policy on the copying of copyright material. This obligation covers photocopying of any material using the University’s photocopying machines, and the recording off air, and making subsequent copies, of radio or television broadcasts, and photocopying textbooks. Students who flagrantly disregard University policy and copyright requirements will be liable to disciplinary action under the Code of Conduct.
13.2 Academic Misconduct
occurs when the work (including such things as text, figures, ideas, or conceptual structure, whether verbatim or not) created by another person or persons is used and presented as one’s own creation, unless the source of each quotation or piece of borrowed material is acknowledged with an appropriate citation. Encouraging or assisting another person to commit plagiarism is a form of improper collusion and may attract the same penalties. To prevent Academic Misconduct occurring, students are expected to familiarize themselves with the University policy, the Subject Outline statements, and specific assignment guidelines.
13.3 Guidelines to Avoid Plagiarism
Whenever you copy more than a few words from any source, you must acknowledge that source by putting the quote in quotation marks and providing the name of the author. Full details must be provided in your bibliography. If you copy a diagram, statistical table, map, etc., you must acknowledge the source. The recommended way is to show this under the diagram. If you quote any statistics in your text, the source should be acknowledged. Again full details must be provided in your bibliography. Whenever you use the ideas of any other author you should acknowledge those, using the APA (American Psychological Association) style of referencing.
Students are encouraged to co-operate, but collusion is a form of cheating. Students may use any sources (acknowledged of course) other than the assignments of fellow students. Unless your Subject Leader informs you otherwise, the following guideline should be used: Students may work together in obtaining references, discussing the content of the references and discussing the assignment, but when they write, they must write alone.
13.4 Referencing For Written Work
Referencing is necessary to acknowledge others' ideas, avoid plagiarism, and allow readers to access those others’ ideas. Referencing should:
1. Acknowledge others' ideas 2. Allow readers to find the source 3. Be consistent in format and
4. Acknowledge the source of the referencing format
To attain these qualities, the school recommends use of either the Harvard or American Psychological Association style of referencing, both of which use the author/date.
13.5 Referencing Standards
Approval
Designed by:
Atif Ikram
Assistant Professor Dept. Computer Science & IT
Syeda Synnia Tanveer
Lecturer
Dept. Computer Science & IT
Approved by: