Software Project Practices and Management
Unit code: HIT3309
| Credit points | 12.5 Credit Points |
| Duration | 1 Semester or equivalent |
| Contact hours | 48 hours |
| Campus | Hawthorn, Sarawak |
| Prerequisites | |
| Corequisites | Nil |
Related course(s)
A unit of study in the Bachelor of Engineering (Robotics and Mechatronics)/ Bachelor of Science (Computer Science and Software Engineering), , Bachelor of Science (Information Technology), , Bachelor of Engineering (Telecommunication and Network Engineering), Bachelor of Engineering (Telecommunication and Network Engineering)/ Bachelor of Science (Computer Science and Software Engineering) and Bachelor of Applied Information and Communication Technology.Aims and objectives
The aim of this unit is to expose students to the range of project management practices that are used in contemporary software development projects, so that they learn and understand the major issues that project managers have to handle.
Learning Outcomes
After successfully completing this unit, students should be able to:
Learning Outcomes
After successfully completing this unit, students should be able to:
- Identify the fundamental issues that a project manager has to consider, and describe, chiefly in the context of software development projects, what approaches exist to manage these issues
- Identify and analyse software project activities using contemporary work breakdown techniques
- Identify and apply selected techniques for estimating the effort and duration of project activities
- Construct a schedule of project activities using contemporary planning techniques
- Construct a quality model for a software development project, including identification of suitable quality attributes, suitable metrics for measuring these, and suitable threshold values for these metrics to indicate acceptable quality
- Describe implications in terms of scope, time, cost and quality in taking a certain action for a given project scenario
- Identify and record the nature of software quality defects in such a way that facilitates reproduction and correction
- Identify and prioritise project risks based on the impact and probability within the context of the project and propose techniques to manage these risks
- Select, use and describe techniques for tracking the progress and status of a project
Swinburne Engineering Competencies for this Unit of Study
This Unit of Study will contribute to you attaining the following Swinburne Engineering Competencies:
This Unit of Study will contribute to you attaining the following Swinburne Engineering Competencies:
- Discipline Specific: Proficiently applies advanced technical knowledge of the specific discipline within that context.
- Professional Practice: Appreciates the principles of professional engineering practice in a sustainable context.
- Engineering Methods: Applies engineering methods in practical applications.
- Problem Solving: Systematically uses engineering methods in solving complex problems.
- Project Management: Systematically uses engineering methods in conducting and managing projects.
- Communication: Demonstrates effective communication to professional and wider audiences.
- Information Management: Demonstrates seeking, using, assessing and managing information.
- Professional Self: Demonstrates professionalism.
- Management of Self: Demonstrates self-management processes.
Content
Project Management Issues
- Scope, Time, Cost, Quality
- Risk
- Work breakdown structures
- Estimation techniques
- Project Planning techniques
Risk management
- Common project risk categories
- Risk identification and prioritisation
- Managing risks using spikes
Quality Management
- Defect identification and classification
- Quality reviews
- Defect reporting
- Change logs
Measurement
- Size and complexity metrics
- Metrics tools
- Relationships between defects and metrics
Tracking and Reporting
Reading materials
Kent Beck and Martin Fowler, Planning Extreme Programming, Addison-Wesley, 2001.
Scott Berkun, The Art of Project Management, O’Reilly, 2005.
Bob Hughes and Mike Cotterell, Software Project Management (5th Edition), McGraw-Hill, 2009.
Robert K. Wysocki, Effective Project Management (5th Edition), Wiley, 2009.
Jim Highsmith, Agile Project Management – Creating Innovative Projects, Addison-Wesley, 2004.
Roger S. Pressman, Software Engineering – A Practitioners Approach (7th Edition), McGraw-Hill, 2010.
Ken Schwaber and Mike Beedle, Agile Software Development with SCRUM, Prentice Hall, 2001.
Additional references will be given during the semester.
Scott Berkun, The Art of Project Management, O’Reilly, 2005.
Bob Hughes and Mike Cotterell, Software Project Management (5th Edition), McGraw-Hill, 2009.
Robert K. Wysocki, Effective Project Management (5th Edition), Wiley, 2009.
Jim Highsmith, Agile Project Management – Creating Innovative Projects, Addison-Wesley, 2004.
Roger S. Pressman, Software Engineering – A Practitioners Approach (7th Edition), McGraw-Hill, 2010.
Ken Schwaber and Mike Beedle, Agile Software Development with SCRUM, Prentice Hall, 2001.
Additional references will be given during the semester.