Abstract:-The information technology industry cannot be imagined without large-or small-scale projects. They are implemented to develop systems enabling key business processes and improving performance and enterprise resource management. However, projects often experience various difficulties during their execution. These problems are usually related to the three objectives of the project -costs, quality and deadline. A way these challenges can be solved is project risk management. However, not always the main problems… Show more
“…The vast majority of these tasks were definable, however, with sufficient detail within the first three weeks of the summer. Fleshing out these earlier would have clarified the project's direction for all team members, mitigated schedule risk by adding increased clarity and details to schedule planning, and reduced stress on the project manager (Ancveire et al, 2015;Rose, 2013). We recommend "when in doubt, attempt to plan it out" as a good rule of thumb.…”
Universities offer unique environments for software development, where the need for small custom software projects to support teaching, research, and outreach intersects with an abundance of young talent seeking to gain experience before entering the workforce. We present a case study on software development on versions (v) 2.1-4 of the People in Ecosystems/Watershed Integration (PEWI), a student-developed digital game-based learning application designed to teach students and land managers about land use decision tradeoffs. PEWI v2.1-4 was developed over four years by a professor who served as project director, a Ph.D. student who served as project manager, and teams of between two and six student interns. We used a custom software development methodology that integrated Agile principles into the top-down decision making of the Waterfall approach and employed Scrum-based sprint workload cycles to maximize our efficiency with our limited budgetary resources and ambitious but novice workforce. Over 90% of individual work tasks were completed in each of the four development years and student interns reported a high level of skill development. Release-ready increments were only achieved in two of the four years, however. We discuss elements of the methodology that worked well (i.e., sprint cycles, paired programming), were underutilized (i.e., engagement with an accessible population of users), or were insufficient (i.e., planning, training materials). We further discuss barriers that inhibit software development projects in environmental fields at academic institutions and how they might be overcome.
“…The vast majority of these tasks were definable, however, with sufficient detail within the first three weeks of the summer. Fleshing out these earlier would have clarified the project's direction for all team members, mitigated schedule risk by adding increased clarity and details to schedule planning, and reduced stress on the project manager (Ancveire et al, 2015;Rose, 2013). We recommend "when in doubt, attempt to plan it out" as a good rule of thumb.…”
Universities offer unique environments for software development, where the need for small custom software projects to support teaching, research, and outreach intersects with an abundance of young talent seeking to gain experience before entering the workforce. We present a case study on software development on versions (v) 2.1-4 of the People in Ecosystems/Watershed Integration (PEWI), a student-developed digital game-based learning application designed to teach students and land managers about land use decision tradeoffs. PEWI v2.1-4 was developed over four years by a professor who served as project director, a Ph.D. student who served as project manager, and teams of between two and six student interns. We used a custom software development methodology that integrated Agile principles into the top-down decision making of the Waterfall approach and employed Scrum-based sprint workload cycles to maximize our efficiency with our limited budgetary resources and ambitious but novice workforce. Over 90% of individual work tasks were completed in each of the four development years and student interns reported a high level of skill development. Release-ready increments were only achieved in two of the four years, however. We discuss elements of the methodology that worked well (i.e., sprint cycles, paired programming), were underutilized (i.e., engagement with an accessible population of users), or were insufficient (i.e., planning, training materials). We further discuss barriers that inhibit software development projects in environmental fields at academic institutions and how they might be overcome.
“…Studies have applied Bayesian networks for supporting risk management for many specific purposes including setting a schedule [25]; budget definition [18]; quality assessment [1]; and defect prediction [20]. Fenton et al [9] created a Bayesian Network for risk management that supports decision making in various software design activities.…”
Section: Bn For Software Risk Managementmentioning
confidence: 99%
“…Khodakarami and Abdi [18] used a real example lived by one of the authors. Such validation strategy was also applied by Ancveire [1]. Fenton et al [9] made a simulation with two examples of projects to compare the view of experts with the results of the Bayesian network.…”
Section: Bn For Software Risk Managementmentioning
confidence: 99%
“…These studies have shown promising results, but they do not focus on risk factors related to the technological aspects of software projects. The risk factors used in their approach include information on requirements, human resources, management knowledge, quality process, and deliveries [1,9,18,25]. Some researchers investigate risk factors related to technological characteristics but simplify the analysis by defining only one risk factor to deal with all the project's complexity related to technologies [5,26].…”
Section: Bn For Software Risk Managementmentioning
confidence: 99%
“…Considering our proposed BN as a framework, the Core fragment would be the framework's cold spot. The Supplementary Material presents the definition for each Core node 1 .…”
Risk management is essential in software project management. It includes activities such as identifying, measuring and monitoring risks. The literature presents different approaches to support software risk management. In particular, the researchers popularly used Bayesian Networks because they can be learned from data or elicited from domain experts. Even though the literature presents many Bayesian networks (BN) for software risk management, none focus on technological risk factors. Given this, this paper presents a BN for managing risks of software projects and the results of a static validation performed through a focus group with eight practitioners. As a result, the practitioners agreed that our proposed to manage technological risks of software projects using BN is valuable and easy to use. Given the successful results, we concluded that the proposed solution is promising.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.