INMR65-IT Project Management
Module Provider: Business Informatics, Systems and Accounting
Number of credits: 20 [10 ECTS credits]
Level:7
Terms in which taught: Spring term module
Pre-requisites:
Non-modular pre-requisites:
Co-requisites:
Modules excluded:
Current from: 2022/3
Module Convenor: Prof Yinshan Tang
Email: y.tang@henley.ac.uk
Type of module:
Summary module description:
Detailed descriptions of the delivery methods coupled with the assessment details have been included in this module description. The module consists of theoretical foundation with practical focus for the topic of IT project management. The assessment uses a real-life case scenario asking the students to apply theories and techniques learned from this module.
Aims:
To understand management theories associated with management principles and most up-to-date methodologies including project planning and delivery for different types of IT projects. After completing the module, students will be able to carry out project planning with different methods, exercise risk management and quality control techniques. Students will also be able to understand the characteristics of IT projects and measures on how to improve the success rate. Understand how to use change control to manage scope changes.
Assessable learning outcomes:
After completing this module, students should be able to demonstrate the following learning outcomes:
- Understand theories and principles for project management;
- Analyse requirements of projects in an organisational context;
- Apply methodologies for IT project management;
- Select and use appropriate project planning, risk management, and quality control techniques.
Intended learning outcomes:
- Understand the fundamentals of management theories;
- Understand the characteristics of IT projects;
- To be able to use popular management methods.
Additional outcomes:
- Understand the differences of current popular project management methodologies, such as: PMBoK, PRINCE2, Agile;
- Understand the relationships between project management and software development life cycle;
- Understand management strategies and theories and their development history.
Outline content:
(If naming individual staff, a caveat is required ‘the staffing of modules is correct at the time of writing/publication’):
The content will cover the following areas:
- concepts and principles of project management;
- project management in organisations;
- methodologies (e.g., Agile and PRINCE2) for project management.
- project planning (e.g., estimating, scheduling, resourcing, and monitoring);
- risk management;
- quality control mechanisms.
Global context:
Business values of project management;
- Problem analysis and problem-solving capabilities;
- Report preparation and writing;
- Presentation skills;
- Team work.
Brief description of teaching and learning methods:
A range of teaching and learning methods will be employed, but will focus largely on lectures, in-class practical, group work and independent supported learning. Special attention will be given to the use of project management applied to the course itself. Learning technology support via the Internet and learning management systems in the future.
Autumn | Spring | Summer | |
Lectures | 20 | ||
Seminars | 10 | ||
Guided independent study: | |||
Wider reading (independent) | 40 | ||
Wider reading (directed) | 20 | ||
Completion of formative assessment tasks | 110 | ||
Total hours by term | 0 | 200 | 0 |
Total hours for module | 200 |
Method | Percentage |
Written assignment including essay | 100 |
Summative assessment- Examinations:
None
Summative assessment- Coursework and in-class tests:
Students are required to produce a 5,000 word report based on a given case study. Within the report the students are expected to:
- Explain and compare how quality is assured when using Agile and Prince 2 methods;
- Review and explain how the principle focus of management theories have been developed from tasks to contingency approaches;
- Explain how changes in management theories is applicable to IT project managements;
- Prepare the product breakdown structure base on the scenario and explain how the PBS is used in preparing project plans.
Formative assessment methods:
One exercise is included during the module delivery focusing on the product break down methodologies with popular daily activities. Feedback and comments are provided. The exercise will allow the student with hand on experience to carry out planning in their future work environment.
Assessment will consist of coursework only.
Penalties for late submission:
(University standard penalties for late submission are automatically generated):
The Module Convener will apply the following penalties for work submitted late:
- where the piece of work is submitted after the original deadline (or any formally agreed extension to the deadline): 10% of the total marks available for that piece of work will be deducted from the mark for each working day (or part thereof) following the deadline up to a total of five working days;
- where the piece of work is submitted more than five working days after the original deadline (or any formally agreed extension to the deadline): a mark of zero will be recorded.
The University policy statement on penalties for late submission can be found at:
http://www.reading.ac.uk/web/FILES/qualitysupport/penaltiesforlatesubmission.pdf
Assessment requirements for a pass:
Students will be required to obtain a mark of 50% overall based on the coursework.
Pass criteria - To pass this module, the students must demonstrate their overall knowledge, understanding and perception of the concepts and principles of the methods. They should be able to analyse and design an organisation with knowledge management.
Reassessment arrangements:
(During the August University Resit Period). Students will be required to obtain a mark of 50% based on resubmission of the coursework.
Additional Costs (specified where applicable):
Cost | Amount |
---|---|
1. Required text books | £60.00 per student |
Last updated: 22 September 2022
THE INFORMATION CONTAINED IN THIS MODULE DESCRIPTION DOES NOT FORM ANY PART OF A STUDENT'S CONTRACT.