The DOI matches its Crossref record; 34 of the 34 references it cites were found in a registry or an index; none of the 10 sources its claims cite is checked for support yet.
Analysis of Risk Assessment Framework Using Agile Methodology and Computer-Aided Software Engineering Tools
Open accessAbstract
This research paper presents a risk assessment framework developed through the integration of the Scrum process with a Computer-Aided Software Engineering (CASE) tool, specifically Microsoft Excel. The framework aims to automate risk assessment processes, facilitating more accurate calculations of risk based on impact and probability using a matrix system. Initially, data is collected and recorded in the Risk Register, serving as the foundation for risk evaluation. The integration of the CASE tool enhances the efficiency and effectiveness of the process, allowing for real-time updates and tracking of risks. As updates occur within the Risk Register, a real-time dashboard is generated, providing stakeholders with an immediate overview of the risk landscape. The dashboard feature significantly improves decision making capabilities by presenting visual insights into risk levels and potential impacts on the projects. This dynamic monitoring tool is crucial for effective decision-making and timely responses to emerging risks. By leveraging agile methodologies design, this framework not only streamlines the risk management process but also ensures that relevant data is readily accessible to project teams. The findings from this research contribute to the fields of project management and software engineering by demonstrating the benefits of incorporating agile approaches with automated tools in risk assessment. The potential implications of this framework extend beyond individual projects, offering a model that can be adopted by various organizations seeking to enhance their risk management practices in a streamlined and efficient manner. Keywords: Risk Assessment, Scrum, CASE Tool, Risk Register, Dashboard
Overview
AI snapshot
Written from the paper’s full text.
TL;DR
The paper develops E-RAF, an Excel-based CASE tool integrated with Scrum to automate risk assessment through probability-impact scoring, risk registers, heatmaps, and dashboards. It reports reduced “Very High” risks across five sprints and presents E-RAF as a low-cost middle ground between enterprise risk tools and generic Excel logs.
Key findings
- E-RAF calculates risk as RR = P × I on a 5×5 matrix; the example risk RSK-001 (“Delay in component delivery,” Sprint 2) had P=4, I=5, rating=20, classified “Very High,” and was 5 days overdue.
- Table 8 reports “Very High” risks falling from 4 in Sprint 1 and 5 in Sprint 2 to 0 in Sprints 3–5; Sprint 5 had six “Very Low” risks and no High or Medium risks.
- Scrum integration used five two-week sprints, with risk data feeding Sprint Planning, Daily Scrums, Sprint Reviews, and Retrospectives; dashboards tracked open, closed, overdue, and category-specific risks.
- Compared with Primavera Risk Analysis and generic Excel logs, E-RAF is described as low cost, highly accessible, with risk scoring automation and visual dashboards, but limited collaboration support and no advanced analytics such as Monte Carlo simulation.
Methods
- Mixed-methods design: quantitative project performance metrics (schedule adherence, cost control, risk reduction trends) generated through the Excel-based E-RAF using probability-impact matrices and automated dashboards, plus qualitative practitioner feedback gathered during Scrum ceremonies.
- E-RAF was built in Microsoft Excel with VBA, data input forms, conditional formatting, charts, heatmaps, and automated formulas. The Scrum team comprised a Product Owner, Scrum Master, Accountant, Security specialist, Operations Manager, and three Developers; development ran over 5 sprints of two weeks each.
- Data came from a custom dataset combining anonymized historical risk logs from archived ICT and construction project documents previously managed by consulting firms and government departments, plus simulated sprint-level risk scenarios for Agile e-government projects. The full dataset is not publicly hosted due to confidentiality, but key samples and anonymized structures can be provided upon request.
Limitations
- The paper states that evaluation relied partly on simulated datasets, which may not capture full real-world project complexity; Excel’s file-based architecture limits scalability for large, distributed teams; and VBA/advanced Excel dependence may affect adoption. It concludes E-RAF is effective for small-to-medium projects, while larger organizations may require web-based or integrated platforms.
- Evident from the text: risk-level thresholds are inconsistent between Table 1 (Very High 20–25, Low 5–9) and Table 7 (Very High 21–25, Low 6–10). Some Table 9 formulas also appear mislabeled, e.g., “No of Overdue” uses `COUNTIF(..., "CLOSED")`, and category formulas reference mismatched columns.
Model-written summary. Check it against the paper before relying on it.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
0 of 10 cited sources checked · 0 supported · 0 flagged
- Findingreasoning
The E-RAF framework integrates the Scrum process with a CASE tool, specifically Microsoft Excel, to automate risk assessment.
“This research paper presents a risk assessment framework developed through the integration of the Scrum process with a Computer-Aided Software Engineering (CASE) tool, specifically Microsoft Excel.”
Quote in the paperSubstantial claim - Findingnone given
The E-RAF application was created by combining Excel capabilities and VBA scripting to emulate CASE environment.
“The E-RAF application was created by combining Excel capabilities and VBA scripting to emulate CASE environment.”
Quote in the paperSubstantial claim - Findingown data
Trend charts showed how risk intensity and mitigation efficacy changed over time.
“Visual heat maps made it easy to identify high-risk zones across sprints, while trend charts showed how risk intensity and mitigation efficacy changed over time.”
Quote in the paperNot a substantial claim - Findingnone given
For each sprint cycle, E-RAF created a risk register with unique risk identifiers, complete descriptions, associated sprint numbers, risk owners, probability and impact scores, and automatically calculated severity ratings.
“For each sprint cycle, the program created a risk register with unique risk identifiers, complete descriptions, associated sprint numbers, risk owners, probability and impact scores, and automatically calculated severity ratings.”
Quote in the paperNot a substantial claim - Findingown data
The E-RAF tool generated a comprehensive set of risk assessment results, providing both quantitative and qualitative insights into project vulnerabilities throughout agile sprints.
“The E-RAF tool generated a comprehensive set of risk assessment results, providing both quantitative and qualitative insights into project vulnerabilities throughout and agile sprints.”
Quote in the paperSubstantial claim
- Findingown data
Sprint 1 and 2 contained the highest number of Very High risks (4 and 5 respectively).
“Sprint 1 and 2: These contain the highest number of Very High risks (4 and 5 respectively), indicating elevated project vulnerability.”
Quote in the paperSubstantial claim - Findingreasoning
As updates occur within the Risk Register, a real-time dashboard is generated, providing stakeholders with an immediate overview of the risk landscape.
“As updates occur within the Risk Register, a real-time dashboard is generated, providing stakeholders with an immediate overview of the risk landscape.”
Quote in the paperSubstantial claim - Findingnone given
Sprint Reviews enabled stakeholders to evaluate dashboards.
“Sprint Planning facilitated the adoption of standardized scoring methods; Daily Scrums ensured risks were logged and tracked in real time; Sprint Reviews enabled stakeholders to evaluate dashboards; and Retrospectives contributed to iterative tool refinements.”
Quote in the paperNot a substantial claim - Findingnone given
Daily Scrums ensured risks were logged and tracked in real time.
“Sprint Planning facilitated the adoption of standardized scoring methods; Daily Scrums ensured risks were logged and tracked in real time; Sprint Reviews enabled stakeholders to evaluate dashboards; and Retrospectives contributed to iterative tool refinements.”
Quote in the paperSubstantial claim - Findingnone given
The integration of Scrum methodology with Excel's automation and visualization features enabled the organized capture, classification, prioritizing, and mitigation of risks throughout five sprint cycles.
“The integration of Scrum methodology with Excel's extensive automation and visualization features enabled the organized capture, classification, prioritizing, and mitigation of risks throughout five sprint cycles.”
Quote in the paperSubstantial claim - Findingnone given
The integration of CASE tool risk data prompted adaptations to standard Scrum ceremonies and deliverables.
“Further, the integration of CASE tool risk data prompted adaptations to standard Scrum ceremonies and deliverables.”
Quote in the paperSubstantial claim - Findingnone given
Retrospectives contributed to iterative tool refinements.
“Sprint Planning facilitated the adoption of standardized scoring methods; Daily Scrums ensured risks were logged and tracked in real time; Sprint Reviews enabled stakeholders to evaluate dashboards; and Retrospectives contributed to iterative tool refinements.”
Quote in the paperNot a substantial claim - Findingnone given
Sprint Planning facilitated the adoption of standardized scoring methods.
“Sprint Planning facilitated the adoption of standardized scoring methods; Daily Scrums ensured risks were logged and tracked in real time; Sprint Reviews enabled stakeholders to evaluate dashboards; and Retrospectives contributed to iterative tool refinements.”
Quote in the paperNot a substantial claim - Findingreasoning
By linking formulas to dynamic named ranges and data visualizations, the E-RAF tool delivers an up-to-date and interactive project risk dashboard.
“By linking these formulas to dynamic named ranges and data visualizations, the E-RAF tool delivers an up-to-date and interactive project risk dashboard.”
Quote in the paperSubstantial claim - Interpretationcitation
By embedding probability-impact matrices, dashboards, and overdue tracking into the sprint workflow, the framework addresses critiques that Scrum alone lacks sufficient mechanisms for managing complex or nonrequirements-related risks.
“By embedding probability-impact matrices, dashboards, and overdue tracking into the sprint workflow, the framework addresses critiques that Scrum alone lacks sufficient mechanisms for managing complex or nonrequirements-related risks [15] [16].”
Quote in the paperSubstantial claim0 of 2 sources checked- cites [15]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites [16]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationown data
The observed reduction in Very High risks over sprints demonstrates that iterative monitoring and ongoing feedback allow teams to respond proactively to emergent difficulties rather than relying on static risk registers.
“The observed reduction in”
Quote in the paperSubstantial claim - Interpretationown data
E-RAF is effective in iterative risk control, as validated through simulated and real project data.
“Validating the E-RAF tool through simulated and real project data, showcasing effectiveness in iterative risk control.”
Quote in the paperSubstantial claim- Rests on an assumption: The simulated and real project data used to validate E-RAF are sufficiently representative of real-world project environments to support conclusions about its effectiveness.
- Interpretationnone given
Visual heat maps made it easy to identify high-risk zones across sprints.
“Visual heat maps made it easy to identify high-risk zones across sprints, while trend charts showed how risk intensity and mitigation efficacy changed over time.”
Quote in the paperNot a substantial claim - Interpretationreasoning
E-RAF uses basic spreadsheet capabilities, reinforced by VBA, to provide iterative risk monitoring in Agile-driven environments, particularly for digital government initiatives that require transparency and adaptability.
“It uses basic spreadsheet capabilities, reinforced by VBA, to provide iterative risk monitoring in Agile-driven environments, particularly for digital government initiatives that require transparency and adaptability.”
Quote in the paperSubstantial claim - Interpretationreasoning
Unlike purely implicit approaches, the E-RAF framework provides a structured and quantitative mechanism that complements Scrum practices.
“However, unlike purely implicit approaches, the E-RAF framework provides a structured and quantitative mechanism that complements Scrum practices.”
Quote in the paperSubstantial claim - Study design and conductreasoning
A custom dataset was developed using a combination of anonymized historical records and simulated project scenarios to evaluate the performance and validity of the E-RAF tool.
“To evaluate the performance and validity of the E-RAF tool, a custom dataset was developed using a combination of anonymized historical records and simulated project scenarios.”
Quote in the paperSubstantial claim- Rests on an assumption: There is no publicly available, domain-specific dataset reflecting the dynamic nature of Agile risk environments in the public sector.
- Rests on an assumption: The anonymized historical records and simulated scenarios are realistic enough to model project risks and validate the E-RAF tool.
- Interpretationreasoning
This paper demonstrates how risk matrices, heatmaps, and mitigation tracking can be automated and visualized using Excel's native capabilities.
“• Demonstrating how risk matrices, heatmaps, and mitigation tracking can be automated and visualized using Excel's native capabilities.”
Quote in the paperSubstantial claim - Interpretationnone given
The comparison of E-RAF, Primavera Risk Analysis, and generic Excel-based risk logs reveals various trade-offs in cost, usability, scalability, and methodological depth.
“The comparison of E-RAF, Primavera Risk Analysis, and generic Excel (Table 10)-based risk logs reveals various trade-offs in cost, usability, scalability, and methodological depth.”
Quote in the paperSubstantial claim - Interpretationown data
The findings show that incorporating structured risk assessment methods into iterative Scrum cycles can result in substantial gains in risk visibility, prioritization, and mitigation efficacy.
“The findings show that incorporating structured risk assessment methods into iterative Scrum cycles can result in substantial gains in risk visibility, prioritization, and mitigation efficacy.”
Quote in the paperSubstantial claim - Study design and conductcitation
The method aligns with established research protocols where synthetic or non-publicly available data is utilized to validate tools under realistic yet controlled conditions.
“This method aligns with established research protocols where synthetic or non-publicly available data is utilized to validate tools under realistic yet controlled conditions [37] [38].”
Quote in the paperSubstantial claim0 of 2 sources checked- cites [37]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites [38]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationown data
The high number of Very High risks in Sprints 1 and 2 indicates elevated project vulnerability.
“Sprint 1 and 2: These contain the highest number of Very High risks (4 and 5 respectively), indicating elevated project vulnerability.”
Quote in the paperSubstantial claim - Study design and conductnone given
The evaluation relied partly on simulated datasets, which may not capture the full complexity of real-world project environments.
“The evaluation relied partly on simulated datasets, which may not capture the full complexity of real-world project environments.”
Quote in the paperSubstantial claim - Interpretationreasoning
The matrix-based risk scoring system, dynamic dashboards, and automated heat maps demonstrated that meaningful risk analysis can be achieved even with limited resources, leveraging widely accessible platforms like Excel.
“The matrix-based risk scoring system, dynamic dashboards, and automated heat maps demonstrated that meaningful risk analysis can be achieved even with limited resources, leveraging widely accessible platforms like Excel.”
Quote in the paperSubstantial claim- Rests on an assumption: Microsoft Excel is sufficiently familiar and accessible to intended users that E-RAF can be adopted without complex software investments.
- Interpretationown data
Microsoft Excel, often overlooked as a CASE tool, can serve as an effective, low-cost platform for implementing risk management frameworks.
“Another key outcome is the demonstration that Microsoft Excel, often overlooked as a CASE tool, can serve as an effective, low-cost platform for implementing risk management frameworks.”
Quote in the paperSubstantial claim- Rests on an assumption: Microsoft Excel is sufficiently familiar and accessible to intended users that E-RAF can be adopted without complex software investments.
- Interpretationreasoning
By embedding probability impact matrices and dashboards into sprint workflows, the framework transformed risk management from a static, document-based activity into a dynamic process aligned with Scrum's incremental delivery model.
“By embedding probability impact matrices and dashboards into sprint workflows, the framework transformed risk management from a static, document-based activity into a dynamic process aligned with Scrum's incremental delivery model.”
Quote in the paperSubstantial claim - Interpretationreasoning
The iterative cycles of Scrum provided the feedback loops necessary for continuous risk identification, monitoring, and mitigation.
“The iterative cycles of Scrum provided the feedback loops necessary for continuous risk identification, monitoring, and mitigation.”
Quote in the paperSubstantial claim - Interpretationcitation
E-RAF bridges the gap identified in prior literature between expensive enterprise tools and overly simplistic manual logs.
“This bridges the gap identified in prior literature between expensive enterprise tools and overly simplistic manual logs [25] [26].”
Quote in the paperSubstantial claim0 of 2 sources checked- cites [25]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites [26]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationcitation
This process-driven visibility supports the argument that successful risk management in agile settings requires alignment between tools and team practices.
“This process-driven visibility supports the argument that successful risk management in agile settings requires alignment between tools and team practices [26] [28].”
Quote in the paperSubstantial claim0 of 2 sources checked- cites [26]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites [28]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- Interpretationreasoning
Systematic, tool-based risk assessment can coexist with Scrum's flexibility.
“Overall, the discussion emphasizes that systematic, tool-based risk assessment can coexist with Scrum's flexibility.”
Quote in the paperSubstantial claim
- Probably not a substantial claim. 32
- It may state two separate claims as one. 28
Probably not a substantial claim. The paper’s conclusions may not depend on it. It may state two separate claims as one.
FindingreasoningThe architecture was intentionally lightweight to accommodate deployment within Excel, requiring no external database or dependencies.
“The architecture was intentionally lightweight to accommodate deployment within Excel, requiring no external database or dependencies.”
Quote in the paperNot a substantial claimProbably not a substantial claim. The paper’s conclusions may not depend on it.
FindingreasoningThe matrix cells are color-coded to indicate risk intensity, providing users with a quick overview of the risk environment.
“The matrix cells are color-coded to indicate risk intensity, providing users with a quick overview of the risk environment.”
Quote in the paperNot a substantial claimProbably not a substantial claim.
Findingnone givenThe E-RAF framework was designed to support systematic identification, analysis, evaluation, and monitoring of project risks.
“The E-RAF framework was designed to support systematic identification, analysis, evaluation, and monitoring of project risks.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
FindingreasoningThis study introduces the Excel-based Risk Assessment Framework (E-RAF), a lightweight, agile-compatible CASE tool that combines the familiarity and accessibility of Excel with the adaptability of Scrum-based iterative development.
“To address these gaps, this study introduces the Excel-based Risk Assessment Framework (E-RAF), a lightweight, agile-compatible CASE tool that combines the familiarity and accessibility of Excel with the adaptability of Scrum-based iterative development.”
Quote in the paperSubstantial claim- Rests on an assumption: There is a government need for an accessible, low-cost, and simply deployable risk management solution.
Probably not a substantial claim. The paper’s conclusions may not depend on it.
Findingnone givenE-RAF converts the 5×5 matrix into an interactive risk heatmap that displays each risk's likelihood and impact scores.
“E-RAF converts the 5×5 matrix into an interactive risk heatmap that displays each risk's likelihood and impact scores.”
Quote in the paperNot a substantial claimIt may state two separate claims as one.
Findingown dataSprint 5 showed a risk reduction trend with no High or Medium risks and six Very Low risks.
“Sprint 5: Shows a risk reduction trend with no High or Medium risks and six Very Low risks.”
Quote in the paperNot a substantial claimIt may state two separate claims as one.
Findingown dataIn Sprints 3 and 4, Very High risks disappeared with an increase in Medium and High risks.
“Sprint 3 and 4: We observe a shift, with Very High risks disappearing with an increase in Medium and High risks.”
Quote in the paperSubstantial claimProbably not a substantial claim.
FindingreasoningHigh and Very High risks (red and orange zones) are clearly identifiable from Moderate or Low risks, allowing for quick judgments.
“High and Very High risks (red and orange zones) are clearly identifiable from Moderate or Low risks, allowing for quick, judgments.”
Quote in the paperSubstantial claimProbably not a substantial claim.
FindingreasoningThe E-RAF tool evaluates each identified risk in two key dimensions: probability (P) and impact (I).
“The E-RAF tool evaluates each identified risk in two key dimensions: probability (P) and impact (I).”
Quote in the paperSubstantial claim- Rests on an assumption: The 5×5 Probability-Impact Matrix is commonly used in project management and risk analysis for its simplicity and efficacy.
It may state two separate claims as one.
InterpretationreasoningBy leveraging agile methodologies design, the framework streamlines the risk management process and ensures that relevant data is readily accessible to project teams.
“By leveraging agile methodologies design, this framework not only streamlines the risk management process but also ensures that relevant data is readily accessible to project teams.”
Quote in the paperSubstantial claimProbably not a substantial claim.
InterpretationreasoningThe integration of Scrum methodology serves to introduce agility into the tool development process and the risk assessment workflow itself.
“The integration of Scrum methodology serves to introduce agility into the tool development process and the risk assessment workflow itself.”
Quote in the paperSubstantial claimProbably not a substantial claim. The paper’s conclusions may not depend on it. The paper may give no reason why it holds.
Study design and conductnone givenA data flow model and modular design approach were adopted to ensure scalability and maintainability.
“A data flow model and modular design approach were adopted to ensure scalability and maintainability.”
Quote in the paperNot a substantial claimIt may state two separate claims as one.
Interpretationown dataThe transition in Sprint 5 toward green in the heat map represents improved risk handling, system stability, and maturity in mitigation planning.
“This transition toward green in the heat map represents improved risk handling, system stability, and maturity in mitigation planning.”
Quote in the paperNot a substantial claimProbably not a substantial claim.
InterpretationreasoningThe E-RAF in Excel was created to meet the government need for an accessible, low-cost, and simply deployable risk management solution.
“The E-RAF in Excel was created to meet the government need for an accessible, low-cost, and simply deployable risk management solution.”
Quote in the paperSubstantial claim- Rests on an assumption: There is a government need for an accessible, low-cost, and simply deployable risk management solution.
Probably not a substantial claim. The paper’s conclusions may not depend on it.
Study design and conductnone givenScrum artefacts including Product Backlog, Sprint Backlog, and Burndown Charts were maintained using Excel sheets to ensure transparency and traceability.
“Scrum artefacts including Product Backlog, Sprint Backlog, and Burndown Charts were maintained using Excel sheets to ensure transparency and traceability.”
Quote in the paperNot a substantial claimProbably not a substantial claim.
Interpretationnone givenThe literature review reveals several significant gaps in current understanding of how Scrum methodologies integrate with CASE tool-supported risk assessment frameworks.
“The literature review reveals several significant gaps in current understanding of how Scrum methodologies integrate with CASE tool-supported risk assessment frameworks:”
Quote in the paperSubstantial claimProbably not a substantial claim.
InterpretationcitationSuccessful tool integration requires alignment with agile principles and team workflows.
“These research indicates that successful tool integration requires alignment with agile principles and team workflows, suggesting that risk assessment tools must be compatible with Scrum's iterative and collaborative nature to be effective.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
InterpretationreasoningThe integration of the CASE tool enhances the efficiency and effectiveness of the risk assessment process, allowing for real-time updates and tracking of risks.
“The integration of the CASE tool enhances the efficiency and effectiveness of the process, allowing for real-time updates and tracking of risks.”
Quote in the paperSubstantial claimProbably not a substantial claim. The paper may give no reason why it holds. It may state two separate claims as one.
Premisenone givenGeneric Excel logs are the most basic type of risk documentation, with no structure, analytical depth, or integration with iterative project frameworks.
“Generic Excel logs, on the other hand, are the most basic type of risk documentation, with no structure, analytical depth, or integration with iterative project frameworks.”
Quote in the paperNot a substantial claimProbably not a substantial claim. The paper may give no reason why it holds. It may state two separate claims as one.
PremisereasoningGeneric Excel logs frequently suffer from inconsistency, manual errors, and insufficient insight generation.
“They frequently suffer from inconsistency, manual errors, and insufficient insight generation.”
Quote in the paperNot a substantial claimIt may state two separate claims as one.
InterpretationreasoningThis paper contributes to research and practice by presenting a novel integration of Scrum and CASE tool development within an Excel environment for risk management.
“This paper contributes to research and practice • Presenting a novel integration of Scrum and CASE tool development within an Excel environment for risk management.”
Quote in the paperSubstantial claimProbably not a substantial claim.
InterpretationreasoningPrimavera's high cost and learning curve make it less accessible to small teams or public sector initiatives with limited funding.
“Its high cost and learning curve make it less accessible to small teams or public sector initiatives with limited funding.”
Quote in the paperSubstantial claimProbably not a substantial claim.
InterpretationreasoningThis structured approach enables project teams to prioritize and focus their mitigation efforts on the risks that present the most significant threat to project success.
“This structured approach enables project teams to prioritize and focus their mitigation efforts on the risks that present the most significant threat to project success.”
Quote in the paperSubstantial claim- Rests on an assumption: Quantifying risks reduces subjective bias when determining criticality.
Probably not a substantial claim. It may be too vague to check against evidence. The paper may give no reason why it holds.
Interpretationnone givenThe systematic identification, analysis, and mitigation of risks within agile contexts remains an area of research that requires further exploration.
“However, the systematic identification, analysis, and mitigation of risks within these agile contexts remains an area of research that requires further exploration, particularly when enhanced with technological innovations such as artificial”
Quote in the paperNot a substantial claimProbably not a substantial claim. The paper may give no reason why it holds.
InterpretationreasoningThe dashboard feature significantly improves decision making capabilities by presenting visual insights into risk levels and potential impacts on the projects.
“The dashboard feature significantly improves decision making capabilities by presenting visual insights into risk levels and potential impacts on the projects.”
Quote in the paperNot a substantial claimProbably not a substantial claim. It may state two separate claims as one.
Study design and conductnone givenThe Scrum methodology was selected to enhance adaptability, foster team collaboration, and ensure iterative refinement of the E-RAF tool.
“The Scrum methodology was selected to enhance adaptability, foster team collaboration, and ensure iterative refinement of the E-RAF tool.”
Quote in the paperSubstantial claimProbably not a substantial claim. The paper’s conclusions may not depend on it. It may state two separate claims as one.
Study design and conductreasoningThe modular spreadsheet structure separated raw data, computation logic, and output visualization, thereby following good practices of software modularity and separation of concerns.
“The modular spreadsheet structure separated raw data, computation logic, and output visualization, thereby following good practices of software modularity and separation of concerns.”
Quote in the paperNot a substantial claimIt may state two separate claims as one.
InterpretationreasoningE-RAF outputs offered situational knowledge to project teams and acted as a strategic tool for sprint planning, resource allocation, and stakeholder reporting.
“These outputs not only offered situational knowledge to project teams but also acted as a strategic tool for sprint planning, resource allocation, and stakeholder reporting.”
Quote in the paperSubstantial claimProbably not a substantial claim. It may state two separate claims as one.
InterpretationreasoningE-RAF offers an accessible, iterative, and visually driven solution that enables organizations to strengthen risk management practices without complex software investments.
“By leveraging Agile values and low-code technologies, E-RAF offers an accessible, iterative, and visually driven solution that enables organizations strengthen their risk management practices without the need for complex software investments.”
Quote in the paperSubstantial claim- Rests on an assumption: Microsoft Excel is sufficiently familiar and accessible to intended users that E-RAF can be adopted without complex software investments.
It may state two separate claims as one.
InterpretationreasoningE-RAF sits between Primavera and generic Excel logs, demonstrating how a well-structured Excel-based CASE tool can contain complex functionality such as automated scoring, conditional heat maps, sprint-wise tracking, and mitigation dashboards without requiring a large software investment.
“E-RAF, which sits between these two extremes, demonstrates how a well-structured Excel-based CASE tool can contain complex functionality such as automated scoring, conditional heat maps, sprint-wise tracking, and mitigation dashboards without requiring a large software investment.”
Quote in the paperSubstantial claimProbably not a substantial claim. The paper’s conclusions may not depend on it.
PremisecitationThis finding aligns with previous studies that argue agile practices implicitly address certain risks through frequent feedback and adaptation.
“This finding aligns with previous studies that argue agile practices implicitly address certain risks through frequent feedback and adaptation [12][13].”
Quote in the paperNot a substantial claim0 of 2 sources checked- cites [12]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
- cites [13]
Couldn’t be matched to a paper in Crossref, so it can’t be checked.
Probably not a substantial claim. The paper’s conclusions may not depend on it. It may state two separate claims as one.
Study design and conductnone givenThe design of E-RAF was informed by established risk management standards and customized to be lightweight, user-friendly, and compatible with common project management practices.
“The design was informed by established risk management standards and customized to be lightweight, user-friendly, and compatible with common project management practices.”
Quote in the paperNot a substantial claimProbably not a substantial claim. The paper’s conclusions may not depend on it. It may state two separate claims as one.
InterpretationreasoningThis metric supports real-time performance monitoring and feeds into dashboard visuals that track unresolved or overdue risks.
“This metric supports real-time performance monitoring and feeds into dashboard visuals that track unresolved or overdue risks.”
Quote in the paperNot a substantial claimProbably not a substantial claim. The paper’s conclusions may not depend on it. It may state two separate claims as one.
InterpretationreasoningThis table supports accountability and tracking by clearly linking risks to assigned mitigation actions and response performance, thereby enhancing transparency and improving decision-making within Agile project cycles.
“This table supports accountability and tracking by clearly linking risks to assigned mitigation actions and response performance, thereby enhancing transparency and improving decision-making within Agile project cycles.”
Quote in the paperNot a substantial claimIt may state two separate claims as one.
Interpretationown dataThe shift in Sprints 3 and 4 suggests that while critical threats were addressed, new risks continued to emerge, showing characteristic of dynamic project environments.
“This suggests that while critical threats were addressed, new risks continued to emerge showing characteristic of dynamic project environments.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
Interpretationown dataThis paper validates the E-RAF tool through simulated and real project data, showcasing effectiveness in iterative risk control.
“• Validating the E-RAF tool through simulated and real project data, showcasing effectiveness in iterative risk control.”
Quote in the paperSubstantial claimProbably not a substantial claim. The paper may give no reason why it holds.
InterpretationreasoningThrough iterative software-use phases, E-RAF evolves with ongoing stakeholder feedback, delivering incremental improvements in usability, automation, and analytical accuracy.
“Through iterative software-use phases, E-RAF evolves with ongoing stakeholder feedback, delivering incremental improvements in usability, automation, and analytical accuracy.”
Quote in the paperNot a substantial claimProbably not a substantial claim.
InterpretationreasoningThe integration of Scrum ceremonies with the E-RAF results illustrates the value of combining process and technology.
“The integration of Scrum ceremonies with the E-RAF results further illustrates the value of combining process and technology.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
InterpretationreasoningE-RAF is effective for small-to-medium-scale projects, while larger organizations may require web-based or integrated platforms.
“These constraints suggest that while the E-RAF is effective for small-to medium-scale projects, larger organizations may require web-based or integrated platforms.”
Quote in the paperSubstantial claimProbably not a substantial claim. The paper may give no reason why it holds.
Interpretationnone givenExcel's file-based architecture limits its scalability for large, distributed teams.
“Additionally, Excel's file-based architecture limits its scalability for large, distributed teams.”
Quote in the paperNot a substantial claimProbably not a substantial claim. It may be too vague to check against evidence. The paper may give no reason why it holds. It may state two separate claims as one.
InterpretationreasoningThis enhances project governance, executive reporting, and sprint planning in e-government and other complex project environments.
“This enhances project governance, executive reporting, and sprint planning in e-government and other complex project environments.”
Quote in the paperNot a substantial claimProbably not a substantial claim.
InterpretationreasoningE-RAF bridges the gap between high-cost enterprise risk tools and over simplified generic logs by offering a middle-ground solution that is affordable, customizable, and iterative.
“It bridges the gap between high-cost enterprise risk tools and over simplified generic logs by offering a middle-ground solution that is affordable, customizable, and iterative.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
InterpretationreasoningThe research contributes by showcasing how CASE tool development can benefit from agile principles and how Excel can be repurposed as a lightweight but effective development environment for risk management.
“The research contributes to both academic inquiry and practical application by showcasing how CASE tool development can benefit from agile principles and how Excel can be repurposed as a lightweight but effective development environment for risk management.”
Quote in the paperSubstantial claimProbably not a substantial claim. It may state two separate claims as one.
Interpretationnone givenVBA scripts and conditional formatting provide a level of automation, but they are dependent on the user's familiarity with Excel's advanced features, which could affect adoption.
“Additionally, while VBA scripts and conditional formatting provide a level of automation, they are dependent on the user's familiarity with Excel's advanced features, which could affect adoption.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
InterpretationreasoningThe study contributes to the current literature by indicating that agile risk management benefits from hybrid techniques that combine quantitative monitoring with qualitative practitioner feedback, resulting in a more comprehensive awareness of project risks and mitigation.
“The study contributes to the current literature by indicating that agile risk management benefits from hybrid techniques that combine quantitative monitoring with qualitative practitioner feedback, resulting in a more comprehensive awareness of project risks and mitigation.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
Interpretationown dataEven lightweight spreadsheet-based systems can automate scoring, generate visual heatmaps, and support decision-making in agile environments.
“While enterprise solutions such as Primavera Risk Analysis provide advanced capabilities, the results show that even lightweight spreadsheet-based systems can automate scoring, generate visual heatmaps, and support decision-making in agile environments.”
Quote in the paperSubstantial claimIt may state two separate claims as one.
Study design and conductreasoningBeing built in Excel, E-RAF is constrained by file-based operations and limited scalability, which may restrict its utility in large-scale, collaborative environments.
“Being built in Excel, E-RAF is constrained by file-based operations, limited scalability which may restrict its utility in large-scale, collaborative environments.”
Quote in the paperSubstantial claimProbably not a substantial claim. It may state two separate claims as one.
Interpretationnone givenThe Registration_Form standardizes the risk entry process and enables accurate comparison and prioritization across different risks.
“The use of the Registration_Form standardizes the risk entry process and enables accurate comparison and prioritization across different risks.”
Quote in the paperSubstantial claim
The paper relies on this without support.
There is a government need for an accessible, low-cost, and simply deployable risk management solution.
“The E-RAF in Excel was created to meet the government need for an accessible, low-cost, and simply deployable risk management solution.”
The paper relies on this without support.
Excel is widely available in organizational environments and familiar among project managers.
“Excel was chosen as the platform for tool development due to its widespread availability in organizational environments, built-in support for data processing and visualization, and the ability to extend its functionality using Visual Basic for Applications (VBA).”
The paper relies on this without support.
There is no publicly available, domain-specific dataset reflecting the dynamic nature of Agile risk environments in the public sector.
“This approach was necessary due to the absence of a publicly available, domain-specific dataset reflecting the dynamic nature of Agile risk environments in the public sector.”
The paper relies on this without support.
The anonymized historical records and simulated scenarios are realistic enough to model project risks and validate the E-RAF tool.
“These records were stripped of identifying details and used to model realistic project risks and mitigation workflows.”
The paper relies on this without support.
The 5×5 Probability-Impact Matrix is commonly used in project management and risk analysis for its simplicity and efficacy.
“The 5×5 Probability-Impact Matrix is commonly used in project management and risk analysis for its simplicity and efficacy.”
The paper relies on this without support.
Quantifying risks reduces subjective bias when determining criticality.
“Quantifying risks reduces subjective bias when determining criticality.”
The paper relies on this without support.
Traditional risk assessment tools frequently require specialized software platforms or extensive training.
“While traditional risk assessment tools frequently require specialized software platforms or extensive training, Excel was chosen due to its familiarity among project managers, powerful built-in functionalities, and flexibility to support data manipulation and visualization tasks.”
The paper relies on this without support.
The simulated and real project data used to validate E-RAF are sufficiently representative of real-world project environments to support conclusions about its effectiveness.
“Validating the E-RAF tool through simulated and real project data, showcasing effectiveness in iterative risk control.”
The paper relies on this without support.
Microsoft Excel is sufficiently familiar and accessible to intended users that E-RAF can be adopted without complex software investments.
“By leveraging Agile values and low-code technologies, E-RAF offers an accessible, iterative, and visually driven solution that enables organizations strengthen their risk management practices without the need for complex software investments.”
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
Each contradiction between two passages listed here was confirmed by an independent check.
Heatmap formula cannot produce Very Low for scores of 1-5
MajorTable 7 classifies scores of 1-5 as Very Low, but the Table 8 formula classifies each of those scores as Low. For scores on the stated 1-25 scale, the formula never returns Very Low.
“| IF(L2<=6,"Low","Very Low")))) | l |”
“| 1-5 | Very Low |”
A rating of 20 has two different risk levels
MinorThe registration example classifies a rating of 20 as Very High, while Table 7 assigns ratings of 16-20 to High. The conflicting thresholds affect risk prioritization.
“| RSK-001 | Delay in component delivery | Sprint 2 | admin Open | admin@ex ample.com | 2025-04-10 | 2025-05-05 | 4 | 5 | 20 | Very High |”
“| 16-20 | High |”
Sprint 5 is said to have no High risks despite two being listed
MinorThe sprint counts list two High risks in Sprint 5, contradicting the interpretation that Sprint 5 has no High risks.
“• Sprint 5: Shows a risk reduction trend with no High or Medium risks and six Very Low risks.”
“Sprint 1 Sprint 2 Sprint 3 Sprint 4 Sprint 5 Very High 4 5 0 0 0 High 1 2 3 2 2 Medium 1 0 5 6 0 Low 0 0 0 0 0 Very Low 0 0 0 0 6”
Citations
Cites
Software risk management: principles and practices
BOEHM, B. W. (1991) · IEEE Software · doi:10.1109/52.62930 · Cited by 1,599
Balancing Agility and Discipline: A Guide for the Perplexed
BOEHM, B. W. (2004) · Lecture notes in computer science · doi:10.1007/978-3-540-24675-6_1 · Cited by 1,183
Structured software development versus agile software development: a comparative analysis
Mishra, A., & Alzoubi, Y. I. (2023) · International Journal of Systems Assurance Engineering and Management · doi:10.1007/s13198-023-01958-5 · Cited by 188
Risk Analysis in Healthcare Organizations: Methodological Framework and Critical Variables
Pascarella, G., Rossi, M., Montella, E., Capasso, A., Feo, G. D., Botti, G., Nardone, A., Montuori, P., Triassi, M., D’Auria, S., et al. (2021) · Risk Management and Healthcare Policy · doi:10.2147/rmhp.s309098 · Cited by 118
COMPREHENSIVE REVIEW OF AGILE METHODOLOGIES IN PROJECT MANAGEMENT
Daraojimba, C., Nwasike, C. N., Adegbite, A. O., Ezeigweneme, C. A., & Gidiagba, J. O. (2024) · Computer Science & IT Research Journal · doi:10.51594/csitrj.v5i1.717 · Cited by 109
Agile software development projects–Unveiling the human-related critical success factors
Barros, L., Tam, C., & Varajão, J. E. (2024) · Information and Software Technology · doi:10.1016/j.infsof.2024.107432 · Cited by 79
Moran, A. (2014) · SpringerBriefs in computer science · doi:10.1007/978-3-319-05008-9 · Cited by 69
A framework for risk management in Scrum development process
Chaouch, S., Mejri, A., & Ghannouchi, S. A. (2019) · Procedia Computer Science · doi:10.1016/j.procs.2019.12.171 · Cited by 56
A Current Study on the Limitations of Agile Methods in Industry Using Secure Google Forms
Agrawal, A., Atiq, M. A., & Maurya, L. S. (2016) · Procedia Computer Science · doi:10.1016/j.procs.2016.02.056 · Cited by 39
QRA Model‐Based Risk Impact Analysis of Traffic Flow in Urban Road Tunnels
Meng, Q., Qu, X., Yong, K. T., & Wong, Y. H. (2011) · Risk Analysis · doi:10.1111/j.1539-6924.2011.01624.x · Cited by 35
A Risk Management Tool for Agile Software Development
Tavares, B. G., Keil, M., da Silva, C. E. S., & de Souza, A. D. (2020) · Journal of Computer Information Systems · doi:10.1080/08874417.2020.1839813 · Cited by 35
Behaviour-driven development and metrics framework for enhanced agile practices in scrum teams
Natarajan, T., & Pichai, S. (2024) · Information and Software Technology · doi:10.1016/j.infsof.2024.107435 · Cited by 35
Commonalities in Risk Management and Agile Process Models
Nyfjord, J., & Kajko‐Mattsson, M. (2007) · International Conference on Software Engineering Advances · doi:10.1109/icsea.2007.22 · Cited by 34
Project Management Tools for Agile Teams
MIHALACHE, A. (2017) · Informatica Economica · doi:10.12948/issn14531305/21.4.2017.07 · Cited by 31
A methodology for controlling bias and fairness in synthetic data generation
Barbierato, E., Vedova, M. L. D., Tessera, D., Toti, D., & Vanoli, N. (2022) · Applied Sciences · doi:10.3390/app12094619 · Cited by 30
Shafiee, S., Wautelet, Y., Friis, S., Lis, L., Harlou, U., & Hvam, L. (2021) · Computers in Industry · doi:10.1016/j.compind.2021.103432 · Cited by 30
Risk Management in Agile Software Development: A Survey
Hammad, M., Inayat, I., & Zahid, M. (2019) · International Conference on Frontiers of Information Technology (FIT) · doi:10.1109/fit47737.2019.00039 · Cited by 27
Risk management framework in Agile software development methodology
Zahedi, M. H., Kashanaki, A. R., & Farahani, E. D. (2023) · International Journal of Power Electronics and Drive Systems/International Journal of Electrical and Computer Engineering · doi:10.11591/ijece.v13i4.pp4379-4387 · Cited by 24
Challenges in Large-Scale Agile Software Development Projects
Saeeda, H., Ahmad, M. O., & Gustavsson, T. (2023) · ACM Symposium on Applied Computing · doi:10.1145/3555776.3577662 · Cited by 21
A Systematic Review of SCRUM in Software Development
Wonohardjo, E. P., Sunaryo, R. F., & Sudiyono, Y. (2019) · JOIV : International Journal on Informatics Visualization · doi:10.30630/joiv.3.2.167 · Cited by 17
A New Risk Assessment Approach for Agile Projects
Anes, V., Abreu, A. J. P. D. C. F., & Sousa-Santos, R. (2020) · International Young Engineers Forum (YEF-ECE) · doi:10.1109/yef-ece49388.2020.9171808 · Cited by 16
A Risk Management Framework for Scrum Projects
Lopes, S. D. S., de Souza, R. C. G., Contessoto, A. D. G., de Oliveira, A. L., & Braga, R. T. V. (2021) · International Conference on Enterprise Information Systems · doi:10.5220/0010448300300040 · Cited by 15
CASE Tools Usage and Impact on System Development Performance
Limayem, M., Khalifa, M., & Chin, W. W. (2004) · Journal of Organizational Computing and Electronic Commerce · doi:10.1207/s15327744joce1403_01 · Cited by 14
Software quality and CASE tools
Low, G., & Leenanuraksa, V. (2003) · International Workshop on Software Technology and Engineering Practice (STEP) · doi:10.1109/step.1999.798787 · Cited by 9
Sources of software development task friction
Bradley, N. C., Fritz, T., & Holmes, R. (2022) · Empirical Software Engineering · doi:10.1007/s10664-022-10187-6 · Cited by 8
Vaezi, A., Jones, S., & Asgary, A. (2024) · Journal of risk analysis and crisis response · doi:10.54560/jracr.v13i4.411 · Cited by 8
Shafir, M., Saha, P. P., Araf, A. T., Nishi, J. F., Hasan, M., & Sadia, F. (2025) · Procedia Computer Science · doi:10.1016/j.procs.2025.02.338 · Cited by 8
Evaluating Waterfall vs. Agile Models in Software Development for Efficiency and Adaptability
Gupta, S., Dutta, P. K., Roy, S., Bhaduri, A., Maji, K., Choudhary, A., & Sarkar, A. (2024) · Advances in logistics, operations, and management science book series · doi:10.4018/979-8-3693-3318-1.ch008 · Cited by 6
Explicit Risk Management in Agile Software Projects: Its Relevance and Benefits
Thom-Manuel, O. M. (2022) · Asian Journal of Research in Computer Science · doi:10.9734/ajrcos/2022/v14i330340 · Cited by 4
Creating High-Quality Synthetic Health Data: Framework for Model Development and Validation
Sichani, E. K., Smith, A. M., Emam, K. E., & Mosquera, L. (2024) · JMIR Formative Research · doi:10.2196/53241 · Cited by 3
Esiefarienrhe, B. M., & Monageng, T. (2024) · Journal of Infrastructure Policy and Development · doi:10.24294/jipd.v8i8.4503 · Cited by 3
Self-citationRequirements Risk Management for Continuous Development: Organisational Needs
Kainulainen, S., Tuunanen, T., & Vartiainen, T. (2024) · AJIS. Australasian journal of information systems/AJIS. Australian journal of information systems/Australian journal of information systems · doi:10.3127/ajis.v28.4441 · Cited by 3
(2025) · Texila international journal of management · doi:10.21522/tijmg.2015.11.01.art015 · Cited by 3
How to Make Sure Your Design Is Reasonably Safe and Sustainable
Moran, S. (2015) · Elsevier eBooks · doi:10.1016/b978-0-12-800242-1.00015-3 · Cited by 1
Flagged first, then by citations
Research works printed but not linked: 4
- Thapelo Monageng, 'Development using Scrum: A CASE Tool Approach', vol. 13, no. 2, pp. 1542- 1549, 2025.
- I. Sommerville, Software Engineering, 10th ed. Boston, MA: Pearson, 2016.
- PMI, 'A guide to the project management body of knowledge (PMBOK® guide) (7th ed.)'. Project Management Institute, 2021.
- K. C. Obondia, 'The utilization of project risk monitoring and control practices and their relationship with pro-ject success in construction projects', Journal of Project Management, vol. 7, no. 1, pp. 35- 25, 2022.
Cited by
Still being checked.
Metadata
- Authors
- Monageng, T., & Esiefarienrhe, B. M.
- Affiliations
- North-West University (ZA)
- Venue
- Indonesian Journal of Information Systems
- Publisher
- Universitas Atma Jaya Yogyakarta
- Published
- 2026-02-28
- Volume
- 8
- Issue
- 2
- Pages
- 157-174
- ISSN
- 2623-0119 (ISSN-L)
- 2623-2308
- OpenAlex
- W7165476883
- Semantic Scholar
- ffd8d41fbaf035b7eeef9a9ffe1465f1d9136d7e
- Cited by
- 0
- References
- 34
- FWCI
- 0.00
- Type
- journal article
- Language
- en
- Open access
- diamond
- doi.org
- Licence
- Locations
- Indonesian Journal of Information Systems (publishedVersion, cc-by-sa)
- Topics
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Social Sciences › Decision Sciences › Management Science and Operations Research › Construction Project Management and Performance
- Social Sciences › Business, Management and Accounting › Management Information Systems › Decision Support System Applications
- Keywords
- risk assessment, risk management, Scrum, computer-aided software engineering, Microsoft Excel, risk register, risk matrix, real-time dashboard, automated risk assessment
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
A language model drew the claims from the paper on 2026-11-07, under version 3 of the claim definition (model deepseek-v4.1-flash, prompt extract-v3).
A second model labelled each claim on 2026-11-07 (model jev-1.13-20260917, definition revision gold-guideline-v0.2).
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review