Swinburne University of Technology - Melbourne Australia
Future Students - Courses
Duration
Contact Hours
Campus
Prerequisite
Corequisite
1 Semester or equivalent
48 hours
Hawthorn, Sarawak
HIT2308 Software Development Practices or HIT1031 Introduction to Software Engineering or (75% in HIT2405 Requirements Analysis and Modelling and 2nd level programming eg. HIT2037 Software Development in Java or HIT3181 Technical Software Development. Preclusions: HIT2056 Software Project Management, HIT3407 Information Systems Project Management.
Nil
Credit Points: 12.5 Credit Points
A unit of study in the Bachelor of Engineering (Robotics and Mechatronics)/ Bachelor of Science (Computer Science and Software Engineering), Bachelor of Science (Computer Science), Bachelor of Science (Information Technology), Bachelor of Science (Professional Software Development), 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.
The aim of this unit is to expose students to the range of project management practices that are used in contemporary software development projects. Learning OutcomesAfter successfully completing this unit, students should be able to: Identify and classify project activities using contemporary work breakdown techniquesEstimate duration and schedule project activities using contemporary planning techniquesDescribe implications in terms of scope, time, cost and quality in taking a certain action for a given project scenarioIdentify and document the nature of defects in software in such a way that facilitates reproduction and correctionMeasure the size and complexity of code, and use these measures to identify defect-prone areasIdentify and prioritise risks based on the impact and probability within the context of the project and propose techniques to manage these risksUse and describe techniques for tracking the progress and status of a project
Lecture (24 hrs), Tutorial (24 hrs)
Examination, assignments, on-going assessment tasks
Project Management Issues Scope, Time, Cost, QualityRiskWork breakdown structuresEstimation techniquesProject Planning techniques Risk management Common project risk categoriesRisk identification and prioritisationManaging risks using spikes Quality Management Defect identification and classificationQuality reviewsDefect reportingChange logs Measurement Size and complexity metricsMetrics toolsRelationships between defects and metrics Tracking and Reporting
Project Management Issues
Risk management
Quality Management
Tracking and Reporting
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.