Software Startup Book

We are inviting high-quality chapters for an edited book “Fundamentals of Software Startups: Concepts, Methods and Case studies”

A book to be published by Springer and edited by:

  • Assc. Prof. Anh Nguyen-Duc, University of South Eastern Norway.
  • Prof. Jürgen Münch, Reutlingen University
  • Assc. Prof. Pafael Prikladnicki, Pontifícia Universidade Católica do Rio Grande do Sul
  • Dr. Xiaofeng Wang, Free University of Bolzano
  • Prof. Pekka Abrahamsson, University of Jyväskylä

OVERVIEW

Software startups launch worldwide every day as a result of an increase of new markets, accessible technologies, and venture capital. “Software startups” is referred to as organizations focused on the creation of high-tech and innovative products, with little or no operating history, aiming to grow by aggressively scaling their business in highly scalable markets. Although adopting different technologies such as dynamic websites, mobile applications and embedded systems, these companies have a commonality of having software as a fundamental part of their products or services. Slack, Spotify, Snapchat, Pininterest and Github to name a few, are examples of successful software startups with fast user acquisitions and rapid growths.

While there can be many different components contributing to successful growing startups, i.e. team, finance, business, market, etc., it is not doubt about the importance of a great product. Moreover, the management of the product development is also essential for aligning development and engineering activities with business and marketing activities. Startups adopt certain approaches to develop their products, and to some extent, have a direct impact on business objective and activities. For instance, products might need to be developed in a fast way to satisfy time-to-market demands (speed). Product development needs to be agile enough to support entrepreneurs in responding to sudden opportunities and threats when arriving (agility). Many entrepreneurs and business professionals are becoming more cautious about their bottom lines, reorganizing resources, the process to minimize the redundancy and to reduce costs and to restructure their resources.
Engineering aspects of software startups does not only include the activity areas of typical software engineering, such as requirement engineering, product prototyping, design, implementation and testing, but also areas of production that are specifically important in startup context, such as idea generation, customer development, market research, and scaling the product. The book is the structured collection of empirical evidence on various phenomenon in software startups.The book will addresses practical and challenging problems for entrepreneurs, such as different types of pivoting and their consequences on product development, governance and evolution of technical debts, institutional influencing factors on startup engineering aspects, and how to maintain a sustainable outsourcing relationship. Product development matters in the book are described in the connection with human factors, market factors and ecosystem factors.

BACKGROUND TOPICS

All chapters should consider the a problem observed in community of entrepreneurs or entrepreurial education. All chapters should have empirical evidence in a form of case studies, exeriments, survey and ethnography. We do NOT accept Secondary study, such as Literature review or Systematic mapping. The book chapter should be marked with one of the four categories: (1) Fundamental phenomenon in Startups, (2) Startup engineering methodology, (3) Successful startup cases and (4) Failure startup case. Topics include, but are not restricted to, the following:

  • Pivot: i.e. how startups change their business ideas overtime
  • Minimum Viable Products: i.e. methods to effectively prototype
  • Failure: i.e. reasons startups fail
  • Success: i.e. common practices from growing startups
  • Innovation: i.e. how to measure innovation in software startups
  • Metrics: i.e. KPI, best practices with using metrics
  • Quality assurance: i.e. how to achieve good-quality products
  • Technical debt: i.e. impact of work-around code on startups
  • Startup Tools: i.e. experience on using tools in startups
  • User Experience: i.e. its impact on startup activities
  • Competence: i.e. management of the needs for skills and human resources overtime
  • Startup ecosystems: i.e. impact factors from coworking spaces, incubators, etc
  • Requirement engineering: i.e. how software startups extract and manage requirements from customers

Chapters should be accessible to entrepreneurs, business/technical people, undergraduate students and graduate students with a background in Software Engineering, Information System and Business/ Entrepreneurship.

PROCEDURE

To ensure the quality of the book, we would like to have an interactive collaboration with our invited writers. We expect high quality contribution, which will pass a peer-review process. The book chapter should be written in the following format:

  1. EXECUTIVE SUMMARY: In a few paragraphs, explain the information your chapter will cover. This section should give people a reason to continue reading. Be sure to summarise your main points and key takeaways.
  2. INTRODUCTION: Give a context of the investigated problem. Present the current understanding of the problem. State the purpose of the work in the form of the hypothesis, question, or problem you investigated. Use the active voice as much as possible. Some use of first person is okay, but do not overdo it
  3. RELATED WORK: briefly summarise relevant scientific or known publications, i.e. book, scientific papers, white papers, etc.
  4. RESEARCH METHOD: briefly describes how the results were generated
  5. MAIN POINT 1: Cluster the points you want to make. Provide evidence to support your arguments
  6. MAIN POINT 2 …
  7. CONCLUSION: Discuss the findings. Provide implications for entrepreneurs, and researchers.

IMPORTANT DATES

  • Chapters due: 28 February 2019

  • Notifications of feedbacks: 31 March 2019

 

SUBMISSION FORMAT

Submissions must conform to Springer’s LNCS format and should not exceed 15 pages, including all text, figures, references and appendices. Information about the Springer LNCS format can be found at http://www.springer.com/gp/computer-science/lncs/conference-proceedings-guidelines.

The chapter should be submitted via Easy Chair:   https://easychair.org/conferences/?conf=secse2019

Advertisements