Work Breakdown Structure: A Tool for Software Project Scope Verification

Hans, Robert T.

doi:10.5121/ijsea.2013.4402

Cited by 5 publications

(5 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…WBS is used as a verification tool for project scope. It basically uses user/system requirements and provides resource and task for cost estimation [49]. However, it is limited to gauge the requirements and tasks into deliverable.…”

Section: B Scope Definition Techniques/toolsmentioning

confidence: 99%

“…In software projects, modifications are considered agreed upon scope of the project. These modifications are due [5] Agile EVM [26] Burn-down charts [46] Burn-up charts [46] Function Points [48] Work-Breakdown Structure [49] Expert judgement [51] Performance analysis [52] Feature Transition Charts [53] Story Mapping [54] Stakeholder analysis [55] Benefit analysis [56] Requirement Matrix [56] Scope Change Control System [57] Functional Size Measurement (FSM) [58] Feature Survival Charts [59] Feature Growth Charts [60] SPSRI [61] Activity Based (top down) [62]- [63] Task based (bottom up) [62]- [63] PERT [64] Object point [65] Source line of code (SLOC) [65] Analogy technique [65] Price-to-win [62] VOLUME , 2020 to inevitable change and complexity of the project scope. According to [50] author "Half of the system requirements change till deployment".…”

Section: B Scope Definition Techniques/toolsmentioning

confidence: 99%

“…Occurrences in research articles ef1-Project Priority [6], [7], [51], [77] ef2-Lack of Motivation and Direction [14], [18], [19], [66], [67], [78] ef3-Change Cost [5], [7], [8], [10], [18], [19], [47], [49], [50], [66], [69], [70], [71], [72], [74], [77], [79], [82], [83], [84], [85] ef4-Project Resources [7], [10], [67], [71], [86], [74], [80], [83], [72] ef5-Project Risks [7], [9], [10], [50], [66], [70], [77] ef6-Rework [7], [14], [19],…”

Section: Effectsmentioning

confidence: 99%

See 2 more Smart Citations

Measuring the Impact of Scope Changes on Project Plan Using EVM

et al. 2020

View full text Add to dashboard Cite

Earned Value Management (EVM) measures project performance against a baseline plan. It identifies deviations in budget and schedule, aids project managers in taking earlier corrective actions against cost and schedule overruns. Although the literature highlights the significance of scope by adopting it as a leading indicator to measure project success or failure. However, EVM does not include scope when evaluating the performance of any software project. While considering the importance of scope and its ever-changing nature, it is imperative to measure the effect of changes in scope on the project plan. To analyse such effects, this study aims to enhance the traditional EVM by incorporating scope into it. The main objectives of this paper are: i) to extract the effects of project scope changes, ii) to map extracted effects of project scope changes with Software Project Scope Rating Index (SPSRI) elements, and iii) to quantify the extracted effects and integrate them with EVM. An extensive literature review is conducted to achieve the first objective, which results in the seventeen unique effects; that were used to map with SPSRI elements. To forecast the variations in scope for a given project budget, Monte Carlo simulations were run on the top eight scope elements, whereas, the results were incorporated with EVM to identify the deviations between actual and projected values of scope's score and cost. Finally, the multivariate regression model was used to evaluate the influence of individual element on the overall estimated cost of the project. The correlation between the independent variables (SPSRI elements) and the dependent variable (overall cost) was calculated along with the valuation of each independent variable on the dependent variable. Moreover, the effects are statistically shown that independent variables have influenced the dependent variable. This technique could assist the project managers to forecast deviations in project scope earlier.

show abstract

Section: B Scope Definition Techniques/toolsmentioning

confidence: 99%

Section: B Scope Definition Techniques/toolsmentioning

confidence: 99%

Section: Effectsmentioning

confidence: 99%

See 1 more Smart Citation

Measuring the Impact of Scope Changes on Project Plan Using EVM

et al. 2020

View full text Add to dashboard Cite

show abstract

“…WBS is a process of breaking down from project work into smaller and more manageable components (PMBOK, 2017). WBS is a structured grouping and oriented on the activities and work contained in the project that defines the overall scope of the project (Hans, 2013). WBS is a tool for project management because it provides a basis for planning, scheduling, controlling, assignment of responsibilities and information management thus WBS can be used in any way including care and maintenance (Ibrahim, 2009) (Park & Cai, 2017).…”

Section: Referring To Regulation Of the Ministry Of Public Workmentioning

confidence: 99%

Development of Preventive Maintenance Guidelines for Architectural Components on Government Building Based on Work Breakdown Structure

Wijaya¹,

Latief²,

Machfudiyanto³

2020

cea

View full text Add to dashboard Cite

To reduce the occurrence of damage to government buildings, the efforts for preventive maintenance work must be made. In a building's preventive maintenance work process, the scope of work can be arranged using Work Breakdown Structure (WBS), so that it becomes structured and activity-oriented. However, in the application of government buildings, there are no guidelines for preventive maintenance work that is standardized by WBS. Therefore, developing guidelines for preventive maintenance work is important to improve maintenance and upkeep on a work package. The purpose of this research is to develop the guidelines for preventive maintenance work based on Work Breakdown Structure (WBS) on the architectural components of government buildings. The research methodology comprises several steps, named the literature study, analysis of archives with data and information from previously related research and projects, case studies, as well as through the validation of experts. The results of this study are WBS-based preventive maintenance work guidelines for architectural components of government buildings that can improve the quality of buildings and the effectiveness and efficiency of building maintenance and upkeep.

show abstract

“…Due to the significant role of scope definition in the success of software projects, the literature states various methods and tools that have been established to assist with scope definition. These methods and tools help in identifying the features of scope definition such as Work Breakdown Structure (WBS) [46], controlling scope by dealing with scope changes such as feature break down structure and Feature Transition Charts (FTC) [47], scope verification using WBS [46], [48], and quantifying scope using the given requirements such as Function Points (FP) and Function Size Measurement (FSM) [49], [50]. None of these tools or methods help in defining the scope, although they do help with managing the scope that is already defined.…”

Section: Introductionmentioning

confidence: 99%

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

Hassan

Asghar

2021

IEEE Access

View full text Add to dashboard Cite

Software project scope definition is complicated due to the diversity and magnitude of the information needed. An inadequate scope definition often results in project failure as it continues to emerge as the major cause of delays, changes/rework, and cost and schedule overruns. Literature mentions different tools and methods to verify, quantify, and control software scope definition. However, none of these methods and tools help in defining a complete scope. Since a well-defined scope in the early stages is a core ingredient for project success, therefore, previously we developed a method that includes 45 elements of the software project scope definition. Although these elements are noteworthy for project scope, some may influence others; and should be concentrated on more when defining the scope of the software projects. The objective of this present study is that it builds on our previous research and uses Interpretive Structural Modeling (ISM) to extract the interrelationships among the elements and Decision Making Trial and Evaluation Laboratory (DEMATEL) to determine the intensity of these relationships. Experts from academia and the software development industry were consulted to identify the relationships among the elements. ISM-DEMATEL approach indicates that the project manager's competence is the main driver. Further, requirements, stakeholders' expectations, cost estimates, project schedule, resource estimation, project summary, communication, consultation, top management support are among the most influential elements that are critical to focus on. Moreover, the findings of the study provide project managers with a better understanding of the elements and their interconnections thus, helping in achieving a better scope definition.INDEX TERMS Interpretive structural modeling (ISM), decision making trial and evaluation laboratory (DEMATEL), scope definition, scope elements, scope management, software projects.

show abstract

Work Breakdown Structure: A Tool for Software Project Scope Verification

Abstract: ABSTRACT

Cited by 5 publications

References 6 publications

Measuring the Impact of Scope Changes on Project Plan Using EVM

Measuring the Impact of Scope Changes on Project Plan Using EVM

Development of Preventive Maintenance Guidelines for Architectural Components on Government Building Based on Work Breakdown Structure

A Framework of Software Project Scope Definition Elements: An ISM-DEMATEL Approach

Contact Info

Product

Resources

About