Module Details |
The information contained in this module specification was correct at the time of publication but may be subject to change, either during the session because of unforeseen circumstances, or following review of the module at the end of the session. Queries about the module should be directed to the member of staff with responsibility for the module. |
Title | MANAGING SOFTWARE PROJECTS | ||
Code | CKIT538 | ||
Coordinator |
Mr K Dures Computer Science K.Dures@liverpool.ac.uk |
||
Year | CATS Level | Semester | CATS Value |
Session 2022-23 | Level 7 FHEQ | Whole Session | 15 |
Aims |
|
1. To provide students with a deep and systematic understanding of software project management skills as evidenced by leading industry examples and state-of-the-art research. 4. Provide student with the necessary skills to allow them to manage software projects successfully from inception to close. |
Learning Outcomes |
|
(LO1) An ability to critically assess strategies for the management of project scope, budget and schedule. |
|
(LO2) Comprehensive ability to evaluate and develop cost estimates for software projects, with respect to both human and non-human resources. |
|
(LO3) A comprehensive ability to analyse how to best monitor and control projects as well as how to facilitate a strong communication plan. |
|
(LO4) An ability to critically evaluation software quality and how to integrate evaluation into the project goals. |
|
(LO5) A deep and systematic ability to assess software and hardware project requirements. |
|
(LO6) A comprehensive knowledge of the issues that affect team productivity and how they can be resolved. |
|
(S1) Organisational skills |
|
(S2) IT skills |
|
(S3) Communication and collaboration online participating in digital networks for learning and research |
|
(S4) Information literacy online, finding, interpreting, evaluating, managing and sharing information |
|
(S5) Learning skills online studying and learning effectively in technology-rich environments, formal and informal |
|
(S6) Problem solving/ critical thinking/ creativity analysing facts and situations and applying creative thinking to develop appropriate solutions. |
|
(S7) Team (group) working respecting others, co-operating, negotiating / persuading, awareness of interdependence with others |
Syllabus |
|
Week 1: Managing software projects - scope, schedule, costs and risk. Week 5: Roles and resources in software projects, what influences the adoption of established and emerging approaches and methodologies such as Agile and SCRUM? |
Teaching and Learning Strategies |
|
Teaching Method 1 - online Learning |
Teaching Schedule |
Lectures | Seminars | Tutorials | Lab Practicals | Fieldwork Placement | Other | TOTAL | |
Study Hours |
60 |
60 | |||||
Timetable (if known) | |||||||
Private Study | 90 | ||||||
TOTAL HOURS | 150 |
Assessment |
||||||
EXAM | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
CONTINUOUS | Duration | Timing (Semester) |
% of final mark |
Resit/resubmission opportunity |
Penalty for late submission |
Notes |
Report: Group Project in Software Management (Part 4) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 7 to 8 | 0 | 10 | ||||
Report: Group Project on Software Management (Part 3) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Weeks 5 to 6 | 0 | 9 | ||||
Report: Analysis of failed software projects - what can we learn? Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 5 | 0 | 9 | ||||
Report: Group Project on Software Management (Part 2) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 4 (assigned in week 3 | 0 | 9 | ||||
Case study analysis: Software project management Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 3 | 0 | 9 | ||||
Report: Group Project on Software Management (Part 1) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Week 2 | 0 | 9 | ||||
Report: Review of industry architecture methodologies, standards and practices Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :W | 0 | 9 | ||||
Moot/debate: Weekly discussion questions (eight) Standard UoL penalty applies for late submission. This is not an anonymous assessment. Assessment Schedule (When) :Whole session | 0 | 36 |
Recommended Texts |
|
Reading lists are managed at readinglists.liverpool.ac.uk. Click here to access the reading lists for this module. |