plugg7, plugg6, plugg5, plugg4, plugg2, plugg

186. Refactoring is a key way of preventing technical debt. - True - False

True Comment: The key to managing technical debt is to be constantly vigilant, avoid using shortcuts, use simple design, and refactor relentlessly.

253. No one, not even the Scrum Master, tells the development team how to build the product. • True • False

True Comment: 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.

112: A visual control used in Lean software development to represent the velocity of business solutions delivered over time is a: - Business Value Delivered - Chart - Burndown Chart - Cumulative Flow Diagram - Burn up chart

Business Value Delivered

267. How long is the Sprint Planning meeting? • 4 hours • 8 hours • Depends on the length of the Sprint • 3 hours

Depends on the length of the Sprint Comment: The duration of the Sprint planning meeting varies based upon Sprint length. For a one month Sprint, the planning meeting is 8 hours, two hours per week of Sprint.

214. Incremental delivery means: • Deliver non-functional increments in the iteration retrospectives • Release working software only after testing each increment • Improve and elaborate our Agile process with each increment delivered • Deploy functional increments over the course of the project

Deploy functional increments over the course of the project

94. Technical debt is the total amount of less-than-perfect _________ in your project. -Defects -Design and implementation decisions -Code commenting -Code sharing

Design and implementation decisions

140. When we use the term "container" in Scrum what are we referring to? - A Sprint or Iteration - Source code repository - Development team room - A vertical slice of functionality

A Sprint or Iteration Comment: A container is a closed space where things can get done, regardless of the overall complexity of the problem. In the case of Scrum, a container is a Sprint, an iteration.

339. This role champions the products, provides the budget and supports the Scrum Master in removing impediments. • Subject Matter Expert • Product Owner • Business Owner • Project Manager

Business Owner

254. The development team should have a lead developer to ensure the work is properly executed. • True • False

False Comment: The Scrum Team is cross-functional and self-organizing. There is no lead developer.

357. Operations and Maintenance staff should not be part of the Agile team. • True • False

False Comment: The approach of DevOps suggests that Operations and Maintenance staff should be incorporated into Agile Teams.

252. The Product Owner does not have to be a single person but may be a committee or a shared responsibility between multiple individuals. • True • False

False Comment: 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.

336. Kanban cards should always be written using User Stories. • True • False

False Comment: There are many formats for Kanban Cards. Using User Stories is just one approach.

238. With multiple Scrum teams, you should have a separate product backlog. • True • False

False Comment: There is only one product backlog when multiple Scrum teams are working on the same project.

367. It is not possible to have a fixed price contract in Agile. • True • False

False Comment: Though a time and materials contract is an easier alternative for an Agile contract, the reality is that fixed-price contracts are often necessary. In a perfect world, they should be limited to Agile discovery. If you are required to have fixed price contracts, create separate contracts for each iteration.

308. Scrum dictates the use of User Stories. • True • False

False Comment: User Stories are an Agile requirement gathering technique, but not an artifact of the Scrum framework.

87. Which of the following is not recognized as a "unit" that can be used for estimating the size of the requirements on your Agile project? - real time - relative size - ideal time - ideal size

Ideal size Comment: real time, relative size, and ideal time are all used in Agile estimating.

62. This approach includes a visual process management system and an approach to incremental, evolutionary process changes for organizations. - Kanban - Scrum - Extreme programming - Agile Unified Process

Kanban

331. The number of days needed between customer request and producton delivery is called: • Cycle time • Lead time • Ideal time • Real time

Lead time

126. Pick the one factor that is NOT part of the Agile Scaling Model. - Team size - Geographical distribution - Domain complexity - Leadership style - Organizational distribution - Technical complexity - Organizational complexity

Leadership style Comment: Leadership style is not part of Agile Scaling Model. The rest of them are.

134. When the Agile team works in a single location, the team is said to be _______. - Co-located - Distributed - Outsourced - Functional

Co-located

211. Which 5 Roles are defined by Extreme Programming? Scrum Master Coach Customer Stakeholder Programmer Tracker Product Owner Tester

Coach Customer Programmer Tracker Tester

166. What is the correct sequence of activities in release planning? - Identity features - Prioritize features - Split features using the MMF perspective - Estimate the value of the features - Estimate the cost of the features - Write stories for features - Create release plan by date or scope

- 1 Identity features - 2 Prioritize features - 3 Split features using the MMF perspective - 4 Estimate the value of the features - 5 Estimate the cost of the features - 6 Write stories for features - 7 Create release plan by date or scope

167. Sequence the following concepts to create the popular acronym for creating good User Stories. - Independent - Negotiable - Valuable - Estimable - Small - Testable

- 1 Independent - 2 Negotiable - 3 Valuable - 4 Estimable - 5 Small - 6 Testable

189. Sequence the activities that occur in a Retrospective meeting. - Set the Stage - Gather Data - Generate Insights - Decide What We Do - Close the Retrospective

- 1 Set the Stage - 2 Gather Data - 3 Generate Insights - 4 Decide What We Do - 5 Close the Retrospective

130. How do you read a burndown bar chart? Match the phrases below to create instructions. (Left) As tasks are completed When tasks are added to the original set. When tasks are removed from the original set When the amount of work Involved in a task changes (Right) The top of the bar is lowered The bottom of the bar is lowered The bottom of the bar is raised. The top of the bar moves up or down

- As tasks are completed / The top of the bar is lowered - When tasks are added to the original set / The bottom of the bar is lowered - When tasks are removed from the original set / The bottom of the bar is raised. - When the amount of work Involved in a task changes / The top of the bar moves up or down

122. The 3 items are requires for an Agile, adaptive environment: - People - Process - Product - Tools - Technology

- People - Process - Product Comment: People, Process, Product are requires for an Agile, adaptive environment.

120. Identify the three components of the Agile Triangle. - Quality - Value - Cost - Constraints - Scope - Leadership

- Quality - Value - Constraints

131. What are the three components of an Agile Project Charter? - Success Criterias - Vision - Objectives - Scope - Mission - Risks

- Success Criterias - Vision - Mission

368. Match the traditional contract model on the top with the Agile alternative on the bottom. -Analysis, design, development and testing occur sequentially -No value delivered until the entire project has been completed -There is no attempt to control the order in which the requirements are tackled. -Success is measured by reference to conformance with the plans. -Changes 'controlled' by means of the change control mechanism. *There is concurrent design and development. *Value delivered at the end of every Sprint. *The highest risk and highest value items are tackled first. *Success is measured by conformance reference to the realization of the desired business outcomes. *Change is accommodated within the non-contractual product backlog.

-Analysis, design, development and testing occur sequentially *There is concurrent design and development. -No value delivered until the entire project has been completed *Value delivered at the end of every Sprint. -There is no attempt to control the order in which the requirements are tackled. *The highest risk and highest value items are tackled first. -Success is measured by reference to conformance with the plans. *Success is measured by conformance reference to the realization of the desired business outcomes. -Changes 'controlled' by means of the change control mechanism. *Change is accommodated within the non-contractual product backlog.

132. Match each activity (on the left) to its definition (on the right). (Left) -Communication -Coordination -Cooperation -Collaboration (Right) -A slide presentation by the Product Owner to stakeholders -The developer submits code for testing. The UX designer checks that the developer implemented the elements correctly. -The Product Owner adjusts some story priority to meet the dependency of another team. -Pair programming.

-Communication / A slide presentation by the Product Owner to stakeholders -Coordination / The developer submits code for testing. The UX designer checks that the developer implemented the elements correctly. -Cooperation / The Product Owner adjusts some story priority to meet the dependency of another team. -Collaboration / Pair programming.

124. While managing the Agile Product Lifecycle, match the frequency with which you update the five Agile plans. (Left) 1. Product Roadmap 2. Sprint Plan 3. Daily Plan (Scrum) 4. Release Plan 5. Product Vision (Right) A. Semi-Annually by The Product Owner B. Each iteration by the team C. Daily by the individual D. Quarterly by the Product Owner and teams E. Annually by Product Owner

1. Product Roadmap A. Semi-Annually by The Product Owner 2. Sprint Plan B. Each iteration by the team 3. Daily Plan (Scrum) C. Daily by the individual 4. Release Plan D. Quarterly by the Product Owner and teams 5. Product Vision E. Annually by Product Owner

299. How long is the time-box for the daily Scrum? • It depends • 5 minutes per person on the Development Team • 15 minutes • Whatever the Team decides

15 minutes

165. Based on the following information, determine the number weeks until the next release. Length of Sprint = 2 weeks Velocity of team = 35 points Number of story points assigned to minimum marketable features (MMF) = 280 points - 8 weeks - 12 weeks - 16 weeks - 9 weeks

16 weeks Comment: 16 weeks. 280 points divided by 35 points of velocity = 8 Sprints. 8 Sprints of 2 weeks = 16 weeks.

143. The PM Declaration of Interdependence is a set of six management principles initially intended for project managers of Agile software development projects. Match the item numbers and letters below to identify the principles. 1. We deliver reliable results 2. We expect uncertainty 3. We boost performance 4. We improve effectiveness and reliability 5. We unleash creativity and innovation 6. We increase our return on investment A. By engaging customers in frequent interactions & shared ownership B. And manage for it through iterations, anticipation & adaptation C. Through group accountability for results & shared responsibility for team effectiveness D. Through situationally specific strategies, processes & practices E. By recognizing that individuals are the ultimate source of value F. By making continuous flow of value our focus

1A: We deliver reliable results / By engaging customers in frequent interactions & shared ownership 2B: We expect uncertainty / And manage for it through iterations, anticipation & adaptation 3C: We boost performance / Through group accountability for results & shared responsibility for team effectiveness 4D: We improve effectiveness and reliability / Through situationally specific strategies, processes & practices 5D: We unleash creativity and innovation / By recognizing that individuals are the ultimate source of value 6E: We increase our return on investment / By making continuous flow of value our focus

57. The best description of the Sprint backlog is: - daily progress for a Sprint over the Sprint's length - a prioritized list of tasks to be completed during the project - a prioritized list of requirements to be completed during the Sprint - a prioritized list of requirements to be completed for a release

A prioritized list of requirements to be completed during the Sprint.

240. Which of the following does NOT describe Scrum? • Simple to understand • A lightweight framework • Difficult to master • A process or a technique for building products

A process or a technique for building products Comment: Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques.

99. Setting up development work in a way that the team can figure out what to do next is called: -A pull system -Push system -Critical path -Sprint backlog

A pull system

313. What happens if all the necessary testing doesn't occur in a Sprint? • The user Story is moved to the next Sprint • Additional testers are added in the next Sprint • A risk of not creating a potentially shippable product occurs • The burndown chart is updated

A risk of not creating a potentially shippable product occurs

208. A reminder for the developer and Product Owner to have a conversation is: • The Sprint planning meeting • Backlog grooming • A User Story • An Agile reminder

A user story

161. Which of the following is an example of an information radiator? - An email of a status report - A text of a quick question to the Product Owner - A whiteboard showing the statement of work - A face-to-face conversation

A whiteboard showing the statement of work Comment: Whiteboards showing state of work. An information radiator is a large, highly visible display used by software development teams to track progress.

98. A technique in which a team collaboratively discusses acceptance criteria and then distills them into a set of concrete tests before development begins is called: -Feature driven development (FDD) -Acceptance test driven development (ATDD) -Test driven development (TDD) -User story workshops

Acceptance test driven development (ATDD)

341. Match the following roles on the bottom to the RASCI on the top: Accountable Consulted Informed Supportive Responsible Product Owner Subject Matter Experts Stakeholders & Business Owner Scrum Master Team Members

Accountable / Product Owner Consulted / Subject Matter Experts Informed / Stakeholders & Business Owner Supportive / Scrum Master Responsible / Team Members

129. When reading a burn-down chart, what does each status measurement say about project performance? Match the items below. (Left) Actual Work Line is Above the Ideal Work Line Actual Work Line is Below the ideal Work Line Actual Work Line is On the Ideal Work Line (Right) Behind Schedule Ahead of Schedule On Schedule

Actual Work Line is Above the Ideal Work Line / Behind Schedule Actual Work Line is Below the ideal Work Line / Ahead of Schedule Actual Work Line is On the Ideal Work Line / On Schedule

323. Pick the two PMLC models that are based upon the Agile Project Management (APM) approach: • Linear • Adaptive • Incremental • Iterative

Adaptive

123. What is the name of this facilitated process? One or more team members sequence the product backlog from smallest to largest User Story. The rest of the team validates the sequence. The whole team uses a sizing method such as T-shirt size or Fibonacci sequence to group the user stories. - Relative estimation - Pairwise comparison - Planning Poker - Affinity estimating

Affinity Estimating

147. When is the best time to perform Earned Value Measurement (EVM) in Agile Projects? - After the iteration - After a release - During an iteration - Never - we don't perform EVM in Agile

After the iteration Comment: Typically, in Agile EVM, a measure of performance on an Agile project is performed after the iteration.

348. Which of the following frameworks has the following practices? - Supports an envision, explore, adapt culture. - Supports a self-organizing, self-disciplined team. - Promotes reliability and consistency to the extent possible given the level of project uncertainty. - Provides management checkpoints for review. • Dynamic Systems Development Method (DSDM) • Crystal Clear • Feature Driven Development (FDD) • Agile Delivery Framework.

Agile Delivery Framework.

325. This management approach is based on knowing well defined goals but not the means for a solution. • Traditional Project Management • Emertxe Project Management • Extreme Project Management • Agile Project Management

Agile Project Management

371. Similar to inspect and adapt in Scrum, this can be represented as Build, Measure, Learn. • Six sigma • Kaizen • DMAIC • Agile learning cycle

Agile learning cycle Comment: Learning cycles assume that we are continually engaging in iterative cycles of learning where doing is connected to observing to reflecting to improving and then repeating. In Agile, this can be represented as Build, Measure, Learn.

322. Based upon this Burndown Chart, is this project ahead of schedule or behind schedule? End of Week 2 / 40 Story Points Complete 70----------------------------------- 60---------#*----------------------- 50-------------*--------------------- 40-------------#-------------------- 30-------------------#-------------- 20-------------------*-------------- 10------------------------#--------- 0 ----------------------------#---- ===Week==0===1===2===3===4 * Actual # Velocity

Ahead of Schedule

222. What of the following is not a step in the Value Stream Mapping process? • Define the current state • Collect data • Amplify Learning • Depict the future state • Develop an implementation plan

Amplify Learning Comment: Amplify Learning is a Lean development principle.

78. During Sprint planning, the architect is constantly estimating higher than everyone else, and team members are increasing their estimates to accommodate her. This is an example of: -Dominating -Influencing -Dictating -Anchoring

Anchoring. Comment: anchoring is when people hear a number and if that number is not relevant, it still seems to influence their estimates.

247. A cross-functional team in Scrum consists of which types of team members? • A specialist In QA • An architect • A release manager • Anyone with the skills to accomplish the work

Anyone with the skills to accomplish the work Comment: Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team.

356. Match the story types on the top to their definition on the bottom: (Type) A rchitecturally Significant Analysis Infrastructure Spike (Definition) Stories are functional Stories that cause the team to make architectural decisions Stories that are created to find other stories. Stories to improve the infrastructure the team is using. Stories that figure out answers to tough technical or design problems.

Architecturally Significant -Stories are functional Stories that cause the team to make architectural decisions Analysis -Stories that are created to find other stories. Infrastructure -Stories to improve the infrastructure the team is using. Spike -Stories that figure out answers to tough technical or design problems.

289. How often should Development Team members change? • No more than every three Sprints • Never • Each Sprint • As needed

As Needed Comment: Team members come and go for a variety of reasons outside of anyone's control. Each time someone leaves there will be a short-term reduction in productivity.

297. If a customer really wants a feature added to a Sprint, how should the Development Team respond? • Add the feature into the current Sprint backlog • Escalate to the Scrum Master • Add the item to the Product Backlog for prioritization in the next Sprint • Ask the Product Owner to work with the customer

Ask the Product Owner to work with the customer Comment: The Development Team should ask the Product Owner to work with the customer to resolve the issue.

245. When does Adaptation occur in Scrum? • At the Sprint Review • During Sprint Planning • In the daily Scrum • At all four Scrum events • As Part of the Sprint Retrospective

At all four Scrum events

236. Based upon this Burndown Chart of weeks, is this project ahead of schedule or behind schedule? End of Week 1, 10 Story Points Complete 70------------------------------- 60----*-#----------------------- 50--------\-#------------------- 40-----------*------------------- 30--------------*----------------- 20-----------------*------------- 10---------------------\---------- 0 -------------------------*----- =====W0===1==2=3======4 * Velocity # Actual

Behind Schedule Comment: If the actual line is above the velocity line, the Burndown chart shows that the project is behind schedule.

255. The optimum size of the Scrum Team is: • 7 • Between 3 and 9 • 5 • It depends

Between 3 and 9 Comment: Less than 3 may not be an efficient team and greater than 9 makes coordination difficult. Any number in within the range of 3-9 is acceptable.

91. Which of these statements is not correct about ideal time and calendar time? -Ideal time is the time that is actually required to complete the work -Both of them convey the same meeting -Calendar time is the amount of time that passes on the clock (calendar days) -Normally calendar days are not equal to ideal days

Both of them convey the same meeting. Comment: ideal time is not the same as calendar time. Calendar is the available duration to complete work whereas ideal time is the time required to complete the work.

296. If the Sprint Backlog cannot be completed in a Sprint, who resolves the issue? • Product Owner • Scrum Master • Development Team • Both the Product Owner and Development Team

Both the Product Owner and Development Team Comment: The Development Team and the Product Owner collaborate to determine the impact on the Sprint Backlog.

104: The trend of work remaining across time in a Sprint, a release, or a product, with work remaining tracked on the vertical axis and the time periods tracked on the horizontal axis is called a ______ • Burndown Chart • Burnup Chart • Progress Chart • Parking Lot Chart

Burndown Chart Comment: A Burndown Chart tracks work remaining on the vertical axis and the time periods on the horizontal axis.

223. At completion of iteration planning, the team has finished identifying the tasks they will commit to for the next iteration. Which of the following tools best provides transparency into the progress throughout the iteration? • Burndown chart • Gantt chart • Hours expended chart • Management baseline chart

Burndown chart Comment: A Sprint Burndown chart will show work completed and working remaining throughout the iteration.

358. Which of the following is NOT a metric that measures the performance of DevOps in Agile? • Release date adherence percentage • Defects attributable to platform/support requirements • Percentage of NFRs met • Business value realized per release • Percentage increase in the number of releases

Business value realized per release Comment: Business value metrics are attributed to the business and are captured by the product owner and business owner, not DevOps.

328. Which of the following is weakness of an Adaptive PMLC Model? • Does not waste time on non-value-added work • Does not waste time planning uncertainty • Cannot identify what will be delivered at the end of the project • Avoids all management issues processing scope change requests

Cannot identify what will be delivered at the end of the project

262. All of the following are true about change during a Sprint EXCEPT: • Changes that can be made that impact the Sprint goal • The development team can change tasks in the Sprint backlog • The Product Owner is the only person that can add or remove a User Story in the Sprint Backlog • Change may occur as scope is clarified between the Product Owner and the Development Team

Changes that can be made that impact the Sprint goal Comment: Changes that impact the Sprint Goal are not allowed. The other listed changes are allowed.

242. Which of the following is NOT part of the Scrum Framework? • Roles • Events • Characteristics • Artifacts

Characteristics Comment: The Scrum framework consists of Scrum Teams and their associated roles, events, artifacts, and rules.

324. Which of the following is NOT a characteristic of an Adaptive PMLC Model? • Iterative Structure • Clear up front requirements • Mission Critical Projects • JIT Planning

Clear up front requirements Comment: Adaptive models have minimal information at the beginning of the project.

369. What is the Japanese business philosophy focused on making constant improvements? • Shu-Ha-Ri • Sashimi • Aikido • Kaizen

Kaizen

137. Suppose you are a Scrum Master on a new Agile team. Which of the following strategies is best way to resolve conflict on the team? - Collaborate - Negotiate - Smooth over - Ignore - Use your authority

Collaborate Comment: Collaborate is a formal term for resolving conflict on a team.

133. In XP, the practice that any developer can change any line of code to add functionality, fix bugs, improve designs, or refactor demonstrates: - Collective Code Ownership - Source Code Control - Pair Programming - Continuous Integration

Collective Code Ownership

148. Emotional intelligence includes all of the following except: - Self-awareness - Motivation - Commitment - Influence - Intuitiveness - Conscientiousness

Commitment Comment: The 7 elements of emotional awareness are: Self awareness; Emotional resilience; Interpersonal sensitivity; Motivation; Influence; Intuitiveness, and Conscientiousness

125. What are the 5 values of Agile Modeling? - Communication, Simplicity, Feedback, Courage, Humility - Communication, Efficiency, Transparency, Courage, Humility - Communication, Simplicity, Feedback, Adaptation, Continuous Improvement

Communication, Simplicity, Feedback, Courage, Humility

139. Which of the following is NOT one of the 5 common conflict types? - Compensation anxiety - Lack of role clarity - Difference in prioritizing tasks - Working in silos - Waiting on completion of task dependencies - Lack of communication

Compensation anxiety Comment: Compensation anxiety is not a conflict type. The rest of the list are the common types of conflict.

361. The definition of an Epic can be written using the acronym CURB. What does CURB stand for. • Create/update/replace/big • Compound/unknown/risky/basic • Complicated/unusual/really big • Complex/unknown/risky/big

Complex/unknown/risky/big

128. The ultimate goal of ___________ is to deploy all but the last few hours of work at any time. - Continuous Integration - Collective Code Ownership - Synchronous Builds - Asynchronous Builds

Continuous Integration

229. Which of the following is NOT a principle from the Agile Manifesto? • Our highest priority is to satisfy the customer through early and continuous delivery of valuable hardware. • Business people and developers must work together daily throughout the project. • Continuous creation of technical debt and good design enhances agility. • Working software is the primary measure of progress.

Continuous creation of technical debt and good design enhances agility. Comment: Continuous creation of technical debt and good design enhances agility is NOT a principle of the Agile Manifesto. The real one is, "continuous attention to technical excellence and good design enhances agility".

141. Prioritize from high to low the sequence of User Story development - High-value, high-risk stories - High value, low-risk - Lower-value, low-risk - Low-value, high-risk

Correct order: - High-value, high-risk stories - High value, low-risk - Lower-value, low-risk - Low-value, high-risk

355. CRUD is an acronym that defines a way to split stories. What does CRUD stand for? • Create/update/delete • Capture/replace/update/define • Create/review/update/done • Create/replace/update/define

Create/update/delete

58. This Agile methodology focuses on efficiency and habitability as components of project safety. - Scrum - Kanban - Extreme Programming - Crystal Clear

Crystal Clear

347. This Agile methodology's properties include Focus, Osmotic Communication and Project Safety. • Scrum • Crystal Clear • Extreme Programming • Kanban

Crystal Clear Comment: The Crystal family of methodologies focuses on efficiency and habitability as components of project safety. Crystal Clear focuses on people, not processes or artifacts.

334. The following is a picture of which of the following Information Radiators? (NOT ABLE TO DISPLAY IMAGE) - Burndown chart - Kanban Tracking System - Cumulative Flow Diagram - Burnup Chart

Cumulative Flow Diagram

111. In Kanban, a diagram that describes the overall flow and provides a measurement for every significant step in the workflow is the: - Kanban board - Cumulative Flow diagram - Burn Down chart - Parking Lot Chart

Cumulative Flow diagram

230. Which chart shows the total number of story points completed through the end of each iteration? • Iteration Burndown chart • Cumulative story point Burndown chart • Daily Burndown chart • Burnup chart

Cumulative story point Burndown chart Comment: A cumulative story point burndown chart shows the total number of story points completed through the end of each iteration.

246. Who is NOT part of the Scrum Team? • Product Owner • Scrum Master • Customer • Development Team

Customer Comment: The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. The customer is not part of the Team.

330. The number of days needed between feature specification and production delivery is called: • Cycle time • Calendar time • Ideal time • Real time

Cycle Time

142. The number of days needed between feature specification and production delivery is called: - Cycle time - Real time - Ideal time - Calendar time

Cycle time Cycle time is the number of days needed between feature specification and production delivery.

107: During which meeting do team members synchronize their work and progress and report and impediments to the Scrum Master for removal? • Sprint Planning meeting • Daily Scrum • Sprint Retrospective • Weekly Status meeting

Daily Scrum

207. Match the time box to the Scrum meeting for a one month Sprint. Daily Scrum Sprint Review Sprint Planning Sprint Retrospective 15 min 4 hrs 8 hrs 3 hrs

Daily Scrum, 15 min Sprint Review, 4 hrs Sprint Planning, 8 hrs Sprint Retrospective, 3 hrs

364. Which of the following is not part of Agile Discovery? • Document business outcomes that are quantifiable and measurable • Outline a plan for the technical and business architure/design of the solution • Describe essential governance and organization aspects of the project and how the project will be managed • Define the tasks that the team will perform during an iteration

Define the tasks that the team will perform during an iteration Comment: Agile Discovery occurs before the project begins. Task planning occurs with the team during iteration planning.

241. Scrum is NOT: • A set of software project management principles • Founded on empirical process control theory, or empiricism • A process framework used to manage the development of products • Designed for static requirements

Designed for static requirements Comment: Scrum is intended for use with adaptive requirements not static requirements.

101: The acronym for a good product backlog is DEEP. What does it stand for? • Detailed Appropriately, Emergent, Estimated, and Practical • Detailed Appropriately, Emergent, Estimated and Prioritized • Descriptive, Emergent, Estimated, and Prioritized • Detailed appropriately, Exact, Estimated, and Prioritized

Detailed Appropriately, Emergent, Estimated and Prioritized

225. The purpose of a Sprint Retrospective is from the Scrum Team to: • Review stories planned for the next Sprint and provide estimates • Demonstrate completed User Stories to the Product Owner • Determine what to stop doing, start doing, and continue doing • Individually provide status updates on the User Stories in progress

Determine what to stop doing, start doing, and continue doing

237. Which of the following occurs in the first Sprint? • Create a project plan • Develop a shippable piece of functionality • Complete your reference architecture • Develop the Product Roadmap

Develop a shippable piece of functionality

96. Which type of estimation refers to splitting a story into smaller and easier to manage pieces? -Expert opinion -Analogy -Disaggregation -Bottom up

Disaggregation

346. Which Agile enterprise framework adopts and tailors methods such as Scrum, Extreme Programming (XP), and Agile Modeling (AM) in order to support scaling. • Disciplined Agile Delivery (DAD) • Agile Delivery Framework (ADF) • DSDM • Crystal

Disciplined Agile Delivery (DAD) Comment: Disciplined Agile Delivery DAD adopts and tailors proven strategies from existing methods such as Scrum, Extreme Programming (XP), Agile Modeling (AM), Unified Process (UP), Kanban, Outside-in software development, and Agile Data (AD).

145. The way that we calculate the number of years it takes to break even from undertaking a project which also takes into account the time value of money is the: - Pay-back period - Discounted pay-back period - NPV - Cumulative cash flow

Discounted pay-back period Comment: In contrast to an NPV analysis, which provides the overall value of a project, a discounted payback period gives the number of years it takes a break even from undertaking the initial expenditure.

135. Teams of members working in different physical locations are called: - Co-located Teams - Distributed Teams - Outsourced Teams - Global Teams

Distributed Teams

75. Suppose eight new members joined the development team, and the team size is now 15. The daily scrum is getting noisy and exceeding the 15 minute time box. What is the most effective way to address this situation? -Divide the team into two teams with minimum dependency and have two separate daily scrums -Do nothing. Allow the large team to exceed the time box by a few minutes each meeting -Increase the time box for the daily scrum to 30 minutes -Ask the team members to only update on the impediments and highlight only the important ones

Divide the team into two teams with minimum dependency and have two separate daily scrums. Comment : the real problem is the team size. The best way to address it is to split the teams with minimal interdependencies and conducted two separate daily scrums.

146. DRY is an acronym for which Agile development principle? - Development Requires You - Don't Repeat Yourself - Deploy Repeatedly - Development, Refactor, Yagni

Don't Repeat Yourself Comment: The DRY (Don't Repeat Yourself) Principle states: every piece of knowledge must have a single, unambiguous, authoritative representation within a system.

363. Which development mastery model of skill acquisition lies in helping the teacher understand understand how to assist the learner in advancing to the next level? • Shu-Ha-Ri • Kaizen • Rickman • Tuckman • Dreyfus

Dreyfus

54. Which of the following describes the roles in pair programming? - pilot and the navigator - driver and the navigator - coder and the planner - leader and the second chair

Driver and the navigator Comment : the programmer at the keyboard is usually called the driver, the other person, also actively involved in the programming task but focusing more on overall direction is the navigator.

216. Which Agile method goes through the following stages: 1a.the Feasibility Study 1b.The Business Study 2.Functional Model 3.System Design and Build Iteration 4.Implementation • Rational Unified Process (RUP) • Feature Driven Development (FDD) • Dynamic Systems Development Method (DSDM) • Lean Software Development • Scrum

Dynamic Systems Development Method (DSDM)

172. Match a definition (on the top) to a Lean principle (on the bottom). Eliminate waste Create knowledge Build quality in Defer commitment Optimize the whole Deliver fast / Create nothing but value Maintain a culture of constant improvement Refactor - eliminate code duplication to zero Schedule irreversible decisions at the last responsible moment Focus on the entire value stream Limit work to capacity

Eliminate waste Create nothing but value Create knowledge Maintain a culture of constant improvement Build quality in Refactor - eliminate code duplication to zero Defer commitment Schedule irreversible decisions at the last responsible moment Optimize the whole Focus on the entire value stream Deliver fast Limit work to capacity

286. What type of process control is Scrum? • Empirical • Inspection • Adaptive

Empirical Comment: Scrum is an empirical process since it provides control through frequent inspection and adaptation for processes.

171. Which one is NOT a level of need in the Kano Model? - Basic needs - Performance needs - Enabling needs - Excitement needs

Enabling needs Comment: Different categories of customer satisfaction in the Kano model include basic needs, performance needs, and excitement needs.

218. Which one is not a value of Lean Development? • Pursue perfection • Ensure collective code ownership • After a project flows, keep improving it • Balance long-term improvement and short-term improvements

Ensure collective code ownership Comment: Collective code ownership is an XP principle.

127. What are the 5 phases of the Agile Project Management (APM) delivery framework? - Envision, Speculate, Explore, Adapt, Close - Elaborate, Speculate, Examine, Adapt, Close - Envision, Enable, Explore, Enhance, Close

Envision, Speculate, Explore, Adapt, Close

151. Bugs reported by the customer that have slipped by all software quality processes are represented in this metric. - Technical debt - Escaped defects - Risk burndown - Code quality

Escaped defects

209. Wideband Delphi is used by an Agile Project Manager to support what activity? • Prioritization • Scheduling • Estimation • Risk Management

Estimation Comment: The Wideband Delphi estimation method is a consensus-based technique for estimating effort.

228. In the Kano Model of customer satisfaction this type of feature makes a product unique from its competitors and contributes 100% to positive customer satisfaction: • Excitement • Performance • Must-have • Threshold

Excitement Comment: Excitement attributes are for the most part unforeseen by the customer but may yield the most satisfaction.

113: Suppose the current release will be complete after 6 two-week iterations. A team member is insisting that the Product Owner write the acceptance test cases for the entire release. How should the Scrum Master respond? - Since the release duration is not very long, agree with the idea and explain the advantage of doing this to Product Owner - It's up to the team and Product Owner to determine if it is a good idea - Explain that stories should only be discussed in detail prior to development. Elaborating stories not in the next couple of iterations is wasteful. - Decide to dedicate first Sprint to elaborating all the stories.

Explain that stories should only be discussed in detail prior to development. Elaborating stories not in the next couple of iterations is wasteful. Comment: Making decisions at the last possible moment is a key Agile concept. Detailed acceptance criteria should wit to be created until the iteration in which they will be needed.

152. Testing that often occurs between "Done" and "Done, Done" is: - Exploratory testing - Acceptance testing - Unit testing - Test driven development

Exploratory testing Comment: Exploratory testing, unscripted manual testing, is typically done after all of the development iterations are complete and are being made ready for production, sometimes called, "Done, Done".

115. Which of the following testing is done manually by the XP team? - Regression testing - Unit testing - Integration testing - Exploratory testing

Exploratory testing Comment: In XP, all testing tasks are automated. The only manual testing an XP team might perform is exploratory testing.

114. Suppose your team is working to create a commercial website and is in the process of developing User Stories by role. One team member suggests rather than only thinking about the target user, we should also think of some exceptional users who use the system very differently. What type of user is this team member referring to? - High Risk User - Admin Role - Extreme Persona - Performance Tester

Extreme Persona Comment: An extreme persona is a team-manufactured user that is strongly exaggerated in order to elicit requirements that are non-standard.

195. Which Agile method promotes the practice of risk-based Spike or Spike solutions? - Scrum - AgileUP - ADSM - Extreme Programming

Extreme Programming Comment: Spikes, another invention of XP are a special type of story used to drive out risk and uncertainty in a user story or other project facet.

212. Simple Design, Pair Programming, Test Driven Development, Design Improvement are all practices of which Agile Methodology? • Scrum • Feature Drive Development (FDD) • Extreme Programming (XP) • Dynamic Systems Development Method (DSDM) • Crystal Clear • Rational Unified Process (RUP) • Agile Unified Process

Extreme Programming (XP)

92. Which of the following is not an extreme programming practice? -Pair programming -Planning game -Test driven development -Extreme persona

Extreme persona Comment: an extreme persona is a user modeling technique not specifically attributed to XP.

221. Pick which 3 activities are the responsibilities of the Scrum Master in Scrum. Provides estimates Prioritizes the backlog Commits to the Sprint Performs user acceptance Facilitates meetings Champions Scrum Volunteers for tasks Makes technical decisions Remove impediments

Facilitates meetings Champions Scrum Remove impediments

365. Agile Analysis is a phase in the lifecycle of an Agile project. • True • False

False Comment: Agile Analysis isn't a phase in the lifecycle of your project. It is an ongoing and iterative activity.

204. Agile development prevents technical debt. • True • False

False Comment: Agile development does not prevent technical debt. Technical debt is often more prevalent in Agile due to the urgency to "ship" the software.

288. There must be a release every Sprint. • True • False

False Comment: Each Sprint should create a shippable piece of functionality, but is up to the Product Owner when to release.

282. If there are multiple Scrum teams working on a product, each needs its own definition of Done. • True • False

False Comment: If there are multiple Scrum Teams working on the same product, they each need the same definition of "done".

303. In Scrum, the development team decides which events or ceremonies tale place during a Sprint. • True • False

False Comment: In Scrum, ALL events take place. "Failure to include any of these events results in reduced transparency and is a lost opportunity to inspect and adapt."

136. On Agile teams, conflict is to be avoided at all cost. - True - False

False Comment: Innovation occurs only with the free interchange of conflicting ideas, a phenomenon that was studied and documented by Hirotaka Takeuchi and Ikujiro Nonaka, the godfathers of Scrum.

354. Non-functional requirements should be written as user stories whenever possible. • True • False

False Comment: NFRs don't have to be written s User Stories. Instead they are often part of the Definition of Done or part of the Acceptance Criteria.

177. Pareto Analysis is the exercise of determining what 40% of functionality can be delivered with 60% of the effort. - True - False

False Comment: Pareto Analysis is the exercise of determining what 80% of the functionality can be delivered with 20% of the effort.

309. Scrum is a software development methodology. • True • False

False Comment: Scrum is a process control methodology and is not used only for software development projects.

283. To truly adopt a Scrum, you must pick and choose what roles, artifacts, events, and rules are right for your organization. • True • False

False Comment: Scrum's roles, artifacts, events, 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.

269. No one but the Scrum Team attends the Sprint Planning meeting, • True • False

False Comment: The Development Team may also invite other people to attend in order to provide technical or domain advice.

326. This Emertxe Project Management (MPx) approach is when neither a goal nor solution is defined. • True • False

False Comment: The Emertxe Project Management approach is when the solution is well defined, however, the goal is not defined.

275. The Product Backlog is baselined at the start of the project and not changed for at least three Sprints. • True • False

False Comment: The Product Backlog is reviewed during each Sprint and updated if necessary.

256. The Product Owner and Scrum Master are never part of the Development Team. • True • False

False Comment: The Scrum Master and Product Owner can be part of the Development Team if they can help create the product.

263. The Scrum Team and Development Team are the same thing. • True • False

False Comment: The Scrum Team includes the Development Team, Scrum Master and Product Owner.

163. Match each Agile requirement type (on the left) to its definition (on the right). (Left) Feature User Story Story Task (Right) Business solution, capability, or enhancement that ultimately provides value to the business. Describes the interaction of the users with the system. Any requirement that is NOT a User Story (e.g. technical enabling, analysis, reminder to have conversation) Fundamental unit of work that must be completed to make a progress on a Story

Feature / Business solution, capability, or enhancement that ultimately provides value to the business. User Story / Describes the interaction of the users with the system. Story / Any requirement that is NOT a User Story (e.g. technical enabling, analysis, reminder to have conversation) Task / Fundamental unit of work that must be completed to make a progress on a Story

79. Traditional project management uses the work breakdown structure to develop requirements in terms of activities. What type of breakdown structure is used in Agile for this purpose? -Feature breakdown structure -Product roadmap -Product breakdown structure -Sprint backlog

Feature breakdown structure Comment: a feature breakdown structure is an Agile artifact that displays the backlog of features for each release of the Agile project.

180. Personas are used in Agile requirements to depict which type of user? - Real users - Fictitious users - Super users - Beta testers

Fictitious users

181. When is Planning Poker used? - During backlog prioritization - As part of Pareto Analysis - During User Story sizing and estimating - As part of the Daily Stand-up

Fictitious users Comment: Planning Poker ® is a consensus-based estimating technique. Planning Poker can be used with story points ideal days, or any other estimating unit.

158. Team members who are part-time on your project will see at least a 15% reduction in their productivity per hours. This type of resource model in Agile is called: - Co-located - Fractional assignments - Distributed resources - Over-allocated resources

Fractional assignments Comment: Fractional Assignments impact team productivity. Team members who are part-time on your project will see at least a 15% reduction in their productivity per hour.

249. When does Inspection occur? • Throughout the Sprint • Only at the end of the Sprint • Whenever the Product Owner wishes • Frequently, but not so often that it gets in the way of work

Frequently, but not so often that it gets in the way of work Comment: Inspection occurs frequently, but only enough to detect variances in the work.

81. Suppose you are performing integrated testing on each of the different product increments developed during an iteration to ensure that the increments work together as a whole. What type of iteration is this? -A hybrid iteration -Hardening iteration -Heuristic iteration -Handoff Iteration

Hardening iteration

72. An iteration prior to a release that includes final documentation, integration testing, training and some small tweaks is called: -Hardening iteration -Buffer iteration -Release iteration -Integration iteration

Hardening iteration. Comment: a hardening iteration is used for readying the product for production.

305. If the Development Team does not have all the skills to accomplish the Sprint Goal, the Scrum Master should: • Cancel the Sprint • Stop using Scrum • Have the development team determine the definition of "Done" and work through the Sprint backlog • Remove the impacted stories from the Sprint backlog

Have the development team determine the definition of "Done" and work through the Sprint backlog Comment: The Development Team needs to self-organize to determine what can be accomplished with the team members it has; they develop the additional skills over time to improve the definition of Done.

93. On XP teams, what is expected from the project manager? -Coach the team on agile practices -Help the team work with the rest of the organization -Provide domain expertise to the team -Define the software

Help the teamwork with the rest of the organization

118. An iteration takes place in a time frame with specific start and end dates called a time-box. Which of the following is NOT an advantage of time-boxing? - Establishes a WIP limit - Forces prioritization - Demonstrates progress - Helps control technical debt

Helps control technical debt Comment: Establishing a WIP limit, forcing prioritization, and demonstrating progress are all advantages of time-boxing.

194. In what order do you select requirements to work on in a risk adjusted backlog? - High Risk High Value - Low Risk High Value - Low Risk Low Value - High Risk Low Value

High Risk High Value 1 Low Risk High Value 2 Low Risk Low Value 3 High Risk Low Value 4 Comment: The order is as listed above exactly, top to bottom.

97. The ___________ the technical debt means the _______ the intrinsic quality? -Higher, higher -Higher, lower -Lower, lower -Lower, higher

Higher, lower Comment: the higher the technical debt means the lower the intrinsic quality.

343. Which role is external to the Scrum Team but provides a skill that does not exist on the Team? • Subject Matter Expert • Team Member • Scrum Mater • Project Manager

Subject Matter Expert

160. What type of estimation excludes non-programming time? - Ideal time - Calendar time - Duration - Real time

Ideal time. Comment: Ideal Time excludes non-programming time. When a team uses Ideal Time for estimating, they are referring explicitly to only the programmer time required to get a feature or task done, compared to other features or tasks.

159. Frequent verification and validation is key in Agile but each approach produces a very different result. Verification determines ______ whereas Validation determines _________. - If the product is "done" / if the product is "done-done" - If I am building the product right / if I am building the right product - If I am building the right product / if I am building the product right - If the product has passed unit testing / if the product has passed acceptance testing

If I am building the product right / if I am building the right product

360. Your project management office (PMO) has suggested your project could benefit from self-assessment work at the next retrospective. Which of the following benefits would they most likely be looking to achieve from a self-assessment? • Assess compatibilities for pair programming assignments • Improve personal and team practices • Identify personal traits for human resources counseling • Gain insights for salary performance reviews

Improve personal and team practices Comment: The benefits would they most likely be looking to achieve from a self-assessment would be to improve personal and team practices.

284. When was Scrum first introduced? • In 2001 with the Agile Manifesto • In 1995 at a conference presentation • At General Electric as part of a Lean approach • In 2000 along with Extreme Programming

In 1995 at a conference presentation

261. Put the following in order of first occurrence in a Sprint. • Sprint Planning • Daily Scrum • Sprint Review • Sprint Retrospective

In order as shown. • Sprint Planning • Daily Scrum • Sprint Review • Sprint Retrospective

350. Sequence the steps to User Story. • Product Roadmap Definition • User Story Definition • User Story Decomposition • Release Planning

In order as written • Product Roadmap Definition • User Story Definition • User Story Decomposition • Release Planning

338. Order the 5 focusing steps of the Theory of Constraints. • Identify the System Constraint • Decide How to Exploit the Constraint • Subordinate Everything Else • Elevate the Constraint • Go back to Step 1, Repeat

In order as written: • Identify the System Constraint • Decide How to Exploit the Constraint • Subordinate Everything Else • Elevate the Constraint • Go back to Step 1, Repeat

353. In what order do you select requirements to work on in a risk adjusted backlog? • Low Risk High Value • High Risk High Value • Low Risk Low Value • High Risk Low Value

In order as written: • Low Risk High Value • High Risk High Value • Low Risk Low Value • High Risk Low Value

329. Sequence the core practices of Kanban in order of execution. • Visualize the workflow • Limit WIP • Manage the flow • Make the process policies explicit • Implement Feedback Loops • Improve collaboratively

In order as written: • Visualize the workflow • Limit WIP • Manage the flow • Make the process policies explicit • Implement Feedback Loops • Improve collaboratively

168. Match the definitions (on the top) to each of the characteristics of a good User Story (on the bottom): Independent Negotiable Valuable Estimable Small Testable / Stories can be worked on in any order A story is not a contract If a story does not have discernable value it should not be done A story has to be able to be sized so it can be properly prioritized User Stories average 3-4 days of work Each story needs to be proven that it is "done"

Independent Stories can be worked on in any order Negotiable A story is not a contract Valuable If a story does not have discernable value it should not be done Estimable A story has to be able to be sized so it can be properly prioritized Small User Stories average 3-4 days of work Testable Each story needs to be proven that it is "done"

321. Scrum users must frequently review Scrum artifacts and progress toward a Sprint Goal to detect undesirable variances. Which pillar of Scrum does this represent? • Transparency • Inspection • Adaptation

Inspection

121. There are four critical actions that should be embraced by an adaptive leader: improving speed-to-value, having a passion to quality, doing less, and ________ - Inspiring staff - Managing conflict - Facilitating meetings - Ensuring effective communication

Inspiring staff

162. Assuming all projects require the same amount of up-front investment, the project with the highest _______ would be considered the best and undertaken first. - Earned Value Management (EVM) - Internal Rate of Return (IRR) - Net Present Value (NPV) - Budget at Completion (BAC)

Internal Rate of Return (IRR) Comment: Generally speaking, the higher a project's internal rate of return (IRR), the more desirable it is to undertake the project.

215. When we practice active listening, what are the levels through which our listening skills progress? • Global listening, Focused listening, Intuitive listening • Interested listening, Focused listening, Global listening • Self-centered listening, Focused listening, Intuitive listening • Internal listening, Focused listening, Global listening

Internal listening, Focused listening, Global listening

370. Which of the following is an Agile improvement technique to address issues continuously, e.g. after daily stand-up? • Retrospectives • Verification sessions • Intraspectives • Futurespectives

Intraspectives Comment: Intraspectives: Discussions within the Sprint to address issues. Typically as a result of issues raised during the daily Scrum.

71. The sprint retrospective: -Is intended to promote continuous process improvements -Is held at the end of each release -Is conducted to provide the sponsor with key information on team progress -Is optional

Is intended to promote continuous process improvements.

157. Which of the following is NOT a reason to use a Feature Breakdown Structure (FBS) instead of a Work Breakdown Structure (WBS)? - It allows communication between the customer and the development team in terms both can understand. - It allows you to baseline your project plan due to absence of change. - It allows tracking of work against the actual business value produced. - It allows the customer to prioritize the team's work based on business value.

It allows you to baseline your project plan due to absence of change Comment: A Feature Breakdown Structure does not allow you to baseline your project plan due to absence of change. That is a use of the Work Breakdown Structure in traditional project management.

295. How long is a Sprint Review? • 2 hours • 4 hours • It depends on the length of the Sprint

It depends on the length of the Sprint Comment: A Sprint Review is 4 hours for a full month Sprint, but less if the Sprint is shorter.

290. What is a time-boxed event? • It happens at the same time as a conflicting task • It has a maximum duration • It has a minimum duration • It has a fixed place and time

It has a minimum duration

116. Which of the 2 attributes of Exploratory testing? - It involves minimum planning and maximum test execution - It is typically automated - It is unscripted testing - It is often the sole testing technique

It involves minimum planning and maximum test execution, AND It is unscripted testing Comment: Exploratory testing is manual unscripted testing that has a minimum of planning but a high amount of execution. It is often done in conjunction with other testing.

174. What is the Agile Open Space concept? - When cubicle walls are removed for an Agile team - It is a meeting designed to allow Agile practitioners to meet in self-organizing groups where they can share their latest ideas and challenges - The choice to collocate all team members for the beginning of a project - It is a core principle of ADSM

It is a meeting designed to allow Agile practitioners to meet in self-organizing groups where they can share their latest ideas and challenges

144. All of the following are attributes of the definition of "done" EXCEPT: - It is a static artifact - It is an audible checklist - It is a primary reporting mechanism for team members on User Story progress - It is crucial to high performing teams

It is a static artifact Comment: The Definition of Done is not static. It should be improved over time.

66. Which statement is least accurate when providing a definition of "Done"? -It is the exit criteria to determine whether a product backlog item is complete - It may very depending on the project - It is defined by the Scrum Master - It becomes more complete overtime

It is defined by the scrum master . Comment: the definition of "done" is defined by the development team and the product owner, not the scrum master.

63. Which following statement is the least accurate regarding the burn down chart? - it is calculated using hours or points - it is updated by the development team daily - it provides insight into the quality of the product - it reflects work remaining

It provides insight into the quality of the product . Comment: the burn down chart does not measure quality. It measures work completed and work remaining.

89. Agile project management and product development uses several types of documents specific to each iteration; they are known as "artifacts". All of the following documents are Agile iteration artifacts except: -Iteration vision statement -Iteration backlog -Iteration plan -Iteration burn down chart

Iteration vision statement Comment: the iteration vision statement is not an iteration artifact. Product vision statements are created and updated annually.

310. If the Development Team doesn't like the time of the daily Scrum, what should the Scrum Master do? • Find a time that is open on everyone's calendar • Let the Development Team come up with a new time • Ask the Team to try the existing time for one Sprint • Tell them that Scrum is immutable and that they need to stick to it

Let the Development Team come up with a new time Comment: Let the Development Team come up with a new time since they are self-organized.

76. While developing a story during the iteration, team discovered new tasks that were not identified earlier. Newly discovered task is such that the user story cannot be completed during the iterations. What is the most appropriate action for the team to perform? -Let the product owner decide if there is still a way to meet the iteration goals -Discuss the situation with the scrum master and see if there is still a way to meet the iteration goals -Drop the user story and inform the product owner that it will be delivered in the next iteration -Modify the scope of other user stories to allow completion of the Sprint backlog

Let the product owner decide if there is still a way to meet the iteration goals. Comment: let the product owner decide if there is still a way to meet the Sprint goal. The Owner may choose to reduce the functionality of a story or drop one entirely.

138. Match the response options to each level of conflict. (Left) Level 1: Problem to Solve Level 2: Disagreement Level 3: Contest Level 4: Crusade Level 5: World War (Right) -Collaboration or consensus -Support & safety -Accommodate, negotiate, get factual -Establish safe structures again -Do whatever is necessary

Level 1: Problem to Solve / Collaboration or consensus Level 2: Disagreement / Support & safety Level 3: Contest / -Accommodate, negotiate, get factual Level 4: Crusade / -Establish safe structures again Level 5: World War / -Do whatever is necessary

88. Extreme Programming (XP) defines four basic activities that are performed during the software development process. These include designing, coding, testing and ______________? -Collaborating -Leveling -Communicating -Listening

Listening Comment: one of the four basic activities of XP is listening to the customer and also to other development team members.

67. All of the following are among the seven principles of the Lean approach with the exception of: -Amplified learning -Decide as late as possible -Build integrity in -Maximize the work performed

Maximize the work performed

61. Simplicity-the art of ________________ -is essential. - maximizing the amount of work not done - minimizing the amount of work not done - maximizing the customer collaboration - minimizing contract negotiation

Maximizing the amount of work not done. Comment : Agile Manifesto Principle - simplicity: the art of maximizing the amount of work not done is essential.

226. Question: Which of the following BEST describes ROTI? • Measure of product backlog items (PBI) remaining • Measure of quality of features delivered in an iteration • Measure of required effort to complete an iteration • Measure of the effectiveness of the retrospective meeting

Measure of the effectiveness of the retrospective meeting Comment: Return on Time Investment (ROTI) is used to measure the effectiveness of the retrospective meetings from the team members' perspective.

155. Which of the following is NOT one of the 12 core practices of XP: - Pair Programming - Collective Code Ownership - 40-hour work week - Minimize waste

Minimize waste Comment: Minimize Waste is a Lean principle

217. What is a Japanese term used in Lean software development is an activity that is wasteful, unproductive, and doesn't add value? • Sashimi • Kanban • Muda • Kairoshi

Muda

235. DSDM uses MoSCoW technique to create the prioritized requirements list. In MoSCoW technique, 'M' stands for: • Most useful • Must have • Must not have • Minimum marketable feature

Must have Comment: MoSCoW is an acronym for: Must Have, Should Have, Could Have, Won't Have

187. Which Agile estimation technique is based upon relative sizing? - Ideal time - Bottom up - Story points - Little's law

Story points Comment: Story points are relative values that do not translate directly into a specific number of hours.

74. At the end of the first iteration, the team finishes user stories A, B and 50% of C. What is the team velocity? The story sizes were: Story A equals eight points Story B equals one point Story C equals five points Story D equals three points -11.5 -9 -14 -16

Nine Comment : stories are either done or not done. There is no concept of an unfinished story or 50% complete.

294. Who is responsible for the Project Plan and Gantt Chart in Scrum? • Project Manager • Scrum Master • Product Owner • No Scrum role

No Scrum role Comment: There is neither a project manager nor Gantt Charts in Scrum.

85. When implementing Agile project management, risk management that occurs simply by following Agile best practices such as iterative planning and review activities is called: -Inherent risk management -Organic risk management -Overt risk management -Intrinsic risk management

Organic risk management

277. Which item is NOT an attribute of the Product Backlog? • Description • Order • Estimate • Value • Owner

Owner Comment: Owner is not an attribute of the Product Backlog; all the other items are.

164. 80% of the value comes from 20% of the work. Which law is this referring to? - Parkinson's Law - Moore's Law - Pareto's Law - Jevon's Paradox

Pareto's Law Comment: Pareto's Law is commonly known as the 80/20 rule. This means that typically 80% of your results come from only 20% of your efforts.

176. The 80 / 20 rule is also known as what law? - Little Law - Pareto's Law - Mohr's Law - The Law of Averages

Pareto's Law Comment: The Pareto principle (also known as the 80 / 20 rule, the law of the vital few, and the principle of factor sparsity) states that, for many events, roughly 80% of the effects come from 20% of the causes.

178. The length of time to recover the cost of a project investment is the: - Net Present Value - Payback Period - Earned Value - ROI

Payback Period

179. An archetypal user of a system is called a(n): - Super user - Admin - Persona - UX engineer

Persona

153. Which of the following is NOT one of the 12 core practices of XP: - The Planning Game - Planning Poker - Small Releases - System Metaphor

Planning Poker Comment: AF: Planning Poker is an Agile estimating technique.

349. Which of the following is NOT a prioritization technique? • User Story Mapping • Kano analysis • Minimally Marketable Features (MMF) • Kitchen Prioritization • Planning Poker

Planning Polker

170. The Kano Model supports what Agile planning activity? - Estimation - Prioritization - Sizing - Continuous integration

Prioritization Comment: The Kano model is an effective technique to prioritize the product backlog by customer satisfaction.

332. Class of Services in Kanban are used to: • Support estimation for Kanban Cards • Prioritize the queue by risk • All of the above • Ensure WIP limits are realistic

Prioritize the queue by risk Comment: Classifying classes of services are typically priorities defibed based on business impact and cost of delay.

220. Pick which 4 activities are the responsibilities of the Product Owner in Scrum. Provides estimates Prioritizes the backlog Create User Stories Commits to the Sprint Performs user acceptance Facilitates meetings Champions Scrum Perform release planning Design software

Prioritizes the backlog Create User Stories Performs user acceptance Perform release planning

198. On a risk map or a risk heat nap, the vertical and horizontal axes represent: - Effort and impact - Probability and impact - Probability and exposure - Impact and exposure

Probability and impact

73. Analyzing the current organizational processes, project requirements, and making needed process changes is called: -Value stream mapping -Release planning -Use case development -Process tailoring

Process tailoring Comment: process tailoring takes an organization's standard process definition and tailors it to the specific needs of the project.

318. What Scrum event or artifact is the single source of requirements for any changes to be made to the product? • Product Backlog • Sprint Backlog • Sprint • Scrum • Working Product Increment

Product Comment: The Product Backlog is an order 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.

108: Who is responsible for change management in Scrum projects? • Project Manager • Project Sponsor • Scrum Master • Product Owner

Product Owner

276. Who is responsible for ordering the Product Backlog? • Senior Executives • The Product Owner • The Scrum Master • The Development Team

Product Owner

280. Who tracks work remaining in the Product Backlog? • The Development Team • The Scrum Master • The Product Owner • Senior Executives

Product Owner

233. What Agile planning artifact should be updated at minimum semi-annually? • Product Vision • Product Roadmap • Release Plan • Sprint Plan • Daily Plan

Product Roadmap Comment: The Product Roadmap should be update at least twice a year by the Product Owner.

65. This artifact contains release names with expected dates and includes major features, client side impacts, server-side applications, platform support and markets served: -Risk burn down graph -Product roadmap -Release migration plan -Product vision

Product roadmap

80. The Agile artifact that describes the incremental nature of how the product will be built and delivered over time, along with the important factors that drive each individual release is called: -Product vision statement -Product wireframe -Product roadmap -Product team

Product roadmap

232. What Agile planning artifact is updated minimally once a year by the Product Owner? • Product Vision • Product Roadmap • Release Plan • Sprint Plan • Daily Plan

Product vision Comment: The Product Vision is updated annually by the Product Owner and stakeholders.

213. Which of the following is not an Agile methodology? • Scrum • Feature Drive Development (FDD) • Extreme Programming (XP) • Dynamic Systems Development Method (DSDM) • Program Evaluation Review Technique (PERT) • Crystal Clear • Rational Unified Process (RUP) • Agile Unified Process

Program Evaluation Review Technique (PERT) Comment: Program Evaluation Review Technique (PERT) is a traditional project management scheduling technique All of the others are Agile techniques.

184. Which is the process of continuously improving and detailing a plan as more detailed and specific information and more accurate estimates become available as the project progresses? - Process Tailoring - Pareto Analysis - Progressive Elaboration - Open Space Planning

Progressive Elaboration

219. Pick 5 activities that are the responsibilities of the development team in Scrum. Provides estimates Prioritizes the backlog Create User Stories Commits to the Sprint Performs user acceptance Facilitates meetings Champions Scrum Volunteers for tasks Makes technical decisions Designs software

Provides estimates Commits to the Sprint Volunteers for tasks Makes technical decisions Designs software

103: Which type of risk analysis does an Agile team use to identify risks on their project? • Risk Burndown Chart • Pareto Analysis • Qualitative Risk Analysis • Quantitative Analysis

Qualitative Risk Analysis Comment: Qualitative analysis uses judgment, intuition, and experience in determining risks and potential losses.

83. All of the following are metrics used in Agile except: -Real-time -Velocity -Escaped defects -Cycle time

Real-time. Comment: velocity, escaped defects, and cycle time are all metrics that are used in Agile project management. Real-time is an Agile estimation "sizing unit" that refers to the actual time during each day that the team members are available and are productively working on specific agile project tasks.

102: Which of the following is NOT a characteristic of an Agile plan? • Follows rolling wave planning approach • Are top down • Easy to change • Shows dependencies of one task to others

Shows dependencies of one task to others Comment: Showing dependencies of one task on others is not a characteristic of an Agile plan.

90. In Sprint planning, the development team estimates user stories provided by the product owner and agrees to ones that can be completed in the Sprint. This is an example of: -Osmotic communication -Reciprocal commitment -Universal acceptance -Tacit agreement

Reciprocal commitment Comment: this is an example of reciprocal commitment, where the development team commits to delivering the specified functionality according to the definition of done and the product owner agrees not to change the priorities during the Sprint.

185. What is a change made to the internal structure of software to make it easier to understand and cheaper to modify without changing its observable behavior? - Pair programming - Continuous improvement - Test driven development - Refactoring

Refactoring

117. A change made to the internal structure of software that makes it easier to understand and cheaper to modify but does not change its observable behavior is: - A spike - Technical debt - A User Story - Refactoring

Refactoring Comment: Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the cost yet improves its internal structure.

300. How does the Scrum Master provide the most value to the Team? • By facilitating discussions between the Product Owner and the Development Team • Ensuring time-boxes are kept • Removing impediments to the Development Team • Scheduling Scrum events

Removing impediments to the Development Team

197. Which artifact is useful for seeing total project risk increasing or decreasing over time? - Burndown bar chart - Risk Burn-Up chart - Risk Burndown Graph - Risk map

Risk Burndown Graph

227. What Agile concept expresses delivering value in slices rather than in layers/stages? • Definition of Done • Value Mapping • Sashimi • Lean Value

Sashimi

317. What Scrum event or artifact supports daily inspection and adaptation? • Product Backlog • Sprint Backlog • Sprint • Scrum • Working Product Increment

Scrum Comment: The Development Team uses the daily Scrum to inspect progress toward the Sprint Goal and to inspect how progress is trending toward completing the work in the Sprint Backlog.

274. Match the following top to bottom items: (Top) Scrum Event Scrum Artifact Scrum Role Not Scrum (Bottom) Daily Scrum Product Backlog Product Owner Gantt Chart

Scrum Event / Daily Scrum Scrum Artifact / Product Backlog Scrum Role / Product Owner Not Scrum Gantt Chart

70. The best architectures, requirements, and designs emerge from: -Hand-picked teams -Co-located teams -Self organizing teams -Cross functional teams

Self organizing teams. Comment: Agile Manifesto Principle - the best architectures, requirements, and designs emerge from self organizing teams.

51. On an Agile team, the project leader works to remove impediments from blocking the team's progress. This is known as what type of leadership? - Servant - Command and control - Consensus-driven - Functional management

Servant

199. The Project Leader's primary responsibilities are to "move boulders and carry water." What is this an example? - Servant leadership - Leadership by example - Command and control leadership - The leadership metaphor

Servant leadership

362. The Japanese terms for an Agile developmental mastery model are: • Kaizen • Mud • Muda • Sashimi • Shu-Ha-Ri

Shu-Ha-Ri Comment: Shu-Ha-Ri is an Agile development mastery model taken from Japanese martial arts.

84. Alistair Cockburn created the Crystal family of Agile methods, all of those names contain colors of quartz crystals taken from geology. What two characteristics of an Agile project are used to determine the color of the Crystal method? -Size and complexity -Duration and complexity -Size and criticality -Duration and criticality

Size and criticality Comment: Crystal comes from Alistair Cockburn's characterization of projects along the two dimensions of "size" (meaning the size of the project team) and "criticality" (meaning the damage that will be caused if the developed product or system fails).

105: Which list below includes the attributes of a good User Story? • Small, estimable, independent, negotiable • Testable, estimable, renewable, valuable • Negotiable, small, explainable, valid • Valuable, estimable, dependent, small

Small, estimable, independent, negotiable Comment: INVEST in good User Stories. (Independent, Negotiable, Valuable, Estimable, Small, Testable)

59. A time-boxed period to research a concept and/or create a simple prototype is called a(an): -Sprint -Iteration -Spike -Retrospective

Spike

188. What kind of User Story is written to provide an opportunity to research a solution in order to provide an estimate? - Sprint story - Persona story - Spike story - Needle story

Spike story

319. What Scrum event or artifact is the set of items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal? • Product Backlog • Sprint Backlog • Sprint • Scrum • Working Product Increment

Sprint Backlog Comment: 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.

234. What Agile planning artifact is created by the Product Owner and the development team? • Product Vision • Product Roadmap • Release Plan • Sprint Plan • Daily Plan

Sprint Plan Comment: The Sprint Plan is created by the Product Owner and the Development Team.

316. Match the activity (on the top) to the Scrum event (on the bottom). Sprint Planning Sprint Retrospective Daily Scrum Sprint Review Sprint Goal creation Adapt the definition of "Done" Inspect and adapt Demonstrate Functionality

Sprint Planning / Sprint Goal creation Sprint Retrospective / Adapt the definition of "Done" Daily Scrum / Inspect and adapt Sprint Review / Demonstrate Functionality

315. Match each of the following items with its associated time-boxed duration for a one-month Sprint. Sprint Review Sprint Retrospective Sprint Planning Sprint Daily Scrum 4 hours 3 hours 8 hours 1 month 15 minutes

Sprint Review / 4 hours Sprint Retrospective / 3 hours Sprint Planning / 8 hours Sprint / 1 month Daily Scrum / 15 minutes

190. Triple Nickels is a technique used in what kind of meeting? - Sprint planning - Daily scrum - Sprint retrospective - XP planning game

Sprint retrospective Comment: Triple Nickels is a Sprint Retrospective technique. It is a brainstorming approach where it is very easy to have everyone express their thoughts which encourage everybody to be attentive to what others think.

106: The Agile Manifesto principle, "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software," is achieved through which Scrum practice? • Daily Scrum • Sprints • Release Planning • Sprint Planning

Sprints Comment: Sprints which are no longer than one month and often shorter promote continuous delivery to the customer.

193. Which is NOT one of the 5 common risk areas mitigated by Agile. - Intrinsic schedule flaw - Specification breakdown - Scope creep - Stakeholder apathy - Personnel loss - Productivity variation

Stakeholder apathy Comment: The book Waltzing with Bears list the 5 common risk areas as: 1) Intrinsic Schedule Flaw 2) Specification Breakdown 3) Scope Creep 4) Personnel Loss 5) Productivity Variance

77. Suppose your team velocity is eight story points, and the product backlog items are ordered by priority as shown below. If you are in a sprint planning meeting and need to commit to the user stories for the next iteration, which ones will you select? Story one equals three story points Story two equals four story points Story three equals three story points Story four equals one story point -Story one, two, and three -Story one, two, and four -Story one and two -Story two, three and four

Story one, two, and four Comment: stories one, two, four - the team only commits to their velocity. They are allowed to take a lower priority story in order to meet their target velocity.

202. Which XP practice promotes the restriction on overtime? • Sustainable Pace • Pair Programming • Servant Leadership • Small Releases

Sustainable Pace Comment: Sustainable pace suggests working no more than 40 hours a week, and never working overtime a second week in a row.

340. The behavior where the Scrum Team focuses on one or more stories until they are done is called: • Collaboration • Swarming • Pair-programming • Sprinting

Swarming

100. What Agile development approach is being used when the whole team works towards solving a complex problem? -Swarming -Norming -Performing -Collaborating

Swarming. Comment: swarming is when the whole team works towards solving a complex problem.

200. In XP, what is the practice of creating a story about a future system that everyone - customers, programmers, and managers - can tell about how the system works? • Extreme persona • Wireframe • System metaphor • Simple Design

System metaphor Comment: Kent Beck, author of Extreme Programming Explained defines a system metaphor as" "a story that everyone - customers, programmers, and managers - can tell about how the system works."

203. What is the Agile term for the time period when some or all of the following occur: beta testing, regression testing, product integration, integration testing, documentation, defect fixing. • Spike • Code Freeze • Tail • Lag

Tail

359. Which of the following is NOT a KPI (key performance indicator) of Agile? • Actual stories completed vs. Committed stories • Quality delivered to customers • Team enthusiasm • Team attendance • Team velocity • Technical debt management

Team attendance Comment: Team Attendance is not a KPI of Agile. Agile teams are self-managing so less focus is spent on micro-managing time in the office, etc.

224. A common reason a story may not be estimable is the: • Team lacks domain knowledge • The story did not include a role • Developers do not understand the tasks related to the story • Team has no experience in estimating

Team lacks domain knowledge Comment: There are three common reasons why a story may not be estimable: 1) Developers lack domain knowledge 2) Developers lack technical knowledge 3) The story is big

205. In Agile development, what is the term for the internal things that you choose not to do now, knowing they will impede future development if left undone? • Escaped defects • Verification and validation results • Technical debt • Intrinsic quality

Technical debt Comment: Technical Debt is the development that you choose not to do now, knowing that it will impede future development if left undone.

56. Continuous attention to _______________ and good design enhances agility . - best architectures - technical excellence - robust plans - change control

Technical excellence Comment: Agile Manifesto principle - continuous attention to technical excellence and good design enhances agility.

82. Which of the following is an Agile practice promoted by XP that is often used in conjunction with other Agile methods? -Dynamic systems development method (DSDM) -Feature driven development (FDD) -Adaptive software development (ASD) -Test driven development (TDD)

Test driven development Comment: test driven development (TDD), also called test driven design, is a method of software development in which unit testing is repeatedly done on source code.

110: Which of the following defines the goal of testing in Lean software development? - Testing is to improve the process and quality - Testing plays the most crucial role in ensuring the intrinsic value of the product - In Lean software development, testing always refers to Test Driven Development - Testing is primarily performed to ensure that we don't have escaped defects

Testing is to improve the process and quality Comment: In Lean software development, testing is done to improve the process and quality.

281. Who can change the Sprint Backlog during a Sprint? • Senior Executives • The product Owner • The Scrum Master • The Development Team

The Development Team Comment: Only the Development Team can change the Sprint Backlog during a Sprint. The Product Owner is responsible for the Product Backlog.

292. Who updates work remaining during the Sprint? • Senior Executives • The Product Owner • The Scrum Master • The Development Team

The Development Team Comment: The Development Team tracks this total work remaining at least for every Daily Scrum to project the likelihood of achieving the Sprint Goal.

169. At minimum, all Kanban boards should have the following columns: - To-Do, Doing, Done - Analysis, Design, Develop, Test, Deploy - Backlog, Design, Develop, Unit Test, Acceptance Test, Ready-to-Ship - The Kanban columns are determine by the team

The Kanban columns are determine by the team

257. The Scrum Master as a Servant Leader is in service to which of the following? • The Development Team • The Organization • The Product Owner and the Development Team • The Organization, the Product Owner and the Development Team

The Organization, the Product Owner and the Development Team

251. Who is responsible for maximizing the value of the product? • Senior Executives • The Product Owner • The Scrum Master • The Development Team

The Product Owner

312. Who is responsible for maximizing the value of the product backlog? • The Customer • The Scrum Master and Product Owner • The Product Owner • The Development Team and Product Owner

The Product Owner

191. Who is responsible for managing ROI in Agile projects? - The Project Sponsor - The Product Owner - The Agile Project Manager - The Scrum of Scrums Master

The Product Owner Comment: In Scrum, the product owner has full product responsibility, which includes securing funding, managing to ROI objectives, release planning and more.

265. Who can cancel a Sprint? • The Development Team • Executive Stakeholders • The Product Owner • The Scrum Master

The Product Owner Comment: Only the Product Owner has the authority to cancel a Sprint.

266. What happens if the customer no longer wants the feature that the Sprint Goal intended to meet? • The Development Team should determine if there is value in the Sprint. • The Executive Stakeholders should determine if the Sprint should continue. • The Product Owner should cancel the Sprint. • The Scrum Master should cancel the Sprint.

The Product Owner should cancel the Sprint. Comment: If the Sprint goal is no longer valid, the Product Owner may cancel a Sprint if the Sprint backlog is no longer valuable.

268. In the first part of the Sprint Planning meeting, what is NOT accomplished? • Items are selected from the Product Backlog • The Development Team decides how much work can be accomplished • The Scrum Team defines the Sprint Goal • The Tasks are identified

The Tasks are identified Comment: The Tasks are defined in the second part of the Sprint planning meeting.

239. What is the best definition of "Done"? • Whatever will please the Product Owner • It is determined by the Scrum Master • The product has passed QA and has all of the required release documentation • The definition of "Done" is one that would allow the development work to be ready for a release

The definition of "Done" is one that would allow the development work to be ready for a release Comment: The definition of "Done" is one that would allow development work to be ready for a release.

69. All of the following occur in the second half of the Sprint planning except : -The development team identifies improvements that it will implement in the next Sprint -The product owner answers questions and clarifies user stories -The development team commits to work in the Sprint -Tasks are defined for the user stories

The development team identifies improvements that it will implement in the next Sprint.

60. In Scrum, who is responsible for managing the team? - Scrum master - Project manager - Development team - Product owner

The development team. Comment : the development team is responsible for self management.

302. Who creates the Sprint Goal? • The Development Team • The Scrum Master • The Product Owner • The entire Scrum Team

The entire Scrum Team Comment: The Scrum Team consisting of the Development Team, Scrum Master, and Product Owner creates the Sprint Goal.

311. The backlog is ordered by: • The needs of the Product Owner • Risk • Complexity • Size

The needs of the Product Owner

244. What does Scrum mean by Transparency? • Users can perform code reviews at any time • Documentation is available to anyone • All team members sit in a visible location • The process is understandable by all stakeholders

The process is understandable by all stakeholders Comment: Transparency requires work be performed, documented, or presented in a common standard so observers can share a common understanding of all document artifacts and the progress of work.

231. What is the order of the hierarchy of product definition? • Product Vision • Product Roadmap • Theme • Epic • User Story • Task

Top to bottom as written • Product Vision • Product Roadmap • Theme • Epic • User Story • Task

52. Which should not take place at the daily SCRUM? - The product owner gives an update - The scrum master manages the time-box - The development team answers the three questions - Issues are raised and documented

The product owner gives an update. Comment: the product owner should not speak at the daily scrum unless they are working on a story in the Sprint backlog.

149. In a burndown chart, if the remaining work line is above the expected work line, what does this signify? - The project is ahead of schedule - The project is behind schedule - The resources are performing above expectation - The project is being well managed

The project is behind schedule

173. Net present value (NPV) is a ratio that compares the value of a dollar today to the value of that same dollar in the future. An NPV that is negative suggests what? - The project should be rejected - I don't have enough information - The project should be deferred - The project should be put on hold until the value is 0

The project should be deferred Comment: A negative NPV suggests that the project should be deferred over another project that has a positive NPV.

306. The Project Manager plays the following role in Scrum: • Collects the status from the Scrum Master • Updates the Burndown chart • Creates the release plan • There is no project manager role in Scrum

There is no project manager role in Scrum

335. The measure of productivity of a Kanban team is: • Cycle time • Lead Time • Work in Progress • Velocity • Throughput

Throughput

196. Which is NOT a reason to perform a Spike? - To perform basic research to familiarize the team with a new technology or domain - To analyze the expected behavior of a large story so the team can split the story into estimable pieces - To defer a story until a later Sprint while still showing progress to the Product Owner - To do some prototyping to gain confidence in a technological approach

To defer a story until a later Sprint while still showing progress to the Product Owner Comment: Spikes are used for different reasons: perform research, analyze a story or do prototyping to validate a design approach, not to defer the work.

53. What is the purpose of practicing asking the "5 Why's"? - to determine the scope of the Sprint - to determine the root cause of an issue - to determine the end result - to determine the prioritized backlog

To determine the root cause of an issue. Comment : 5 Why's is an iterative question asking technique used to explore the cause and effect relationships underlying a particular problem.

206. What is the purpose of running a test before you develop the code? • To complete all test cases • To ensure if it fails • To ensure it passes • To be cross functional

To ensure if it fails Comment: You run a test first to ensure it fails. If the test passes before you have written the code first then it is a flawed test.

86. One of the major tools and techniques used in Lean software development is value stream mapping. What is the primary purpose of value stream mapping? -To improve business processes -To identify and eliminate waste -To ensure product quality -To increase customer value

To identify and eliminate waste

192. The purpose of the Scrum of Scrums is to perform what function? - To increase knowledge of Agile within the organization. - To provide dashboard reporting to executives. - To manage cross-team dependencies working on the same project or product. - To ensure team building and staff development occurs.

To manage cross-team dependencies working on the same project or product. Comment: When you scale Scrum to more teams, you handle dependencies and coordination among teams working on the product with a Scrum of Scrums.

320. The Scrum Master's job is to work with the Scrum Team and the organization to increase the awareness of the artifacts. Which pillar of Scrum does this represent? • Transparency • Inspection • Adaptation

Transparency Comment: The Scrum Master must work with the Product Owner, Development Team, and other involved parties to understand if the artifacts are completely transparent.

150. Empirical process control constitutes a continuous cycle of inspecting the process for correct operation and results and adapting the process as needed. What characteristics does this apply to in Scrum? - Self organization, Collaboration, and Time-boxing - Quality, Cost and Scope - Scrums, Sprint and Releases - Transparency, Inspection, and Adaptation

Transparency, Inspection, and Adaptation

243. What are the three pillars of Scrum? • Transparency, Inspection, and Adaptation • Transparency, Inspection and Empiricism • Transparency, Acceptance and Adaptation • Retrospective, Inspection, and Adaptation

Transparency, Inspection, and Adaptation

95. ____________ an estimate refers to estimating a story based on its relationship to one or more of your stories. -Triangulating -Triaging -Aggregating -Disintegrating

Triangulating

175. Osmotic communication is when team members obtain information from overheard conversations. - True - False

True

250. The Product Owner is the sole person responsible for managing the Product Backlog. • True • False

True

259. A new Sprint starts immediately following the previous Sprint. • True • False

True

272. The feedback from the Sprint Review impacts the next Sprint planning meeting. • True • False

True

278. Backlog Grooming and Backlog Refinement are the same thing. • True • False

True

342. The product owner should spend at least 3 hours per day with the development team? • True • False

True

352. "Fail Sooner" is a benefit of of Incremental Development. • True • False

True

327. Every Project Management Life Cycle (PMLC) has a sequence of processes that include these phases: Scoping Planning Launching Monitoring & Controlling Closing • True • False

True Comment: Every valid project management life cycle must include each of these processes one more more times.

210. The purpose of Work in Progress (WIP) limits is to prevent the unintentional accumulation of work, so there isn't a bottleneck. • True • False

True Comment: One of the core properties in the Kanban method is that Work In Progress is limited. Limiting WIP is to match team's development capacity and to prevent bottlenecks.

333. The purpose of the Work In Progress (WIP) limits is to prevent the unintentional accumulation of work, so there isn't a bottleneck. • True • False

True Comment: One of the core properties in the Kanban method is that Work In Progress is limited. Limiting WIP is to match team's development capacity and to prevent bottlenecks.

182. Process Tailoring is the iterative approach implementing your SDLC process. - True - False

True Comment: Process tailoring is best done in an iterative manner: tailor some, implement some, and then repeat.

183. Product roadmaps are more accurate the closer we get to an actual release. - True - False

True Comment: Product roadmaps should be updated and made more accurate the closer we get to an actual release.

285. Scrum is a container for other techniques and methodologies. • True • False

True Comment: Scrum is a container or framework for other product development approaches, e.g. XP, TDD, etc.

248. Scrum is both an iterative and incremental Agile process. • True • False

True Comment: Scrum is both an iterative and incremental Agile process.

260. Sprints lengths can vary each Sprint as long as they don't exceed a month. • True • False

True Comment: Sprint lengths should remain a consistent length throughout a project.

264. In Scrum, Sprints are never longer than a calendar month. • True • False

True Comment: Sprints are limited to one calendar month. When a Sprint's horizon is too long the definition of what is being built may change, complexity may rise, and risk may increase.

287. The Scrum Master is a management role. • True • False

True Comment: The Scrum Master has to be a member of management to be able to remove impediments for the Development Team.

304. The Scrum Master is a participant in the Sprint Retrospectives. • True • False

True Comment: The Scrum Mater is a participant in the Sprint Retrospective.

201. What Agile requirements management approach displays a roadmap using the following approach? The horizontal axis shows a high level overview of the system under development and the value it adds to the users. The vertical axis organizes detailed stories into releases according to importance, priority, etc. • Release Planning Matrix • User Story Map • Agile Requirements Map • User Story Burndown Map

User Story Map Comment: The User Story Map presents the product roadmap with features on the horizontal axis and detailed stories ordered by priority on the vertical axis.

64. What can be described as "one or two written sentences; a series of conversations about the desired functionality ". -User story -Story point -Epic -Product roadmap

User story

119. Match each component of the Agile Triangle (on the left) to its associated description (on the right). (Left) Value Quality Constraints (Right) Releasable Product Reliable, Adaptable, Product Cost, Schedule, Scope

Value - > Releasable Product Quality -> Reliable, Adaptable, Product Constraints -> Cost, Schedule, Scope

109: The technique used to analyze the flow of information and materials through a system to eliminate waste is: - Fishbone diagramming - Flow charting - Value Stream mapping - Pareto analysis

Value Stream mapping Comment: The value stream map is a Lean tool that practitioners use to analyze the value stream.

68. Typically calculated in story points, this is the rate at which the team converts "done" items in a single Sprint: -Burn down rate -Burn up rate -Velocity -Capacity

Velocity Comment: velocity is calculated in story points. It is the rate at which the team converts "done" items in a single Sprint.

154: Which of the following is NOT one of the 12 core practices of XP: - Simple Design - Continuous Testing - Vertical Slicing - Refactoring

Vertical Slicing Comment: Vertical slicing is taking a backlog that has a database component, some business logic and a user interface and breaking it down into small stepwise progressions where each step cuts through every slice.

156. Which of the following is NOT one of the 12 core practices of XP: - Visualize the flow - On-site customer - Coding standards - System metaphor

Visualize the flow Comment: Visualize the flow is a Kanban practice.

258. Which one of the following is NOT a Scrum Event? • Sprint • Daily Scrum • Sprint Review • Weekly Status • They are all Scrum events

Weeklky Status

298. When does a Sprint get canceled or end early? • When the Sprint backlog is complete • When the Sprint Goal cannot be met • When the definition of "Done" is met • When a key resource is out sick

When the Sprint Goal cannot be met

291. When is a Sprint finished? • When the definition of "Done" is met • When the Product Owner accepts the increment • When the time-boxed duration is met • When the work remaining is zero

When the time-boxed duration is met Comment: The only time a Sprint is finished is when the time-boxed duration is met. If the team completes the Sprint backlog, the Product Owner adds more work to the Sprint.

345. Which of the following is NOT considered an enterprise Agile method? • DAD • XP • LeSS • SAFe

XP

55. Which Agile methodology runs one week iterations; leverages the use of pair programming; and includes the roles of coach, programmer, tracker, and tester? - Lean - Agile One - Scrum - XP

XP

344. Pick the 3 common Kanban Katas. • Daily Standup Meeting • Iteration Demo • Improvement Kata • Sprint Retrospective • Weekly Status • Operations Review

• Daily Standup Meeting • Improvement Kata • Operations Review

366. Pick the THREE statements that are true about Agile Analysis. • It is a highly evolutionary and collaborative process. • It occurs at the beginning and end of a project. • It only includes the project team. • It is communication rich. • It explores the problem statement.

• It is a highly evolutionary and collaborative process. • It is communication rich. • It explores the problem statement.

273. Which of the following are TRUE about the Sprint Retrospective (Choose 2) • It is three hours for a one month Sprint. • It occurs before the Sprint review. • It is an opportunity to inspect the people, relationships, process, and tools in the last Sprint • It is the only time improvements are made during a Sprint

• It is three hours for a one month Sprint. • It is an opportunity to inspect the people, relationships Comment: It occurs after the Sprint Review. This meeting is only one of the opportunities to Inspect and Adapt. The duration is three hours long for a one month Sprint.

270. Which three of the following points about the daily Scrum are TRUE? • It is time-boxed. • It is held at the same place and time every day • The Product Owner provides an update • The Scrum Master enforces the rule that only Development Team members

• It is time-boxed. • It is held at the same place and time every day • The Scrum Master enforces the rule that only Development Team members Comment: All are correct except that the Product Owner does not speak at the daily Scrum unless they have a task on a User Story.

351. Choose which three statements are true about Approved Iterations: • Meets the definition of Done • The Architect has approved it • It is communicated to all Team members and stakeholders • As a result, the Product Owner updates Roadmaps and Release Plans • There is no technical debt

• Meets the definition of Done • It is communicated to all Team members and stakeholders • As a result, the Product Owner updates Roadmaps and Release Plans

337. A term used to describe the work that can be delivered which meets the business requirements without exceeding them. (Choose Two). • Epic • Minimum Viable Product • Theme • User Story • Minimum Marketable Features

• Minimum Viable Product • Minimum Marketable Feature

293. Identify all members of a Scrum Team: • Customer • Stakeholder • Product Owner • Scrum Master • Project Manager • Development Team

• Product Owner • Scrum Master • Development Team Comment: The Scrum Team consists of the Scrum Master, Product Owner, and the Development Team.

279. Which of the following 2 statements are TRUE about Product Refinement? • Should take no more than 10% of the Development Team's time. • The Scrum Master facilitates these sessions. • Multiple Scrum Teams may participate in this process. • The Product Owner is responsible for all estimates.

• Should take no more than 10% of the Development Team's time. • Multiple Scrum Teams may participate in this process. Comment: Product refinement should take no more than 10% of the Development Team's time. The Product Owner and Development Team collaborate to refine the backlog. It should include all Scrum Teams working on a product. The Development Team is responsible for estimating.

271. Which of the following are TRUE about the Sprint Review? (Choose two). • It should be a formal presentation. • Stakeholders may attend • The Product Owner presents what backlog items are "Done" • The Scrum Master demonstrates the product.

• Stakeholders may attend • The Product Owner presents what backlog items are "Done" Comment: The Sprint Review is an informal event where the Development Team demonstrates the product. Other stakeholders may attend, and the Product Owner presents the backlog items that are Done.

314. Pick roles that support the Scrum Master in removing impediments. (Choose two) • The Development Team • Senior Management • The Product Owner • The Customer

• The Development Team • Senior Management

301. Select the statements that are TRUE about the Product Owner. (Choose two) • The Product Owner can clarify the backlog during the Sprint • The Product Owner estimates the size of the Sprint backlog • The Product Owner prioritizes the Product backlog • The Product Owner defines the Sprint Goal before the Sprint Planning meeting

• The Product Owner can clarify the backlog during the Sprint • The Product Owner prioritizes the Product backlog Comment: The Product Owner is responsible for the ordering of the product backlog and can provide clarification during the Sprint. He or she does not estimate the work, nor should they have the Sprint goal defined before the Sprint Planning meeting.

307. What is the purpose of the Sprint Review? (Choose three) • To collaborate with stakeholders • To inspect and adapt • To provide status on the Sprint • To demonstrate what is "Done"

• To collaborate with stakeholders • To inspect and adapt • To demonstrate what is "Done" Comment: Inspect and Adapt, collaborate with stakeholders, and demonstrate "Done" are performed during the Sprint Review.