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 15. The Developer
Most XP practices concern the day-to-day work of producing code. This is the job of the developer: to turn customer stories into working code.
The developer role in planning and implementing features depends on knowing and understanding technical issues. Developers create and maintain the system as it evolves. They must answer the questions: “How will we implement it?”, “How long will it take?”, and “What are the risks?”
Developers work with the customer to understand his stories. From a story, the developers decide its implementation. The developers then estimate the amount of work each story will take, based on the implementation decisions and their experience on the project so far. These estimates help the customer to schedule the most valuable work for the next iteration by answering the question of how long.
While creating task cards from the story cards or implementing tasks during the programming cycle, developers may identify features that depend on other features. They may also find risky features that use new technology, are poorly understood, or are otherwise complicated. Developers raise these issues with the customer, who considers them while making the schedule. In practice, these risks are rare—practicing simplicity reduces them.
Developer Rights
XP recognizes several developer rights:
To estimate their own work, by giving developers authority over technical decisions. (See Business Practice 2: Play the Planning Game in Part II.)
To work a sensible ...
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.