Book ChapterDOI
Using Silent Grouping to Size User Stories
Ken Power
- pp 60-72
Reads0
Chats0
TLDR
This paper describes a technique called Silent Grouping that can be used to compliment Planning Poker, explaining how to apply it so that large sets of user stories can be sized in minutes.Abstract:
User stories are used to describe the functionality delivered in a product or system. Planning Poker is a common technique for sizing user stories, however it has challenges. It can be time consuming and teams can get bogged down in unnecessary discussion. This paper describes a technique called Silent Grouping that can be used to compliment Planning Poker, explaining how to apply it so that large sets of user stories can be sized in minutes. Experiences of seven Scrum teams from Cisco’s Unified Communications Business Unit are used as examples. The paper shows how to apply the technique with co-located teams, and includes an example of how it was used with distributed teams. Silent Grouping has several advantages. It is fast, which in turn leads to significant time and cost savings. It also has more subtle benefits. This paper discusses the techniques, challenges, cost savings and benefits of Silent Grouping.read more
Citations
More filters
Proceedings ArticleDOI
Effort estimation in agile software development: a systematic literature review
TL;DR: Subjective estimation techniques, e.g. expert judgment-based techniques, planning poker or the use case points method are the one used the most in agile effort estimation studies, thus suggesting numerous possible avenues for future work.
Proceedings ArticleDOI
Effort Estimation in Global Software Development: A Systematic Literature Review
TL;DR: The results suggest that there is room to improve the current state of the art on effort estimation in GSD, as there are evidences that the colocated approaches do not fit to GSD.
Journal ArticleDOI
A systematic review of distributed Agile software engineering
TL;DR: The objectives of this work are to investigate and find out the most important risks that threaten a DASE approach and what mitigation strategies exist to address them.
Journal ArticleDOI
Effort estimation across mobile app platforms using Agile processes: a systematic literature review
TL;DR: This paper presents the results of a Systematic Literature Review (SLR) concerning effort and size estimation models in mobile application development; this is followed by a summary of estimation techniques used across mobile apps.
Challenges of using software size in agile software development: A systematic literature review
Tuna Hacaloglu,Onur Demirörs +1 more
TL;DR: Academic Papers at IWSM Mensura 2018; Beijing; China; 19 September 2018 through 20 September 2018.
References
More filters
Book
Extreme Programming Explained: Embrace Change
TL;DR: You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Book
Agile Software Development with SCRUM
Ken Schwaber,Mike Beedle +1 more
TL;DR: This book describes building systems using the deceptively simple process, Scrum, a new approach to systems development projects that cuts through the ocmplexity and ambiguity of complex, emergent requiremetns and unstable technology to iteratively and quickly produce quality software.
Book
User Stories Applied: For Agile Software Development
TL;DR: The best way to build software that meets users' needs is to begin with "user stories": simple, clear, brief descriptions of functionality that will be valuable to real users.
Book
Agile Estimating and Planning
TL;DR: This book describes how a two year planning assignment on two large aerospace programs and prior experience as a Program Management Officer for the IT portion of a very large Department of Energy program led to this book.
Book
Succeeding with Agile: Software Development Using Scrum
TL;DR: In this paper, Cohn presents detailed recommendations, powerful tips, and real-world case studies drawn from his unparalleled experience helping hundreds of software organizations make Scrum and agile work, including how to transition to new roles, structuring teams, scaling up, working with a distributed team, and implementing effective metrics and continuous improvement.