BIBLIOGRAPHY
The following are suggested additional reading materials, subdivided by section and/or topic:
SECTION 2—AN INTRODUCTION TO AGILE
Briggs, Sara. “Agile Based Learning: What Is It and How Can It Change Education?” Opencolleges.edu.au February 22, 2014, retrieved from http://www.opencolleges.edu.au/informed/features/agile-based-learning-what-is-it-and-how-can-it-change-education/.
Manifesto for Agile Software Development, 2001, http://agilemanifesto.org/.
Peha, Steve. “Agile Schools: How Technology Saves Education (Just Not the Way We Thought it Would).” InfoQ. June 28, 2011, retrieved from https://www.infoq.com/articles/agile-schools-education.
Principles behind the Agile Manifesto, 2001, http://agilemanifesto.org/principles.html.
Rothman, Johanna. 2007. Manage It! Your Guide to Modern, Pragmatic Project Management. Raleigh: Pragmatic Bookshelf.
Sidky, Ahmed (Keynote). 2015. https://www.slideshare.net/AgileNZ/ahmed-sidky-keynote-agilenz.
Stacey Complexity Model. 2016. http://www.scrum-tips.com/2016/02/17/stacey-complexity-model/.
SECTION 3—LIFE CYCLE SELECTION
“Agile Modeling (AM) Home Page: Effective Practices for Modeling and Documentation,” Agile Modeling, (n.d.), http://www.agilemodeling.com/
Anderson, David, and Andy Carmichael. 2016. Essential Kanban Condensed. Seattle: Blue Hole Press.
Anderson, David. 2010. Kanban: Successful Evolutionary Change for Your Technology Business. Seattle: Blue Hole Press.
Benson, Jim, and Tonianne DeMaria Barry. 2011. Personal Kanban: Mapping Work | Navigating Life. Seattle: Modus Cooperandi Press.
Burrows, Mike. 2014. Kanban from the Inside: Understand the Kanban Method, connect it to what you already know, introduce it with impact. Seattle: Blue Hole Press.
Domain Driven Design Community. 2016. http://dddcommunity.org/.
Gothelf, Jeff, and Josh Seiden. 2016. Lean UX: Designing Great Products with Agile Teams. Sebastopol: O'Reilly Media.
Hammarberg, Marcus, and Joakim Sunden. 2014. Kanban in Action. Shelter Island: Manning Publications.
“Kanban,” Wikipedia, last modified May 4, 2017, retrieved on November 22, 2016 from https://en.wikipedia.org/wiki/Kanban.
“Kanban (development),” Wikipedia, last modified May 4, 2017, retrieved on November 29, 2016 from https://en.wikipedia.org/wiki/Kanban_(development).
Larsen, Diana, and Ainsley Nies. 2016. Liftoff: Start and Sustain Successful Agile Teams. Raleigh: Pragmatic Bookshelf.
“Learning Kanban,” Leankit, (n.d.), https://leankit.com/learn/learning-kanban/.
Leopold, Klaus, and Siegrfried Kaltenecker. 2015. Kanban Change Leadership: Creating a Culture of Continuous Improvement. Hoboken: Wiley.
“Make a big impact with software products and projects!” Impact Mapping, (n.d.), https://www.impactmapping.org/.
Patton, Jeff, and Peter Economy. 2014. User Story Mapping: Discover the Whole Story, Build the Right Product. Sebastopol: O'Reilly Media.
Reinertsen, Donald. 2009. The Principles of Product Development Flow: Second Generation Lean Product Development. Redondo Beach: Celeritas Publishing.
Rothman, Johanna. “Dispersed vs. Distributed Teams,” Rothman Consulting Group, Inc., October 25, 2010, http://www.jrothman.com/mpd/2010/10/dispersed-vs-distributed-teams/.
Schwaber, Ken, and Jeff Sutherland. “The Scrum Guide™,” Scrum.org, July 2016, http://www.scrumguides.org/scrum-guide.html and http://www.scrumguides.org/docs/scrumguide/v2016/2016-Scrum-Guide-US.pdf#zoom=100.
Skarin, Mattias. 2015. Real-World Kanban: Do Less, Accomplish More with Lean Thinking. Raleigh: Pragmatic Bookshelf.
“The High Cost of Multitasking: 40% of Productivity Lost by Task Switching,” Wrike.com, September 24, 2015, https://www.wrike.com/blog/high-cost-of-multitasking-for-productivity/.
Wells, Don. “Extreme Programming: A Gentle Introduction,” Extreme Programming, October 8, 2013, http://www.extremeprogramming.org/.
SECTION 4—IMPLEMENTING AGILE:
Amabile, Teresa, and Steven Kramer. 2011. The Progress Principle: Using Small Wins to Ignite Joy, Engagement, and Creativity at Work. Boston: Harvard Business Review Press.
“Early Warning Signs of Project Trouble—Cheat Sheet, 2017, https://agilevideos.com/wp-content/uploads/2017/02/WarningSignsOfProjectTrouble-CheatSheet.pdf.
Dweck, Carol. 2006. Mindset: The New Psychology of Success. New York: Penguin Random House.
Kaner, Sam. Facilitator's Guide to Participatory Decision-Making. 3rd ed. 2014. San Francisco: Jossey-Bass.
Keith, Kent. The Case for Servant Leadership. 2008. Westfield: Greenleaf Center for Servant Leadership.
Rothman, Johanna. 2016. Agile and Lean Program Management: Scaling Collaboration Across the Organization. Victoria, British Columbia: Practical Ink.
Rothman, Johanna. “Dispersed vs. Distributed Teams,” Rothman Consulting Group, Inc., October 25, 2010, http://www.jrothman.com/mpd/2010/10/dispersed-vs-distributed-teams/.
Rothman, Johanna. 2007. Manage It! Your Guide to Modern, Pragmatic Project Management. Raleigh: Pragmatic Bookshelf.
Rothman, Johanna. 2016. Manage Your Project Portfolio: Increase Your Capacity and Finish More Projects. Raleigh: Pragmatic Bookshelf.
Schwaber, Ken, and Jeff Sutherland. “The Scrum Guide™,” Scrum.org, July 2016, http://www.scrumguides.org/scrum-guide.html and http://www.scrumguides.org/docs/scrumguide/v2016/2016-Scrum-Guide-US.pdf#zoom=100.
Sinek, Simon. 2011. Start with Why: How Great Leaders Inspire Everyone to Take Action. New York: Portfolio, Penguin Random House.
“The High Cost of Multitasking: 40% of Productivity Lost by Task Switching,” Wrike.com, September 24, 2015, https://www.wrike.com/blog/high-cost-of-multitasking-for-productivity/.
EXPERIENCE REPORTS:
“Experience Reports,” Agile Alliance, (n.d.), https://www.agilealliance.org/resources/experience-reports/.
PROJECT AND TEAM HEALTH:
“Early Warning Signs of Project Trouble—Cheat Sheet.” 2017. https://agilevideos.com/wp-content/uploads/2017/02/WarningSignsOfProjectTrouble-CheatSheet.pdf
“TeamHealth Radar – Summary View,” Agilehealth. 2014. http://agilityhealthradar.com/wp-content/uploads/2014/11/bigradar.gif.
RESOURCE EFFICIENCY:
Modig, Niklas, and Pär Åhlström. 2015. This is Lean: Resolving the Efficiency Paradox. London: Rheologica Publishing.
Rothman, Johanna. “Resource Efficiency vs. Flow Efficiency, Part 5: How Flow Changes Everything,” Rothman Consulting Group, Inc., September 20, 2015, http://www.jrothman.com/mpd/agile/2015/09/resource-efficiency-vs-flow-efficiency-part-5-how-flow-changes-everything/.
SCALING:
Disciplined Agile 2.X—A Process Decision Framework. 2016. http://www.disciplinedagiledelivery.com/.
Kniberg, Henrik. “Scaling Agile @ Spotify with Tribes, Squads, Chapters & Guilds,” Crisp, November 14, 2012, http://blog.crisp.se/2012/11/14/henrikkniberg/scaling-agile-at-spotify.
“Overview—Large Scale Scrum,” LeSS. 2016. http://less.works/.
“SAFe® for Lean Software and System Engineering,” SAFe®. 2016. http://www.scaledagileframework.com/.
SKILLS:
Beck, Kent. Paint Drip People, August 4, 2016, https://www.facebook.com/notes/kent-beck/paint-drip-people/1226700000696195/.
“Generalizing Specialists: Improving Your IT Career Skills,” Agile Modeling, (n.d.), http://www.agilemodeling.com/essays/generalizingSpecialists.htm.
Hunter, Brittany. “Of Software Designers & Broken Combs,” Atomic Object, June 27, 2013, https://spin.atomicobject.com/2013/06/27/broken-comb-people/.
SECTION 5—IMPLEMENTING AGILE: DELIVERING IN AN AGILE ENVIRONMENT
Larsen, Diana, and Ainsley Nies. 2016. Liftoff: Start and Sustain Successful Agile Teams. Raleigh: Pragmatic Bookshelf.
RETROSPECTIVES:
Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Raleigh: Pragmatic Bookshelf.
Gonçalves, Luis, and Ben Linders. 2015. Getting Value out of Agile Retrospectives: A Toolbox of Retrospective Exercises. Victoria, British Columbia: Leanpub.
BACKLOG:
Adzic, Gojko, Marjory Bissett, and Tom Poppendieck. 2012. Impact Mapping: Making a Big Impact with Software Products and Projects. Woking, Surrey: Provoking Thoughts.
Patton, Jeff, and Peter Economy. 2014. User Story Mapping: Discover the Whole Story, Build the Right Product. Sebastopol: O'Reilly Media.
Rothman, Johanna. “We Need Planning; Do We Need Estimation?” Rothman Consulting Group, Inc., January 21, 2015, http://www.jrothman.com/mpd/project-management/2015/01/we-need-planning-do-we-need-estimation/.
STANDUPS:
Brodzinski, Pawel. “Effective Standups around Kanban Board,” Brodzinski.com, December 30, 2011, http://brodzinski.com/2011/12/effective-standups.html.
Fowler, Martin. “It's Not Just Standing Up: Patterns for Daily Standup Meetings,” Martinfowler.com, February 21, 2016, http://martinfowler.com/articles/itsNotJustStandingUp.html.
Hefley, Chris. “How to Run Effective Standups and Retrospectives,” Leankit, September 15, 2014, https://leankit.com/blog/2014/09/run-effective-standups-retrospectives/.
EARNED VALUE:
Griffiths, Mike. “A Better S Curve and Simplified EVM,” Leading Answers, June 6, 2008, http://leadinganswers.typepad.com/leading_answers/2008/06/a-better-s-curve-and-simplified-evm.html.
SECTION 6—ORGANIZATIONAL CONSIDERATIONS FOR AGILE PROJECTS
Bankston, Arlen, and Sanjiv Augustine. Agile Team Performance Management: Realizing the Human Potential of Teams, June 14, 2010, www.lithespeed.com/transfer/Agile-Performance-Management.pptx.
Browder, Justin, and Brian Schoeff. Perfect Strangers: How Project Managers and Developers Relate and Succeed. CreateSpace Independent Publishing Platform, 2016, https://www.createspace.com/.
Griffiths, Mike. “Agile Talent Management,” Leading Answers, October 14, 2015, http://leadinganswers.typepad.com/leading_answers/2015/10/agile-talent-management.html.
Kohn, Alfie. 1999. Punished by Rewards: The Trouble with Gold Stars, Incentive Plans, A's, Praise, and Other Bribes. New York: Mariner Books.
Mar, Kane. “How to do Agile Performance Reviews,” Scrumology, (n.d.), https://scrumology.com/how-to-do-agile-performance-reviews/.
McChrystal, Stanley, Tantum Collins, David Silverman, and Chris Fussell. 2015. Team of Teams: New Rules of Engagement for a Complex World. New York: Portfolio, Penguin Random House.
Pink, Daniel. 2011. Drive: The Surprising Truth About What Motivates Us. New York: Riverhead Books.
SECTION 7—A CALL TO ACTION (INSPECTION WITHOUT ADAPTATION IS FUTILE)
Dennis, Pascal. 2006. Getting the Right Things Done: A Leader's Guide to Planning and Execution. Cambridge: Lean Enterprise Institute.
Griffiths, Mike. “Introducing Agile Methods: Mistakes to Avoid—Part 3,” Leading Answers, March 15, 2007, http://leadinganswers.typepad.com/leading_answers/2007/03/introducing_agi_2.html.
Little, Jason. Lean Change Management: Innovative Practices for Managing Organizational Change. Happy Melly Express, 2014, http://www.happymelly.com/category/hm-express/.
Rising, Linda, and Mary Lynne Manns. 2004. Fearless Change: Patterns for Introducing New Ideas. Upper Saddle River: Addison-Wesley Professional.
“The IDEAL Model,” Software Engineering Institute, Carnegie Mellon, 2006, http://www.sei.cmu.edu/library/assets/idealmodel.pdf.
ANNEX A1—PMBOK® GUIDE MAPPING
Larsen, Diana and Ainsley Nies. 2016. Liftoff: Start and Sustain Successful Agile Teams. Raleigh: Pragmatic Bookshelf.
ANNEX A2—AGILE MANIFESTO MAPPING
Manifesto for Agile Software Development, 2001, http://agilemanifesto.org/.
Principles behind the Agile Manifesto, 2001, http://agilemanifesto.org/principles.html.
ANNEX A3—OVERVIEW OF AGILE AND LEAN FRAMEWORKS
Agile Business Consortium, 2014, https://www.agilebusiness.org/what-is-dsdm.
Ambler, Scott. “The Agile Unified Process,” Ambysoft, May 13, 2006, http://www.ambysoft.com/unifiedprocess/agileUP.html.
Anderson, David. 2010. Kanban: Successful Evolutionary Change for Your Technology Business. Seattle: Blue Hole Press.
Beedle, Mike. Enterprise Scrum: Executive Summary: Business Agility for the 21st Century, January 7, 2017, http://www.enterprisescrum.com/enterprise-scrum/.
Cockburn, Alistair. 2004. Crystal Clear: A Human-Powered Methodology for Small Teams. Upper Saddle River: Pearson Education.
Cockburn, Alistair. “Crystal Methodologies,” alistair.cockburn.us, March 28, 2014, http://alistair.cockburn.us/Crystal+methodologies.
Disciplined Agile 2.X—A Process Decision Framework, 2016, http://www.disciplinedagiledelivery.com/.
Joint MIT-PMI-INCOSE Community of Practice on Lean in Program Management. 2012. The Guide to Lean Enablers for Managing Engineering Programs. Newtown Square, PA: Author.
“Kanban,” Wikipedia, last modified May 4, 2017, retrieved on November 22, 2016 from https://en.wikipedia.org/wiki/Kanban.
“Kanban (development),” Wikipedia, last modified May 4, 2017, retrieved on November 29, 2016 from https://en.wikipedia.org/wiki/Kanban_(development).
Reddy, Ajay, and Jack Speranza. 2015. The Scrumban [R]Evolution: Getting the Most Out of Agile, Scrum, and Lean Kanban. Boston: Addison-Wesley Professional.
“Overview—Large Scale Scrum,” LeSS, 2016, http://less.works/.
“SAFe® for Lean Software and System Engineering,” SAFe®, 2016, http://www.scaledagileframework.com/.
Schwaber, Ken, and Jeff Sutherland. “The Scrum Guide™,” Scrum.org, July 2016, http://www.scrumguides.org/scrum-guide.html and http://www.scrumguides.org/docs/scrumguide/v2016/2016-Scrum-Guide-US.pdf#zoom=100.
“Scrum of Scrums,” Agile Alliance, (n.d.), https://www.agilealliance.org/glossary/scrum-of-scrums/.
“Scrumban,” Wikipedia, March 2, 2017, https://en.wikipedia.org/wiki/Scrumban.
“State of Agile Report: Agile Trends,” VersionOne, 2017, http://stateofagile.versionone.com/.
Sutherland Jeff. “Agile Can Scale: Inventing and Reinventing SCRUM in Five Companies.” Cutter IT Journal 14, no. 12 (2001): 5–11. http://www.controlchaos.com/storage/scrum-articles/Sutherland200111proof.pdf.
“The 2015 State of Agile Development,” Scrum Alliance®, 2015, https://www.forrester.com/report/The+2015+State+Of+Agile+Development/-/E-RES122910
Wells, Don. “Extreme Programming: A Gentle Introduction,” Extreme Programming, October 8, 2013, http://www.extremeprogramming.org/.
Why Scrum? State of Scrum Report, 2016, https://www.scrumalliance.org/why-scrum/state-of-scrum-report/2016-state-of-scrum.
APPENDIX X2—ATTRIBUTES THAT INFLUENCE TAILORING
Griffiths, Mike. “Agile Suitability Filters,” Leading Answers, 2007, http://leadinganswers.typepad.com/leading_answers/files/agile_suitability_filters.pdf.
Jeffries, Ron. “We Tried Baseball and It Didn't Work,” ronjeffries.com, May 2, 2006, http://ronjeffries.com/xprog/articles/jatbaseball/.
Rothman, Johanna. “One Experimental Possibility: Self-Organization from Component Teams to Feature Teams,” Rothman Consulting Group, Inc., September 23, 2014, http://www.jrothman.com/mpd/agile/2014/09/one-experimental-possibility-self-organization-from-component-teams-to-feature-teams/.