Your SlideShare is downloading. ×
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Agile, Shakespeare-Style - Tim Berglund
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Agile, Shakespeare-Style - Tim Berglund

83

Published on

By now, we are all familiar with the new orthodoxy: the product owner discerns the needs of the customer and feeds them to developers in the form a prioritized backlog. Developers pull work from that …

By now, we are all familiar with the new orthodoxy: the product owner discerns the needs of the customer and feeds them to developers in the form a prioritized backlog. Developers pull work from that backlog, always confident that they're working on the highest-priority feature at the moment, and never having to worry about how those priorities are allocated. This system is simple, efficient, and has helped many teams function better than they used to. It's also time for the system to die. A few revolutionary companies are experimenting with the idea that developers should be in charge not only of when they build new features, but _what_ features to build. Rather than mere code technicians following the will of a product and marketplace expert, developers themselves become experts in their product domain, building the tools users need—by conceiving of those tools themselves. Dispensing with the product owner creates an entirely new organizational tenor: one in which everyone is encouraged to master the business's domain, to organize their work in autonomous ways, and to take ownership of the purpose for which the organization exists.

Published in: Education, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
83
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. TheRebellionofJackCade2Tuesday, June 4, 13
  • 2. AgileOrthodoxy3Tuesday, June 4, 13
  • 3. Developers?4Tuesday, June 4, 13
  • 4. Drive5Tuesday, June 4, 13
  • 5. Autonomy6Tuesday, June 4, 13
  • 6. Mastery7Tuesday, June 4, 13
  • 7. Purpose8Tuesday, June 4, 13
  • 8. All-VolunteerArmy9Tuesday, June 4, 13
  • 9. Happiness10Tuesday, June 4, 13
  • 10. AsynchronousWork11Tuesday, June 4, 13
  • 11. Objections12Tuesday, June 4, 13
  • 12. AndoftentimesexcusingofafaultDothmakethefaulttheworsebytheexcuse.13Tuesday, June 4, 13
  • 13. CrapWork?14Tuesday, June 4, 13
  • 14. YouMakeDevTools15Tuesday, June 4, 13
  • 15. Youarethetop1%16Tuesday, June 4, 13
  • 16. RealExceptions?17Tuesday, June 4, 13
  • 17. Consulting18Tuesday, June 4, 13
  • 18. InternalIT19Tuesday, June 4, 13
  • 19. NoMoreExcuses20Tuesday, June 4, 13
  • 20. Rebellion!21Tuesday, June 4, 13
  • 21. 22Tuesday, June 4, 13

×