Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Scaling Agile with Jira Align

You're reading from   Scaling Agile with Jira Align A practical guide to strategically scaling agile across teams, programs, and portfolios in enterprises

Arrow left icon
Product type Paperback
Published in Nov 2020
Publisher Packt
ISBN-13 9781800203211
Length 326 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Authors (2):
Arrow left icon
Dean MacNeil Dean MacNeil
Author Profile Icon Dean MacNeil
Dean MacNeil
Aslam Cader Aslam Cader
Author Profile Icon Aslam Cader
Aslam Cader
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

Preface 1. Section 1: Preparing for Jira Align
2. Chapter 1: Introducing Jira Align FREE CHAPTER 3. Chapter 2: Implementing Jira Align 4. Chapter 3: Navigating Jira Align 5. Section 2: Problem-Solving with Jira Align
6. Chapter 4: Team Challenges 7. Chapter 5: Program Planning Challenges 8. Chapter 6: Program Execution Challenges 9. Chapter 7: Enterprise and Portfolio Challenges 10. Section 3: Special Use Cases and Add-Ons
11. Chapter 8: Bimodal Development, Advanced Data Security, and Analytics 12. Assessments 13. Other Books You May Enjoy

Sizing stories with estimation games

Estimation, the process of predicting the most realistic effort required to deliver work items based on incomplete and uncertain input, is a typical challenge among development teams. Agile frameworks leverage relative estimating to mitigate this challenge. The power of relative estimating lies in accuracy over precision. If we were to ask you to look out the window and tell us how tall two buildings across the street are, chances are you couldn't give precise heights in feet or meters, but you could accurately state that one building is twice as tall as the other. Relative estimating allows teams to do the same thing with user stories. For reference, they start with a small, simple, and well-understood story (typically something that their team could build, test, and deploy in a day) and call it a 1-point story. They then estimate other stories relative to the 1-point story. For example, are they 2, 3, 5, or 8 times the volume, complexity...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime