Topic
Software product management
About: Software product management is a research topic. Over the lifetime, 177 publications have been published within this topic receiving 4292 citations.
Papers published on a yearly basis
Papers
TL;DR: A method for optimally allocating requirements to increments, a means of assessing and optimizing the degree to which the ordering conflicts with stakeholder priorities within technical precedence constraints, and an overall method aimed at the continuous planning of incremental software development are provided.
Abstract: To achieve higher flexibility and to better satisfy actual customer requirements, there is an increasing tendency to develop and deliver software in an incremental fashion. In adopting this process, requirements are delivered in releases and so a decision has to be made on which requirements should be delivered in which release. Three main considerations that need to be taken account of are the technical precedences inherent in the requirements, the typically conflicting priorities as determined by the representative stakeholders, as well as the balance between required and available effort. The technical precedence constraints relate to situations where one requirement cannot be implemented until another is completed or where one requirement is implemented in the same increment as another one. Stakeholder preferences may be based on the perceived value or urgency of delivered requirements to the different stakeholders involved. The technical priorities and individual stakeholder priorities may be in conflict and difficult to reconcile. This paper provides (i) a method for optimally allocating requirements to increments; (ii) a means of assessing and optimizing the degree to which the ordering conflicts with stakeholder priorities within technical precedence constraints; (iii) a means of balancing required and available resources for all increments; and (iv) an overall method called EVOLVE aimed at the continuous planning of incremental software development. The optimization method used is iterative and essentially based on a genetic algorithm. A set of the most promising candidate solutions is generated to support the final decision. The paper evaluates the proposed approach using a sample project.
506 citations
TL;DR: It is found that with increasing institutionalization of a consistent and empowered product management role, the success rate of projects in terms of schedule predictability, quality and project duration improves.
182 citations
TL;DR: The introduction of a method for the application of SCRUM principles to software product management results in the 'agile requirements refinery', an extension to the SCRum process that enables product managers to cope with complex requirements in an agile development environment.
Abstract: Context: Although agile software development methods such as SCRUM and DSDM are gaining popularity, the consequences of applying agile principles to software product management have received little attention until now. Objective: In this paper, this gap is filled by the introduction of a method for the application of SCRUM principles to software product management. Method: A case study research approach is employed to describe and evaluate this method. Results: This has resulted in the 'agile requirements refinery', an extension to the SCRUM process that enables product managers to cope with complex requirements in an agile development environment. A case study is presented to illustrate how agile methods can be applied to software product management. Conclusions: The experiences of the case study company are provided as a set of lessons learned that will help others to apply agile principles to their software product management process.
163 citations
Book•
15 Jan 2009
TL;DR: The core elements of software product management and pricing are discussed and recommendations are given on how to deal with these elements depending on different types of organizations and products in order to achieve the long-term success.
Abstract: Software product management and pricing are key success factors for any organization providing software, be it a software company or an organization responsible for software in a company that belongs to a different industry. After defining the term "software product" and looking at the business and organizational sides, the core elements of software product management and pricing are discussed. Recommendations are given on how to deal with these elements depending on different types of organizations and products in order to achieve the long-term success.
138 citations
4 Jun 2010
TL;DR: In this article, a generic method for developing focus area maturity models based on both extensive industrial experience and scientific investigation is presented, which is used for enterprise architecture and software product management.
Abstract: Maturity models are a well-known instrument to support the improvement of functional domains in IS, like software development or testing While maturity models may share a common structure, they have to be developed anew for each functional domain Focus area maturity models are distinguished from fixed-level maturity models, like CMM, in that they are especially suited to the incremental improvement of functional domains In this paper we present a generic method for developing focus area maturity models based on both extensive industrial experience and scientific investigation In doing so, we show two examples of focus area maturity models, one for enterprise architecture and one for software product management We used a design science research process to develop the method presented.
135 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2022 | 1 |
| 2021 | 3 |
| 2020 | 5 |
| 2019 | 10 |
| 2018 | 9 |
| 2017 | 12 |