|Period:||Possible in any periode individually|
|Participants:||see Osiris Docent|
|Schedule:||Official schedule representation can be found in Osiris|
ICT Startups is a domain that is relatively new as a research field: it concerns the definition and study of success in ICT entrepreneurship. It has as a goal to support the practitioner field, whether that is incubators, entrepreneurs, software engineers, software product managers, chief technology officers, or entrepreneurship lecturers, with up to date knowledge and practices. These should in turn support entrepreneurs in better decision making in their daily, and often nightly, work. One of the main aspects of this work concerns the construction and engineering of ICT products and services.
ICT Startups is a continuation course of ICT Entrepreneurship: it cannot be followed without first successfully finishing ICT Entrepreneurship.
After this course a student should:
The way in which the learning goals are achieved are:
The research project in the course can be about one of the following topics:Startups and new venture creation
Success factors for software-intensive startups
Software startup processes
Disruptive innovation and adoption of startups
Managing startup and growth hacking
Intertwined software product and business model development
Platform-based business models and value co-creation
Software Development and Product Management
Software engineering management and productivity
Speeding up time-to-market
Effective business model transformation and improvement
Software Business Development
Business modeling for software products and services
Economics of software companies
Internationalization of software-intensive companies
New ideas and emerging areas
Disruptive trends in software business
Business Analytics, data analytics
The future of software-intensive business
Software business and entrepreneurship education
Game business and gamification in software-intensive business
Ries, E. (2011), The Lean Startup: How Constant Innovation Creates Radically Successful
Businesses. Kindle Edition, Penguin Books Limited. New York, NY.
Osterwalder, A., Pigneur, Y., Bernarda, G. & Smith, A. (2014), Value proposition design: How to create products and services customers want, John Wiley & Sons.
Paternoster, N., Giardino, C., Unterkalmsteiner, M., Gorschek, T. & Abrahamsson, P. (2014), ‘Software development in startup companies: A systematic mapping study’, Information and Software Technology 56(10), 1200–1218.
Jansen, S. & van Cann, R. (2012), Software business start-up memories: Key decisions in success stories, Springer.
Dorst, K. (2011), ‘The core of ’design thinking’ and its application’, Design studies 32(6), 521–532.
Blank, S. & Dorf, B. (2012), The startup owner’s manual: The step-by-step guide for building a great company, K&S Ranch.
Lucassen, G., Dalpiaz, F., van der Werf, J. M. E., & Brinkkemper, S. (2016). Improving agile requirements: the quality user story framework and tool. Requirements Engineering, 21(3), 383-403.
Siamak Farshidi, Slinger Jansen, Rolf de Jong & Sjaak Brinkkemper (2018) A decision support system for software technology selection, Journal of Decision Systems
The course is highly personalized and can be tailored to the ambitions of the students and the advising lecturer. A research plan must be created by the student and signed by both the course supervisor and the student before a student is allowed to enter the course. The research plan should at least list: (1) The project goal, (2) the project deliverables, (3) the project’s envisioned outcome, and (4) an assessment plan from the supervisor. The assessment plan describes how the envisioned outcome will be judged and what objectives lead to what grades for the course. A research plan is optional. If a student does not communicate with the lecturer in writing for 4 weeks or more, the supervisor may terminate the project and judge it with a “NVD”.
|Minimum effort to qualify for 2nd chance exam:||Om aan de aanvullende toets te mogen meedoen moet de oorspronkelijke uitslag minstens 4 zijn.|