Facilitating Task Breakdown in Sprint Planning Meeting 2 with an Interaction Room: An Experience Report

Grapenthin, Simon; Poggel, Steven; Book, Matthias; Gruhn, Volker

doi:10.1109/seaa.2014.71

Cited by 9 publications

(6 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In addition to our previously published findings from Project A [8], this article provides additional quantitative and qualitative observations from Project B. We present the quantitative results from both projects in the following section, report on our qualitative observations in Sect.…”

Section: Methodsmentioning

confidence: 91%

See 1 more Smart Citation

Improving task breakdown comprehensiveness in agile projects with an Interaction Room

Grapenthin

Poggel²,

Book

et al. 2015

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

Section: Methodsmentioning

confidence: 91%

“…(We have redrawn the burndown charts in this article to improve readability. Some of the original hand-drawn charts can be found in [8]. )…”

Section: Methodsmentioning

confidence: 99%

Improving task breakdown comprehensiveness in agile projects with an Interaction Room

Grapenthin

Poggel²,

Book

et al. 2015

Information and Software Technology

Self Cite

View full text Add to dashboard Cite

“…Prior work analyzed a variety of factors influencing the software development effort (so-called effort drivers). Trendowicz et al [20] reviewed and divided the most commonly used effort drivers into four categories: personnel factors (i.e., team capabilities and experience [5], [9], [21], [22]), process factors (i.e., quality of methods, tools and technologies applied [23]- [25]), project factors (i.e., project resources and management activities [26], [27]) and product factors (i.e., effort for requirements analysis, design and coding [28]). Personnel factors and project factors are the top mentioned effort drivers in agile projects [12].…”

Section: Factors Influencing Software Development Effortmentioning

confidence: 99%

Factors Affecting On-Time Delivery in Large-Scale Agile Software Development

Kula

Greuter²,

Deursen

et al. 2022

IIEEE Trans. Software Eng.

View full text Add to dashboard Cite

Late delivery of software projects and cost overruns have been common problems in the software industry for decades. Both problems are manifestations of deficiencies in effort estimation during project planning. With software projects being complex socio-technical systems, a large pool of factors can affect effort estimation and on-time delivery. To identify the most relevant factors and their interactions affecting schedule deviations in large-scale agile software development, we conducted a mixed-methods case study at ING: two rounds of surveys revealed a multitude of organizational, people, process, project and technical factors which were then quantified and statistically modeled using software repository data from 185 teams. We find that factors such as requirements refinement, task dependencies, organizational alignment and organizational politics are perceived to have the greatest impact on on-time delivery, whereas proxy measures such as project size, number of dependencies, historical delivery performance and team familiarity can help explain a large degree of schedule deviations. We also discover hierarchical interactions among factors: organizational factors are perceived to interact with people factors, which in turn impact technical factors. We compose our findings in the form of a conceptual framework representing influential factors and their relationships to on-time delivery. Our results can help practitioners identify and manage delay risks in agile settings, can inform the design of automated tools to predict schedule overruns and can contribute towards the development of a relational theory of software project management.

show abstract

“…This approach has the advantage of engaging team members in improving the team's deficiencies. Graphenthin et al [1] facilitates task breakdown by using a meeting room with four whiteboards. Each board is used to analyze a single aspect, i.e., business, integration, data, and interaction) of a backlog item.…”

Section: Related Workmentioning

confidence: 99%

“…In a scenario of sustained unpredictability, where projects suffer from constant scope changes, agile methods tend to reflect stakeholders' requirements along the project course. During the last few years, the Scrum framework becomes standard for most companies in the software industry, despite presenting challenges in the planning phase [1]. Another challenge is its dependency on empirical methods based on developers' experience to estimate project tasks accurately.…”

Section: Introductionmentioning

confidence: 99%

Improving Workload Estimation in Inexperienced Teams with Hybrid Agile Approach

Pires¹,

Pahins²,

Fonseca³

2020

Computer Science &Amp; Information Technology (CS &Amp; IT)

View full text Add to dashboard Cite

SCRUM framework is an agile technique that is widely used by development teams in order deliver incremental value to customers and dynamically react to project needs. SCRUM framework might be adapted to conform the development team specificities. In the context of an industry project, we have found that an inexperienced development team frequently faced difficulties with estimating the time needed to complete tasks, which led to missed deadlines in most of the projects. Such problem hampers the risk management and degrades the relationship with the customer. Upon closer analysis, it was identified that the main reason to this issue was the team's inability to breaking down a larger task into smaller sub-tasks and associate a realistic workload to each part. Then, based on traditional techniques, a structured approach to workload estimation was introduced in the SCRUM planning meeting to leverage the team's estimation skill. This approach was implemented in two development projects and increased the accuracy in the estimate defined by the team, yielding realistic schedules and increasing technical visibility.

show abstract

Facilitating Task Breakdown in Sprint Planning Meeting 2 with an Interaction Room: An Experience Report

Cited by 9 publications

References 2 publications

Improving task breakdown comprehensiveness in agile projects with an Interaction Room

Improving task breakdown comprehensiveness in agile projects with an Interaction Room

Factors Affecting On-Time Delivery in Large-Scale Agile Software Development

Improving Workload Estimation in Inexperienced Teams with Hybrid Agile Approach

Contact Info

Product

Resources

About