Scrum Glossary

Edit Answers
REKUDIVCVDMEVITCEPSORTER-TNIRPSWNOX DSTAKEHOLDEROAOFDZCFCYUGIU-TVRHFUTO KDS-QFKRDOEGKZFRMZLRSLKDEVJNZLISZBL KIM-YGUEQPKBAMRCRWOHMGLIZXREIPAESUU WBMFPWCFVILYDMEGHMVOKFBUVCSMSSRUWRS U-FIJBSIMCTTGXIFVHBNCTRHLB-EAPELVEP EGBOXICNWARIXTQWCCPRJPZPIHSNQRPAWAR IIGUEZREHKWCEXSTPYGABFXQSGHICIOVHXI SVBIWTUMESRONSGDVMGNYDFQFLOFMNL-C-N PSYSUDMENKALCDVVHWCDKRBYTA-EHTEMJLT YPDTMA-NOWXEHNSFLLJOTESDNOSRQ-VUPL- NRSRSITTDBCV-VSQVDRSONCAIZZ-YRERFLG ZITACLES-PVVEOZETPAWZWRYRQVGGEDCUXO LNMHRYAAFSRWRWNBUCP-KOUZPTKOWVUS-BA LTGCU-MXONVOKTEYELWJY-MASWXLRIHOSHL A-Q-MSHT-GC-DDRRKKAAXT-CSSQKIEXCPXN OBEN-CQNNMMR-UOH-CJVECMG-RGCBWRB-SE GADWGRQNOUHLEFCOZRCKZUADEUMARUXLCHO -CLOUU-XIRAWNH-TJPPBUDSANPMBMSRGAQY TKSDIM-NTCRSPJDS-EPZGOTRAHC-PU-NRUB CLP-DSUBISDRDA-YUBJRNREIWVBTKITXDJE UORNEG-NNEMERGENCEAKEPRZMO-CXCDAFSY DGIRAIHXIICNXMPZYAICTMUZACIUHHOPMU- OINUSCIZFWCCHLXUMOUPKBDRHBNDFOQAHTJ RLTBEMONEVGFDCAAMBESRLDOMDHOSXRICNQ PI-TCUBWDTTUCVOMTCLFHVOLIQQRGAXICYK ORPYNMDEDIWUYNLB-JOXSIIGSRSPURIARBV ZMLBKIMTYYRJMFDNWN-HZHISMSICIRIPMEA BSAEBVBJWTXPKUWDQ-RQEXOFZSPHLHFYLMY OBNQINCREMENTGEHMMULGRINWLGNBIULIDH J-NTZFTSDRADNATS-GNIREENIGNEXCJZATL TNIEDTHRJATHVKNJMAEPINMNCBHCBSVEZMV KGNIGANAM-FLESHDBUABPRWNCZGPHORFMSY TTGBMUMHOEYYXE--A-NEWMDDPEFNFSBWOKW SBSPNDAOKAMACTTEGRIIXDFHNYEOKIGSPDC
1.
4-4-5, A chart which shows the amount of work which is thought to remain in a backlog. Time is shown on the horizontal axis and work remaining on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing
2.
4-2-5, A chart which shows the amount of work which has been completed. Time is shown on the horizontal axis and work completed on the vertical axis. As time progresses and items are drawn from the backlog and completed, a plot line showing the work done
3.
9, The quality of the relationship between certain Product Backlog items which may make them worthy of consideration as a whole. See also: Sprint Goal.
4.
5-5, Scrum Event that is a 15-minute time-boxed event held each day for the Developers. The _____ _____ is held every day of the Sprint. At it, the Developers plans work for the next 24 hours. This optimizes team collaboration and performance by inspectin
5.
10-2-4, A formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the __________ __ ____, an Increment is born. The __________ __ ____ creates transparency by pr
6.
9, Any member of a Scrum Team, that is committed to creating any aspect of a usable Increment each Sprint regardless of technical, functional or other specialty.
7.
9, The process of the coming into existence or prominence of new facts or new knowledge of a fact, or knowledge of a fact becoming visible unexpectedly.
8.
10, The philosophy that all knowledge originates in experience and observations. It’s a cornerstone of the scientific method and underlies much of modern science and medicine. In the context of Scrum, __________ refers to the idea that solving complex pro
9.
11-9, A shared set of development and technology standards that Developers apply to create releasable Increments of software.
10.
8, The selection of items from the Product Backlog Developers deems feasible for implementation in a Sprint.
11.
9, Scrum Artifact that defines the complete and valuable work produced by the Developers during a Sprint. The sum of all _________s form a product.
12.
7-7, A Scrum Artifact that consists of an ordered list of the work to be done in order to create, maintain and sustain a product. Managed by the Product Owner.
13.
7-7-10, The activity in a Sprint through which the Product Owner and the Developers add granularity to one of the Artefacts.
14.
7-5, Role in Scrum accountable for maximizing the value of a product, primarily by incrementally managing and expressing business and functional expectations for a product to the Developers.
15.
7-4, Describes a future state of the product which can serve as a target for the Scrum Team to plan against. The _______ ____ is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the _______ ____.
16.
5, A shared understanding by the Product Owner and the Developers regarding the preferred level of description of Product Backlog items introduced at Sprint Planning.
17.
10, See "Product Backlog __________"
18.
5, A lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems as defined in the _____ Guide
19.
5-5, A physical _____ to visualize information for and by the Scrum Team, often used to manage Sprint Backlog. _____ _____s are an optional implementation within Scrum to make information visible.
20.
5-5, The definition of Scrum, written and provided by Ken Schwaber and Jeff Sutherland, co-creators of Scrum. This definition consists of Scrum’s accountabilities, events, artifacts, and the rules that bind them together.
21.
5-6, Role within a Scrum Team accountable for guiding, coaching, teaching and assisting a Scrum Team and its environments in a proper understanding and use of Scrum.
22.
5-4, A self-managing team consisting of one Scrum Master, one Product Owner, and Developers.
23.
5-6, A set of fundamental ______ and qualities underpinning the Scrum framework; commitment, focus, openness, respect and courage.
24.
4-8, Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also ____-________, meaning they internally decide who does what, when, and how.
25.
6, Scrum Event that is time-boxed to one month or less, that serves as a container for the other Scrum events and activities. ______s are done consecutively, without intermediate gaps.
26.
6-7, Scrum Artifact that provides an overview of the development work to realize a Sprint’s goal, typically a forecast of functionality and the work needed to deliver that functionality. Managed by the Developers.
27.
6-4, A short expression of the purpose of a Sprint, often a business problem that is addressed. Functionality might be adjusted during the Sprint in order to achieve the ______ ____.
28.
6-8, Scrum Event that is time-boxed to 8 hours, or less, to start a Sprint. It serves for the Scrum Team to inspect the work from the Product Backlog that’s most valuable to be done next and design that work into Sprint backlog.
29.
6-13, Scrum Event that is set to a time-box of 3 hours, or less, to end a Sprint. It serves for the Scrum Team to inspect the past Sprint and plan for improvements to be enacted during future Sprints.
30.
6-6, Scrum Event that is set to a time-boxed of 4 hours, or less, to conclude the development work of a Sprint. It serves for the Scrum Team and the stakeholders to inspect the Increment of product resulting from the Sprint, assess the impact of the work
31.
11, A person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review.
32.
9-4, The typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the Increment or introduced purposefully to realize value ear
33.
6, When the ______ of commitment, courage, focus, openness and respect are embodied and lived by the Scrum Team, the *Scrum pillars* of transparency, inspection, and adaptation *come to life* and *build trust* for everyone. The Scrum Team members learn an
34.
8, An optional, but often used, indication of the amount of Product Backlog turned into an Increment of product during a Sprint by a Scrum Team, tracked by the Developers for use within the Scrum Team.