Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
The Extreme Decade
Progress, Pain, Paradox
Ron Jeffries   Chet Hendrickson
Knowing all the tasks...
He's Canadian,
you know...
Chris Matts
Mary Poppendieck
Estimating work...
Watch the video at
http://link.jbrains.ca/pVURX3
Knowing how quickly we go...
He's Canadian,
you know...
Promiscuous Pairing and Beginner’s Mind:
                                                Embrace Inexperience



         ...
Promiscuous Pairing and Beginner’s Mind:
                                                Embrace Inexperience



         ...
Eliyahu Moshe Goldratt
31.03.1947–11.06.2011
I promised you a paradox...
Agile
agile
Ron Jeffries   Chet Hendrickson
Corey Haines
               J. B. Rainsberger
XP
Bill Caputo




FOR ME, XP AIN’T OUT THERE,
        IT’S IN HERE.
Watch the video at
http://link.jbrains.ca/ojPnyd
ME@JBRAINS.CA
         europeantour2011.com




The Extreme Decade
Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
The Extreme Decade: Progress, Pain, Paradox
You’ve finished this document.
Download and read it offline.
Upcoming SlideShare
The Next Decade (of Agile Software Development)
Next
Upcoming SlideShare
The Next Decade (of Agile Software Development)
Next
Download to read offline and view in fullscreen.

Share

The Extreme Decade: Progress, Pain, Paradox

Download to read offline

I have had the privilege of observing and participating in the agile software community for ten years, and in that time have witnessed much success, much failure, much consternation and much confusion. I will take a random walk through the Extreme decade, during which the community has pushed the limits of what it means to do less and achieve more.

I won’t try to answer the question of whether we’ve advanced the start of the art, but I’ll share with you what I’ve seen, what I’ve done, what I’d like to see next, and perhaps how you can make your mark. I hope that you’ll leave with tougher questions than you had when you came in.

Related Books

Free with a 30 day trial from Scribd

See all

The Extreme Decade: Progress, Pain, Paradox

  1. 1. The Extreme Decade Progress, Pain, Paradox
  2. 2. Ron Jeffries Chet Hendrickson
  3. 3. Knowing all the tasks...
  4. 4. He's Canadian, you know...
  5. 5. Chris Matts
  6. 6. Mary Poppendieck
  7. 7. Estimating work...
  8. 8. Watch the video at http://link.jbrains.ca/pVURX3
  9. 9. Knowing how quickly we go...
  10. 10. He's Canadian, you know...
  11. 11. Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience Arlo Belshee Architect Silver Platter Software Pasadena, CA 91103 (503) 265-1263 a_xp@arlim.org the paramount concerns. Performance was second, and Abstract features were a distant third. The company was a startup, so we were tight on both Many traditional software practices stress the cash and time. The company was typically operating with importance of programming in Flow. XP directly between -30 and 180 Days ‘Till Broke. Our contracts all challenges the assertion that Flow is critical and had lead times of 3-5 years. This meant that sales had to proclaims Pair Flow. start at the same time as engineering. Thus, engineering Both Flow states are fragile. They are easily disrupted had to produce many sales demos and to frequently alter by outside distraction or task rotation. Both take a long the product to more closely fit the needs of a particular time to enter. Furthermore, it takes days for a given pair customer. to be comfortable enough with each other to be able to Due to these influences, we chose a software process achieve Pair Flow at all. with rapid feedback and change. We ran the shortest My team at Silver Platter discovered that there is a third iterations we could (1 week) to get the most data possible. option to achieve high-efficiency programming. Our team We tracked our metrics closely, and we ran several spent the majority of its time in Beginner’s Mind. experiments each iteration. We used the metrics to decide Whereas Flow depends on stability, Beginner’s Mind what worked and to what degree. We then adopted those depends on instability, yet provides similar efficiency things that worked and started the next set of experiments. gains to a constant state of Flow. Chief among these experiments were variations on
  12. 12. Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience Arlo Belshee Architect Silver Platter Software Pasadena, CA 91103 (503) 265-1263 a_xp@arlim.org the paramount concerns. Performance was second, and Abstract features were a distant third. The company was a startup, so we were tight on both Many traditional software practices stress the cash and time. The company was typically operating with importance of programming in Flow. XP directly between -30 and 180 Days ‘Till Broke. Our contracts all challenges the assertion that Flow is critical and had lead times of 3-5 years. This meant that sales had to proclaims Pair Flow. start at the same time as engineering. Thus, engineering Both Flow states are fragile. They are easily disrupted had to produce many sales demos and to frequently alter by outside distraction or task rotation. Both take a long the product to more closely fit the needs of a particular time to enter. Furthermore, it takes days for a given pair customer. to be comfortable enough with each other to be able to Due to these influences, we chose a software process achieve Pair Flow at all. with rapid feedback and change. We ran the shortest My team at Silver Platter discovered that there is a third iterations we could (1 week) to get the most data possible. option to achieve high-efficiency programming. Our team We tracked our metrics closely, and we ran several spent the majority of its time in Beginner’s Mind. experiments each iteration. We used the metrics to decide Whereas Flow depends on stability, Beginner’s Mind what worked and to what degree. We then adopted those depends on instability, yet provides similar efficiency things that worked and started the next set of experiments. gains to a constant state of Flow. Chief among these experiments were variations on
  13. 13. Eliyahu Moshe Goldratt 31.03.1947–11.06.2011
  14. 14. I promised you a paradox...
  15. 15. Agile
  16. 16. agile
  17. 17. Ron Jeffries Chet Hendrickson
  18. 18. Corey Haines J. B. Rainsberger
  19. 19. XP
  20. 20. Bill Caputo FOR ME, XP AIN’T OUT THERE, IT’S IN HERE.
  21. 21. Watch the video at http://link.jbrains.ca/ojPnyd
  22. 22. ME@JBRAINS.CA europeantour2011.com The Extreme Decade Progress, Pain, Paradox
  • whilpert

    Mar. 12, 2020
  • up1

    May. 31, 2015
  • nfrolov

    Sep. 26, 2011

I have had the privilege of observing and participating in the agile software community for ten years, and in that time have witnessed much success, much failure, much consternation and much confusion. I will take a random walk through the Extreme decade, during which the community has pushed the limits of what it means to do less and achieve more. I won’t try to answer the question of whether we’ve advanced the start of the art, but I’ll share with you what I’ve seen, what I’ve done, what I’d like to see next, and perhaps how you can make your mark. I hope that you’ll leave with tougher questions than you had when you came in.

Views

Total views

1,306

On Slideshare

0

From embeds

0

Number of embeds

64

Actions

Downloads

9

Shares

0

Comments

0

Likes

3

×