Scrum (software development)#Artifacts

The use of the term scrum in software development came from a 1986 Harvard Business Review paper titled "The New New Product Development Game" by Hirotaka Takeuchi and Ikujiro Nonaka. Based on case studies from manufacturing firms in the automotive, photocopier, and printer industries, the authors outlined a new approach to product development for increased speed and flexibility. They called this the rugby approach, as the process involves a single cross-functional team operating across multiple overlapping phases in which the team "tries to go the distance as a unit, passing the ball back and forth".{{Cite journal |last1=Takeuchi |first1=Hirotaka |last2=Nonaka |first2=Ikujiro |date=January 1, 1986 |title=The New New Product Development Game |url=https://cb.hbsp.harvard.edu/cbmp/product/86116-PDF-ENG |journal=Harvard Business Review |access-date=June 9, 2010 |quote=Moving the Scrum Downfield}} The authors later developed scrum in their book, The Knowledge Creating Company.{{Cite book |url=https://books.google.com/books?id=B-qxrPaU1-MC&q=The+Knowledge+Creating+Company |title=The Knowledge Creating Company |publisher=Oxford University Press |year=1995 |isbn=978-0-19-976233-0 |page=3 |access-date=March 12, 2013}}

In the early 1990s, Ken Schwaber used what would become scrum at his company, Advanced Development Methods. Jeff Sutherland, John Scumniotales, and Jeff McKenna developed a similar approach at Easel Corporation, referring to the approach with the term scrum.{{cite web |title=Agile Development: Lessons learned from the first Scrum |url=https://www.scrumalliance.org/resource_download/35 |last=Sutherland |first=Jeff |author-link=Jeff Sutherland |date=October 2004 |format=PDF |archive-url=https://web.archive.org/web/20140630020607/http://www.scrumalliance.org/resource_download/35 |archive-date=June 30, 2014 |access-date=September 26, 2008}} Sutherland and Schwaber later worked together to integrate their ideas into a single framework, formally known as scrum. Schwaber and Sutherland tested scrum and continually improved it, leading to the publication of a research paper in 1995,{{Cite book |last1=Sutherland |first1=Jeffrey Victor |title=Business object design and implementation: OOPSLA '95 workshop proceedings |last2=Schwaber |first2=Ken |publisher=The University of Michigan |year=1995 |isbn=978-3-540-76096-2 |page=118 |author-link=Jeff Sutherland |author-link2=Ken Schwaber}} and the Manifesto for Agile Software Development in 2001.{{cite web |title=Manifesto for Agile Software Development |url=https://agilemanifesto.org |access-date=October 17, 2019}} Schwaber also collaborated with Babatunde Ogunnaike at DuPont Research Station and the University of Delaware to develop Scrum. Ogunnaike believed that software development projects could often fail when initial conditions change if product management was not rooted in empirical practice.

In 2002, Schwaber with others founded the Scrum Alliance and set up the Certified Scrum accreditation series.{{Cite book |last=Maximini |first=Dominik |url=https://books.google.com/books?id=ShojBgAAQBAJ |title=The Scrum Culture: Introducing Agile Methods in Organizations |date=January 8, 2015 |publisher=Springer |isbn=978-3-319-11827-7 |series=Management for Professionals |location=Cham |publication-date=2015 |page=26 |quote=Ken Schwaber and Jeff Sutherland presented Scrum for the first time at the OOPSLA conference in Austin, Texas, in 1995. [...] In 2001, the first book about Scrum was published. [...] One year later (2002), Ken founded the Scrum Alliance, aiming at providing worldwide Scrum training and certification. |access-date=August 25, 2016}} Schwaber left the Scrum Alliance in late 2009 and subsequently founded Scrum.org, which oversees the parallel Professional Scrum accreditation series.{{cite web |title=Home |url=https://www.scrum.org/index |access-date=January 6, 2020 |website=Scrum.org |language=en}} Since 2009, a public document called The Scrum Guide{{cite web |last1=Sutherland |first1=Jeff |author1-link=Jeff Sutherland |last2=Schwaber |first2=Ken |author2-link=Ken Schwaber |year=2013 |title=Scrum Guides |url=http://www.scrumguides.org/ |access-date=June 15, 2023 |publisher=ScrumGuides.org}} has been published and updated by Schwaber and Sutherland. It has been revised six times, with the most recent version having been published in November 2020.

A scrum team is organized into at least three categories of individuals: the product owner, developers, and the scrum master. The product owner liaises with stakeholders, those who have an interest in the project's outcome, to communicate tasks and expectations with developers.{{Cite book |last=Morris |first=David |title=Scrum: an ideal framework for agile projects |publisher=In Easy Steps |year=2017 |isbn=978-1-84078-731-3 |pages=178–179 |oclc=951453155}} Developers in a scrum team organize work by themselves, with the facilitation of a scrum master.{{Cite book |last=Cobb |first=Charles G. |title=The Project Manager's Guide to Mastering Agile: Principles and Practices for an Adaptive Approach |date=2015 |publisher=John Wiley & Sons |isbn=978-1-118-99104-6 |location=Hoboken, NJ |page=37}}

Each scrum team has one product owner.{{Cite book |last=Cohn |first=Mike |title=Succeeding with Agile: Software Development Using Scrum |date=2010 |publisher=Addison-Wesley |isbn=978-0-321-57936-2 |location=Upper Saddle River, NJ |author-link=Mike Cohn}} The product owner focuses on the business side of product development and spends the majority of time liaising with stakeholders and the team. The role is intended to primarily represent the product's stakeholders, the voice of the customer, or the desires of a committee, and bears responsibility for the delivery of business results.{{Citation |last=Rubin |first=Kenneth |title=Essential Scrum. A Practical Guide to the Most Popular Agile Process |page=173 |date=2013 |publisher=Addison-Wesley |language=EN |isbn=978-0-13-704329-3}}{{Cite book |last1=McGreal |first1=Don |url=https://books.google.com/books?id=cEBbDwAAQBAJ&q=scrum+product+owner+accountable+backlog&pg=PT173 |title=The Professional Product Owner: Leveraging Scrum as a Competitive Advantage |last2=Jocham |first2=Ralph |date=June 4, 2018 |publisher=Addison-Wesley Professional |isbn=978-0-13-468665-3 |language=en}}{{Cite book |last=Pichler |first=Roman |title=Agile Product Management with Scrum: Creating Products that Customers Love |date=March 11, 2010 |publisher=Addison-Wesley Professional |isbn=978-0-321-68413-4 |language=en}}{{cite web |last=Ambler |first=Scott |title=The Product Owner Role: A Stakeholder Proxy for Agile Teams |url=http://agilemodeling.com/essays/productOwner.htm |access-date=July 22, 2016 |publisher=agilemodeling.com |quote=[...] in practice there proves to be two critical aspects to this role: first as a stakeholder proxy within the development team and second as a project team representative to the overall stakeholder community as a whole.}} Product owners manage the product backlog and are responsible for maximizing the value that a team delivers. They do not dictate the technical solutions of a team but may instead attempt to seek consensus among team members.{{cite web |title=The Scrum Guide |url=https://scrumguides.org/docs/scrumguide/v2016/2016-Scrum-Guide-US.pdf |access-date=June 15, 2023 |publisher=Scrum.org |page=6}}{{cite web |title=The Role of the Product Owner |url=https://resources.scrumalliance.org/Webinar/the-role-of-the-product-owner/ |access-date=May 26, 2018 |publisher=Scrum Alliance}}

As the primary liaison of the scrum team towards stakeholders, product owners are responsible for communicating announcements, project definitions and progress, RIDAs (risks, impediments, dependencies, and assumptions), funding and scheduling changes, the product backlog, and project governance, among other responsibilities.{{cite web |title=The Product Owner Role |url=http://scrum-master.thinkific.com/pages/the-product-owner-role |website=Scrum Master Test Prep |access-date=February 3, 2017}}{{Better source needed|reason=The current source is insufficiently reliable (WP:NOTRS).|date=July 2023}} Product owners can also cancel a sprint if necessary, without the input of team members.

In scrum, the term developer or team member refers to anyone who plays a role in the development and support of the product and can include researchers, architects, designers, programmers, etc.{{Cite book |last1=Rad |first1=Nader K. |title=Agile Scrum Foundation Courseware, Second Edition |last2=Turley |first2=Frank |date=2018 |publisher=Van Haren |isbn=978-94-018-0279-6 |location='s-Hertogenbosch, Netherlands |page=26}}

Scrum is facilitated by a scrum master, whose role is to educate and coach teams about scrum theory and practice.{{cite web |author=Ken Schwaber |author2=Jeff Sutherland |title=The Scrum Guide |url=https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-US.pdf |access-date=June 15, 2023 |publisher=Scrum.org}} Scrum masters have differing roles and responsibilities from traditional team leads or project managers. Some scrum master responsibilities include coaching, objective setting, problem solving, oversight, planning, backlog management, and communication facilitation. On the other hand, traditional project managers often have people management responsibilities, which a scrum master does not. Scrum teams do not involve project managers, so as to maximize self-organisation among developers.{{cite web |title=The Scrum Primer: A Lightweight Guide to the Theory and Practice of Scrum (Version 2.0) |url=http://www.infoq.com/minibooks/Scrum_Primer |last1=Pete Deemer |last2=Gabrielle Benefield |date=December 17, 2012 |publisher=InfoQ |last3=Craig Larman |last4=Bas Vodde}}

{{Distinguish|Hackathon#Code sprints}}

File:Scrum Framework.png

File:Scrum process.svg

A sprint (also known as a design sprint, iteration, or timebox) is a fixed period of time wherein team members work on a specific goal. Each sprint is normally between one week and one month, with two weeks being the most common. The outcome of the sprint is a functional deliverable, or a product which has received some development in increments. When a sprint is abnormally terminated, the next step is to conduct new sprint planning, where the reason for the termination is reviewed.

Each sprint starts with a sprint planning event in which a sprint goal is defined. Priorities for planned sprints are chosen out of the backlog. Each sprint ends with two events:

• A sprint review (progress shown to stakeholders to elicit their feedback)
• A sprint retrospective (identifying lessons and improvements for the next sprints)

The suggested maximum duration of sprint planning is eight hours for a four-week sprint.

{{Main|Daily scrum meeting}}

File:Daily sprint meeting.jpg

Each day during a sprint, the developers hold a daily scrum (often conducted standing up) with specific guidelines, and which may be facilitated by a scrum master.{{cite web |title=What is a Daily Scrum? |url=https://www.scrum.org/resources/what-is-a-daily-scrum |website=Scrum.org |access-date=January 6, 2020}} Daily scrum meetings are intended to be less than 15 minutes in length, taking place at the same time and location daily. The purpose of the meeting is to announce progress made towards the sprint goal and issues that may be hindering the goal, without going into any detailed discussion. Once over, individual members can go into a 'breakout session' or an 'after party' for extended discussion and collaboration.{{Cite book|last=Flewelling|first=Paul|title=The Agile Developer's Handbook: Get more value from your software development: get the best out of the Agile methodology|date=2018|publisher=Packt Publishing Ltd|isbn=978-1-78728-020-5|location=Birmingham, UK|page=91}} Scrum masters are responsible for ensuring that team members use daily scrums effectively or, if team members are unable to use them, providing alternatives to achieve similar outcomes.{{Cite book |last=McKenna |first=Dave |title=The Art of Scrum: How Scrum Masters Bind Dev Teams and Unleash Agility |date=2016 |publisher=CA Press |isbn=978-1-4842-2276-8 |location=Aliquippa, PA |page=126 |language=en}}{{Cite book|last1=Drongelen|first1=Mike van|title=Lean Mobile App Development: Apply Lean startup methodologies to develop successful iOS and Android apps|last2=Dennis|first2=Adam|last3=Garabedian|first3=Richard|last4=Gonzalez|first4=Alberto|last5=Krishnaswamy|first5=Aravind|date=2017|publisher=Packt Publishing Ltd|isbn=978-1-78646-704-1|location=Birmingham, UK|page=43}}

Conducted at the end of a sprint, a sprint review is a meeting that has a team share the work they've completed with stakeholders and liaise with them on feedback, expectations, and upcoming plans. At a sprint review completed deliverables are demonstrated to stakeholders. The recommended duration for a sprint review is one hour per week of sprint.

A sprint retrospective is a separate meeting that allows team members to internally analyze the strengths and weaknesses of the sprint, future areas of improvement, and continuous process improvement actions.{{Citation |last=Rubin |first=Kenneth |title=Essential Scrum. A Practical Guide to the Most Popular Agile Process |page=375 |publication-date=2013 |year=2012 |publisher=Addison-Wesley |language=EN |isbn=978-0-13-704329-3}}

Backlog refinement is a process by which team members revise and prioritize a backlog for future sprints.{{sfn|Project Management Institute|2021|loc=Glossary §3 Definitions}} It can be done as a separate stage done before the beginning of a new sprint or as a continuous process that team members work on by themselves. Backlog refinement can include the breaking down of large tasks into smaller and clearer ones, the clarification of success criteria, and the revision of changing priorities and returns.

{{more citations needed section|date=March 2013}}

Artifacts are a means by which scrum teams manage product development by documenting work done towards the project. There are seven scrum artifacts, with three of them being the most common: product backlog, sprint backlog, and increment.{{Cite web |title=What are Scrum Artifacts? {{!}} The Ultimate Guide {{!}} Miro |url=https://miro.com/agile/what-are-scrum-artifacts/ |access-date=2024-11-29 |website=miro.com/ |language=en-US}}

{{main|Product backlog}}

The product backlog is a breakdown of work to be done and contains an ordered list of product requirements (such as features, bug fixes and non-functional requirements) that the team maintains for a product. The order of a product backlog corresponds to the urgency of the task. Common formats for backlog items include user stories and use cases. The product backlog may also contain the product owner's assessment of business value and the team's assessment of the product's effort or complexity, which can be stated in story points using the rounded Fibonacci scale. These estimates try to help the product owner gauge the timeline and may influence the ordering of product backlog items.{{cite web |last=Higgins |first=Tony |date=March 31, 2009 |title=Authoring Requirements in an Agile World |url=http://www.batimes.com/articles/authoring-requirements-in-an-agile-world.html |publisher=BA Times}}

The product owner maintains and prioritizes product backlog items based on considerations such as risk, business value, dependencies, size, and timing. High-priority items at the top of the backlog are broken down into more detail for developers to work on, while tasks further down the backlog may be more vague.

The sprint backlog is the subset of items from the product backlog intended for developers to address in a particular sprint.{{Cite book |last1=Russ J. Martinelli |url=https://books.google.com/books?id=SbA7CwAAQBAJ&pg=PA304 |title=Project Management ToolBox: Tools and Techniques for the Practicing Project Manager |last2=Dragan Z. Milosevic |date=January 5, 2016 |publisher=Wiley |isbn=978-1-118-97320-2 |page=304}} Developers fill this backlog with tasks they deem appropriate to fill the sprint, using past performance to assess their capacity for each sprint. The scrum approach has tasks on the sprint backlog not assigned to developers by any particular individual or leader. Team members self organize by pulling work as needed according to the backlog priority and their own capabilities and capacity.{{cite web |author=Ken Schwaber |author2=Jeff Sutherland |title=The Scrum Guide |url=http://www.scrumguides.org/docs/scrumguide/v2017/2017-Scrum-Guide-US.pdf |access-date=May 25, 2018 |publisher=Scrum.org}}

An increment is a potentially releasable output of a sprint, which meets the sprint goal. It is formed from all the completed sprint backlog items, integrated with the work of all previous sprints.

File:SampleBurndownChart.svg

{{Main|Burndown chart}}

Often used in scrum, a burndown chart is a publicly displayed chart showing remaining work.{{Cite book |last=Charles G. Cobb |url=https://books.google.com/books?id=vHjTBQAAQBAJ&pg=PA378 |title=The Project Manager's Guide to Mastering Agile: Principles and Practices for an Adaptive Approach |date=January 27, 2015 |publisher=John Wiley & Sons |isbn=978-1-118-99104-6 |page=378}} It provides quick visualizations for reference. The horizontal axis of the burndown chart shows the days remaining, while the vertical axis shows the amount of work remaining each day. During sprint planning, the ideal burndown chart is plotted. Then, during the sprint, developers update the chart with the remaining work.

File:SampleBurnupChart.png)|384x384px]]

{{main|Burnup chart}}

Updated at the end of each sprint, the release burn-up chart shows progress towards delivering a forecast scope. The horizontal axis of the release burnup chart shows the sprints in a release, while the vertical axis shows the amount of work completed at the end of each sprint.

{{main|Velocity (software development)}}

Some project managers believe that a team's total capability effort for a single sprint can be derived by evaluating work completed in the last sprint. The collection of historical "velocity" data is a guideline for assisting the team in understanding their capacity.

Some have argued that scrum events, such as daily scrums and scrum reviews, hurt productivity and waste time that could be better spent on actual productive tasks.{{cite web |last=Jenson |first=John |date=March 8, 2019 |title=Meetings: The productivity killer for developers |url=https://www.tandemseven.com/blog/meetings-productivity-killer-for-developers/ |archive-url=https://web.archive.org/web/20200605155907/https://www.tandemseven.com/blog/meetings-productivity-killer-for-developers/ |archive-date=2020-06-05 |access-date=June 5, 2020 |website=TandemSeven – The Experience Innovation Company}}{{Cite magazine |date=December 4, 2019 |title=Not all developers like agile, and here are 5 reasons why |url=https://www.bmmagazine.co.uk/in-business/not-all-developers-like-agile-and-here-are-5-reasons-why/ |magazine=Business Matters |access-date=June 5, 2020}} Scrum has also been observed to pose difficulties for part-time or geographically distant teams; those that have highly specialized members who would be better off working by themselves or in working cliques; and those that are unsuitable for incremental and development testing.{{Cite journal |last1=Turk |first1=Dan |last2=France |first2=Robert |last3=Rumpe |first3=Bernhard |year=2014 |orig-date=2002 |title=Limitations of Agile Software Processes |journal=Proceedings of the Third International Conference on Extreme Programming and Flexible Processes in Software Engineering |pages=43–46 |arxiv=1409.6600}}{{Cite journal |date=August 2012 |title=Issues and Challenges in Scrum Implementation |url=http://www.ijser.org/researchpaper/Issues-and-Challenges-in-Scrum-Implementation.pdf |journal=International Journal of Scientific & Engineering Research |volume=3 |issue=8 |access-date=December 10, 2015}}

Scrum is frequently tailored or adapted in different contexts to achieve varying aims.{{Cite journal|last1=Hron|first1=Michal|last2=Obwegeser|first2=Nikolaus|date=January 1, 2022|title=Why and how is Scrum being adapted in practice: A systematic review|url=https://www.sciencedirect.com/science/article/pii/S0164121221002077|journal=Journal of Systems and Software|language=en|volume=183|page=111110|doi=10.1016/j.jss.2021.111110|s2cid=240950847 |issn=0164-1212}} A common approach to adapting scrum is the combination of scrum with other software development methodologies, as scrum does not cover the whole product development lifecycle.{{Cite journal |last1=Hron, M. |last2=Obwegeser, N. |date=January 2018 |title=Scrum in practice: an overview of Scrum adaptations |url=http://pure.au.dk/portal/files/116906219/Hron_Obwegeser_Scrum_in_practice_An_overview_of_Scrum_adaptations.pdf |journal=Proceedings of the 2018 51st Hawaii International Conference on System Sciences (HICSS), January 3–6, 2018}} Various scrum practitioners have also suggested more detailed techniques for how to apply or adapt scrum to particular problems or organizations. Many refer to these techniques as 'patterns', an analogous use to design patterns in architecture and software.{{cite web |title=Scrum as Organizational Patterns |url=https://sites.google.com/a/scrumorgpatterns.com/www/ |last1=Bjørnvig |first1=Gertrud |last2=Coplien |first2=Jim |date=June 21, 2008 |publisher=Gertrude & Cope}}{{cite web |title=Scrum Pattern Community |url=http://www.scrumplop.org |website=ScrumPLoP.org |access-date=July 22, 2016}}

{{Main|Scrumban}}

Scrumban is a software production model based on scrum and kanban. To illustrate each stage of work, teams working in the same space often use post-it notes or a large whiteboard.{{cite web |last=Ladas |first=Corey |date=October 27, 2007 |title=scrum-ban |url=http://leansoftwareengineering.com/ksse/scrum-ban/ |archive-url=https://web.archive.org/web/20180823232934/http://leansoftwareengineering.com/ksse/scrum-ban/ |archive-date=August 23, 2018 |access-date=September 13, 2012 |publisher=Lean Software Engineering}} Kanban models allow a team to visualize work stages and limitations.{{cite web |title=Kanban and Scrum – Making the most of both |url=https://www.infoq.com/minibooks/kanban-scrum-minibook |last1=Kniberg |first1=Henrik |last2=Skarin |first2=Mattias |date=December 21, 2009 |publisher=InfoQ |format=PDF |access-date=July 22, 2016}}

Scrum of scrums is a technique to operate scrum at scale for multiple teams coordinating on the same product. Scrum-of-scrums daily scrum meetings involve ambassadors selected from each individual team, who may be either a developer or scrum master. As a tool for coordination, scrum of scrums allows teams to collectively work on team-wide risks, impediments, dependencies, and assumptions (RIDAs), which may be tracked in a backlog of their own.{{cite web |title=Risk Management – How to Stop Risks from Screwing Up Your Projects! |url=http://www.allaboutagile.com/risk-management-how-to-stop-risks-from-screwing-up-your-projects/ |publisher=Kelly Waters}}{{cite web |date=December 17, 2015 |title=Scrum of Scrums |url=http://guide.agilealliance.org/guide/scrumofscrums.html |archive-url=https://web.archive.org/web/20140209200853/http://guide.agilealliance.org/guide/scrumofscrums.html |archive-date=February 9, 2014 |access-date=December 17, 2013 |publisher=Agile Alliance}}

Large-scale scrum is an organizational system for product development that scales scrum with varied rules and guidelines, developed by Bas Vodde and Craig Larman.{{cite web |year=2014 |title=Large-Scale Scrum (LeSS) |url=http://less.works}}{{cite web |last=Grgic |year=2015 |title=Descaling organisation with LeSS (Blog) |url=https://less.works/blog/2015/05/08/less-scaling-descaling-organizations-with-less.html}} There are two levels to the framework: the first level, designed for up to eight teams; and the second level, known as 'LeSS Huge', which can accommodate development involving hundreds of developers.{{cite periodical |title=Scaling Agile Development |periodical=Crosstalk |date=May–June 2013 |url=http://www.crosstalkonline.org/storage/issue-archives/2013/201305/201305-larman.pdf |last1=Larman, Craig |author2=Bas Vodde}}

{{stub section|date=June 2024}}

A systematic review found "that Distributed Scrum has no impact, positive or negative on overall project success" in distributed software development.{{cite journal |last1=Santos |first1=Ronnie de Souza |last2=Ralph |first2=Paul |last3=Arshad |first3=Arham |last4=Stol |first4=Klaas-Jan |title=Distributed Scrum: A Case Meta-Analysis |journal=ACM Computing Surveys |date=5 October 2023 |volume=56 |issue=4 |pages=1–37 |doi=10.1145/3626519|s2cid=263672588 |doi-access=free }}

Martin Fowler, one of the authors of the Manifesto for Agile Software Development, has criticized what he calls "faux-agile" practices that are "disregarding Agile's values and principles",{{cite web |last1=Fowler |first1=Martin |author1-link=Martin Fowler (software engineer) |title=The State of Agile Software in 2018 |url=https://martinfowler.com/articles/agile-aus-2018.html |website=martinfowler.com |access-date=14 September 2023 |archive-url=https://web.archive.org/web/20230914005209/https://martinfowler.com/articles/agile-aus-2018.html |archive-date=14 September 2023 |date=25 August 2018 |url-status=live}} and "the Agile Industrial Complex imposing methods upon people" contrary to the Agile principle of valuing "individuals and interactions over processes and tools" and allowing the individuals doing the work to decide how the work is done, changing processes to suit their needs.

In September 2016, Ron Jeffries, a signatory to the Agile Manifesto, described what he called "Dark Scrum", saying that "Scrum can be very unsafe for programmers."{{cite web |last1=Jeffries |first1=Ron |title=Dark Scrum |url=https://ronjeffries.com/articles/016-09ff/defense/ |website=ronjeffries.com |access-date=6 May 2024 |date=8 September 2016}}

• Agile software development
• Agile testing
• Agile learning
• Disciplined agile delivery
• Comparison of scrum software
• High-performance teams
• Lean software development
• Project management
• Unified process

{{reflist}}

{{Refbegin}}

• {{Cite web |last1=Deemer |first1=Pete |last2=Benefield |first2=Gabrielle |last3=Larman |first3=Craig |last4=Vodde |first4=Bas |year=2009 |title=The Scrum Primer |url=http://www.scrumprimer.org |access-date=June 1, 2009}}
• {{Cite web |last1=Janoff |first1=N. S. |last2=Rising |first2=L. |year=2000 |title=The Scrum Software Development Process for Small Teams |url=http://faculty.salisbury.edu/~xswang/Research/Papers/SERelated/scrum/s4026.pdf |access-date=February 26, 2015 |archive-date=November 6, 2015 |archive-url=https://web.archive.org/web/20151106053048/http://faculty.salisbury.edu/~xswang/Research/Papers/SERelated/scrum/s4026.pdf }}
• {{Cite book |last1=Münch |first1=Jürgen |title=Software Process Definition and Management |last2=Armbrust |first2=Ove |last3=Soto |first3=Martín |last4=Kowalczyk |first4=Martin |year=2012 |publisher=Springer |isbn=978-3-642-24291-5}}
• {{Cite book |title=A guide to the project management body of knowledge (PMBOK guide) |edition=7th |location=Newtown Square, PA |publisher=Project Management Institute |date=2021 |isbn=978-1-62825-664-2 |ref={{sfnref|Project Management Institute|2021}} }}
• {{Cite book |last=Rubin |first=Kenneth |date=2013 |title=Essential Scrum: A Practical Guide to the Most Popular Agile Process |publisher=Addison-Wesley |page=173 |language=EN |isbn=978-0-13-704329-3}}
• {{Cite web |last=Vacaniti |first=Daniel |date=February 2018 |title=The Kanban Guide for Scrum Teams |url=https://scrumorg-website-prod.s3.amazonaws.com/drupal/2018-02/2018%20Kanban%20Guide%20for%20Scrum%20Teams_0.pdf |website=scrum.org |access-date=March 12, 2018 }}
• Verheyen, Gunther (2013). Scrum – A Pocket Guide (A Smart Travel Companion). {{ISBN|978-90-8753-720-3}}.

{{Refend}}

{{Commons category|Scrum (development)}}

{{Wikisource|The Scrum Guide}}

{{Prone to spam|date=May 2015}}

• [http://cf.agilealliance.org/articles/article_list.cfm?CategoryID=17 Agile Alliance's Scrum library]
• [https://web.archive.org/web/20170605114816/http://epf.eclipse.org/wikis/scrum/ A scrum process description] by the Eclipse process framework (EPF) project

{{Software engineering}}

{{Authority control}}

Category:Agile software development

Category:Software development

Category:Software development philosophies

Category:Software project management