July 2003
Intermediate to advanced
106 pages
2h 11m
English
Content preview from Extreme Programming Pocket GuideBecome an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 8. Iteration Planning
A project’s primary purpose will remain constant—to produce the most valuable software for the customer. The customer’s values will change over time. Every iteration offers the chance to adjust the schedule to match those values. The iteration planning meeting brings the customer and developers together to reassess the project and to schedule the upcoming iteration. This meeting is customer driven. The customer sets priorities for the developers, choosing features to be implemented and delivered during the iteration.
Stories and Tasks
The customer presents his desired features as story cards (see Chapter 11 in Part IV). Story cards communicate the customer’s specifications to the developers. The customer has decided what must be done. Developers then estimate how long it will take. In this sense, iteration planning is also developer driven. These discussions produce task cards (see Chapter 12 in Part IV), one for each step required to implement the story.[7]
All stories should represent a few days worth of work at most. When first described, some stories may be too large or too difficult to estimate. Ask the customer to elaborate or to split one story into smaller stories. Over time, everyone will develop a sense for what makes a good story.
As the project progresses, business changes can affect pending stories. The customer should re-evaluate them as necessary. Tasks can also change if their stories change or if existing code can be reused for the story. ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
More than 5,000 organizations count on O’Reilly
O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.Julian F.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.Addison B.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.Amir M.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.