scrum Flashcards
(156 cards)
1
Q
Hvor mange mennesker kan indgå som product owner?
A
En! - PO er en person, ikke en commite,
Men må gerne aggere på vegne af en commite.
The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a Product Backlog item’s priority must address the Product Owner
2
Q
Hvordan kan product owneren hjælpe med at få en plan for hvordan man får et “done” proiduct increment under sprint planning?
A
The Product Owner can help to clarify the selected Product Backlog items and make trade-offs. If the Development Team determines it has too much or too little work, it may renegotiate the selected Product Backlog items with the Product Owner. The Development Team may also invite other people to attend to provide technical or domain advice.
3
Q
Hvad skal scrum masteren gøre med interaktioner fra folk uden fra scrum teamet?
A
Han skal hjælpe dem med at forstå hvilke interaktioner som gavner scrum teamet og hvilke der ikke gør.
Han hjælper også alle med at ændre disse interaktioner, så holdet leverer så meget værdi som muligt.
4
Q
Who creates the definition of “Done”?
A
The development organization (or Development Team if none is available from the development organization)
If the definition of “done” is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum. The Development Team of the Scrum Team can complement it with elements specific for the product or context.
If “done” for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of “done” appropriate for the product.
5
Q
Hvad giver det at have de vigtige værdier når man laver scrum?
A
Når disse værdier er levet i scrum teamet, vil de tre milepæle komme til live.
Scrumet teamets medlemmer udforsker og lærer disse værdier ved at arbejde med roller, events og artefakter.
6
Q
Hvad er nogle eksempler på spørgsmål under daily scrum?
A
- What did I do yesterday that helped the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
7
Q
Hvornår bliver product backlog items refined?
A
This is an ongoing process in which the Product Owner and the Development Team collaborate on the details of Product Backlog items.
Product Backlog items can be updated at any time by the Product Owner or at the Product Owner’s discretion.
8
Q
Hvad er yderst kristisk for at en product owner kan få success?
A
At hele organisationen accepterer og respekterer hans beslutninger.
For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner’s decisions are visible in the content and ordering of the Product Backlog. No one can force the Development Team to work from a different set of requirements
9
Q
Hvad bruger man sprint goal til under sprintet?
A
As the Development Team works, it keeps the Sprint Goal in mind. In order to satisfy the Sprint Goal, it implements functionality and technology. If the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.
10
Q
Kan man undlade nogle af scrum events?
A
Nej!
. Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt.
11
Q
Beskriv
Topic Two: How will the chosen work get done?
A
Efter at have fundet et mål, og efter at have valgt product backlog items for sprintet,
skal development teamet afgøre hvordan de vil lave denne funktionalitet til et “done” product increment under sprintet.
12
Q
Hvor stort skal et development team være?
A
3 - 9
Smaller Development Teams may encounter skill constraints during the Sprint, causing the Development Team to be unable to deliver a potentially releasable Increment. Having more than nine members requires too much coordination. Large Development Teams generate too much complexity for an empirical process to be useful. The Product Owner and Scrum Master roles are not included in this count unless they are also executing the work of the Sprint Backlog.
13
Q
Kan man undlade dele af scrum og stadig kalde det scrum?
A
Nej.
Scrum’s roles, events, artifacts, and rules are immutable and although implementing only parts of Scrum is possible, the result is not Scrum.
Scrum exists only in its entirety and functions well as a container for other techniques, methodologies, and practices.
14
Q
Hvad er de fire formælle events for inspektion og adaption?
A
Sprint planning
Daily scrum
sprint review
Sprint retrospective
15
Q
Hvad giver det hvis en defintion af “done” er en del af konventionerne for scrum teamet?
A
Development Teams deliver an Increment of product functionality every Sprint. This Increment is useable, so a Product Owner may choose to immediately release it.
If the definition of “Done” for an increment is part of the conventions, standards or guidelines of the development organization, all Scrum Teams must follow it as a minimum.
16
Q
Hvordan leverer et scrum team produkter og nye udvidelser dertil?
A
Scrum Teams deliver products iteratively and incrementally, maximizing opportunities for feedback. Incremental deliveries of “Done” product ensure a potentially useful version of working product is always available.
17
Q
Hvad er et sprint mål?
A
Each Sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product increment.
18
Q
Hvad er essensen af scrum?
A
Scrum er et lille team af mennesker
Hvert team er yder fleksibel og kan tilpasse sig omstændigheder
Disse styrker kan derefter fortsat virke ved skalering, hvor flere og flere små teams arbejder sammen og udvikling, release, vedligeholdelse af arbejde og produkter.
19
Q
Hvad kræves der før en product backlog item kan trækkes over i sprint backloggen?
A
Product Backlog items that can be “Done” by the Development Team within one Sprint are deemed “Ready” for selection in a Sprint Planning. Product Backlog items usually acquire this degree of transparency through the above described refining activities.
20
Q
Hvad er mulighederne ved et sprint retrospective?
A
The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint.
21
Q
Hvor lang tilbage har scrum været brugt?
A
De tidlige 1990’ere
22
Q
Hvordan tjener scrum masteren product owneren?
A
- Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;
- Finding techniques for effective Product Backlog management;
- Helping the Scrum Team understand the need for clear and concise Product Backlog items;
- Understanding product planning in an empirical environment;
- Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
- Understanding and practicing agility;
- Facilitating Scrum events as requested or needed.
23
Q
Kan nogle komponenter tages ud af scrum frameworket?
A
Nej!
Hvet komponent tjener et bestemt formål og er essentiel t
24
Q
Hvad er instepection for en af de tre milepæle?
A
Scrum brugere, skal ofte undersøge scrum artefakter og fremskridt mod et sprint mål for at opdage uønskede variationer.
Inspektion bør ikke ske så ofte at det står i vejen for selve arbejdet.
Inspektion er mest anvendelig når den bliver udført af erfarne inspektører under selve arbejdet
25
Er scrum kun til IT udvikling?
Nej - det blev lavet til at styre og udvikle produkter, men er også set blevet brugt til:
* Research og identifikation af marked, teknology og produktmuligheder
* Udvikle produkter og udvidelser
* Release produkter og udvidelser
* Udvikle og vedligeholde cloud (online - secure - on demand) og andre operationelle miljøer for produkt brug
* Vedligeholde og fornye produkter
scrum har været brugt til Software, hardware, selvkørende biler, skoler, marketing, og næsten alt vi gør i vores daglige liv som individer og som samfund.
26
Hvad er et sprint
Hjertet i scrum
Time boxed tid (en måned eller mindre) hvori et "done", brugbart og potentielt releaseable produkt inkrement bliver lavet.
27
Hvordan kan ting tilføjes og fjernes fra sprint backloggen?
As new work is required, the Development Team adds it to the Sprint Backlog. As work is performed or completed, the estimated remaining work is updated.
When elements of the plan are deemed unnecessary, they are removed.
28
Hvem er ansvarlig for product backloggen?
The Product Owner is responsible for the Product Backlog, including its content, availability, and ordering.
29
Hvad indgår i at styre produkt backloggen?
* Clearly expressing Product Backlog items;
* Ordering the items in the Product Backlog to best achieve goals and missions;
* Optimizing the value of the work the Development Team performs;
* Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and,
* Ensuring the Development Team understands items in the Product Backlog to the level needed.
The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.
30
Hvad er daily scrum?
The Daily Scrum is a 15-minute time-boxed event for the Development Team. The Daily Scrum is held every day of the Sprint. At it, the Development Team plans work for the next 24 hours.
31
Er det kun product owneren som må lave backlog management?
Nej - der må gerne uddelegeres, men det er PO som har ansvaret for at det er gjort ordentligt.
The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable.
32
Hvordan håndterer man de første opgaver som kommer i sprintet?
Work planned for the first days of the Sprint by the Development Team is decomposed by the end of this meeting, often to units of one day or less.
33
Hvad består et sprint egentligt af?
Sprints contain and consist of the Sprint Planning, Daily Scrums, the development work, the Sprint Review, and the Sprint Retrospective.
34
Hvilken videnskabs teori bygger scrum på?
Emperisk proces kontrol teori. Eller Emperi.
Som er at viden kommer af erfaring og at tage beslutninger, baseret på hvad der er kendt.
Scrum bruger en iterativ, inkrementiel tilgang for optimere forudsigelighed og kontrol af risici.
35
Hvad er en sprint backlog?
Items fra product backlog samt plan for hvordan man løser dem.
36
Hvad er scrum masterens ansvar ved sprint planning?
At lære holdet at holde sig inde for den timeframe som er sat (8 timer for en måneds sprint).
37
Hvad er en product backlog?
The Product Backlog is an ordered list of everything that is known to be needed in the product. It is the single source of requirements for any changes to be made to the product.
38
Hvilke andre elementer er en del af sprint review?
* The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning;
* Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and,
* Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated releases of functionality or capability of the product
39
Hvad gør man når et sprint bliver afbrudt?
Alle "Done" product backlog items bliver reviewed.
Hvis dele af produktet kan releases, kan product owneren ofte acceptere at gøre dette.
Alle ikke færdige product backlog items, er re-estimated og placeret tilbage i product backlogen
40
Hvad betyder det at scrum teamet er cross-functional?
Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.
41
Hvilke værdier er vigtige at have for at kunne udføre scrum?
commitment, courage, focus, openness and respect
42
Kan sprint backloggen modificeres?
Ja! Grundet ny information ved at løse opgaverne.
The Development Team modifies the Sprint Backlog throughout the Sprint, and the Sprint Backlog emerges during the Sprint.
This emergence occurs as the Development Team works through the plan and learns more about the work needed to achieve the Sprint Goal.
43
Hvad er definitionen på scrum?
Det er et framework til at kunne adressere komplekse adaptive problemer, og samtidigt kunne levere en løsning med højest værdi på en produktiv og kreativ måde.
44
Hvad indeholder sprint backloggen?
The Sprint Backlog makes visible all the work that the Development Team identifies as necessary to meet the Sprint Goal.
To ensure continuous improvement, it includes at least one high priority process improvement identified in the previous Retrospective meeting.
The Sprint Backlog is a plan with enough detail that changes in progress can be understood in the Daily Scrum.
45
Er en product backlog nogensinde færdig?
Nej!!
A Product Backlog is never complete.
If a product exists, its Product Backlog also exists.
46
Hvornår er scrum specielt effektivt?
Ved inkrementiel og iterativ videns overførsel.
Derfor bliver det også brugt til at styre parent organisationer samt produkter og services
47
Kan flere scrum teams arbejde ud fra samme product backlog?
Ja! Der kan dog introduceres grouping attributes for at give overblik.
Multiple Scrum Teams often work together on the same product. One Product Backlog is used to describe the upcoming work on the product.
A Product Backlog attribute that groups items may then be employed.
48
Hvad er det helt præcist der er i en product backlog?
The Product Backlog lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases.
49
Hvordan påvirkes definition of "done" under et retrospective?
During each Sprint Retrospective, the Scrum Team plans ways to increase product quality by improving work processes or adapting the definition of “Done”, if appropriate and not in conflict with product or organizational standards.
50
Er scrum masteren en boss på holdet?
Nej - scrum masteren er en servant-leader
51
Hvad gør man hvis der ikke er nogen definition for "Done" fastlagt for et inkrement?
If "Done" for an increment is not a convention of the development organization, the Development Team of the Scrum Team must define a definition of “Done” appropriate for the product.
52
Hvad er scrum masterens rolle i daily scrum?
The Scrum Master ensures that the Development Team has the meeting, but the Development Team is responsible for conducting the Daily Scrum.
The Scrum Master teaches the Development Team to keep the Daily Scrum within the 15-minute time-box
The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.
53
Hvad er formålet med et sprint retrospective?
* Inspect how the last Sprint went with regards to people, relationships, process, and tools;
* Identify and order the major items that went well and potential improvements;
* Create a plan for implementing improvements to the way the Scrum Team does its work
54
Hvad er udfaldet af et sprint review?
The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.
55
Må ingen andre påvirker product owneren til at afbryde et sprint?
Jo
he or she may do so under influence from the stakeholders, the Development Team, or the Scrum Master.
56
Er det meget vigtigt at teste et inkrement?
Ja!!!
Each Increment is additive to all prior Increments and thoroughly tested, ensuring that all Increments work together.
57
Hvordan monitorer man fremgang i sprint backloggen?
At any point in time in a Sprint, the total work remaining in the Sprint Backlog can be summed.
The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal.
By tracking the remaining work throughout the Sprint, the Development Team can manage its progress
58
Beskriv et sprint review
A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed
During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint
59
Hvad er scrum masterens ansvar?
At understøtte og promovære scrum. Dette gøres ved at hjælpe hele holdet og andre med at forstå scrum i praksis.
The Scrum Master is responsible for promoting and supporting Scrum as defined in the Scrum Guide. Scrum Masters do this by helping everyone understand Scrum theory, practices, rules, and values.
60
Hvad menes der med en definition af "Done"?
When a Product Backlog item or an Increment is described as “Done”, everyone must understand what “Done” means.
Although this may vary significantly per Scrum Team, members must have a shared understanding of what it means for work to be complete, to ensure transparency.
This is the definition of “Done” for the Scrum Team and is used to assess when work is complete on the product Increment.
61
Hvorfor må et sprint ikke være længere end en måned?
Sprints enable predictability by ensuring inspection and adaptation of progress toward a Sprint Goal at least every calendar month. Sprints also limit risk to one calendar month of cost.
62
Hvor lang tid varer et sprint review?
This is at most a four-hour meeting for one-month Sprints.
For shorter Sprints, the event is usually shorter.
63
Hvad betyder det at scrum teamet er self organizing?
Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team
64
Hvordan hjælper det development teamet at der er en defintion of "done"?
The same definition guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning.
The purpose of each Sprint is to deliver Increments of potentially releasable functionality that adhere to the Scrum Team’s current definition of “Done.”
65
Bør diskussioner indbyrdes tage under daily scrum?
Nej! Tages lige bagefter med de vigtige individer
The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint’s work.
66
Hvem fordeler de første opgaver i sprintet?
The Development Team self-organizes to undertake the work in the Sprint Backlog, both during Sprint Planning and as needed throughout the Sprint.
67
Hvad er transparency for en af de tre milepæle?
Vigtige dele af processen skal være synlighe for de personer som er ansvarlige for udfaldet.
Transparency kræver at disse aspekter er defineret af en fælles standard, så observatøre deler en fælles forståelse af hvad der bliver set
Eksempelvis:
Et fælles sprog som referer til processen skal være på plads
Dem som laver arbejdet og dem som undersøger det resulterende inkrement, bør dele en fælles forståelse for "done".
68
Hvor meget tid bør der maksimalt bruges på product backlog refinement af development teamet?
Refinement usually consumes no more than 10% of the capacity of the Development Team.
69
Hvad kan et sprint ses som projekt mæssigt?
Et sprint kan ses som et selvstændigt projekt med en længde på en måned eller mindre (aldrig mere)
70
Hvilke inputs er der i:
Topic One: What can be done this Sprint?
the Product Backlog,
the latest product Increment,
projected capacity of the Development Team during the Sprint,
and past performance of the Development Team.
71
Hvad kan ændre indholdet i en product backlog?
Changes in business requirements, market conditions, or technology may cause changes in the Product Backlog
72
Er burndowns og burn-ups alpha omega?
Nej - intet slår emperi. (lær ud fra erfaring)
Various projective practices upon trending have been used to forecast progress, like burndowns, burn-ups, or cumulative flows.
These have proven useful. However, these do not replace the importance of empiricism. In complex environments, what will happen is unknown.
Only what has already happened may be used for forward-looking decision-making
73
kan et sprint blive forlænget eller forkortet?
Så længe det ikke er begyndt.
Når et sprint begynder, kan det ikke forkortes eller forlænges
De resterende events kan slutte når grunden til dette event er opnået, for at sikre at den passende mængde tid bliver brugt uden at tillade spild i processen.
Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process.
74
Hvad består scrum teamet af?
Product owner,
Development Team,
Scrum master
75
Hvad er sprint backloggen?
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal.
The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
76
Hvilke karakteristikker er der for et development team?
* They are self-organizing. No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality;
* Development Teams are cross-functional, with all the skills as a team necessary to create a product Increment;
* Scrum recognizes no titles for Development Team members, regardless of the work being performed by the person;
* Scrum recognizes no sub-teams in the Development Team, regardless of domains that need to be addressed like testing, architecture, operations, or business analysis;
* Individual Development Team members may have specialized skills and areas of focus, but accountability belongs to the Development Team as a whole
77
Hvad er product backlog refinement?
Product Backlog refinement is the act of adding detail, estimates, and order to items in the Product Backlog.
During Product Backlog refinement, items are reviewed and revised.
78
Skal andre organisere scrum teamet?
Nej - Scrum Teams are self-organizing and cross-functional.
79
Hvilke tre milepæle opretholder implementering af emperisk kontrol proces (emperi)?
transparency, inspection, adaption
80
Er det dem med de bedste kompentencer som har ansvaret for nogle af opgaverne?
Nej - hele development teamet bærer ansvaret som helhed.
81
Er taktikker for hvordan man bruger scrum frameworket beskrevet i scrum guiden?
Nej - de er at finde andetsteds
82
Hvad er det generelle formål med daily scrum?
Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.
83
Hvad giver daily scrum?
optimizes team collaboration and performance by inspecting the work since the last Daily Scrum and forecasting upcoming Sprint work.
The Daily Scrum optimizes the probability that the Development Team will meet the Sprint Goal.
84
Hvad er scrum artefakter og hvorfor bruges de?
Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact
85
Beskriv:
Topic One: What can be done this Sprint?
The Product Owner discusses the objective that the Sprint should achieve and the Product Backlog items that, if completed in the Sprint, would achieve the Sprint Goal.
The Development Team works to forecast the functionality that will be developed during the Sprint.
The entire Scrum Team collaborates on understanding the work of the Sprint.
86
Hvad er team modellen for scrum designet til at kunne?
The team model in Scrum is designed to optimize flexibility, creativity, and productivity. The Scrum Team has proven itself to be increasingly effective for all the earlier stated uses, and any complex work.
87
Hvor meget detaljeret er product backlog items ofte?
Higher ordered Product Backlog items are usually clearer and more detailed than lower ordered ones. More precise estimates are made based on the greater clarity and increased detail;
the lower the order, the less detail.
88
Hvad skal der være af ting i product backloggen i en tidlig fase af systemet?
The earliest development of it lays out the initially known and best-understood requirements.
The Product Backlog evolves as the product and the environment in which it will be used evolves.
The Product Backlog is dynamic; it constantly changes to identify what the product needs to be appropriate, competitive, and useful.
89
Når scrum guiden skriver ordet "develop" hvad mener de så?
komplekst arbejde
90
Hvornår er et "Done" inkrement krævet?
Ved sprint review
91
Hvorfor vil man afbryde et sprint?
Hvis målet er blevet forældet.
A Sprint would be cancelled if the Sprint Goal becomes obsolete. This might occur if the company changes direction or if market or technology conditions change. In general, a Sprint should be cancelled if it no longer makes sense given the circumstances. But, due to the short duration of Sprints, cancellation rarely makes sense.
92
Hvor eksisterer scrum events?
Alle events er for at introducere regelmæssighed (regularity)
og for a minimere nødvendigheden for andre møder som ikke er fastlagt i scrum
93
Tæller product owner og scrum master rollen med i development teamets størrelse
Kun hvis de også udfører arbejdet i sprint backloggen.
94
Hvem må udarbejdet et "Done" Inkrement?
Kun medlemmer af udviklingsholdet.
95
Hvor lang tid varer et sprint retrospective?
This is at most a three-hour meeting for one-month Sprints.
For shorter Sprints, the event is usually shorter.
96
Hvad arbejder udviklings holdet mod?
Et potentielt releaseable inkrement af "Done" product for hvert sprint
97
Kan en ændret definition for "done" kræve ændringer i tidligere arbejde?
Ja!
As Scrum Teams mature, it is expected that their definitions of “Done” will expand to include more stringent criteria for higher quality.
New definitions, as used, may uncover work to be done in previously “Done” increments.
Any one product or system should have a definition of “Done” that is a standard for any work done on it.
98
Hvornår foregår et sprint retrospective?
The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.
99
Hvad svarer sprint planning på?
* What can be delivered in the Increment resulting from the upcoming Sprint?
* How will the work needed to deliver the Increment be achieved?
100
Hvordan laver man en definition af "done", hvis der er flere scrum teams som arbejder ud fra samme product backlog?
If there are multiple Scrum Teams working on the system or product release, the Development Teams on all the Scrum Teams must mutually define the definition of “Done.”
101
Hvem er ansvarlig for estimater af ting i product backloggen?
Development teamet
The Development Team is responsible for all estimates. The Product Owner may influence the Development Team by helping it understand and select trade-offs, but the people who will perform the work make the final estimate.
102
Hvem må modificere på sprint backloggen?
Only the Development Team can change its Sprint Backlog during a Sprint.
The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team.
103
Er scrum en teknik, en process eller en metode?
Det er ingen af delene. Scrum er et framework hvortil man kan benytte forskellige processer, teknikker og metoder
104
Hvem afgører hvornår product backlog refinement er done?
The Scrum Team decides how and when refinement is done
105
Hvad består scrum frameworket af?
scrum teamet
deres roller
events
artefakter
og regler
106
Hvad er utroligt vigtigt for værdierne at scrum teamet og stakeholders acceptere?
The Scrum Team and its stakeholders agree to be open about all the work and the challenges with performing the work. Scrum Team members respect each other to be capable, independent people.
107
Bør man ofte afbryde sprints?
Nej!!
Sprint cancellations consume resources, since everyone regroups in another Sprint Planning to start another Sprint. Sprint cancellations are often traumatic to the Scrum Team, and are very uncommon
108
Hvem er med til et sprint review?
Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
109
Hvem må vælge hvilke product backlog items som er en del af sprintet?
Det er kun op til development teamet
The number of items selected from the Product Backlog for the Sprint is solely up to the Development Team
Only the Development Team can assess what it can accomplish over the upcoming Sprint.
110
Hvordan tjener scrum masteren development teamet?
* Coaching the Development Team in self-organization and cross-functionality;
* Helping the Development Team to create high-value products;
* Removing impediments to the Development Team’s progress;
* Facilitating Scrum events as requested or needed;
* Coaching the Development Team in organizational environments in which Scrum is not yet fully adopted and understood.
111
Hvordan finder teamet frem til et "done" product increment under sprint planning?
The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment.
Work may be of varying size, or estimated effort. However, enough work is planned during Sprint Planning for the Development Team to forecast what it believes it can do in the upcoming Sprint.
112
Hvornår bliver et sprint goal lavet?
Det bliver også lavet som en del af sprint planning
During Sprint Planning the Scrum Team also crafts a Sprint Goal. The Sprint Goal is an objective that will be met within the Sprint through the implementation of the Product Backlog, and it provides guidance to the Development Team on why it is building the Increment.
113
Hvad er strukturen på daily scrum?
Det sættes af udviklingsholdet, nogle vil bruge spørgsmål, andre er mere discussion based.
114
Må sprints variere i længde?
Nej, de har konsistent længde gennem samme udviklingsindsats.
115
Hvad består product backlog items af?
Product Backlog items have the attributes of a description, order, estimate, and value.
Product Backlog items often include test descriptions that will prove its completeness when “Done.”
116
Hvad gælder der altid for et sprint?
* No changes are made that would endanger the Sprint Goal;
* Quality goals do not decrease; and,
* Scope may be clarified and re-negotiated between the Product Owner and Development Team as more is learned
117
Hvad er et increment?
The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints.
At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done.”
An increment is a body of inspectable, done work that supports empiricism at the end of the Sprint.
The increment is a step toward a vision or goal. The increment must be in useable condition regardless of whether the Product Owner decides to release it.
118
Hvad kan scrum masteren gøre for at give gennemsigtighed for artefakter?
The Scrum Master must work with the Product Owner, Development Team, and other involved parties to understand if the artifacts are completely transparent.
There are practices for coping with incomplete transparency; the Scrum Master must help everyone apply the most appropriate practices in the absence of complete transparency.
. A Scrum Master can detect incomplete transparency by inspecting the artifacts, sensing patterns, listening closely to what is being said, and detecting differences between expected and real results.
The Scrum Master’s job is to work with the Scrum Team and the organization to increase the transparency of the artifacts. This work usually involves learning, convincing, and change. Transparency doesn’t occur overnight, but is a path.
119
Giv en detaljeret beskrivelse af et sprint goal.
The Sprint Goal is an objective set for the Sprint that can be met through the implementation of Product Backlog. It provides guidance to the Development Team on why it is building the Increment.
The selected Product Backlog items deliver one coherent function, which can be the Sprint Goal.
The Sprint Goal can be any other coherence that causes the Development Team to work together rather than on separate initiatives.
The Sprint Goal gives the Development Team some flexibility regarding the functionality implemented within the Sprint.
120
What are the two primary ways a Scrum Master keeps a Development Team working at its highest level of productivity?
By facilitating Development Team decisions
By removing impediments that hinder the Development Team
A Scrum Master is a servant-leader for the Development Team. Facilitation and removing impediments serves a team in achieving the best productivity possible.
121
Hvornår starter et nyt sprint?
Med det samme efter konklusionen af det tidligere.
A new Sprint starts immediately after the conclusion of the previous Sprint.
122
Hvordan forbedre scrum ens arbejde?
Scrum gør ens produkt management og arbejdsteknikker i stand til at forbedre produktet, teamet eller arbejdsmiljøet
123
Hvad er scrum masterens ansvar for et sprint retrospective?
The Scrum Master ensures that the event takes place and that attendants understand its purpose
The Scrum Master ensures that the meeting is positive and productive.
The Scrum Master teaches all to keep it within the time-box.
The Scrum Master participates as a peer team member in the meeting from the accountability over the Scrum process
The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint.
124
Hvordan reagerer sprint reviewet på ændringer i product backlog?
Based on that and any changes to the Product Backlog during the Sprint, attendees collaborate on the next things that could be done to optimize value
125
Hvad er udfaldet af sprint retrospective?
By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint.
Implementing these improvements in the next Sprint is the adaptation to the inspection of the Scrum Team itself.
Although improvements may be implemented at any time, the Sprint Retrospective provides a formal opportunity to focus on inspection and adaptation.
126
Hvor bliver daily scrum afholdt?
The Daily Scrum is held at the same time and place each day to reduce complexity.
127
Hvad bør være slutningen på sprint planning?
By the end of the Sprint Planning, the Development Team should be able to explain to the Product Owner and Scrum Master how it intends to work as a self-organizing team to accomplish the Sprint Goal and create the anticipated Increment.
128
Hvorfor er det vigtigt at have gennemsigtighed (transparency) for de forskellige artefakter?
Scrum relies on transparency.
Decisions to optimize value and control risk are made based on the perceived state of the artifacts.
To the extent that transparency is complete, these decisions have a sound basis.
To the extent that the artifacts are incompletely transparent, these decisions can be flawed, value may diminish and risk may increase.
129
Hvilke andre elementer er en del af sprint review? Part 1
* The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
* The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved;
* The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
* The Product Owner discusses the Product Backlog as it stands. He or she projects likely target and delivery dates based on progress to date (if needed);
130
Hvem har ansvaret for product backloggen?
Product owner - og kun ham / hende!
The Product Owner is the sole person responsible for managing the Product Backlog.
131
Hvad bør altid være udfaldet ved et daily scrum?
Every day, the Development Team should understand how it intends to work together as a selforganizing team to accomplish the Sprint Goal and create the anticipated Increment by the end of the Sprint.
132
Hvad er sprint planning?
The work to be performed in the Sprint is planned at the Sprint Planning. This plan is created by the collaborative work of the entire Scrum Team. Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.
133
Hvad er ansvaret for product owner?
The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.
134
Hvad er Adaption for en af de tre milepæle?
Hvis en inspektør afgører at en eller flere aspekter af en proces afviger fra de acceptable grænser, og at de resulterende produkt derfor bliver uacceptabelt, så skal processen eller materialet som bliver processeret justeres.
En justering skal udføres hurtigst muligt for at minimere yderligere avigelse.
135
Kan udviklings holdet blive bedt om at arbejde på noget andet en det som er i product backloggen?
Nej! Det er kun den prioriterede product backlog som der kan arbejdes ud fra.
136
Kan et sprint afbrydes (cancel)?
Ja - men kun af product owneren
137
Hvordan skal product backlog items for det kommende sprint se ud?
Product Backlog items that will occupy the Development Team for the upcoming Sprint are refined so that any one item can reasonably be “Done” within the Sprint time-box
138
Er sprint review et status møde?
Nej!!
is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.
139
Hvordan tjener scrum masteren organisationen?
* Leading and coaching the organization in its Scrum adoption;
* Planning Scrum implementations within the organization;
* Helping employees and stakeholders understand and enact Scrum and empirical product development;
* Causing change that increases the productivity of the Scrum Team;
* Working with other Scrum Masters to increase the effectiveness of the application of Scrum in the organization.
140
Hvordan undersøger man fremgang mod produkt målet?
At any point in time, the total work remaining to reach a goal can be summed
The Product Owner tracks this total work remaining at least every Sprint Review.
The Product Owner compares this amount with work remaining at previous Sprint Reviews to assess progress toward completing projected work by the desired time for the goal.
This information is made transparent to all stakeholders.
141
Hvornår kan man inspecte og adapte noget?
Bortset fra sprintet selv, da det blot er en container for events, er alle events en mulighed for at inspecte og adapte noget. De er designet for at lave kritisk transparens og inspektion.
Other than the Sprint itself, which is a container for all other events, each event in Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical transparency and inspection.
142
Hvad er scrum masterens ansvar for et sprint review?
The Scrum Master ensures that the event takes place and that attendees understand its purpose.
The Scrum Master teaches everyone involved to keep it within the timebox.
143
Who is allowed to change the Sprint Backlog during the Sprint?
Only the Development Team can change its Sprint Backlog during a Sprint. The Sprint Backlog is a highly visible, real-time picture of the work that the Development Team plans to accomplish during the Sprint, and it belongs solely to the Development Team
144
What could be a source of requirements for any changes to be made to the product?
The Product Backlog
The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product.
145
What provides guidance to the Development Team on why it is building the Increment?
The Sprint Goal
146
How does Definition of “Done” help the Scrum Team? Select three most applicable items.
DoD ensures artifact transparency
DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning
DoD is used to assess when work is complete on the product Increment
147
What is the result of the Sprint Review?
A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
The result of the Sprint Review is a revised Product Backlog that defines the probable Product Backlog items for the next Sprint. The Product Backlog may also be adjusted overall to meet new opportunities.
148
How does the Scrum Master help to the Product Owner?
Understanding product planning in an empirical environment
Finding techniques for effective Product Backlog management
Facilitating Scrum events as requested or needed
The Scrum Master serves the Product Owner in several ways, including:
Ensuring that goals, scope, and product domain are understood by everyone on the Scrum Team as well as possible;
Finding techniques for effective Product Backlog management;
Helping the Scrum Team understand the need for clear and concise Product Backlog items;
Understanding product planning in an empirical environment;
Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value;
Understanding and practicing agility; and,
Facilitating Scrum events as requested or needed.
149
Who is allowed to participate in the Daily Scrum?
The Development Team
The Daily Scrum is an internal meeting for the Development Team. If others are present, the Scrum Master ensures that they do not disrupt the meeting.
150
How does Definition of “Done” help the Scrum Team? Select three most applicable items.
DoD ensures artifact transparency
DoD is used to assess when work is complete on the product Increment
DoD guides the Development Team in knowing how many Product Backlog items it can select during a Sprint Planning
151
Explain the five scrum values
Commitment
Focus
Courage
Respect
Openness
152
What are the Scrum Artifacts? Select all applicable items.
Increment
Product Backlog
Sprint Backlog
153
What is the result of the Sprint Review?
A revised Product Backlog that defines the probable Product Backlog items for the next Sprint
154
What are the Scrum Artifacts? Select all applicable items.
The Scrum artifacts are Product Backlog, Sprint Backlog and Increment.
155
156
