5 research outputs found

    Improving IS Functions Step by Step: the Use of Focus Area Maturity Models

    Get PDF
    With new technologies developing rapidly and becoming more common, organizations need to keep up their IS capabilities. Maturity models are designed as a means to support capability development. The existing literature is strongly dominated by studies of fixed-level maturity models, i.e. maturity models that distinguish a limited set of generic maturity levels, such as the well-known CMM. We argue that, while fixed-level maturity models may be well-suited to assessing the maturity of IS capabilities, another form of maturity model, the focus area maturity model, is better suited to supporting incremental improvement. In this paper we define the concept of focus area maturity model. We use a design-science research method, basing our work on both extensive industry experience and scientific investigation

    The Sun also Sets: Ending the Life of a Software Product

    Get PDF
    Abstract. Sunsetting a software product is a painful and frustrating process, whether it happens in times of crisis or in an organized and planned manner. It is surprising that little information is available on how to perform sunsetting and it appears to be a blind spot in software product management literature. This paper describes the sunsetting method and provides practitioners with a welldefined process of how software products must be taken out of development, maintenance, and finally use. With the sunsetting method, product managers will have as little trouble as possible based on the experiences of others. The process description is elaborated using a method description. Furthermore, three retrospective case studies have been conducted to evaluate the method

    COPLAM Description and Evaluation: Method to Support Continuous Planning at the Team Level

    Get PDF
    Continuous planning refers to the planning process in rapid and parallel cycles in a way that plans evolve according to the events. We present COPLAM (Continuous Planning Adoption Method) which supports continuous planning at the team level of agile software development, which covers release, iteration, and day cycles, according to the organization’s context and projects’ needs. We also present the results of a case study in a software development organization focused on e-commerce.&nbsp
    corecore