Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
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
The Mini Book of Agile

You're reading from   The Mini Book of Agile Everything you really need to know about Agile, Agile Project Management and Agile Delivery

Arrow left icon
Product type Paperback
Published in Mar 2022
Publisher Packt
ISBN-13 9781803238715
Length 50 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
YESI EDUCATION YESI EDUCATION
Author Profile Icon YESI EDUCATION
YESI EDUCATION
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

1. Chaper 1: Introduction
2. Chapter 2: What is Agile? FREE CHAPTER
3. Chapter 3: Why go Agile?
4. Chapter 4: How it all began
5. Chapter 5: The Different Agile Methodologies
6. Chapter 6: Agile Principles
7. Chapter 7: The Agile Culture
8. Chapter 8: Agile Roles
9. Chapter 9: Agile Concepts
10. Chapter 10: Agile Artifacts
11. Chapter 11: Agile Rituals
12. Chapter 12: Agile Tools
13. Chapter 13: Agile vs. Waterfall
14. Chapter 14: Agile FAQs
15. Chapter 15: Agile Myths
16. Chapter 16: The Agile Knowledge Base | AgileKB.com

Chapter 9: Agile Concepts

Sprints

A sprint is basically a fixed period of time in which a set of work gets done. In Agile we call this fixed period of time a timebox or sprint and the set of work "user stories." Don't worry we'll go over the concept of user stories soon.

Sprints can last between 1–4 weeks, but they typically last 2 weeks. Just keep in mind this varies from team to team and there's no right or wrong answer on that. 

Some Agile teams have Sprints that last 1 week, others have Sprints that last 2 weeks or 3 whilst others prefer working with 4 week Sprints. The key point here being that Sprints are fixed periods of time, so they shouldn't vary over time but should remain constant at all times.

Although, Agile teams can decide to alter their Sprint duration if they consider it would work best for them after going through a couple of Sprints.

So Sprints end up being like repetitive cycles in which the Agile team delivers a set...

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