Scrum in der Praxis

Erfahrungen, Problemfelder und Erfolgsfaktoren

Literatur

Literaturempfehlungen

Weiterführende Literatur zu den jeweiligen Kapiteln finden Sie unten stehen thematisch geordnet nach Kapiteln:

Literaturverweise

Dieser Abschnitt enthält die im Buch erwähnten Literaturverweise in alphabetischer Reihenfolge.

[URL:5 Whys] Wikipedia: 5 Whys. (http://en.wikipedia.org/wiki/5_Whys)

[Adkins 2010] Adkins, Lyssa: Coaching Agile Teams: A Companion for Scrum Masters, Agile Coaches, and Project Managers in Transition. Addison-Wesley, 2010.

[URL:Ambler] Ambler, Scott: Generalizing Specialists: Improving Your IT Career Skills, 2011. (http://www.agilemodeling.com/essays/generalizingSpecialists.htm)

[Appelo 2010] Appelo, Jurgen: Management 3.0: Leading Agile Developers, Developing Agile Leaders. Addison-Wesley Longman, 2010.

[URL:Appelo b] Appelo, Jurgen: The Happiness Door, Another Great Feedback Method, November 2011. (http://www.noop.nl/2011/11/the-happiness-door.html)

[Beck 2004] Beck, Kent: Extreme Programming Explained: Embrace Change. Addison-Wesley Longman, 2004.

[URL:Cockburn] Cockburn, Alistair: Walking Skeleton, Juni 1996. (http://alistair.cockburn.us/Walking+skeleton)

[Cohn 2004] Cohn, Mike: User Stories Applied (For Agile Software Development). Addison-Wesley, 2004.

[Cohn 2005] Cohn, Mike: Agile Estimating and Planning. Prentice Hall International, 2005.

[Cohn 2009] Cohn, Mike: Succeeding with Agile: Software Development using Scrum. Addison-Wesley Longman, 2009.

[URL:Cohn h] Cohn, Mike: Alternative Scrum Release-Burndown-Chart. (http://www.mountaingoatsoftware.com/scrum/alt-releaseburndown)

[URL:Cohn i] Cohn, Mike: Gasping about the Product Backlog, März 2012. (http://www.mountaingoatsoftware.com/blog/gasping-about-the-product-backlog)

[Covey 2004] Covey, Stephen R.: The 7 Habits of Highly Effective People: Powerful Lessons in Personal Change. Free Press, 2004.

[Csikszentmihalyi 2008] Csikszentmihalyi, Mihaly: Flow: The Psychology of Optimal Experience. Harper Perennial Modern Classics, 2008.

[Denning 2010] Denning, Stephen: The Leader’s Guide to Radical Management: Reinventing the Workplace for the 21st Century. John Wiley & Sons, 2010.

[DerbyLarsen 2006] Derby, Esther; Larsen, Diana: Agile Retrospectives: Making Good Teams Great. Pragmatic Programmers, 2006.

[URL:Deutschmann] Deutschmann, Alan: Inside the Mind of Jeff Bezos. August, 2004. (http://www.fastcompany.com/magazine/85/bezos_ 2.html)

[URL:Duan a] Duan, Shane: Team Estimation Game – By Steve Bockman, Januar 2008. (http://agileworks.blogspot.de/2008/01/team-estimation-game-by-steve-bockman.html)

[URL:Duan b] Duan, Shane: Burn-up and Burn-down Charts, Januar 2009. (http://agileworks.blogspot.de/2009/01/burn-up-and-burn-down-charts.html)

[Eckstein 2009] Eckstein, Jutta: Agile Softwareentwicklung mit verteilten Teams. dpunkt.verlag, 2009.

[Gansch 2006] Gansch, Christian: Vom Solo zur Sinfonie: Was Unternehmen von Orchestern lernen können. Eichborn, 2006.

[Gloger 2008] Gloger, Boris: Scrum: Produkte zuverlässig und schnell entwickeln. Hanser, 2008.

[URL:Goddard] Goddard, Paul: Quija Board Estimation, November 2010. (http://www.scrumalliance.org/articles/195-ouija-board-estimation)

[Greenleaf 2002] Greenleaf, Robert K.: Servant Leadership: A Journey Into the Nature of Legitimate Power and Greatness. Paul & Co, 2002.

[URL:HartmannPreuss] Hartmann Preuss, Deborah: Fearless Journey – the game that gets your team UnStuck. (http://tastycupcakes.org/2012 /03/fearless-journey-the-game-that-gets-your-team-unstuck/)

[URL:Hennessey] Hennessey, Justin: An Agile Team »Reset«, Februar 2012. (http://www.scrumalliance.org/articles/400-an-agile-team-reset)

[Holman 2007] Holman, Peggy: The Change Handbook: The Definitive Resource on Today’s Best Methods for Engaging Whole Systems. McGraw-Hill Professional, 2007.

[URL:James] James, Michael: An Example ScrumMaster’s Checklist, November 2010. (http://www.scrumalliance.org/articles/194-an-example-scrummasters-checklist)

[URL:Jeffries] Jeffries, Ron: Essential XP: Card, Conversation, Confirmation, August 2011. (http://xprogramming.com/articles/expcardconversationconfirmation/)

[Kerth 2001] Kerth, Norman L.: Project retrospectives: A handbook for team reviews. Dorset House Publishing, 2001.

[URL:King] King, James: Estimation Toolkit, Dezember 2010. (http://www.infoq.com/articles/estimation-toolkit)

[URL:Koontz c] Koontz, David A.: Exercise: Definition of Done, Oktober 2011. (http://agilecomplexificationinverter.blogspot.de/2011/09/ exercise-definition-of-done.html)

[URL:Larsen a] Larsen, Diana: Team Agility: Exploring Self-Organizing Software Development Teams. Februar 2004. (http://www.futureworksconsulting.com/resources/TeamAgilityAgileTimesFeb04.pdf)

[URL:Larsen b] Larsen, Diana: Impact and Energy, Mai 2008. (http://www.futureworksconsulting.com/blog/2008/05/16/impact-and-energy)

[LarsenNies 2012] Larsen, Diana; Nies, Ainsley: Liftoff: Launching Agile Teams & Projects. Onyx Neon Press, 2012.

[Leffingwell 2007] Leffingwell, Dean: Scaling software agility: best practices for large enterprises. Addison-Wesley Longman, 2007.

[URL:Mar] Mar, Kane: Scrum Trainers Gathering (4/4): Affinity Estimating, April 2008 (http://kanemar.com/2008/04/21/scrum-trainers-gathering-44-affinity-estimating/)

[URL:Miller] Miller, John: Values-Driven Retrospective, Dezember 2011. (http://tastycupcakes.org/2011/12/values-driven-retrospective-game)

[URL:Patton] Patton, Jeff: The new user story backlog is a map, August 2008. (http://www.agileproductdesign.com/blog/the_new_ backlog.html)

[Pichler 2008] Pichler, Roman: Scrum – Agiles Projektmanagement erfolgreich einsetzen. dpunkt.verlag, 2008.

[Pichler 2010] Pichler, Roman: Agile Product Management with Scrum: creating products that customers love. Addison-Wesley, 2010.

[URL:Pichler f] Pichler, Roman: The Product Owner on one Page, November 2010. (http://www.romanpichler.com/blog/roles/one-page-product-owner/)

[URL:Pichler g] Pichler, Roman: The Product Vision Board, Mai 2011. (http://www.romanpichler.com/blog/agile-product-innovation/the-product-vision-board/)

[Pink 2011] Pink, Daniel: Drive: The Surprising Truth About What Motivates Us. Canongate Books, 2011.

[Poppendieck 2003] Poppendieck, Mary; Poppendieck, Tom: Lean Software Development: An Agile Toolkit for Software Development Managers. Addison-Wesley Longman, 2003.

[Rasmussen 2010] Rasmussen, Jonathan: The Agile Samurai – How Agile Masters deliver great Software. The Pragmatic Bookshelf, 2010.

[URL:Röpstorff 2015] Röpstorff, Sven: Scrum-Team Diagnose, August 2015. (http://scrum-in-der-praxis.de/scrum-team-diagnose/)

[Scharmer 2011] Scharmer, Claus O.: Theorie U – Von der Zukunft her führen. Carl-Auer Verlag, 2011.

[URL:Schiffer c] Schiffer, Bernd: 42 Tasks for a Scrum Master’s Job, November 2011, (http://agiletrail.com/2011/11/14/42-tasks-for-a-scrum-masters-job/)

[URL:Schwaber] Schwaber, Ken; Sutherland Jeff: Scrum Guide 2013, Juli 2013. (http://www.scrumguides.org/)

[Semler 1993] Semler, Ricardo: Das Semco System: Management ohne Manager. Das neue revolutionäre Führungsmodell. Heyne, 1993.

[Senge 2006] Senge, Peter M.: The fifth discipline: Crown Business, 2006.

[ShoreWarden 2007] Shore, Jim; Warden, Shane: The art of agile development. O’Reilly Media, 2007.

[URL:Sims] Sims, Chris: Daily Scrum – The Fourth Question, November 2009. (http://blog.technicalmanagementinstitute.com/2009/11/daily-scrum-the-fourth-question.html)

[URL:Smith] Smith, M. K.: Bruce W. Tuckman – forming, storming, norming and performing in groups, the encyclopaedia of informal education, 2005. (http://www.infed.org/thinkers/tuckman.htm)

[URL:Sonmez] Sonmez, John: Even Backlogs Need Grooming, September 2011. (http://simpleprogrammer.com/2011/09/25/even-backlogs-need-grooming/)

[URL:Sutherland] Sutherland, Jeff: Leading vs. Managing in a Scrum Environment, März 2012. (http://scrum.jeffsutherland.com/2012/03/leading-versus-managing-in-scrum.html)

[URL:VersionOne] State of Agile Development Survey Results. (http://versionone.com/state_of_agile_development_survey/11)

[URL:Vodde a] Vodde, Bas: Top Ten Organizational Impediments, April 2009. (http://www.scrumalliance.org/articles/123-top-ten-organizational-impediments)

[URL: Weisbart 2011] Weisbart, Adam: Retrospective Cookies, September 2011. (http://weisbart.com/cookies)

[URL: Wiechmann 2015] Wiechmann, Robert: Die Sprintübersicht – Team-Verfügbarkeit visualisieren, August 2015. (http://scrum-in-der-praxis.de/die-sprint-uebersicht)

[URL: Wiechmann 2015 a] Wiechmann, Robert: Ein Sprint Review mit mehreren Teams verbessern, Juli 2015. (http://scrum-in-der-praxis.de/die-feedback-box-sprintreview-verbessern)

[Williams 2012] Williams, Laurie: What agile teams think of agile principles. Communications of the ACM Magazine, No. 4, 2012.

[Wirdemann 2011] Wirdemann, Ralf: Scrum mit User Stories. Hanser Verlag, 2011.