On the basis of
IMT4032 Usability and Human Factors in Interaction Design
Basic knowledge of project management (e.g. SMF1212) or software engineering (e.g. IMT2243) is beneficial, but not necessary.
Expected learning outcomes
Project management applies to a wide range of tasks – including developing multimedia systems and interactive Web services. Knowledge of project management in relation to software engineering is therefore of increasing importance to practitioners.
- Students will be able to account for traditional and modern software development models and their relevance and suitability of different types of development projects, including agile software development
- Students will be able to analyze and discuss the different stages and processes in a development course, and discuss challenges related to the different stages
- Students will have experience with the project as a work form in theory and practice
- Students will be familiar with techniques for project management, estimating and risk assessment
- Students will be able to analyze and discuss the appropriateness of system models and processes and their suitability for different types of development projects, as well as be able to manage processes in a project
- Students will be able to analyze, discuss and reflect upon the role of the interaction designer in software engineering within different software engineering process models and paradigms
- Students will be able to critically reflect upon the impact of different paradigms, world and system views on software engineering, user-centered design and interaction design
- Students will be able to efficiently implement knowledge from the program's core courses within a system development and project context
- The graduate is able to contribute to innovative thinking and innovation processes
- Software Engineering methodology and models: plan-driven versus agile development methodologies, and their impact on project management (including Scrum)
- System development: requirements analysis and specification, design, implementation, testing evolution and maintenance
- Project management theory and techniques for project planning (formulation of goals, quality planning, estimation, risk assessment and management activities)
- Leadership theories and styles (full range of leadership, transactional and transformational leadership), personality types, communication, team dynamics and project leadership
- The project as a work form (including organization and group dynamics)
- The impact of paradigms (mechanical, romantic and dialectic world views) on systems thinking (hard, soft, dialectic) and the role of the interaction designer within software development
Form(s) of Assessment
Written exam, 4 hours
Form(s) of Assessment (additional text)
- Written exam, 4 hours (40%)
- Portfolio, consisting of both individual and project work in groups (60%)
- Both parts must be passed separately.
The portfolio may be both individual and team work related to a case-specific collaborative group project.
Alphabetical Scale, A(best) – F (fail)
Internal examiner. External examiner is used periodically, next time spring 2019.
Re-sit August 2016 for the Written exam.
No re-sit for the portfolio, students must hand in a new portfolio next time the course is run.
Dictionary - English/first language
Active participation in group project work.
- Ian Sommerville: Software Engineering (9.edition), Pearson.
- Rory Burke: Project Management Techniques (college edition). John Wiley.
- Transformational Leadership, Second edition, by Bernhard M. Bass and Donald E. Riggio
- Project Management Leadership, by Steve Barron & Rory Burke, ISBN 978-0-9582733-5-0
- Head First Software Development, by Dan Pilone and Russ Miles.
- Computers in Context - The Philosophy and Practice of Systems Design, by Bo Dahlblom and Lars Mathiassen
Changes may occur. Final list is presented at the beginning of the semester.