1. I acknowledge how critical is constant communication with the customer to provide rapid turnaround on their request.

2. I champion the reflection of past experience among the Project Team to learn and make improvement on the next Spring or project.

3.  I prioritize delivering the most value in each Spring, adjusting the scope when needed to preserve the Project Schedule.

4. I involve the customer feedback as early as possible, adapting each Spring to the business need,  maximizing the value delivered on each Spring.

5. My team and I continue improving by constantly learning from the past Spring, reducing time-waste, and making faster deliveries.

6. I maintain effective communication with all stakeholders, knowing how critical they are to the project’s success.

7.  __________ provides the project requirements, unscheduled requirements, and work to define and rank product features.

8. _________ is responsible for planning, tracking, meetings, mentoring, and provide problem resolutions.

9. _________  self-organizes cross-functional members that implement, test, and estimate the assignments durations.

10. _________ collaborate on defining requirements, product design, test development, and reporting of any issue founded.

11. ________ set regression tests based on business functions, processes, and acceptance criteria. Furthermore, their input help to improve upcoming Springs.

12. The voice of QAs, testers, and developers carry the same weight.

13. The following meetings are part of the Scrum Ceremonies.

14. ________ shows the amount of remaining work estimated to be completed in comparison to the planned work.

15. __________ is a type of earned-value chart that shows progress towards a goal vs. The work done toward completed requirements.

16. The “User Story” is written by the Product Owner and has the following attributes:

17. A Defect report shows the failure(s) of a product to function as intended. It is written by __________.

18. An Agile Epic is a collection of Agile Stories, a helpful way to organize the work and to create a hierarchy.

19. The “Technical Story” is written by the Team members and has the following attributes:

20. The Product Backlog Items (PBIs)  has the following required artifacts, except _________.

21. BPIs estimation includes implementation, testing, and debugging. However, these estimations are mean to be rough, no precise to save time and cost.

22. The Task Breakdown is a list of tasks required to implement a PBI.  It provides __________.

23. Task Estimation is measured in person-hours. It is done in an informal team discussion that result in an improved PBI estimation.

24.  Spring is the smallest unit of scheduled working time for a project. It should be of standard length. The three phases of a planning Sprint are ________.

25.  The _______ are the requirements not yet assigned to a Sprint, at the difference that the ________ that are requirements already assigned to a Spring.

26. Tracking answer requires knowledge of  the task’s status, delivery time, estimate effort, and its progress. The must common questions to ask are: where are we now? Where are we going? And when will we get there?

27. Task status reporting are best knowing in real-time, or at least at the end of the day. The information is necessary for billable hours and to refine the estimation process, among others functions.

28. The area Product Owner (APO) is the authority over product requirements and releases content. Their responsibilities include: