軟體新創公司 (Software startup) 致力於推出新的產品，並建立一個可穩定獲利且成長的商業模式，以轉型為成功的軟體公司。在新創公司所面臨的不確定性以及資源缺乏等條件限制的影響下，新創公司對於確保產品成功，成長並且轉型為一般的軟體公司有著迫切的需求。新創公司必須擴大目標客群、消弭產品開發過程中的不確定性，並且建立一個能夠讓公司成長的商業模式，以確保產品的成功。為了消弭不確定性，新創公司會頻繁地釋出產品到市場上進行產品驗證，並且根據客戶回饋來調整產品的定位。本研究提出一個挑選需求排序準則的方法，在規劃產品發佈內容 (Release planning) 時，藉由挑選需求排序準則 (Requirement prioritization criteria selection) 來決定產品發佈的內容，並協助新創公司定位產品價值。為了呈現此方法在新創公司的適用性，此研究以一新創公司進行案例分析，結果指出，透過此方法，新創公司能夠在鎖定的領域、產品類型及目標客群中，定位產品價值，並確認產品與市場的契合度。

Software startups focus on creating innovative products and building a profitable, scalable, and repeatable business model to turn into a successful software company. Due to the uncertainty and the lack of resources, startups are in urgent need of making the products successful and turning into established companies. In order to succeed, startups have to enlarge their target customers, eliminate the uncertainty, and build a business model that allows them to survive and grow. To eliminate the uncertainty, startups iteratively and frequently release products into the market to collect customer feedback and evaluate their products. Startups adjust their products based on the customer feedback. In this thesis, a requirement prioritization criteria selection methodology is proposed for identifying customer value propositions. A case study is conducted to investigate the applicability of the methodology. The result shows that the methodology is able to identify the customer value propositions and establish product/market fit for startups under the application domain, product type, and target customers that startups have set.

[1] J. Azar, R. K. Smith, and D. Cordes. Valueoriented requirements prioritization in a small development organization. IEEE Software, 24(1):32-37, Jan 2007.
[2] S. S. Bajwa, X. Wang, A. N. Duc, R. M. Chanin, R. Prikladnicki, L. B. Pompermaier, and P. Abrahamsson. Start-ups must be ready to pivot. IEEE Software, 34(3):18–22, May 2017.
[3] S. S. Bajwa, X. Wang, A. Nguyen Duc, and P. Abrahamsson. “failures” to be celebrated: an analysis of major pivots of software startups. Empirical Software Engineering, 22(5):2373–2408, Oct 2017.
[4] S. Blank. The Four Steps to the Epiphany: Successful Strategies for Products that Win. Lulu Enterprises Incorporated, 2003.
[5] S. Blank, S. Blank, and B. Dorf. The Startup Owner’s Manual: The Stepbystep Guide for Building a Great Company. K&S Ranch, Incorporated, 2012.
[6] B. W. Boehm. ValueBased Software Engineering: Overview and Agenda, pages 3–14. Springer Berlin Heidelberg, 2006.
[7] J. Bosch, H. H. Olsson, J. Björk, and J. Ljungblad. The early stage software startup development model: A framework for operationalizing lean principles in software startups. In Lean Enterprise Software and Systems, pages 1–15, 2013.
[8] Carmel. Time-to-completion in software package startups. In Proceedings of the TwentySeventh Hawaii International Conference on System Sciences, volume 4, pages 498–507, Jan 1994.
[9] C. Giardino, S. S. Bajwa, X. Wang, and P. Abrahamsson. Key challenges in earlystage software startups. In Agile Processes in Software Engineering and Extreme Programming, pages 52–63, 2015.
[10] C. Giardino, N. Paternoster, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson. Software development in startup companies: The greenfield startup model. IEEE Transactions on Software Engineering, 42(6):585–604, June 2016.
[11] C. Giardino, M. Unterkalmsteiner, N. Paternoster, T. Gorschek, and P. Abrahamsson. What do we know about software development in startups? IEEE Software, 31(5):28–32, Sep. 2014.
[12] C. Giardino, X. Wang, and P. Abrahamsson. Why earlystage software startups fail: A behavioral framework. In Software Business. Towards Continuous Value Delivery, pages 27–41, 2014.
[13] Google. Firebase, 2019.
[14] Google. Google Play Console, 2019.
[15] C. Gralha, D. Damian, A. I. T. Wasserman, M. Goulão, and J. a. Araújo. The evolution of requirements practices in software startups. In Proceedings of the 40th International Conference on Software Engineering, pages 823–833, 2018.
[16] E. Kim and S. Tadisina. Factors impacting customers’ initial trust in ebusinesses: An empirical study. In Proceedings of the 38th Annual Hawaii International Conference on System Sciences, pages 170b–170b, Jan 2005.
[17] E. Klotins, M. Unterkalmsteiner, and T. Gorschek. Software engineering in startup companies: An analysis of 88 experience reports. Empirical Software Engineering, 24(1):68–102, Feb 2019.
[18] A. J. Ko. A threeyear participant observation of software startup software evolution. In Proceedings of the 39th International Conference on Software Engineering: Software Engineering in Practice Track, pages 3–12, 2017.
[19] B. May. Applying lean startup: An experience report – lean lean ux by a ux veteran: Lessons learned in creating launching a complex consumer app. In 2012 Agile Conference, pages 141–147, Aug 2012.
[20] A. NguyenDuc, P. Seppänen, and P. Abrahamsson. Huntergatherer cycle: A conceptual model of the evolution of software startups. In Proceedings of the 2015 International Conference on Software and System Process, pages 199–203, 2015.
[21] H. H. Olsson and J. Bosch. Towards continuous customer validation: A conceptual model for combining qualitative customer feedback with quantitative customer observation. In Software Business, pages 154–166, 2015.
[22] N. Paternoster, C. Giardino, M. Unterkalmsteiner, T. Gorschek, and P. Abrahamsson. Software development in startup companies: A systematic mapping study. Information and Software Technology, 56(10):1200–1218, 2014.
[23] N. Riegel and J. Doerr. A systematic literature review of requirements prioritization criteria. In Requirements Engineering: Foundation for Software Quality, pages 300–317, 2015.
[24] E. Ries. The Lean Startup: How Today’s Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses. Crown Business, 2011.
[25] P. Rodríguez, E. Mendes, and B. Turhan. Key stakeholders’ value propositions for feature selection in softwareintensive products: An industrial case study. IEEE Transactions on Software Engineering, 2018.