On completion of this course, the student should:

- show familiarity with development of products that may include software, electronic and mechanical components,
- demonstrate comprehension of practical aspects of Agile product development, including project planning and different activities,
- display knowledge of tools and methods for different activities of project work acquired in the first year courses relevant for the respective area

- demonstrate the ability to sustain cross-discipline teams for product development
- demonstrate the ability to deliver intermediate results in an iterative and incremental fashion
- demonstrate the ability to draw a project to a satisfactory conclusion

- demonstrate an understanding of different roles in cross-discipline teams during product development
- demonstrate the ability to identify, plan and implement enhancements to an existing product

The course supports student teams in the specification and delivery of a software product. The requirement for the product may originate from an external company or organisation, from a need internal to the University, or from an original idea from the students. The software product will be developed through an Agile lifecycle, with clearly defined intermediate deliverable points leading to project closure ready for hand-off to future development or maintenance.
The course covers the following aspects of software delivery:
- Requirements, design and test specification
- Prototype development and unit testing
- Test-driven development (TDD) and paired programming
- Simplest design, continuous redesign and refactoring
- Integration and system testing
- Behaviour-driven development and acceptance testing
- Release planning

The course will consist primarily of practical work, supported by supervision meetings and review seminars. Students will work in teams..

The teaching is conducted in English.

Passed courses at least 90 credits within the major subject in Computer Engineering, Electrical Engineering (with relevant courses in Computer Engineering), Informatics, Computer Science, Interaction Design (with relevant courses in web programming) or equivalent, and completed courses Product Development in Cross-discipline Teams 1,6 credits and either Software Product Architectures - From Chip to Enterprise, 7,5 credits and Software Product Quality Assurance, 6 credits or User Experience Design, 6 hp and Enterprise Architecture and IT Architecture, 7,5 credits. Proof of English proficiency is required (or the equivalent).

The course is graded 5,4,3 or Fail.

The final grade for the course is based upon a balanced set of assessments.
The final grade will only be issued after satisfactory completion of all assesments.

Name of the Test	Value	Grading
Project work	8 credits	5/4/3/U
Report and presentation	1 credit	5/4/3/U

The product development project will continue work on the code base delivered at the end of Part 1. For situations where this is not possible (for example, exchange students or where teams have had to be reformed), then alternative arrangements will be made.

The literature list for the course will be provided one month before the course starts
Suryanarayana, G., Samarthyam, G., & Sharma, T., Refactoring for software design smells: Managing technical debt., Morgan Kaufmann (2014).
Humble, J., & Farley, D., Continuous delivery: reliable software releases through build, test, and deployment automation., Pearson Education (2010).
Hunt, A., & Thomas, D., The pragmatic programmer: from journeyman to master., Addison-Wesley Professional (2000).