
Scrum (software development)
Scrum is a framework for project management with an initial emphasis on software development, although it has been used in other fields including research, sales, marketing and advanced technologies. It is designed for teams of ten or fewer members who break their work into goals that can be completed within time-boxed iterations, called sprints, no longer than one month and most commonly two weeks. The scrum team assesses progress in time-boxed daily meetings of 15 minutes or fewer, called daily scrums (a form of stand-up meeting). At the end of the sprint, the team holds two further meetings: one sprint review intended to demonstrate the work done for stakeholders and elicit feedback, and one sprint retrospective intended to enable the team to reflect and improve.
- Comment
- enScrum is a framework for project management with an initial emphasis on software development, although it has been used in other fields including research, sales, marketing and advanced technologies. It is designed for teams of ten or fewer members who break their work into goals that can be completed within time-boxed iterations, called sprints, no longer than one month and most commonly two weeks. The scrum team assesses progress in time-boxed daily meetings of 15 minutes or fewer, called daily scrums (a form of stand-up meeting). At the end of the sprint, the team holds two further meetings: one sprint review intended to demonstrate the work done for stakeholders and elicit feedback, and one sprint retrospective intended to enable the team to reflect and improve.
- Date
- enFebruary 2016
- Depiction
- DifferentFrom
- Hackathon
- Has abstract
- enScrum is a framework for project management with an initial emphasis on software development, although it has been used in other fields including research, sales, marketing and advanced technologies. It is designed for teams of ten or fewer members who break their work into goals that can be completed within time-boxed iterations, called sprints, no longer than one month and most commonly two weeks. The scrum team assesses progress in time-boxed daily meetings of 15 minutes or fewer, called daily scrums (a form of stand-up meeting). At the end of the sprint, the team holds two further meetings: one sprint review intended to demonstrate the work done for stakeholders and elicit feedback, and one sprint retrospective intended to enable the team to reflect and improve.
- Homepage
- scrum.org
- Hypernym
- Framework
- Is primary topic of
- Scrum (software development)
- Label
- enScrum (software development)
- Link from a Wikipage to an external page
- scrumorg-website-prod.s3.amazonaws.com/drupal/2018-02/2018%20Kanban%20Guide%20for%20Scrum%20Teams_0.pdf
- cf.agilealliance.org/articles/article_list.cfm%3FCategoryID=17
- www.scrumguides.org/
- web.archive.org/web/20170605114816/http:/epf.eclipse.org/wikis/scrum/
- faculty.salisbury.edu/~xswang/Research/Papers/SERelated/scrum/s4026.pdf
- web.archive.org/web/20151106053048/http:/faculty.salisbury.edu/~xswang/Research/Papers/SERelated/scrum/s4026.pdf
- www.scrumprimer.org
- Link from a Wikipage to another Wikipage
- Acronym
- Agile testing
- Agilo for Trac
- Assembla
- Babatunde Ogunnaike
- Category:Agile software development
- Category:Software development
- Category:Software development philosophies
- Category:Software project management
- Colocation (business)
- Command and control
- Committee
- Comparison of Scrum software
- Continual improvement process
- Craig Larman
- Cross-functional team
- Customer centricity
- Decision-making
- Dependency (project management)
- Design pattern
- Design sprint
- Disciplined agile delivery
- Earned value management
- Economic sector
- Exit-criteria
- Fibonacci scale (agile)
- File:Daily sprint meeting.jpg
- File:SampleBurndownChart.svg
- File:SampleBurnupChart.png
- File:Scrum Agile events.png
- File:Scrum Framework.png
- File:Scrum process.svg
- Goal
- Harvard Business Review
- High-performance teams
- High tech
- Hirotaka Takeuchi
- Holistic
- Ikujiro Nonaka
- Iterative and incremental development
- Iterative design
- Jeff Sutherland
- Jira (software)
- Kanban (development)
- Ken Schwaber
- Lean software development
- Legacy system
- Management
- Manifesto for Agile Software Development
- Micromanagement
- Mike Beedle
- New product development
- Non-functional requirement
- OOPSLA
- Patch (computing)
- Planning poker
- Predictability
- Product backlog
- Product Backlog
- Productivity
- Product life-cycle theory
- Product owner
- Project management
- Project manager
- Project risk management
- Quality control
- Refinement (computing)
- Regression testing
- Requirement
- Requirement prioritization
- Retrospective
- Return on investment
- Rugby football
- Scrum (rugby)
- Scrum Alliance
- Servant leadership
- Software bug
- Software development
- Software feature
- Software lifecycle
- Software maintenance
- Specification
- Sprint (software development)
- Stakeholder (corporate)
- Stand-up meeting
- Team leader
- Technical debt
- Technology demo
- Timeboxing
- Tracer ammunition
- Trademark
- T-shaped skills
- Unified Process
- Use case
- User acceptance testing
- User story
- Voice of the customer
- Waterfall model
- Workflow
- Reason
- enan anon gave the concern that the reference gives the opinion of a single author and could hardly be considered authoritative
- SameAs
- 4GCX3
- m.0ck p8
- Q460387
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum
- Scrum (desarrollo de software)
- Scrum (desenvolvimento de software)
- Scrum (développement)
- Scrum (informatica)
- Scrum (programare)
- Scrum (projectmanagementmethode)
- Scrum (software development)
- Scrum (zhvillimi)
- Skram
- Σκραμ
- Скрам
- اسکرام (توسعه نرمافزار)
- سكرم (تطوير البرمجيات)
- இசுக்கிரம்
- สกรัม
- スクラム (ソフトウェア開発)
- 스크럼 (애자일 개발 프로세스)
- Subject
- Category:Agile software development
- Category:Software development
- Category:Software development philosophies
- Category:Software project management
- Thumbnail
- WasDerivedFrom
- Scrum (software development)?oldid=1123112500&ns=0
- WikiPageLength
- 70341
- Wikipage page ID
- 4743665
- Wikipage revision ID
- 1123112500
- WikiPageUsesTemplate
- Template:Authority control
- Template:Better source needed
- Template:Citation needed
- Template:Cite book
- Template:Cite web
- Template:Commons category
- Template:Copy edit
- Template:Distinguish
- Template:ISBN
- Template:Lead rewrite
- Template:Main
- Template:More citations needed
- Template:More citations needed section
- Template:Multiple issues
- Template:Original research
- Template:Peacock
- Template:Prone to spam
- Template:Refbegin
- Template:Refend
- Template:Reflist
- Template:Short description
- Template:Software development process
- Template:Software engineering
- Template:TOC limit
- Template:Unreliable sources
- Template:Use American English
- Template:Use mdy dates
- Template:Wikisource