You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1591,7 +1591,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
1591
1591
### What should Developers do if the Product Owner is unavailable?
1592
1592
1593
1593
-[ ] Wait until the Product Owner is available again.
1594
-
-[ ] Management should assign a substitue Product Owner to fill in where the Product Oner cannot be there.
1594
+
-[ ] Management should assign a substitue Product Owner to fill in where the Product Owner cannot be there.
1595
1595
-[ ] Ask the Product Owner's manager to decide in the Product Owner's absence.
1596
1596
-[x] Within the Sprint, the Developers make the best decisions posssible to assure progress towards the Sprint Goal, re-aligning with the Product Owner once they are available again.
1597
1597
@@ -1601,7 +1601,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
1601
1601
1602
1602
-[ ] They should work apart as much as posssible in order to keep the concerns of business and technology separated.
1603
1603
-[x] They collaborate often so the Developers build Increments keeping end-user and stakeholder concerns in mind.
1604
-
-[x] They collaborate often so the Product Oner can make informed decisions in balancing effort and value of Product Backlog Items.
1604
+
-[x] They collaborate often so the Product Owner can make informed decisions in balancing effort and value of Product Backlog Items.
1605
1605
-[ ] They should share no more than the Sprint Planning and the Sprint Review meeting.
1606
1606
-[ ] The Product Owner should be with the Developers full-time to grow a deep understanding of the technology being used.
1607
1607
@@ -1620,7 +1620,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
1620
1620
-[ ] The Product Owner provides the stakeholders with acceptance forms at the Sprint Review to record their formal agreement over the delivered software.
1621
1621
-[x] The Product Owner actively asks for stakeholder input and expectations to incorporate into the Product Backlog.
1622
1622
-[ ] The Product Owner has the final call over the requirements and should involve the stakeholders as little as possible.
1623
-
-[ ] The Product Oner rites the Usser Storiess as provided by the stakeholders.
1623
+
-[ ] The Product Owner rites the Usser Storiess as provided by the stakeholders.
1624
1624
1625
1625
**[⬆ Back to Top](#table-of-contents)**
1626
1626
@@ -1637,7 +1637,7 @@ We are so thankful for every contribution, which makes sure we can deliver top-n
1637
1637
### Is the Product Owner required to be present at the Sprint Retrospective?
1638
1638
1639
1639
-[ ] They are not allowed. The Sprint Retrosspective is an opportunity for the Developerss to improve.
1640
-
-[ ] They are optional. Attendance is only required when the Product Oner gets invited by the Scrum Master.
1640
+
-[ ] They are optional. Attendance is only required when the Product Owner gets invited by the Scrum Master.
1641
1641
-[x] Their attendance is mandatory. The Sprint Retrospective is an opportunity for the Scrum Team to assess and improve itself.
0 commit comments