Short answer

When designing solutions for software start-ups, consider how their needs and priorities change as they move from early-stage development to growth and maturity, and provide adaptable tools and guidance.

Field: Innovation & Design
Source: IEEE Transactions on Software Engineering (2019)
Method: Case survey method combined with open coding, cross-case analysis, and statistical analysis.
Sample: 84 start-up cases
Evidence: Strong effect

Software engineering goals, challenges, and practices in start-ups are not static but evolve significantly across different stages of the company's lifecycle, from inception to maturity. This innovation & design research insight is drawn from a 2019 study published in IEEE Transactions on Software Engineering. Using Case survey method combined with open coding, cross-case analysis, and statistical analysis. with 84 start-up cases, researchers explored how this design variable affects real-world outcomes. The key design takeaway: When designing solutions for software start-ups, consider how their needs and priorities change as they move from early-stage development to growth and maturity, and provide adaptable tools and guidance.

Study

Innovation & DesignHigh ImpactStrong effect

Software Engineering Practices in Start-ups Evolve with Company Lifecycle

Software engineering goals, challenges, and practices in start-ups are not static but evolve significantly across different stages of the company's lifecycle, from inception to maturity.

IEEE Transactions on Software Engineering · 2019

Key Findings

01Identified 16 common goals, 9 common challenges, and 16 common engineering practices in software start-ups.
02These goals, challenges, and practices were mapped to the start-up lifecycle stages: inception, stabilization, growth, and maturity.
03The primary software engineering challenge for start-ups is the simultaneous evolution of multiple process areas with minimal room for error.

Application

Design takeaway

How to apply

When developing a new software tool or process for start-ups, consider creating different configurations or feature sets tailored to companies in their inception, stabilization, growth, or maturity phases.

Project actions

01When researching a product for a new company, consider how its needs might change over time.
02Think about how your design could be adapted for different stages of a company's growth.

Method & Evidence

AimTo develop a progression model of software engineering goals, challenges, and practices within start-up companies, mapping them to distinct lifecycle stages.

MethodCase survey method combined with open coding, cross-case analysis, and statistical analysis.

ProcedureResearchers gathered in-depth experiences from a large sample of software start-ups. They analyzed this data to identify common goals, challenges, and practices, and then mapped these findings to different start-up lifecycle stages (inception, stabilization, growth, and maturity) to create a progression model.

Sample84 start-up cases

ContextSoftware start-ups

Variables

IVStart-up lifecycle stage (inception, stabilization, growth, maturity)

DVSoftware engineering goals, challenges, and practices

CVType of start-up (software-intensive), company size, funding stage (implicitly, as these relate to lifecycle)

Strengths & Limitations

Strengths

+Large sample size of 84 start-ups provides robust data.
+Combines qualitative (coding, analysis) and quantitative (statistical) methods for comprehensive findings.
+Focuses on a specific, important context (software start-ups).

Limitations

This study is specific to software start-ups. Your own design project might involve different types of companies or industries with unique evolutionary paths.

Reliability & validity

Reliability: The use of a case survey method with multiple researchers and cross-case analysis aims to enhance reliability. Validity: Triangulation of methods (case survey, coding, statistical analysis) and corroboration of findings with statistical analysis contribute to construct validity. However, reliance on self-reported data in case studies can introduce biases.

Think critically

How might the 'minimal margin for serious errors' challenge influence the design of collaborative tools or automated testing systems for start-ups?

Design Principles

"Lifecycle-aware design: Solutions should adapt to the evolving needs and maturity of the user or organization."

Understanding this evolution is crucial for designing effective support systems and strategies for software start-ups. It allows for tailored interventions that address the specific needs and constraints of a company at each stage, rather than applying a one-size-fits-all approach.

What This Means for Your Design

Software companies change how they build software as they get bigger and older, and designers need to create tools that fit these changing needs.

How to use in your project

1.Use this research to justify why your design solution is appropriate for a start-up at a specific stage of its lifecycle.
2.Refer to the identified goals, challenges, and practices to inform your design requirements and features.

Add to My Project

Quick Cite

Paragraph starter

This research highlights that software engineering practices within start-ups are not static but evolve significantly across the company's lifecycle stages. By understanding this progression, designers can create more effective and relevant solutions that adapt to the changing goals and challenges faced by start-ups from inception through to maturity, ensuring long-term utility and impact.

Source

IEEE Transactions on Software Engineering

A Progression Model of Software Engineering Goals, Challenges, and Practices in Start-Ups

journal · 2019

View source

Questions About This Research

What does the research say about software engineering practices in start-ups evolve with company lifecycle?: When designing solutions for software start-ups, consider how their needs and priorities change as they move from early-stage development to growth and maturity, and provide adaptable tools and guidance. Evidence: IEEE Transactions on Software Engineering (2019).
Why does "Software Engineering Practices in Start-ups Evolve with Company Lifecycle" matter for design?: Understanding this evolution is crucial for designing effective support systems and strategies for software start-ups. It allows for tailored interventions that address the specific needs and constraints of a company at each stage, rather than applying a one-size-fits-all approach.
How can designers apply this research?: When designing solutions for software start-ups, consider how their needs and priorities change as they move from early-stage development to growth and maturity, and provide adaptable tools and guidance.
What were the main findings?: Identified 16 common goals, 9 common challenges, and 16 common engineering practices in software start-ups.. These goals, challenges, and practices were mapped to the start-up lifecycle stages: inception, stabilization, growth, and maturity.. The primary software engineering challenge for start-ups is the simultaneous evolution of multiple process areas with minimal room for error.
What research method was used?: Case survey method combined with open coding, cross-case analysis, and statistical analysis. with 84 start-up cases.
How strong is the evidence?: Evidence strength is rated Strong effect, based on a 2019 journal from IEEE Transactions on Software Engineering.
What should I do differently in my next project?: When developing a new software tool or process for start-ups, consider creating different configurations or feature sets tailored to companies in their inception, stabilization, growth, or maturity phases.
What are the limitations?: The study focuses on software start-ups; findings may not directly apply to hardware start-ups or non-software-intensive companies. The 'progression model' is based on aggregated data and individual start-up experiences may vary.