[Adzic2011] Adzic, Gojko. 2011. Specification by Example. New York: Manning Publications. https://learning.oreilly.com/library/view/specification-by-example/9781617290084.
[Adzic2012] Adzic, Gojko. 2012. Impact Mapping. Victoria, BC: Leanpub.
[Ambler2006] Ambler, Scott, and Pramodkumar Sadalage. 2006. Refactoring Databases: Evolutionary Database Design. Boston: Addison-Wesley Professional.
[Anderson2010] Anderson, David. 2013. Kanban. Blue Hole Press Inc.
[Austin1996] Austin, Robert D. 1996. Measuring and Managing Performance in Organizations. New York: Dorset House Publishing Co.
[Bache2018] Bache, Emily. 2018. “Introducing the Gilded Rose kata and writing test cases using Approval Tests.” YouTube. Video series. Eficode Praqma. https://www.youtube.com/watch?v=zyM2Ep28ED8; https://www.youtube.com/watch?v=OJmg9aMxPDI; https://www.youtube.com/watch?v=NADVhSjeyJA.
[Beck2000a] Beck, Kent. 2000. Extreme Programming Explained: Embrace Change, 1st ed. Boston: Addison-Wesley.
[Beck2000b] Beck, Kent, and Martin Fowler. 2000. Planning Extreme Programming. Boston: Addison-Wesley Professional.
[Beck2001] Beck, Kent et al. 2001. “Manifesto for Agile Software Development.” http://agilemanifesto.org.
[Beck2002] Beck, Kent. 2002. Test-Driven Development: By Example. Boston: Addison-Wesley Professional.
[Beck2004] Beck, Kent. 2004. Extreme Programming Explained, 2nd ed. Boston: Addison-Wesley Professional.
[Beck2007] Beck, Kent. 2007. Implementation Patterns. Boston: Addison-Wesley Professional. https://learning.oreilly.com/library/view/implementation-patterns/9780321413093.
[Beck2018] Beck, Kent. 2018. “test && commit || revert.” Medium. September 28, 2013. https://medium.com/@kentbeck_7670/test-commit-revert-870bbd756864.
[Beckhard1992] Beckhard, Richard, and Wendy Pritchard. 1992. Changing the Essence: The Art of Creating and Leading Fundamental Change in Organizations. San Francisco: Jossey-Bass.
[Belshee2005] Belshee, Arlo. 2005. “Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience.” Proceedings of the Agile Development Conference, July 24–29, 2005, 125–131. Washington, DC: IEEE Computer Society. http://dx.doi.org/10.1109/ADC.2005.37.
[Belshee2016a] Belshee, Arlo. 2016a. “WET: When DRY Doesn’t Apply.” Arlo Being Bloody Stupid (blog). April 7, 2016. https://arlobelshee.com/wet-when-dry-doesnt-apply.
[Belshee2016b] Belshee, Arlo. 2016b. “The Core 6 Refactorings.” Arlo Being Bloody Stupid (blog). May 2, 2016. https://arlobelshee.com/the-core-6-refactorings.
[Belshee2019] Belshee, Arlo. 2019. “Naming as a Process” (article series). Deep Roots (blog). October 10–17, 2019. https://www.digdeeproots.com/articles/on/naming-process.
[Benne1948] Benne, K. D., and Paul Sheats. 1948. “Functional roles of group members.” Journal of Social Issues: 4(2), 41–49. https://doi.org/10.1111/j.1540-4560.1948.tb01783.x.
[Bernhardt2012] Bernhardt, Gary. 2012. “Functional Core, Imperative Shell.” Destroy All Software (blog). July 12, 2012. https://www.destroyallsoftware.com/screencasts/catalog/functional-core-imperative-shell.
[Beyer2016] Beyer, Betsy, Chris Jones, Jennifer Petoff, and Niall Richard Murphy. 2016. Site Reliabililty Engineering: How Google Runs Production Systems, 1st ed. Sebastopol, CA: O’Reilly.
[Bland2019] Bland, David J., Alexander Osterwalder. 2019. Testing Business Ideas. Hoboken, NJ: Wiley. https://learning.oreilly.com/library/view/testing-business-ideas/9781119551447.
[Blank2020a] Blank, Steve. 2013. The Four Steps to the Epiphany, 3rd. ed. Palo Alto, CA: K&S Ranch.
[Blank2020b] Blank, Steve, and Bob Dorf. 2020. The Startup Owner’s Manual: The Step-By-Step Guide for Building a Great Company. Hoboken, NJ: Wiley.
[Bockeler2020] Böckeler, Birgitta, Siessegger, Nina. 2020. “On Pair Programming.” martinFowler.com (website). January 15, 2020. https://martinfowler.com/articles/on-pair-programming.html.
[Boeg2019] Boeg, Jesper. 2019. Level Up Agile with Toyota Kata: Beyond Method Wars, Establishing Core Lean/Agile Capabilities Through Systematic Improvement. (self-pub.)
[Boehm1987] Boehm, Barry. 1987. “Industrial Software Metrics Top 10 List.” IEEE Software 4(9): 84—85.
[Bossavit2013] Bossavit, Laurent. 2013. The Leprechuans of Software Engineering: How Folklore Turns Into Fact and What To Do About It. Victoria, BC: Leanpub.
[Brooks1995] Brooks, Frederick P. 1995. The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition. Boston: Addison-Wesley Professional.
[Cagan2017] Cagan, Marty. 2017. Inspired: How to Create Tech Products Customers Love. Hoboken, NJ: Wiley. https://learning.oreilly.com/library/view/inspired-2nd-edition/9781119387503.
[Clacey2020] Clacey, Kristen, Jay-Allen Morris. 2020. The Remote Facilitator’s Pocket Guide. San Francisco: Berrett-Koehler Publishers. https://learning.oreilly.com/library/view/the-remote-facilitators/9781523089123.
[Cockburn2001] Cockburn, Alistair, and Laurie Williams. 2001. “The Costs and Benefits of Pair Programming.” Extreme Programming Examined, edited by G. Succi and M. Marchesi, 223—247. Boston: Addison-Wesley. https://collaboration.csc.ncsu.edu/laurie/Papers/XPSardinia.PDF.
[Cockburn2006] Cockburn, Alistair. 2006. Agile Software Development: The Cooperative Game. Boston: Addison-Wesley Professional.
[Cockburn2008] Cockburn, Alistair. 2008. “Hexagonal Architecture.” https://alistair.cockburn.us/hexagonal-architecture.
[Cohn2005] Cohn, Mike. 2005. Agile Estimating and Planning. Upper Saddle River, NJ: Prentice Hall.
[Craver2016] Craver, Nick. 2016. “Stack Overflow: A Technical Deconstruction.” Nick Craver (blog). February 3, 2016. https://nickcraver.com/blog/2016/02/03/stack-overflow-a-technical-deconstruction.
[Cunningham1995] Cunningham, Ward. 1995. “EPISODES: A Pattern Language of Competitive Development, Part I.” Paper submitted to the Second International Conference on Pattern Languages of Programs. Monticello, Illinois, September 6–8, 1995. http://c2.com/ppr/episodes.html.
[Dekker2014] Dekker, Sidney. 2014. The Field Guide to Understanding ‘Human Error,’ 3rd ed. Boca Raton, FL: CRC Press.
[DeMarco2002] DeMarco, Tom. 2002. Slack: Getting Past Burnout, Busywork, and the Myth of Total Efficiency. New York: Broadway Books.
[DeMarco2003] DeMarco, Tom, and Timothy Lister. 2003. Waltzing With Bears: Managing Risk on Software Projects. New York: Dorset House Publishing Co.
[DeMarco2013] DeMarco and Lister. 2013. Peopleware: Productive Projects and Teams. 3rd ed. Boston: Addison-Wesley Professional.
[Denne2004] Denne, Mark, and Jane Cleland-Huang. 2004. Software by Numbers: Low-Risk, High-Return Development. Upper Saddle River, NJ: Prentice Hall.
[Derby2006] Derby, Esther, and Diana Larsen. 2006. Agile Retrospectives: Making Good Teams Great. Raleigh, NC and Dallas, TX: Pragmatic Bookshelf.
[Derby2019] Derby, Esther. 2019. 7 Rules for Positive, Productive Change. San Francisco: Berrett-Koehler Publishers. https://learning.oreilly.com/library/view/7-rules-for/9781523085811.
[Dumiak2021] Dumiak, Michael. 2021. “Chaos Engineering Saved Your Netflix.” IEEE Spectrum. March 3, 2021. https://spectrum.ieee.org/telecom/internet/chaos-engineering-saved-your-netflix.
[Duvall2006] Duvall, Paul M. 2006. Continuous Integration: Improving Software Quality and Reducing Risk. Boston: Addison-Wesley Professional.
[Eckstein2020] Eckstein, Jutta, and John Buck. 2020. Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy: Survive & Thrive on Disruption. (self-pub.)
[Edmonson2014] Edmonson, Amy. 2014. “Building a psychologically safe workplace.” YouTube. Video, 11:26. TEDxTalks. https://www.youtube.com/watch?v=LhoLuui9gX8.
[Edmonson2018] Edmonson, Amy. 2018. The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Hoboken, NJ: Wiley.
[Evans2003] Evans, Eric. 2003. Domain-Driven Design: Tackling Complexity in the Heart of Software. Boston: Addison-Wesley Professional.
[Falco2014] Falco, Llewellyn. 2014. “Llewellyn’s Strong-Style Pairing.” The Way Things Work in Llewellyn’s World (blog). June 30, 2014. https://llewellynfalco.blogspot.com/2014/06/llewellyns-strong-style-pairing.html.
[Feathers2004] Feathers, Michael. 2004. Working Effectively with Legacy Code. Upper Saddle River, NJ: Prentice Hall.
[Feynman1974] Feynman, Richard. 1974. “Cargo Cult Science.” https://calteches.library.caltech.edu/3043/1/CargoCult.pdf.
[Fields2015] Fields, Jay. 2015. Working Effectively with Unit Tests. Victoria, BC: Leanpub. https://leanpub.com/wewut.
[Ford2017] Ford, Neal, Rebecca Parsons, and Patrick Kua. 2017. Evolutionary Architectures. Sebastapol, CA: O’Reilly Media.
[Forsgren2018] Forsgren, Nicole, Jez Kimble, and Gene Kim. 2018. Accelerate: Building and Scaling High Performance Technology Organizations. Portland, OR: IT Revolution Press.
[Fowler1997] Fowler, Martin. 1997. “The Almighty Thud.” Distributed Computing 11(1). https://www.martinfowler.com/distributedComputing/thud.html.
[Fowler2000a] Fowler, Martin. 2000. “The New Methodology (Original).” Martin Fowler.com. July 21, 2000. https://www.martinfowler.com/articles/newMethodologyOriginal.html.
[Fowler2004] Fowler, Martin. 2004. “Is Design Dead?” Martin Fowler.com. May 2004. http://www.martinfowler.com/articles/designDead.html.
[Fowler2002] Fowler, Martin. 2002. Patterns of Enterprise Application Architecture. Boston: Addison-Wesley Professional.
[Fowler2003] Fowler, Martin. 2003. “Cannot Measure Productivity.” Martin Fowler.com. August 29, 2003. https://www.martinfowler.com/bliki/CannotMeasureProductivity.html.
[Fowler2011] Fowler, Martin. 2011. “Contract Test.” Martin Fowler.com. January 12, 2011. https://martinfowler.com/bliki/ContractTest.html.
[Fowler2018] Fowler, Martin. 2018. Refactoring: Improving the Design of Existing Code. 2nd ed. Boston: Addison-Wesley Professional.
[Fowler2020a] Fowler, Martin. 2020a. “Keystone Interface.” Martin Fowler.com, April 29, 2020. https://martinfowler.com/bliki/KeystoneInterface.html.
[Fowler2020b] Fowler, Martin. 2020b. “Patterns for Managing Source Code Branches.” Martin Fowler.com. May 28, 2020. https://martinfowler.com/articles/branching-patterns.html.
[Freeman2010] Freeman, Steve, and Nat Pryce. 2010. Growing Object-Oriented Software, Guided by Tests. Boston: Pearson Education.
[Gamma1995] Gamma, Erich, Richard Helm, Ralph Johnson, and John Vlissides ["Gang of Four"]. 1995. Design Patterns: Elements of Reusable Object-Oriented Software. Boston: Addison-Wesley.
[Goldratt1992] Goldratt, Eliyahu M. 1992. The Goal: A Process of Ongoing Improvement. Great Barrington, MA: North River Press.
[Goldratt1997] Goldratt, Eliyahu M. 1997. Critical Chain: A Business Novel. Great Barrington, MA: North River Press.
[Google2021] Google. “Guide: Understand Team Effectiveness.” Accessed May 11, 2021. https://rework.withgoogle.com/print/guides/5721312655835136.
[Graham1995] Graham, Pauline. 1995. Mary Parker Follett: Prophet of Management: A Celebration of Writings from the 1920’s. Fairless Hills, PA: Beard Books.
[Grenning2002] Grenning, James. 2002. “Planning Poker or How to Avoid Analysis Paralysis While Release Planning.” https://wingman-sw.com/papers/PlanningPoker-v1.1.pdf.
[Grenning2016] Grenning, James. 2016. “TDD Guided by ZOMBIES.” James Grenning’s Blog, October 31, 2016. https://blog.wingman-sw.com/tdd-guided-by-zombies.
[Gumbley2020] Gumbley, Jim. 2020. “A Guide to Threat Modelling for Developers.” Martin Fowler.com. May 28, 2020. https://martinfowler.com/articles/agile-threat-modelling.html.
[Hammant2020] Hammant, Paul. 2020. Trunk-Based Development and Branch By Abstraction. Victoria, BC: Leanpub. https://leanpub.com/trunk-based-development.
[Heaton2015] Heaton, Robert. 2015. “Migrating bajillions of database records at Stripe.” Robert Heaton.com. August 31, 2015. https://robertheaton.com/2015/08/31/migrating-bajillions-of-database-records-at-stripe.
[Hendrickson2000] Hendrickson, Elisabeth. 2000. “Better Testing, Worse Quality?” Quality Tree, December 2000. https://www.stickyminds.com/sites/default/files/article/file/2012/XDD2479filelistfilename1_0.pdf.
[Hendrickson2013] Hendrickson, Elisabeth. 2013. Explore It! Reduce Risk and Increase Confidence with Exploratory Testing. Raleigh, NC: Pragmatic Bookshelf.
[Highsmith2001] Highsmith, Jim. 2001. “History: The Agile Manifesto.” https://agilemanifesto.org/history.html.
[Highsmith2002] Highsmith, Jim. 2002. Agile Software Development Ecosystems. Boston: Addison-Wesley Professional.
[Hill2018] Hill, Michael “GeePaw.” 2018. “TDD & The Lump of Coding Fallacy.” Video, 9:04. GeePawHill.org. April 14, 2018. https://www.geepawhill.org/2018/04/14/tdd-the-lump-of-coding-fallacy.
[Hodgson2017] Hodgson, Pete. 2017. “Feature Flags.” Martin Fowler.com. October 9, 2017. https://martinfowler.com/articles/feature-toggles.html#ImplementationTechniques.
[Hohman2002] Hohman, Moses, and Andrew C. Slocum. 2002. “Mob Programming and the Transition to XP.” ResearchGate. https://www.researchgate.net/publication/2522276_Mob_Programming_and_the_Transition_to_XP/link/55de4a1b08ae7983897d11ad/download.
[Hohmann2006] Hohmann, Luke. 2006. Innovation Games: Creating Breakthrough Products Through Collaborative Play. Boston: Addison-Wesley Professional. https://learning.oreilly.com/library/view/innovation-games-creating/0321437292.
[Hope2003] Hope, Jeremy, and Robin Fraser. 2003. Beyond Budgeting. Cambridge, MA: Harvard Business School Publishing.
[Humble2010] Humble, Jez, and David Farley. 2010. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Boston: Addison-Wesley Professional.
[Hunt2019] Hunt, Andrew, and David Thomas. 2019. The Pragmatic Programmer: Your Journey to Mastery, 20th Anniversary Edition. 2nd edition. Boston: Addison-Wesley Professional.
[Janis1982] Janis, Irving L. 1982. Groupthink: Psychological Studies of Policy Decisions and Fiascoes. Boston: Houghton Mifflin.
[Kahn1990] Kahn, William A. 1990. “Psychological Conditions of Personal Engagement and Disengagement at Work.” Academy of Management Journal. 33 (4): 692–724. https://doi.org/10.5465/256287. ISSN 0001-4273.
[Kaner1998] Kaner, Sam. 1998. Facilitator’s Guide to Participatory Decision-Making. San Francisco: Jossey-Bass.
[Katzenback2015] Katzenbach, Jon R., and Douglas K. Smith. 2015. The Wisdom of Teams: Creating the High-Performance Organization. Boston: Harvard Business Review Press.
[Kerievsky2004] Kerievsky, Joshua. 2004. Refactoring to Patterns. Boston: Addison-Wesley Professional.
[Kerievsky2005] Kerievsky, Joshua. 2005. “Industrial XP: Making XP Work in Large Organizations.” Agile Project Management Advisory Service Executive Report 6, no 2. https://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.694.2506&rep=rep1&type=pdf.
[Kerth2001] Kerth, Norman. 2001. Project Retrospectives: A Handbook for Team Reviews. New York: Dorset House Publishing Co.
[Kim2013] Kim, Gene, Kevin Behr, and George Spafford. 2013. The Phoenix Project. Portland, OR: IT Revolution Press.
[Kim2016] Kim, Gene, Jez Humble, Patrick Debois, and John Willis. 2016. The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizations. Portland, OR: IT Revolution Press.
[Kline2015] Kline, Nancy. 2015. Time to Think: Listening to Ignite the Human Mind. London: Cassell.
[Kohn1999] Kohn, Alfie. 1999. Punished By Rewards: The Trouble with Gold Stars, Incentive Plans, A’s, Praise, and Other Bribes. Boston: Mariner Books.
[Lacey2006] Lacey, Mitch. 2006. “Adventures in Promiscuous Pairing: Seeking Beginner’s Mind.” Proceedings of the Conference on AGILE 2006, July 23–28, 263–269. Washington, DC: IEEE Computer Society. http://dx.doi.org/10.1109/AGILE.2006.7.
[Langr2020] Langr, Jeff. 2020. “Remote Collaborative Coding: 6 Ways to Go.” Langr Software Solutions. June 2, 2020. https://langrsoft.com/2020/06/02/git-handover.
[Larman2015] Larman, Craig and Bas Vodde. 2015. Large-Scale Scrum: More with LeSS. Boston: Addison-Wesley Professional.
[Larsen2010] Larsen, Diana. 2010. “Circles and Soup.” Partnerships and Possibilities (blog), July 26, 2010. https://www.futureworksconsulting.com/blog/2010/07/26/circles-and-soup.
[Larsen2016] Larsen, Diana and Ainsley Nies. 2016. Liftoff: Start and Sustain Successful Agile Teams. Raleigh, NC and Dallas, TX: Pragmatic Bookshelf. https://pragprog.com/titles/liftoff/liftoff-second-edition.
[Larsen2021] Larsen, Willem. 2021. “Supercharge Your Retrospectives with TRIPE.” Industrial Logic, January, 31, 2021. https://www.industriallogic.com/blog/supercharge-your-retrospectives-with-tripe.
[Little2006] Little, Todd. 2006. “Schedule Estimation and Uncertainty Surrounding the Cone of Uncertainty,” IEEE Software 23, no. 3: 48-54. https://doi.org/10.1109/MS.2006.82.
[Mah2006] Mah, Michael. 2006. “Agile Productivity Metrics.” Keynote Address, Better Software Conference & EXPO, Las Vegas, June 2006. https://www.stickyminds.com/sites/default/files/presentation/file/2013/06BSOFR_WK2.pdf.
[Mah2018] Mah, Michael. 2018. “Taking the SAFe 4.0 Road to Hyper Speed and Quality.” Keynote Address, Pacific Northwest Software Quality Conference, Portland, October 2018. https://www.youtube.com/watch?v=OldRc6lp3CU.
[Mamoli2015] Mamoli, Sandy, and David Mole. 2015. Creating Great Teams: How Self-Selection Lets People Lead. Raleigh, NC and Dallas, TX: Pragmatic Bookshelf.
[Manns2015] Manns, Mary Lynn, and Linda Rising. 2015. More Fearless Change: Strategies for Making Your Ideas Happen. Boston: Addison-Wesley Professional. https://learning.oreilly.com/library/view/more-fearless-change/9780133966534.
[Marick2007a] Marick, Brian. 2007a. “Six years later: What the Agile Manifesto left out.” Exploration Through Example (blog). May 16, 2007. http://www.exampler.com/blog/2007/05/16/six-years-later-what-the-agile-manifesto-left-out.
[Marick2007b] Marick, Brian. 2007b. “Latour 3: Anthrax and standups.” Exploration Through Example (blog). November 6, 2007. http://exampler.com/blog/2007/11/06/latour-3-anthrax-and-standups/trackback/index.html.
[Marquet2013] Marquet, L. David. 2013. Turn the Ship Around! A True Story of Turning Followers into Leaders. New York: Penguin Group.
[McConnell2006] McConnell, Steve. 2006. Software Estimation: Demystifying the Black Art. Redmond, WA: Microsoft Press.
[Montagna1996] Montagna, Frank C. 1996. “The Effective Postfire Critique.” Fire Engineering Magazine, July 1, 1996. https://www.fireengineering.com/firefighting/the-effective-postfire-critque/#gref.
[Nelson2006] Nelson, R. Ryan. 2006. “Applied Insight - Tracks in the Snow.” CIO Magazine, Sep 1, 2006. https://www.cio.com/article/2444800/applied-insight---tracks-in-the-snow.html.
[Newman2021] Newman, Sam. 2021. Building Microservices, 2nd Edition. Sebastopol, CA: O’Reilly. https://learning.oreilly.com/library/view/building-microservices-2nd/9781492034018.
[Nierenberg2009] Nierenberg, Roger. 2009. Maestro: A Surprising Story About Leading by Listening. New York: Portfolio.
[Nygard2011] Nygard, Michael. 2011. “Documenting Architecture Decisions.” Cognitect (blog). November 15, 2011. https://cognitect.com/blog/2011/11/15/documenting-architecture-decisions.
[Patterson2013] Patterson, Kerry. 2013. Crucial Accountability: Tools for Resolving Violated Expectations, Broken Commitments, and Bad Behavior. New York: McGraw-Hill Education.
[Patton2014] Patton, Jeff. 2014. User Story Mapping. Sebastopol, CA: O’Reilly.
[Pearce2002] Pearce, Craig L., and Jay A. Conger. Shared Leadership: Reframing the Hows and Whys of Leadership. Thousand Oaks, CA: Sage Publications.
[Perry2016] Perry. Thomas L. 2016. The Little Book of Impediments. Victoria, BC: Leanpub. https://leanpub.com/ImpedimentsBook.
[Pixton2014] Pixton, Pollyanna, and Paul Gibson, Niel Nickolaisen. 2014. The Agile Culture: Leading through Trust and Ownership. Boston: Addison-Wesley Professional. https://learning.oreilly.com/library/view/the-agile-culture/9780133463187.
[Poppendieck2003] Poppendieck, Mary, and Tom Poppendieck. 2003. Lean Software Development: An Agile Toolkit for Software Development Managers. Boston: Addison-Wesley Professional.
[Pugh2005] Pugh, Ken. 2005. Prefactoring. Sebastopol, CA: O’Reilly.
[Reina2015] Reina, Dennis. 2015. Trust and Betrayal in the Workplace: Building Effective Relationships in Your Organization. 3rd edition. San Francisco: Berrett-Koehler Publishers.
[Reinertson2009] Reinertson, Donald G. 2009. The Principles of Product Development FLow: Second Generation Lean Product Development. 1st edition. Redondo Beach, CA: Celeritas Publishing.
[Ries2011] Ries, Eric. 2011. The Lean Startup. New York: Crown Business.
[Rosenthal2020] Rosenthal, Casey, and Nora Jones. 2020. Chaos Engineering: System Resiliency in Practice. Sebastopol, CA: O’Reilly.
[Rooney2006] Rooney, Dave. 2006. “The Disengaged Customer.” The Agile Artisan blog, January 20, 2006. http://agileartisan.blogspot.com/2006/01/disengaged-customer-introduction.html.
[Rothman1998] Rothman, Johanna. 1998. “A Problem-Based Approach to Software Process Improvement: A Case Study.” In Proceedings of the 16th Annual Pacific Northwest Software Quality Conference Joint with ASQ Software Division’s 8th International Conference on Software Quality, October 13–14, 1998, 310-316. http://uploads.pnsqc.org/proceedings/pnsqc1998.pdf.
[Rothman2005] Rothman, Johanna. 2005. Behind Closed Doors: Secrets of Great Management. Raleigh, NC: Pragmatic Bookshelf https://learning.oreilly.com/library/view/behind-closed-doors/9781680500332.
[Sawyer2017] Sawyer, Keith. 2017. Group Genius: The Creative Power of Collaboration. New York: Basic Books.
[Schwaber2002] Schwaber, Ken and Mike Beedle. 2002. Agile Software Development with Scrum. Boston: Pearson Education.
[Schatz2004] Schatz, Bob, Ken Schwaber, and Robert Martin. 2004. “Primavera Success Story.” Best Practices in Scrum Project Management and XP Agile Software Development White Paper. Object Mentor, Inc., and Advanced Development Methods. https://www.academia.edu/25855389/Primavera_Success_Story.
[Schein1965] Schein, Edgar, and Warren Bennis. 1965. Personal and Organizational Change Through Group Methods: The Laboratory Approach. New York: John Wiley & Sons, 1965.
[Seashore2013] Seashore, Charles N., Edith W. Seashore, and Gerald M. Weinburg. 2013. What Did You Say? The Art of Giving and Receiving Feedback. Columbia, MD: Bingham House Books.
[Semler1995] Semler, Ricardo. 1995. Maverick: The Success Story Behind the World’s Most Unusual Workplace. New York: Warner Books.
[Sheridan2013] Sheridan, Richard. 2013. Joy, Inc.: How We Built a Workplace People Love. New York: Portfolio.
[Shore2004a] Shore, James. 2004. “Continuous Design.” IEEE Software 21(1):20-22. http://www.martinfowler.com/ieeeSoftware/continuousDesign.pdf.
[Shore2004b] Shore, James. 2004. “Fail Fast.” IEEE Software 21(5):21-25. http://www.martinfowler.com/ieeeSoftware/failFast.pdf.
[Shore2006] Shore, James. 2006. “Change Your Organization: A Diary.” The Art of Agile (blog). http://www.jamesshore.com/v2/projects/change-diary.
[Shore2018a] Shore, James. 2018. “Testing Without Mocks: A Pattern Language.” The Art of Agile (blog). April 27, 2018. https://www.jamesshore.com/v2/blog/2018/testing-without-mocks.
[Shore2018b] Shore, James and Diana Larsen. 2018. “The Agile Fluency Model: A Brief Guide to Success with Agile.” Martin Fowler.com. March 6, 2018. https://martinfowler.com/articles/agileFluency.html.
[Shore2019] Shore, James. 2019. “Bjorn Freeman-Benson: Three Challenges of Distributed Teams.” The Art of Agile (blog). February 19, 2019. https://www.jamesshore.com/v2/blog/2019/three-challenges-of-distributed-teams.
[Shore2020a] Shore, James. 2020a. “Evolutionary Design Animated.” The Art of Agile (blog). February 20, 2020. https://www.jamesshore.com/v2/presentations/2020/evolutionary-design-animated.
[Shore2020b] Shore, James. 2020b. “TDD Lunch & Learn.” The Art of Agile (blog). May–September 2020. https://www.jamesshore.com/v2/projects/lunch-and-learn.
[Shore2021] Shore, James. 2021. “Fireside Chat with Ron Quartel on FAST.” The Art of Agile (blog). April 15, 2021. https://www.jamesshore.com/v2/presentations/2021/fireside-chat-with-ron-quartel-on-fast.
[Shostack2014] Shostack, Adam. 2014. Threat Modeling: Designing for Security. Indianapolis: John Wiley & Sons.
[Sierra2015] Sierra, Kathy. 2015. Badass: Making Users Awesome. Sebastopol, CA: O’Reilly. https://learning.oreilly.com/library/view/badass-making-users/9781491919057.
[Skelton2019] Skelton, Matthew and Manuel Pais. 2019. Team Topologies. Portland, OR: IT Revolution Press.
[Smith2012] Smith, Matt. 2012. “The Failure Bow.” YouTube. Video, 12:12. TEDxTalks. https://www.youtube.com/watch?v=cXuD2zHVeB0.
[Squirrel2020] Squirrel, Douglas, and Jeffrey Fredrick. 2020. Agile Conversations: Transform Your Conversations, Transform Your Culture. Portland, OR: IT Revolution Press.
[Standish1994] Standish Group. 1994. “The CHAOS Report.” The Standish Group International, Inc. https://www.standishgroup.com/sample_research_files/chaos_report_1994.pdf.
[Teasley2002] Teasley, Stephanie, Lisa Covi, M. S. Krishnan, and Judith Olson. 2002. “Rapid Software Development Through Team Collocation.” IEEE Trans. Softw. Eng 28(7):671–83. http://dx.doi.org/10.1109/TSE.2002.1019481.
[Todkar2018] Todkar, Praful. 2018. “How To Extract Data-Rich Service from a Monolith.” Martin Fowler.com. August 30, 2018. https://martinfowler.com/articles/extract-data-rich-service.html#Respectx201catomicStepOfArchitectureEvolutionx201dPrinciple.
[Tuckman1965] Tuckman, B. W. 1965. “Developmental sequences in small groups.” Psychological Bulletin 63:384–99. http://dennislearningcenter.osu.edu/references/GROUP%20DEV%20ARTICLE.doc.
[Ury2007] Ury, William. 2007. The Power of a Positive No: How to Say No and Still Get to Yes. New York: Bantam Books.
[VanSchooenderwoert2006] Van Schooenderwoert, Nancy. 2006. “Embedded Agile Project by the Numbers with Newbies.” The Conference on AGILE 2006 (July 23-28) Washington, DC: IEEE Computer Society, 351-366. http://dx.doi.org/10.1109/AGILE.2006.24.
[Venners2002] Venners, Bill. 2002. “Design Principles and Code Ownership: A Conversation with Martin Fowler, Part II.” Artima. November 11, 2002. https://www.artima.com/articles/design-principles-and-code-ownership.
[Venners2005] Venners, Bill. 2005. “Erich Gamma on Flexibility and Reuse: A Conversation with Erich Gamma, Part II.” Artima. May 30, 2005. https://www.artima.com/articles/erich-gamma-on-flexibility-and-reuse.
[Wiegers1999] Wiegers, Karl E. 1999. Software Requirements. Redmond, WA: Microsoft Press.
[Wiggins2017] Wiggins, Adam. 2017. “The Twelve-Factor App.” https://12factor.net.
[Williams2002] Williams, Laurie. 2002. Pair Programming Illuminated. Boston: Addison-Wesley Professional.
[Woods2010] Woods, David, Sidney Decker, Richard Cook, Leila Johannesen, and Nadine Sarter. 2010. Behind Human Error. Boca Raton, FL: CRC Press.
[Wynne2015] Wynne, Matt. 2015. “Introducing Example Mapping.” Cucumber. December 8, 2015. https://cucumber.io/blog/bdd/example-mapping-introduction.
[Yip2016] Yip, Jason. 2016. “It’s Not Just Standing Up: Patterns of Daily Stand-up Meetings.” Martin Fowler.com. February 21, 2016. http://www.martinfowler.com/articles/itsNotJustStandingUp.html.
[Yourdon1975] Yourdon, Edward, and Larry L. Constantine. 1975. Structured Design: Fundamentals of a Discipline of Computer Program and Systems Design. Upper Saddle River, NJ: Prentice Hall.
[Zuill2021] Zuill, Woody, Kevin Meadows. 2021. Mob Programming: A Whole Team Approach. Victoria, BC: Leanpub.