Print as pdf if you want a pdf! If you want a nicer printout, click off the browser's automatically added header and footer.
Blekinge Institute of Technology
Department of Software Engineering
Revision: 1
Reg.no: BTH-4.1.14-0183-2026
Course syllabus
Software Startups and Software-Intensive Product Management
Software Startups and Software-Intensive Product Management
7.5 credits (7,5 högskolepoäng)
Course code: PA1491
Main field of study: Software Engineering, Computer Science
Disciplinary domain: Technology
Education level: First-cycle
Specialization: G1F - First cycle, has less than 60 credits in first-cycle course/s as entry requirements
Language of instruction: English
Applies from: 2026-03-10
Approved: 2026-03-10
1. Descision
This course is established by Dean 2025-09-15. The course syllabus is approved by Head of Department of Software Engineering 2026-03-10 and applies from 2026-03-10.
2. Entry requirements
Admission to the course requires completed courses equivalent to 40 credits in the main field of study Software Engineering and/or Computer Science, including 12 credits from project courses.
3. Objective and content
3.1 Objective
The aim of this course is to prepare the students to collaborate in a group on exploring the business feasibility of a software-intensive product or service idea and understanding the main elements of entrepreneurship and innovation in software industry.
3.2 Content
The course focuses on aspects related to creating software-intensive products or services and exploring their business feasibility. The course covers knowledge and activities related to creating a business model, defining value proposition, building minimum-viable product, the lean startup principles, and continuous experimentation. The course also covers aspects related to understanding the potential customers for the product, identifying the product features, product quality aspects, and packaging them into a product roadmap and financing plan. The course also introduces the concept of Pivot in software startups and helps understand how to adjust the idea to the changing needs.
4. Learning outcomes
The following learning outcomes are examined in the course:
4.1. Knowledge and understanding
On completion of the course, the student will be able to:
- Explain innovation challenges for creating software-intensive products or services, understanding the principles of minimum-viable product, lean startup, and continuous experimentation.
- Explain the process of identifying product features and how to package them in releases and align with the product roadmap and financing plan.
4.2. Competence and skills
On completion of the course, the student will be able to:
- Develop a business plan for the software-intensive product or service, including the value proposition, intendent market segments and main features and quality aspects.
- Develop a product roadmap and financial plan for a software-intensive product or service including the timeline and associated main risks.
4.3. Judgement and approach
On completion of the course, the student will be able to:
- Evaluate the business feasibility of an example software-intensive product or service, including value proposition, potential customers and product features.
5. Learning activities
The course is organized around several lectures and seminars where the students are expected to actively participate and reflect on the concepts introduced and discussed in this course. The lectures together with practical sessions constitute the pillars over which the group assignments are built upon. The two assignments consist of developing various aspects associated with creating software-intensive products or services in which the students are intended to apply the concepts methods and techniques presented in class. The course contains a presentation where students reflect on their experiences and lessons learned.
6. Assessment and grading
Modes of examinations of the course
| Code | Module | Credit | Grade |
| 2610 | Written Assignment 1 | 3 credits | GU |
| 2620 | Written Assignment 2 | 3 credits | GU |
| 2630 | Presentation | 1.5 credits | GU |
The course will be graded G Pass, UX Failed result, a little more work required, U Fail.
The examiner may carry out oral follow-up of written examinations.
The information before the start of the course states the assessment criteria and make explicit in which modes of examination that the learning outcomes are assessed.
An examiner can, after consulting the Disability Advisor at BTH, decide on a customized examination form for a student with a long-term disability to be provided with an examination equivalent to one given to a student who is not disabled.
7. Course evaluation
The course evaluation should be carried out in line with BTH:s course evaluation template and process.
8. Restrictions regarding degree
The course can form part of a degree but not together with another course the content of which completely or partly corresponds with the contents of this course.
9. Course literature and other materials of instruction
Nguyen-Duc, A., Münch, J., Prikladnicki, R., Wang, X., & Abrahamsson, P. (2020). Fundamentals of Software Startups. Springer International Publishing.
de Mol, E. (2019). What makes a successful startup team. Harvard Business Review.
Boehm, B. W. (1991). Software risk management: principles and practices. IEEE software, 8(1), 32-41.
Gans, J., Scott E., and Scott, S. E. (2018). Strategy for start-ups Harvard Business Review.
Ries, E. (2011). The lean startup: How today's entrepreneurs use continuous innovation to create radically successful businesses. Crown Currency.