Article

A framework for improving effort management in software projects.

Software Process Improvement and Practice 11/2007; 12:549-558. DOI: 10.1002/spip.350
Source: DBLP

ABSTRACT Objective: The objective of this paper is to provide a framework for effort management in software projects to increase effort estimation accuracy. Method: We applied a multimethodological approach employing a case study and constructive research. Results: Based on the case study on four earlier proposed frameworks related to effort management and three popular process maturity assessment models, we constructed a framework to manage effort in a software project in a proactive manner, yet fulfilling the requirements of the assessment models. Conclusions: A project's software engineering process involves various functions which have an effect on the success of effort estimation. Two approaches, proactive and reactive, can be taken to manage effort in a software project. In this paper, a case study is conducted regarding both approaches. Based on the case study, we provide a new framework for effort management in software projects to increase effort estimation accuracy.

0 Bookmarks
 · 
55 Views
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Process maturity reference frameworks such as ISO/IEC 15504 and the Capability Maturity Model Integrated (CMMI) seek to assist software process improvement (SPI) efforts by prescribing a roadmap for improving the capability of the development process. However, such frameworks are not widely adopted in the practice [1], [2], especially in smaller software development organisations where the development process is often modified based on business events [3]. Such modification of the development process represents an attempt to harmonise the process with the changing needs of the business, which is a dynamic capability. Dynamic capabilities refer to the ability of businesses to adapt to changing circumstances and according to the evolutionary theory of the firm [4], organisations that possess greater dynamic capability are more successful. This paper introduces dynamic SPI capability - the ability to adapt the software process relative to changing situational circumstances – as a method for evaluating software process adaptation. KeywordsSPI–Process Adaptation–Situational Factors–Dynamic SPI Capability
    12/2010: pages 28-41;
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: The intended objective of ISP is to develop a comprehensive plan for integrated systems development. Thus, Information Strategy Planning (ISP) is the first step in order for general contractors in the construction industry to introduce Information technology (IT) to their business and project management. Due to a lack of understanding of the role of ISP in systems development, it has been often ignored or not been considered by them. In order to design and develop an integrated system flawlessly, a well-defined software development methodology must be adopted. However, most existing methodologies are proprietary intellectual property of System Integrators (SI) whose fees are too expensive to most contractors. Their methodologies are generic and it requires a thorough understanding of their methodology and business processes in construction in order to implement in an integrated systems development in construction. This paper presents a comprehensive framework of ISP for construction contractors. Methods and tools for each step will be presented and desirable deliverables will be followed. Thus, without professional system integrators, they are able to explore information technologies that might support their business needs. It also can help them to evaluate existing systems, examine their IT and business environments, define a system architecture and functional architecture, and assess the impact on their organization.
  • [Show abstract] [Hide abstract]
    ABSTRACT: Software project assessments and postmortem analyses can increase the success of future projects and forthcoming project phases. However, although assessments and analyses are well-presented in the software engineering literature, they are short of descriptions to assess effort. This paper proposes a stepwise effort assessment method that strives to facilitate learning from past experiences and to increase effort estimation accuracy by exploring realized project effort. The proposed method can be used either to assess the realized project effort of a time span from project's lifecycle or as a part of the whole project postmortem analysis in producing effort information for the project iteration assessment, final report, and annual project portfolio report. In addition, the effort information increases the project team's knowledge on realized activity sets and their relationships, and the information can be utilized in estimation method and model calibration for both re-estimations and future estimations. The method was evaluated with case projects, a sample supplied by Tieto Finland Oy. Copyright© 2010 John Wiley & Sons, Ltd.
    Journal of Software Maintenance and Evolution Research and Practice 12/2010; 22:629-652. · 1.27 Impact Factor