Scrum Project Management

Multiple Choice

1. Which of the following most closely resembles the up-front requirements analysis process with SCRUM?
   1. Capture as many high-level statements as we can within a short period of time and then begin development.
   2. Employ user stories, time-boxing the initial analysis work and then growing the story list while developing the solution.
   3. Develop a comprehensive list of requirements and as much detail as possible before committing to development.
   4. Employ use-case analysis, supporting UML models and other artifacts. Use cases are 1 to 5 pages long as needed.
   5. None of the above.
2. How are change requests handled in an organization using SCRUM?
   1. There is a formal change control process; all changes require approval and sign-off.
   2. Change requests tend to come in constantly and be of high priority, so the developers do what they can to get them into the next release.
   3. Change requests join the Product Backlog and get prioritized along with everything else.
   4. Change requests are placed in a separate Change Request Backlog
   5. Changes always wait until the next sprint
3. How is work assigned in a Scrum team?
   1. People are given specific tasks to perform (coding, analysis, etc.) by the team leader or manager.
   2. People choose what a task to work on from the Sprint backlog.
   3. Work is not assigned. Everyone works on everything.
   4. The team votes on who should do what.
4. With the Scrum process, when significant new technical tasks are discovered and estimates change:
   1. The Product Owner re-prioritizes the backlog and the Development Team determines how work should be re-assigned.
   2. The Project Manager re-assigns tasks.
   3. The Development Team works as hard as possible to accommodate the change and get the project back on track.
   4. The current Sprint is terminated, a Sprint Planning meeting is held, and a new Sprint is started.
5. A Scrum project team consists mostly of:
   1. Generalists who can work on just about any part or section of the project.
   2. Specialists who work on specific areas of the code or within specific technologies.
   3. Chickens.
   4. Cows.
6. Scrum team communication takes places primarily through which of the following:
   1. Requirements and specifications are explicit and detailed; developers reach out to analysts with any questions; change requests and defects are logged and coordinated.
   2. Meetings are held frequently (daily or weekly) among developers, analysts and users all in the same forum to discuss requirements.
   3. People generally seek out whomever they need to see to get an answer.
   4. Team members contact the Scrum Master with issues, which are placed on the agenda for the next Scrum meeting.
7. Which of the following most closely describes the Scrum approach to managing the release plan?
   1. It is feature driven: a release will be delayed until all planned features are included.
   2. It is date driven: an incomplete feature may be omitted from the release to make sure that a working system is ready to deploy on the target release date.
   3. It is test driven: a release will be delayed until all tests have passed.
8. Planning activity with Scrum is best described as:
   1. Plan up-front, and periodically review performance of the team against the plan.
   2. Plan frequently, periodically adjusting the plan.
   3. Plan constantly, making new plans as things change.
9. What is the length of time of the typical Scrum project plan?
   1. A very short period of time, rarely more than a week or two forward.
   2. A short period of time, in detail for only a month to 6 weeks forward. Plans are high-level beyond that.
   3. A long period of time, with details mapped out for 6 months or more.
10. Which of the following best describes who is responsible for Technical Architecture with Scrum?
    1. Architecture is the purview of an architecture group.
    2. Architecture decisions are the responsibility of development teams.
    3. Architecture is determined by the customer.
    4. Architecture is jointly determined by the customer and management.
11. How often does a Scrum team create a complete build of an entire product stack?
    1. Once or more times per day.
    2. Once per week.
    3. Less than once per week.
    4. Once or less per month.
12. How frequently do Scrum developers check in changes?
    1. One or more times per day.
    2. Once per week.
    3. Only upon feature completion.
13. With Scrum, prioritization of the Product Backlog is done by ______.
    1. The ScrumMaster
    2. The Product Owner
    3. The Developers
    4. The Team
    5. The Project Manager
14. With Scrum, the final say on technical decisions belongs to _____.
    1. The ScrumMaster
    2. The Product Owner
    3. The Developers
    4. The Team
    5. The Project Manager
15. With Scrum, each individual team member is empowered to ____.
    1. Choose a task from the Product Backlog
    2. Choose a task from the Sprint Backlog
    3. Choose a task from the Release Backlog
    4. Add a task to the Sprint Backlog
    5. All of the above
16. The team assigns effort or difficulty estimates to ____.
    1. Each item on the Product Backlog
    2. Each item on the Sprint Backlog
    3. Each item on the Release Backlog
    4. All of the above
17. The velocity of the team is NOT ___.
    1. The average number of tested and debugged lines of code that a member of the team can complete per work day
    2. A metric of the team's rate of development, based on the same units used in estimating the difficulty of a user story
    3. Computed by the ScrumMaster
    4. Known to all team members
    5. Used to gauge how many user stories should be included in each sprint or iteration
18. Which of the following is the least reasonable Sprint duration?
    1. two weeks
    2. three weeks
    3. one month
    4. six months
19. Which of the following processes or methodologies use a four-phased approach (Inception, Elaboration, Construction, & Transition)?
    1. JAD
    2. Agile
    3. Waterfall
    4. UP/RUP
    5. TDD
20. Which of the following is NOT part of the Extreme Programming methodology?
    1. User stories
    2. Code units tests first, before the code they are to test
    3. Pair-programming
    4. Unified Modeling Language
    5. Continuous integration
21. Which of the following uses the mantra "If it's worth building, it's worth testing; if it's not worth testing, why are you wasting your time working on it?"
    1. Waterfall
    2. Agile
    3. Test-Driven Development (TDD)
    4. Joint Application Design (JAD)
    5. b and c
22. What type of project is the Scrum method most useful for?
    1. Small
    2. Small to Medium
    3. Medium
    4. Large
    5. a, b, and d
23. A manifesto is a public declaration of principles and intentions. Which process has a manifesto that states: "The most efficient and effective method of conveying information to and within a development team is face-to-face conversation."?
    1. Test-Driven Development (TDD)
    2. UP/RUP
    3. Agile
    4. Joint Application Design (JAD)
    5. none of the above
24. What is the most important element in a Joint Application Design (JAD) session?
    1. A great team that gets along with each other all the time
    2. A skilled facilitator
    3. Comfortable chairs to help evoke great thoughts
    4. Start bottom-up, inside/out
    5. None of the Above
25. In the Test Driven Development (TDD) environment, how much code should a developer develop prior to testing?
    1. All of the code for the project
    2. Just enough code to pass the current test and all previous tests
    3. Only enough for unit testing
    4. 100% of your regression test suite
    5. a and d
26. Which one of the following is NOT a Scrum role?
    1. Product Owner
    2. ScrumMaster
    3. Product Manager
    4. Team
27. Which one of the following is NOT a Scrum artifact?
    1. Product Backlog
    2. User Story
    3. Sprint Backlog
    4. Increment of Potentially Shippable Product Functionality
28. Which one of the following is NOT part of Scrum?
    1. Product review meeting
    2. Sprint review meeting
    3. Sprint planning meeting
    4. Sprint retrospective meeting
29. What is the duration of a sprint in Scrum?
    1. 4 weeks
    2. 28-30 days
    3. anything between 3 - 5 weeks
    4. 30 days
    5. 6 months
30. Which of the following questions is NOT relevant for regular Scrum Meeting?
    1. What have you done since the last Daily Scrum regarding this project?
    2. What will you do between now and the next Daily Scrum meeting regarding this project?
    3. Would you be able to finish your work on time?
    4. What impedes you from performing your work as effectively as possible?
31. Which one of the following is a popular certification associated with Scrum?
    1. Scrum Certified
    2. Certified Scrum Trainer
    3. Certified ScrumManager
    4. Certified ScrumMaster
32. What is a Burndown Graph?
    1. A Sprint plan which is burned to celebrate successful completion of Sprint
    2. The trend of work remaining across time in a Sprint, a release, or a product
    3. The trend of work accomplished across time in a Sprint, a release, or a product
    4. A Graph to measure human Burnout effect due to fast pace of sprint
33. Name the meeting during which the Team demonstrates to the Product Owner and any other interested parties what it was able to accomplish during the Sprint.
    1. Sprint retrospective meeting
    2. Product review meeting
    3. Sprint review meeting
    4. Stakeholder Review Meeting
34. Which one of the following is NOT a valid Scrum rule?
    1. If the Team feels itself unable to complete all of the committed Product Backlog during the Sprint, it can consult with the Product Owner on which items to remove from the current Sprint.
    2. The Team can seek outside advice, help, information, and support during the Sprint.
    3. No one can provide advice, instructions, commentary, or direction to the Team during the Sprint. The Team is utterly self-managing.
    4. If the Team determines that it can address more Product Backlog during the Sprint than it selected during the Sprint planning meeting, it can select and add new items from the product backlog.
35. Scrum is a very lean process with only _____ roles, _____ mandatory artifacts and _____ mandatory meetings apart from the daily scrum meeting in a sprint.
    1. 3,4,5
    2. 4,3,4
    3. 3,3,3
    4. 4,4,4
36. Scrum is an _____ method of software development. (Select all that are true.)
    1. Agile
    2. Iterative
    3. Incremental
    4. Spiral
    5. Waterfall
    6. Formal
37. Which of the following is NOT true of a Scrum user story?
    1. It is an abbreviated use-case description.
    2. It includes a scenario.
    3. It answers the question "Who"?
    4. It answers the questions "Does what?"
    5. It answers the question "Why?"
38. With Scrum, the prioritized list of all work to be performed on a product, including both required features and "wish-list" items, is called the
    1. Sprint backlog
    2. Shall list
    3. Product backlog
    4. Functional requirements list
39. In Scrum, the list of detailed tasks, each typically representing 4-16 hours of work, from which team members select tasks to perform is called the
    1. Shall list
    2. Task queue
    3. Product backlog
    4. Sprint backlog
40. In Scrum, a sprint burn-down chart tracks
    1. The progress of a sprint, in terms of the estimated amount of effort remaining to complete it.
    2. The progress of a sprint, in terms of the number of days remaining until the end of the sprint.
    3. The state of completion of the project, in terms of how may sprints remain to be completed.
    4. The state of the sprint, in terms of how many taks are have been started but not completed.
41. Which of the following is NOT true of the Sprint Planning Meeting?
    1. It is attended by the customers, user, management, Product Owner, and Scrum team.
    2. Its purpose is to set the goal for the sprint.
    3. Its purpose is to plan the tasks and create the sprint backlog list.
    4. It reviews the progress made on the previous sprint, and makes a list of lessons learned to be applied to the next sprint.
42. Which of the following does not apply to the daily scrum meeting?
    1. Only "pigs" may speak.
    2. The Product Owner attends.
    3. It is time-boxed to 15 minutes, and is generally held with everyone standing up.
    4. Each team member answers three standard questions.
43. Which of the following is NOT true of the Sprint Review meeting?
    1. It includes the development team, management, customers, users, and Product Owner.
    2. The development team gives a PowerPoint presentation.
    3. Incomplete work cannot be demonstrated.
    4. The team demonstrates completed work to the stakeholders.
44. Which of the following is NOT true of the Sprint Retrospective meeting?
    1. Participants try to answer the question "What went well?"
    2. Stakeholders evaluate the success of the sprint.
    3. Just the team members and the Product Owner attend.
    4. It is held immediately after the Sprint Review meeting.
45. A person who is committed to delivering the Sprint Goal is called a
    1. Scrum master
    2. Chicken
    3. Pig
    4. Stakeholder
46. Which of the following is NOT true of the Product Owner?
    1. There may be more than one.
    2. Sets the development schedule by prioritizing the Product Backlog.
    3. Participates in Sprint Retrospective meetings.
    4. Is typically the product manager, CTO, CEO, or another high-ranking stakeholder.
47. The Scrum Master is NOT responsible for
    1. Resisting the addition of new features.
    2. Running daily Scrum meetings.
    3. Assigning tasks from the Spri
    4. Assigning tasks from the Sprint Backlog to team members.
    5. Ensuring that code inspections happen.
48. ion Which of the following is NOT characteristic of a Scrum team?
    1. Members are specialized, according to function.
    2. The size may range from 5 to 9 people.
    3. Each member logs time daily, including estimated time to remaining to complete each task.
    4. Fully tests own code.
    5. Checks code into configuration management repository daily, or more often.
    6. May refactor code written by other team members.
49. Which of the following is NOT a "chicken"?
    1. Customers
    2. Managers
    3. Vendors
    4. Product Owner
    5. Consultants
50. "Planning poker" is
    1. A process in which each team member estimates the effort required to complete a task before seeing what other team members think.
    2. A process in which team members bid to see who gets to do what task from the Sprint Backlog.
    3. A process in which team members bid to determine which items from the Product Backlog go into the next Sprint Backlog.
    4. A process in which team members compete to see how many Story Points they can earn during a Sprint.