Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant...
Transcript of Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant...
![Page 1: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/1.jpg)
Requirements Practices in Software Startups
John HoffDivision of Science & Mathematics
University of Minnesota, Morris
November 17, 2018
![Page 2: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/2.jpg)
Big Picture
• Startups are rapidly emerging• 50 million per year
• 80% failure rate• No market
• Lack of funding
• Bad teamwork and practices
• Requirements practices
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 2 / 19
![Page 3: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/3.jpg)
Outline
• Background
• The Evolution of Requirements Practices in Software Startups
• Observations from a Software Startup Chief Technology Officer (CTO)
• Conclusion
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 3 / 19
![Page 4: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/4.jpg)
Outline
• Background
• The Evolution of Requirements Practices in Software Startups
• Observations from a Software Startup Chief Technology Officer (CTO)
• Conclusion
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 4 / 19
![Page 5: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/5.jpg)
Software Startups
• What is a software startup?• Less than 10 years old
• Less than 60 employees
• Extreme uncertainty
Background
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 5 / 19
![Page 6: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/6.jpg)
Software Requirements
• Establish the software product’s needs• Example: Bank application needs a “View Balance” feature
• Stakeholders:• CEO, CTO, Software developers
• Clients
Background
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 6 / 19
![Page 7: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/7.jpg)
Requirements Practices
• Requirements Artifacts
• Knowledge Management
• Requirements-Related Roles• CEO, CTO, Developers, QA
• Planning• Estimate difficulty and prioritize
• Assign to developers
• Technical Debt
• Product Quality
Background
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 7 / 19
![Page 8: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/8.jpg)
Outline
• Background
• The Evolution of Requirements Practices in Software Startups
• Observations from a Software Startup Chief Technology Officer (CTO)
• Conclusion
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 8 / 19
![Page 9: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/9.jpg)
Research Methods
• Studied 16 startups in Europe• Interviews and attending meetings
• Three Phases of Evolution1. Informal and unstructured
2. Semi-formal and semi-structured
3. Formal and structured
The Evolution of Requirements Practices in Software Startups
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 9 / 19
![Page 10: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/10.jpg)
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 10 / 19
![Page 11: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/11.jpg)
Outline
• Background
• The Evolution of Requirements Practices in Software Startups
• Observations from a Software Startup Chief Technology Officer (CTO)
• Conclusion
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 11 / 19
![Page 12: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/12.jpg)
Company & Research Methods
• Andrew J. Ko
• Documented everyday happenings
• Study startup evolution and developer behavior without bias
Observations from a Startup Chief Technology Officer (CTO)
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 12 / 19
![Page 13: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/13.jpg)
Evolution of Requirements Practices
• Requirements Artifacts1. None
2. Based on client feedback
• Knowledge Management1. None
2. Informal and semi-structured
• Requirements-Related Roles1. Everyone does everything
2. Somewhat specific
Observations from a Startup Chief Technology Officer (CTO)
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 13 / 19
![Page 14: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/14.jpg)
Evolution of Requirements Practices
• Planning1. None
2. Based on feedback
• Technical Debt1. Known and accepted
2. Tracked and addressed
• Product Quality1. Not a concern
2. Somewhat important
Observations from a Startup Chief Technology Officer (CTO)
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 14 / 19
![Page 15: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/15.jpg)
Wrap-up
• Second phase of evolution for every practice• Never entered third phase
• 3 years old, 12 employees• Stable
Observations from a Startup Chief Technology Officer (CTO)
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 15 / 19
![Page 16: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/16.jpg)
Outline
• Background
• The Evolution of Requirements Practices in Software Startups
• Observations from a Software Startup Chief Technology Officer (CTO)
• Conclusion
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 16 / 19
![Page 17: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/17.jpg)
Conclusion
• Evolution of practices is not necessary for success
• Evolution of practices lead to company improvements• Better product
• Better work environment
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 17 / 19
![Page 18: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/18.jpg)
Questions
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 18 / 19
![Page 19: Requirements Practices in Software Startups · 2020. 4. 30. · A three-year participant observation of software startup software evolution. InProceedings of the 39th International](https://reader036.fdocuments.in/reader036/viewer/2022063019/5fe07b3759e04879b6327f98/html5/thumbnails/19.jpg)
References
• Catarina Gralha, Daniela Damian, Anthony I. (Tony) Wasserman, Miguel Goulão, and João Araújo. 2018. The evolution of requirements practices in software startups. In Proceedings of the 40th International Conference on Software Engineering (ICSE '18). ACM, New York, NY, USA, 823-833.
• Andrew J. Ko. 2017. A three-year participant observation of software startup software evolution. In Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track (ICSE-SEIP '17). IEEE Press, Piscataway, NJ, USA, 3-12.
John Hoff (U of Minn, Morris) Requirements Practices in Software Startups Nov. 17, 2018 19 / 19