Test your basic knowledge |

Subject : it-skills
Instructions:
  • Answer 22 questions in 15 minutes.
  • If you are not ready to take this test, you can study here.
  • Match each statement with the correct term.
  • Don't refresh. All questions and answers are randomly picked and ordered every time you load a test.

This is a study tool. The 3 wrong answers for each question are randomly chosen from answers to other questions. So, you might find at times the answers obvious, but you will see it re-enforces your understanding as you take the test each time.
1. A short meeting held daily by each Team during which the Team members inspect their work - synchronize their work and progress and report and impediments to the ScrumMaster for removal. Follow-on meetings to adapt upcoming work to optimize the Sprint






2. Complete as mutually agreed to by all parties and that conforms to an organization's standards - conventions - and guidelines. When something is reported as "done" at the Sprint Review meeting - it must conform to this agreed definition.






3. A complete slice of the overall product or system that could be used by the Product Owner or stakeholders if they chose to implement it.






4. The trend of work remaining across time in a Sprint - a Release - or a Product. The source of the raw data is the Sprint Backlog and the Product Backlog - with work remaining tracked on the vertical axis and the time periods (days of a Sprint - or Sp






5. A period of time that cannot be exceeded and within which an event or meeting occurs. For example - a Daily Scrum meeting is time boxed at fifteen minutes and terminates at the end of fifteen minutes - regardless. For meetings - it might last shorter






6. The number of hours that a Team member estimates remain to be worked on any task. This estimate is updated at the end of every day when the Sprint Backlog task is worked on. The estimate is the total estimated hours remaining - regardless of the numb






7. Someone exercising one of the three Scrum roles (Team - Product Owner - ScrumMaster) who has made a commitment and has the authority to fulfill it.






8. Not an acronym - but mechanisms in the game of rugby for getting an out-of-play ball back into play.






9. A list of tasks that defines a Team's work for a Sprint. The list emerges during the Sprint. Each task identifies those responsible for doing the work and the estimated amount of work remaining on the task on any given day during the Sprint.






10. Someone with an interest in the outcome of a project - either because they have funded it - will use it - or will be affected by it.






11. The person responsible for the Scrum process - its correct implementation - and the maximization of its benefits.






12. The person responsible for managing the Product Backlog so as to maximize the value of the project. The Product Owner is responsible for representing the interests of everyone with a stake in the project and its resulting product.






13. A cross-functional group of people that is responsible for managing themselves to develop an increment of product every Sprint.






14. One of the tasks that the Team or a Team member defines as required to turn committed Product Backlog items into system functionality.






15. Product functionality that is developed by the Team during each Sprint that is potentially shippable or of use to the Product Owner's stakeholders.






16. A time boxed three-hour meeting facilitated by the ScrumMaster at which the complete Team discusses the just-concluded Sprint and determines what could be changed that might make the next Sprint more enjoyable or productive.






17. Someone who is interested in the project but does not have formal Scrum responsibilities and accountabilities (Team - Product Owner - ScrumMaster).






18. A time-boxed four hour meeting at the end of every Sprint where the Team collaborates with the Product Owner and stakeholders on what just happened in the Sprint. This usually starts with a demonstration of completed Product Backlog items - a discuss






19. An iteration - or one repeating cycle of similar work - that produces increment of product or system. No longer than one month and usually more than one week. The duration is fixed throughout the overall work and all teams working on the same system






20. Functional requirements - non-functional requirements - and issues - prioritized in order of importance to the business and dependencies and estimated. The precision of the estimate depends on the priority and granularity of the Product Backlog item






21. A prioritized list of requirements with estimated times to turn them into completed product functionality. Estimates are more precise the higher an item is in the Product Backlog priority. The list emerges - changing as business conditions or technol






22. A one-day meeting time boxed to eight hours (for a four week Sprint) that initiates every Sprint. The meeting is divided into two four-hour segments - each also time boxed.. During the first four hours the Product Owner presents the highest priority