{"id":69183,"date":"2019-01-02T11:06:27","date_gmt":"2019-01-02T11:06:27","guid":{"rendered":"https:\/\/www.whizlabs.com\/blog\/?p=69183"},"modified":"2019-04-29T07:11:35","modified_gmt":"2019-04-29T07:11:35","slug":"free-pmi-acp-exam-questions","status":"publish","type":"post","link":"https:\/\/www.whizlabs.com\/blog\/free-pmi-acp-exam-questions\/","title":{"rendered":"Free PMI Agile Certified Practitioner (PMI ACP)\u00ae Exam Questions"},"content":{"rendered":"<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">Preparing for PMI Agile Certified Practitioner (PMI ACP) certification exam? Looking for some <span class=\"s2\">free PMI ACP practice questions<\/span> to help in your preparation? Here we bring the top free PMI ACP exam questions for you so that you can prepare well for the PMI ACP certification exam.<\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">PMI Agile Certified Practitioner (PMI ACP) certification exam is for the project management professionals who follow Agile principles and use Agile methodologies in their projects.<\/span><\/p>\n<p style=\"text-align: justify;\"><a href=\"https:\/\/www.whizlabs.com\/pmi-acp\/free-test\/\" target=\"_blank\" rel=\"noopener noreferrer\"><img decoding=\"async\" class=\"size-full wp-image-69302 aligncenter\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/sites\/2\/2019\/01\/pmi-acp-free-test.jpg\" alt=\"pmi acp free test\" width=\"728\" height=\"90\" srcset=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-free-test.jpg 728w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-free-test-300x37.jpg 300w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-free-test-640x79.jpg 640w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-free-test-681x84.jpg 681w\" sizes=\"(max-width: 728px) 100vw, 728px\" \/><\/a><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">With the experience of using Agile methodologies, the candidate must have some required experience such as <\/span><\/p>\n<ul class=\"ul1\" style=\"text-align: justify;\">\n<li class=\"li1\"><span class=\"s1\">1 year (or 2000 hours) of general project management experience<\/span><\/li>\n<li class=\"li1\"><span class=\"s1\">8 months (or 1500 hours) of Agile-specific project management experience, and <\/span><\/li>\n<li class=\"li1\"><span class=\"s1\">21 hours of training in Agile specific practices<\/span><\/li>\n<\/ul>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">PMI ACP certification exam recognizes and validates the expertise of the aspirants in<\/span><\/p>\n<ul class=\"ul1\" style=\"text-align: justify;\">\n<li class=\"li1\"><span class=\"s1\">Understanding the basic Agile principles and Agile methodologies<\/span><\/li>\n<li class=\"li1\"><span class=\"s1\">Implementing Agile practices and methodologies in the projects<\/span><\/li>\n<\/ul>\n<h2 class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">Practice with Free PMI ACP Exam Questions<\/span><\/h2>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">The basic educational requirement (High school diploma, Secondary degree or Associate\u2019s degree), and the required experience, you need to follow the right preparation guide and the useful resources for the <a href=\"https:\/\/www.whizlabs.com\/blog\/guide-to-prepare-for-pmi-acp\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span class=\"s2\">PMI ACP exam preparation<\/span><\/a>. <\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">Following the right preparation track is the main step in the PMI ACP exam preparation but the practicing is the final step. Mock exams help a lot in checking your preparation level, making you confident, and getting you ready for the real exam.<\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">To help you check the level of your knowledge, our subject matter experts have created a set of <a href=\"https:\/\/www.whizlabs.com\/pmi-acp\/practice-tests\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span class=\"s2\">PMI ACP practice tests<\/span><\/a>. But here we bring some of the free PMI ACP exam questions with a detailed explanation. The experts have given a detailed explanation for the correct and incorrect option as well. Try these free PMI ACP exam questions now to check the extent of your preparation for the PMI ACP Certification exam.<\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">Let\u2019s find out how many questions you can answer with your Agile knowledge and experience!<\/span><\/p>\n<blockquote><p>Give your PMI ACP preparation a new edge with this Ultimate <a href=\"https:\/\/www.whizlabs.com\/blog\/guide-to-prepare-for-pmi-acp\/\" target=\"_blank\" rel=\"noopener noreferrer\">Preparation Guide for PMI ACP exam<\/a>.<\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>1. An agile practitioner is explaining his team about the relationships between the development team and customer as well as and responsibilities of the development team and customer in agile project management. Which of the following statements is most appropriate with respect to the given?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. The customer defines value and checks the user experience, not the development team<\/p>\n<p style=\"text-align: justify;\">B. The development team sets the priority among the features, not the customer<\/p>\n<p style=\"text-align: justify;\">C. The customer determines how to perform the work, not the development team<\/p>\n<p style=\"text-align: justify;\">D. The development team determines which features should be developed first<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice A is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> In agile project management, role and responsibilities of the customer, product owner, development team or other stakeholders are clearly defined. \u00a0The initial product scope and the corresponding features are defined by the customer or their proxies like a product owner. Not only this, these features are represented in the form of user stories and these user stories are also prioritized by the customer or the product owner according to their values that indicate which story to be developed first. Now, the actual development work is on the team. It is the development team that defines how the work will be performed or what approaches and the techniques will be followed in the development process. And finally, after the development work is completed and team handovers it to the customer, it is the customer who defines value and checks the user experience, not the development team. The customer validates whether the delivered product meets the needs and expectations of the customer and the end users. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is correct.<\/b><span style=\"font-weight: 400;\"> In agile project management, values and user experience is defined and checked by the customer, not the development team. So, the option <\/span><i><span style=\"font-weight: 400;\">the customer defines value and checks the user experience, not the development team <\/span><\/i><span style=\"font-weight: 400;\">is correct.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect.<\/b><span style=\"font-weight: 400;\"> It is the customer who sets the priority among the features, not the development team. So, the option <\/span><i><span style=\"font-weight: 400;\">the development team sets the priority among the features, not the customer<\/span><\/i><span style=\"font-weight: 400;\"> is not correct.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect. <\/b><span style=\"font-weight: 400;\">In agile management, it is not the customer who determines how to perform the work rather it is the development team itself that defines how the work will be performed or what approaches and the techniques will be followed. So, the option <\/span><i><span style=\"font-weight: 400;\">the customer determines how to perform the work, not the development team<\/span><\/i><span style=\"font-weight: 400;\"> is incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect. <\/b><span style=\"font-weight: 400;\">In agile project management, the development team does not determine which features should be developed first. Rather, It is done by the customer himself. So, the option <\/span><i><span style=\"font-weight: 400;\">the development team determines which features should be developed first<\/span><\/i><span style=\"font-weight: 400;\"> is not correct.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References<\/b><span style=\"font-weight: 400;\">: Agile Practice Guide, PMI Inc. 2017, Pages 41, 52-53; Agile Project Management: Creating Innovative products, 2e, <\/span><span style=\"font-weight: 400;\">Jim Highsmith, 2009, Agile Benefits.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option A is correct whereas options B, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>2. An experienced agile practitioner has been assigned to work on two different projects at a time. In a day, on a rough approximation, he is spending 50% of his time on each of the projects. Which of the following is the type of waste that will most likely occur in such an arrangement?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Defects<\/p>\n<p style=\"text-align: justify;\">B. Task switching<\/p>\n<p style=\"text-align: justify;\">C. Partially done work<\/p>\n<p style=\"text-align: justify;\">D. Motion<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation: <\/b><span style=\"font-weight: 400;\">Software development includes seven types of waste, these are extra features, extra processes, partially done work, motion, waiting, task switching and defects. Therefore, all given choices are examples of the waste but in the given scenario, as the agile practitioner is working on two different projects and needs to switch between the projects, it is definitely the task switching wastage.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect<\/b><span style=\"font-weight: 400;\">. Defects are also a type of the waste and generally is expected to exist in the code except when the code is enough simple and the developers are quite experienced. But as the question is asking the most likely occurrence of the waste, it is definitely the task switching as the agile practitioner needs to switch between the two different projects. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is correct. <\/b><span style=\"font-weight: 400;\">As the agile practitioner is working on two different projects and needs to switch between the projects, task switching wastage will definitely exist there.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect. <\/b><span style=\"font-weight: 400;\">Although in the given scenario, the agile practitioner is likely to leave the one task partially completed before switching to the second task, the question is asking the most likely form of waste that is task switching in this case.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect. <\/b><span style=\"font-weight: 400;\">Motion is an effort needed to move or communicate the deliverables or the information from one group to another. It is especially associated with the distributed teams. The information provided in the given question is not sufficient to reject or support this assumption, so it can\u2019t be the correct answer. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b> <span style=\"font-weight: 400;\">What is Waste?, <\/span><span style=\"font-weight: 400;\">David Bernstein<\/span><span style=\"font-weight: 400;\">, Agile Alliance, 2016, Available on: <\/span><a href=\"https:\/\/www.agilealliance.org\/what-is-waste\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.agilealliance.org\/what-is-waste\/<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>3. A customer, a tester, and a developer were having a conversation about using the best testing approach on their project when an agile practitioner overheard them. Which of the following approaches would an agile practitioner most likely recommend in this situation?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Using manual, rather than automated testing tools<\/p>\n<p style=\"text-align: justify;\">B. Initiating testing later, rather than early, in the development cycle<\/p>\n<p style=\"text-align: justify;\">C. Limiting the quality assurance activities to identify the defects<\/p>\n<p style=\"text-align: justify;\">D. Developing code as per the results of acceptance tests<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice D is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> Acceptance test-driven development (ATDD) \u00a0involves creating the tests before start developing the code. These tests basically represent the expected behavior of the functionality at an acceptance test level. In this manner, the exact behavior, the software should exhibit is determined and \u2018definition of done\u2019 is provided at a very granular level. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect<\/b><span style=\"font-weight: 400;\">. Automated testing is an efficient testing approach that ensures the quick and wide test coverage of the software in an agile environment.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect<\/b><span style=\"font-weight: 400;\">. Initiating testing early rather than later in the development cycle is as per best agile best practices and reduces the risk of poor quality with early quality checks. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect.<\/b><span style=\"font-weight: 400;\"> Limiting the quality assurance activities to identify the defects is not a good agile strategy as quality assurance is associated with both risk identification as well as preventing the defects.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is correct.<\/b><span style=\"font-weight: 400;\"> Developing code as per the results of acceptance tests helps in improving the quality due to the consideration of quality in the earlier phase of the development by the team. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References<\/b><span style=\"font-weight: 400;\">: Agile Practice Guide, PMI Inc. 2017, Page 56; <\/span><span style=\"font-weight: 400;\">Lean-Agile Software Development: Achieving Enterprise Agility, Alan Shalloway, Guy Beaver, James R. Trott, 2010, Testing.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option D is correct whereas options A, B, and C are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>4. An agile team has been assigned to work on the development of a software product. The project leader is helping the team in prioritizing the requirements by using the dot voting technique. Which of the following is the most appropriate description of the dot voting?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Dot voting, also known as the 100-point method, enables customers to allocate dots to various features<\/p>\n<p style=\"text-align: justify;\">B. Dot voting draws the features on a graph with axes as dots and classifies each feature by how customers will respond<\/p>\n<p style=\"text-align: justify;\">C. Dot voting, also known as multi-voting, provides every attendant a fixed number of dots for voting<\/p>\n<p style=\"text-align: justify;\">D. Dot voting uses a fixed number of votes to rank priorities from high to low in a simple scheme<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice C is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation<\/b><span style=\"font-weight: 400;\">: As there are multiple features or user stories for a product, they are needed to get prioritized. The agile team should emphasize on delivering the maximum customer value throughout the project. Dot voting, also known as multi-voting, is a scheme used for the features\u2019 prioritization. This technique works good on a small scale and does not need any complex tools for implementation. In this technique, attendants are instructed to use common dots to be put next to their choices. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect. <\/b><span style=\"font-weight: 400;\">The 100-Point method is itself a separate customer value prioritization scheme used by project stakeholders in which exactly 100 points are given to each and every participant to assign to the different features. Therefore, Dot voting and 100-point method are different and choice <\/span><i><span style=\"font-weight: 400;\">Dot voting, also known as the 100-point method, enables customers to allocate dots to various features <\/span><\/i><span style=\"font-weight: 400;\">is incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect. <\/b><span style=\"font-weight: 400;\">The given choice <\/span><i><span style=\"font-weight: 400;\">Dot voting draws the features on a graph with axes as dots and classifies each feature by how customers will respond <\/span><\/i><span style=\"font-weight: 400;\">is the incorrect description of the dot voting. Rather it is the description of Kano analysis if the dots are excluded.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is correct. <\/b><span style=\"font-weight: 400;\">In dot voting technique, attendants are instructed to use common dots to be put next to their choices. Dot voting, also known as multi-voting, is a scheme used for the features\u2019 prioritization. So, the option <\/span><i><span style=\"font-weight: 400;\">Dot voting, also known as multi-voting, provides every attendant a fixed number of dots for voting<\/span><\/i><span style=\"font-weight: 400;\"> is the most appropriate description of the dot voting.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect.<\/b> <i><span style=\"font-weight: 400;\">Dot voting uses a fixed number of votes to rank priorities from high to low in a simple scheme <\/span><\/i><span style=\"font-weight: 400;\">is not the correct description of the dot voting. Rather, it is the description of a simple technique (with the exclusion of dots).<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b> <span style=\"font-weight: 400;\">PMI-ACP Exam Prep, Premier Edition: A Course in a Book for Passing the PMI Agile Certified Practitioner(PMI-ACP) Exam, Mike <\/span><span style=\"font-weight: 400;\">Griffiths, 2012.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option C is correct whereas options A, B, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>5. A product owner has set up a room with five laptops and invited four different end users to test the capabilities of a new system. The developers from the project team have been invited in the room to observe the users, take notes, and answer the basic questions. Which of the following agile techniques and tools has been described in this scenario?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Usability testing<\/p>\n<p style=\"text-align: justify;\">B. Automated testing<\/p>\n<p style=\"text-align: justify;\">C. Scripted testing<\/p>\n<p style=\"text-align: justify;\">D. Exploratory testing<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice A is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation: <\/b><span style=\"font-weight: 400;\">Usability testing is a type of testing that involves end users to check their response to the system under realistic circumstances. The main goal of this testing is to identify how easy it is for the end users to use the system and to expose the usability issues or defects that may need changes or redesign. The concerned people, developer in this scenario, observe the end users when they interact with the system, takes notes and answer their questions. To properly analyze the ease of usability of the system, data can be collected using a number of various approaches like videotaping the users, direct observation, eye-tracking tools and conducting post-testing interviews, etc. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is correct. <\/b><span style=\"font-weight: 400;\">Usability testing is a type of testing that involves end users to check their response to the system under realistic circumstances. As in the given scenario, end users are invited to test the capabilities of a new system and developers observe the users while they interact with the system, take notes, and answer the basic questions, scenario describes the usability testing.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect.<\/b><span style=\"font-weight: 400;\"> Automated testing is closely associated with continuous integration and includes testing the software code automatically whenever it is checked in or at the regular intervals to make sure that the changed or added code has not created any defect and compiles correctly.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect.<\/b><span style=\"font-weight: 400;\"> In Scripted testing, there is a dedicated tester that executes all the functionalities of the system against the planned criteria. \u00a0End users are especially not involved in this testing. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect<\/b><span style=\"font-weight: 400;\">. Like scripted testing, exploratory testing also includes a dedicated tester but with a very different goal. The goal of exploratory testing is to expose unexpected behavior and issues in the system. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b> <span style=\"font-weight: 400;\">PMI-ACP Exam Prep, Premier Edition: A Course in a Book for Passing the PMI Agile Certified Practitioner (PMI-ACP) Exam, Mike <\/span><span style=\"font-weight: 400;\">Griffiths, 2012, Usability Testing; Usability Testing, <\/span><span style=\"font-weight: 400;\">Agile Alliance, 2018, Available on: <\/span><span style=\"font-weight: 400;\">\u00a0<\/span><a href=\"https:\/\/www.agilealliance.org\/glossary\/usability\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.agilealliance.org\/glossary\/usability<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option A is correct whereas options B, C, and D are incorrect.<\/span><\/p>\n<blockquote><p>Also Read:\u00a0<a href=\"https:\/\/www.whizlabs.com\/blog\/best-agile-certifications\/\" target=\"_blank\" rel=\"noopener follow noreferrer\" data-wpel-link=\"internal\">Top 5 Agile Certifications<\/a><\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>6. You are an agile practitioner working on the critical medical application development project. In your company, the crystal family of methods is used for such complex projects that involve multiple teams. Which of the following methodology would you recommend as an agile practitioner using the crystal grid?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. A darker color and softer crystal methodology from the upper right corner<\/p>\n<p style=\"text-align: justify;\">B. A darker color and harder crystal methodology from the upper right corner<\/p>\n<p style=\"text-align: justify;\">C. A clearer color and harder crystal methodology from the upper left corner<\/p>\n<p style=\"text-align: justify;\">D. A clearer color and softer crystal methodology from the upper left corner<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> Crystal is a family of methods that is used in agile methodologies for the implementation concerns. Crystal method is used for the different types of projects that involve various team sizes. It determines the unique characteristics of the projects based on several factors such as system criticality, team size, and project priority. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Crystal family of methods is represented by the grid in which team size is shown in the horizontal axis and project critically on the vertical axis. Project criticality represents how critical will be the impact of a defect in the system. Moving to the right of the grid means coordination with more people that requires heavier methodology i.e. choosing a darker color. While the upper movement in the grid represents the more damage from the damage in the system i.e. increased hardness. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">In the given scenario, the project is to develop a critical medical application in which multiple teams are working. When the team size is large, a darker color methodology is used. When the project is more critical i.e. project criticality is higher, a harder crystal methodology is used. So, a darker color and harder crystal methodology from the upper right corner should be selected for the given scenario.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect.<\/b><span style=\"font-weight: 400;\"> The question mentions the development of a critical medical application. For which, the harder crystal methodology is required to be chosen, softer crystal methodology will not work.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is correct.<\/b><span style=\"font-weight: 400;\"> The project involves multiple teams i.e. team size is large, so darker color methodology will be used. Due to the higher criticality of the project, harder crystal methodology will be used. Also, higher criticality corresponds to the upper and right movement to the grid.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect.<\/b><span style=\"font-weight: 400;\"> Clearer color represents a smaller team size. In the given scenario where the multiple teams are working on the project, the team size is large. So, the darker color will be used to represent the team size.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect.<\/b><span style=\"font-weight: 400;\"> Clearer color represents a smaller team size. In the given scenario the team size is large, so the darker color will be used to represent the team size. Also, due to high criticality, the harder methodology will be used, not the softer one.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Agile Practice Guide, PMI Inc., 2017, Page(s) 106-107; Agile Software Development: The Cooperative Game, 2nd Edition by Alistair Cockburn, Chapter 6<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>7. Ryan is a scrum master handling the team that is working on an agile project. The team members complaints that their work is being delayed as the new sponsor (who doesn\u2019t know about the agile methodology and practices) keeps on asking them about the project details every time. What would you do in this situation as a scrum master?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Discuss with the product owner and request him to help in dealing with the new sponsor<\/p>\n<p style=\"text-align: justify;\">B. Contact the sponsor and request him to bring all the questions to you (scrum master) only<\/p>\n<p style=\"text-align: justify;\">C. Discuss with the team and fix one member as the spokesperson for the sponsor<\/p>\n<p style=\"text-align: justify;\">D. Tell the team to take his (scrum master) permission before having any discussion with the sponsor<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> There are a lot of duties of scrum master like promoting conversation and collaboration within teams. \u00a0To keep the team shielded from any type of interruption is also one of the major duties of scrum master. As in the current scenario, the new sponsor is disturbing the team by asking the project details frequently that is an interruption and slows down the progress of the project. It further makes it difficult for the team to accomplish the decided project goals. Therefore, it is the duty of scrum master to contact with the new sponsor and discuss with him the actual working of agile methodology. The scrum master should make a request to new sponsor to contact him in case of any question or query, not the team members. \u00a0<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect. <\/b><span style=\"font-weight: 400;\">\u00a0The product owner is the ultimate key stakeholder who is responsible for delivering the final product to the client. Product owner always wants the uninterrupted growth of the project but taking the assistant from the product owner, in this case, is not the best option. As all have their specific roles and responsibilities and it is the duty of scrum master to shield his team from any interruption.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is correct.<\/b><span style=\"font-weight: 400;\"> To contact with the sponsor is the best option for the scrum master. The scrum master should contact the sponsor to make him understand the agile working and the proper channel of forwarding the questions or queries regarding the project. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect. <\/b><span style=\"font-weight: 400;\">It is the scrums master, not any team member who is responsible for keeping the team away from any interruption. The scrum master should handle the situation himself to make it easy for the team to accomplish the project goals with mutual collaboration. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect. <\/b><span style=\"font-weight: 400;\">\u00a0It is not the way how agile works. It is a scrum master who should shield his team from this type of interruption. Also, the involvement of the team in these type of activities will waste their time in just waiting and responding that will divert them away from their actual project goals. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Agile Practice Guide, PMI Inc. 2017, Page 36; Glossary: Scrum Master, Agile Alliance 2019, Available on: <a href=\"https:\/\/www.agilealliance.org\/glossary\/scrum-master\/\" target=\"_blank\" rel=\"noopener noreferrer\">https:\/\/www.agilealliance.org\/glossary\/scrum-master\/<\/a><\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>8. Daily stand up meeting is very important for an agile team as it allows the team to communicate, collaborate, and make future work plans. Many new agile team members may need to understand the meaning of daily stand up meetings. Which is the following is the most important thing that an agile practitioner should keep in mind for an effective daily stand up meeting?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Every team member should take part in the daily stand up meeting; it will help to keep the meeting short<\/p>\n<p style=\"text-align: justify;\">B. Daily stand up meeting helps to make sure that none of the team members have any doubt about the deliverables and the performance of the team is intact<\/p>\n<p style=\"text-align: justify;\">C. Daily stand up meeting is a short meeting only for 15 minutes; no one can leave the meeting until the discussion is over<\/p>\n<p style=\"text-align: justify;\">D. Daily stand up meeting should be well-structured and short<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice D is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> The daily meeting is used in the different agile methodologies. In the Scrum, it is known as a daily meeting and timeboxed to 15 minutes while in eXtreme Programming (XP), it is known as a daily stand up meeting and timeboxed to 5 minutes. Generally, the daily meeting is a short meeting held daily at the same time, to keep everyone up-to-date about the vital information regarding the project. Team members discuss three questions during the daily meeting. The daily stand up meeting should be well-structured to get the answer to these questions but short.<\/span><\/p>\n<ul style=\"text-align: justify;\">\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">What did you do since last daily standup meeting?<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">What are you planning to do today?<\/span><\/li>\n<li style=\"font-weight: 400;\"><span style=\"font-weight: 400;\">What are the risks\/problems you are facing?<\/span><\/li>\n<\/ul>\n<p style=\"text-align: justify;\"><b>Option A is incorrect.<\/b><span style=\"font-weight: 400;\"> It is recommended that every team member should take part in the daily stand up meeting, but it\u2019s not related to the duration of daily stand up meeting short. Also, it\u2019s not the most important be kept in mind for the effective daily stand up meeting.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect.<\/b><span style=\"font-weight: 400;\"> Daily stand up meeting involves the discussion on three questions. One question is about the impediments i.e. risks and issues that any team member have. It helps to deal with risks and ensures that team performance is intact. But it doesn\u2019t make the daily stand up meeting effective.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect. <\/b><span style=\"font-weight: 400;\">The duration of daily stand up meeting varies in different agile methodologies. As in the question, the term used is daily stand up, it signifies that the XP methodology is being used. In XP, the daily stand up meeting should have the duration a maximum of 5 minutes. Rather, we can\u2019t be ensured about the duration as the methodology has not been specified.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is correct.<\/b><span style=\"font-weight: 400;\"> The daily standup meeting should be short, it is true. Also, it should be well-structured, such that the team members should be focused on answering the three questions. So, it\u2019s the most important point that specifies the effective daily stand up meeting.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Agile Practice Guide, PMI Inc. 2017, Page(s) 53-54; Glossary: Daily Meeting, Agile Alliance 2019, Available on: <\/span><a href=\"https:\/\/www.agilealliance.org\/glossary\/daily-meeting\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.agilealliance.org\/glossary\/daily-meeting<\/span><span style=\"font-weight: 400;\">\/<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option D is correct whereas options A, B, and C are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>9. Harold is a stakeholder in company A. He has recently learned that the team will use an agile framework in the current project. In a planning meeting, Harold tells the team members that they are not doing formal documentation in this project as they were doing in the previous projects. How will the team members react to his statement?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. There is no documentation in the agile projects, they focus on the value-added delivery<\/p>\n<p style=\"text-align: justify;\">B. The documentation is kept barely sufficient to fulfill regulatory requirements in agile methodology<\/p>\n<p style=\"text-align: justify;\">C. In agile, the documentation is done for the clear work items only<\/p>\n<p style=\"text-align: justify;\">D. Documentation is not created in agile methodology, but we used as much documentation possible to make you comfortable with the agile<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation: <\/b><span style=\"font-weight: 400;\">Agile Manifesto value #2 states \u201cWorking software over comprehensive documentation\u201d. In agile, creating the formal documentation with a detailed description of everything is considered wastage of time. It does not mean that documentation is not necessary at all. It is necessary but it should be kept barely sufficient to fulfill regulatory requirements in an agile environment. \u00a0Although for some safety-critical products, some additional documentation and conformance checks are recommended. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Option A is incorrect<\/strong>. \u00a0In agile, working software with sufficient documentation is preferred. Value-based delivery is one of the major aspects of agile methodology but it should be supported with sufficient documentation to meet the regulatory needs.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Option B is correct.<\/strong> In agile, documentation is kept small and barely sufficient to fulfill regulatory requirements in an agile environment. \u00a0Only the required time and effort should be applied to create documentation, neither less nor more.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Option C is incorrect<\/strong>. In agile, documentation is not related to clear or unclear work items. It is intended towards meeting the regulatory needs of the team, organization, and customer.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Option D is incorrect.<\/strong> Documentation has a significant place even in agile methodology. It is not true that the documentation is not created in agile. In Agile, small documentation is created to fulfill the regulatory requirements. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> \u00a0Agile Practice Guide, <\/span><span style=\"font-weight: 400;\">PMI Inc. 2017, Page 122; <\/span><i><span style=\"font-weight: 400;\">T<\/span><\/i><span style=\"font-weight: 400;\">he Agile Manifesto, Scrum Alliance 2018, \u00a0Available on: <\/span><a href=\"https:\/\/www.scrumalliance.org\/forbes\/transformation\/agile-manifesto\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.scrumalliance.org\/forbes\/transformation\/agile-manifesto<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>10. Gerard is a scrum master handling a scrum team working on the customer production system development. \u00a0The members of the team are distributed across the globe. During the iteration, the team found a critical defect so they decided to discuss the troubleshooting steps on the video conference. But suddenly the team members started blaming each other for the defect and the discussion turned into an argument. How would Gerrard handle this situation as a scrum master?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Request the team members to gather on site to resolve this type of critical defects<\/p>\n<p style=\"text-align: justify;\">B. Ask the team to discuss and resolve the issue collaboratively in a professional manner<\/p>\n<p style=\"text-align: justify;\">C. Tell the team to take a break and start the discussion after some time<\/p>\n<p style=\"text-align: justify;\">D. Wait for the retrospective meeting and review the result of team discussion with the team<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> Scrum master acts as a facilitator for his team. It is his responsibility to promote the conversation and collaboration within the team and among teams. He is supposed to extract best out of each member with his managing and collaborating skills. In case of conflicts or bottleneck, it is the duty of scrum master to encourage collaboration among team members. In the current scenario, scrum master should ask his team members to discuss the point of views of each in a collaborative and professional way. He should help team members in understanding that internal conflicts are not good for any team. Views of others should be considered as the other options and the team should try to resolve the issues in a professional way. It\u2019s the collaboration that will help in resolving the conflicts and getting the desired results. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect.<\/b><span style=\"font-weight: 400;\"> Requesting the team members to gather on the site to resolve this type of critical defects is not the best option in this case. Gathering on site will just waste the time that otherwise can be put in development.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is correct.<\/b><span style=\"font-weight: 400;\"> It is the duty of scrum master to promote the collaboration within the team. Asking the team to discuss and resolve the issue collaboratively in a professional manner is the best option in this case. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect.<\/b><span style=\"font-weight: 400;\"> \u00a0Agile teams are self-organizing teams but in this case, as the discussion has turned into a heated argument, it is important for the scrum master to involve in the matter and facilitate the team for mutual collaboration and professional discussion. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect.<\/b><span style=\"font-weight: 400;\"> In simple situations, wait for the retrospective meeting and review the result of team discussion with the team seems a good option. But in the current scenario, \u00a0a critical defect is found in the production system, therefore, the situation demands an urgent resolution. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Agile practice guide, PMI Inc. 2017, Page 35; \u00a0Scrum Roles Demystified, Scrum Alliance 2018, Available on: <\/span><a href=\"https:\/\/www.scrumalliance.org\/agile-resources\/scrum-roles-demystified\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.scrumalliance.org\/agile-resources\/scrum-roles-demystified<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<blockquote><p>The agile project management model is preferred by the teams due to its flexibility. Let&#8217;s find out <a href=\"https:\/\/www.whizlabs.com\/blog\/flexibility-of-agile\/\" target=\"_blank\" rel=\"noopener noreferrer\">what makes agile so flexible<\/a>.<\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>11. The agile team uses a data gathering facilitation technique to gather data in an iteration retrospective. The team creates a graph to provide a visual picture of the status of their satisfaction in any particular area. Choose the correct name for this technique.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Team Radar<\/p>\n<p style=\"text-align: justify;\">B. Satisfaction Histogram<\/p>\n<p style=\"text-align: justify;\">C. Color Code Dots<\/p>\n<p style=\"text-align: justify;\">D. Triple Nickles<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> Satisfaction Histogram is a data gathering technique that is used to know the satisfaction level of individuals in a particular area, process or activity. In this technique, a graph is created to<\/span> <span style=\"font-weight: 400;\">provide a visual picture of the status of their satisfaction that<\/span><span style=\"font-weight: 400;\"> helps the team in having deeper discussions and analysis. <\/span><span style=\"font-weight: 400;\">It is frequently used during the iteration retrospective.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect.<\/b><span style=\"font-weight: 400;\"> Team Radar is also a data gathering technique but it is generally used to evaluate the team\u2019s performance in culture, value and development practices. \u00a0Therefore, this is an incorrect option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is correct.<\/b><span style=\"font-weight: 400;\"> Satisfaction histogram is a technique in which the team creates a graph to provide a visual picture of the status of their satisfaction in any particular area. Therefore, it is the correct option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect. <\/b><span style=\"font-weight: 400;\">Color Code Dots is a technique used for gathering data related to feelings; where the emotions ran high or low<\/span><span style=\"font-weight: 400;\"> in an iteration retrospective, project retrospective or release. <\/span><span style=\"font-weight: 400;\">But in the given scenario, the motive is to analyze the satisfaction level of team members in any particular area, therefore this is an incorrect option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b> Option D is incorrect.<\/b><span style=\"font-weight: 400;\"> Triple Nickels is a brainstorming approach that is used for generating ideas for actions or recommendations. Therefore, it is not the correct option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Esther Derby, D. L. (2006). <\/span><i><span style=\"font-weight: 400;\">Agile Retrospectives: Making Good Teams Great.<\/span><\/i><span style=\"font-weight: 400;\"> Paperback, 2006.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>12. You are an agile practitioner and have recently been assigned to handle an ongoing Agile project. During the sprint retrospective, the project manager asked all the team members to put sticky dots on the project timeline to display the events where the emotions ran high or low. Choose the option that represents this activity.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Pareto Charts<\/p>\n<p style=\"text-align: justify;\">B. Affinity Diagrams<\/p>\n<p style=\"text-align: justify;\">C. Color Code Dots<\/p>\n<p style=\"text-align: justify;\">D. Triple Nickles<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice C is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation: <\/b><span style=\"font-weight: 400;\">Color Code Dots is a data gathering technique which is used in conjunction with a timeline to show how events are experienced by the individuals in a longer iteration or retrospective. It focuses on collecting the data for feelings; where emotions ran high or low. A timeline is drawn on the board and sticky notes are put on it. All members have \u00a05-10 high energy and low energy sticky dots which they have to paste on sticky notes.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect. <\/b><span style=\"font-weight: 400;\">Pareto Chart is used to analyze the frequency of causes or problems in an activity or process. Therefore, it is an incorrect option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect.<\/b> <span style=\"font-weight: 400;\">An affinity diagram is a business tool used to organize ideas, opinions, data, and issues. Therefore, it is also an incorrect choice.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is correct. <\/b><span style=\"font-weight: 400;\">Color Code Dots is a technique where sticky dots are used by team members to show the items or events where emotions ran high or low. \u00a0<\/span><span style=\"font-weight: 400;\">\u00a0<\/span><span style=\"font-weight: 400;\">Items with more dots have higher priority than items with fewer dots. The technique is frequently used during the sprint retrospective activity.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect.<\/b><span style=\"font-weight: 400;\"> \u00a0Triple Nickels is a brainstorming approach that is used for generating ideas for actions or recommendations. Therefore, it is not the correct option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Esther Derby, D. L. (2006). <\/span><i><span style=\"font-weight: 400;\">Agile Retrospectives: Making Good Teams Great.<\/span><\/i><span style=\"font-weight: 400;\"> Paperback, 2006.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option C is correct whereas options A, B, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>13. During a retrospective, an agile team defines the desired state required to achieve. Small groups work for the identification of the factors that could drive the changes they want. They note down the factors and then the group checks the strength of each supporting factor with respect to other factors. Then the team repeats this process for inhibiting factors. Name the technique the team is using.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Brainstorming<\/p>\n<p style=\"text-align: justify;\">B. Fishbone Analysis<\/p>\n<p style=\"text-align: justify;\">C. Working Agreements<\/p>\n<p style=\"text-align: justify;\">D. Force Field Analysis<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice D is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation: <\/b><span style=\"font-weight: 400;\">The team is using force field analysis technique. <\/span><span style=\"font-weight: 400;\">Force Field Analysis is an amazing tool that helps in making the transformational changes by evaluating the contributing factors. In this technique, all the supporting and inhibiting factors for the change are assessed and the feasibility of the change is analyzed in the current environment. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect. <\/b><span style=\"font-weight: 400;\">\u00a0\u00a0Brainstorming is generally a group meeting under the supervision of a facilitator where participants are asked to generate and share their ideas on a particular topic or problem. But in the given scenario, team members are involved in assessing and evaluating all the supporting and inhibiting factors to check the feasibility of change, therefore it is not the correct option.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect.<\/b><span style=\"font-weight: 400;\"> Fishbone analysis is a diagramming tool that categorizes the possible causes of the intended problem with the intention of identification of the root cause.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect. <\/b><span style=\"font-weight: 400;\">Working Agreement is an important tool that is used to establish a mutual understanding, the working style, and approach for the team.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is correct.<\/b><span style=\"font-weight: 400;\"> The team is using force field analysis technique. In this technique, all the factors involved in the change are identified and the strength of all supporting and inhibiting factors is evaluated to check the feasibility of the change. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> Creative Problem-Solving in Agile, <\/span><span style=\"font-weight: 400;\">Robert Weidner<\/span><span style=\"font-weight: 400;\"> (2015), Available on: <\/span><a href=\"https:\/\/www.scrumalliance.org\/community\/articles\/2015\/september\/creative-problem-solving-in-agile\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.scrumalliance.org\/community\/articles\/2015\/september\/creative-problem-solving-in-agile<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option D is correct whereas options A, B, and C are incorrect<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>14. An agile team is working on a software development project. During a retrospective, the team reveals its concerns regarding quality management processes. About 1% of the produced deliverables had some minor defects so, rework is required. What should the team do to bring the future performance of the project to meet the expected quality standards?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Find the root cause with critical chain diagram<\/p>\n<p style=\"text-align: justify;\">B. Investigate the root cause using the fishbone diagram<\/p>\n<p style=\"text-align: justify;\">C. Investigate the root cause with tornado diagram<\/p>\n<p style=\"text-align: justify;\">D. Don\u2019t do anything, ignore the minor defects<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice B is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation: <\/b><span style=\"font-weight: 400;\">The team has observed some minor defects in the produced deliverables. To enhance the quality of deliverables and meet the quality standards, it is necessary to find out the root cause of the problem. Therefore, in the given scenario, root cause analysis will work. Fishbone diagram is a diagrammatic tool used for root cause analysis. In this technique, possible causes of the problem or defect are further divided into different branches to identify the root cause. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect.<\/b><span style=\"font-weight: 400;\"> Critical chain diagram is a project management tool that helps in scheduling the project. It will not help in finding the root cause of the defect.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is correct.<\/b><span style=\"font-weight: 400;\"> Fishbone diagram is a diagrammatic tool which is used to find the root cause of the problem. In this diagram, different causes of a problem are further divided into different branches to reach to the root cause.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is incorrect.<\/b> <span style=\"font-weight: 400;\">Tornado diagram is a diagrammatic tool that is used to demonstrate the possible change in result with the changes in considered variables. Therefore, it won&#8217;t help in finding the root cause of the defect. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect. <\/b><span style=\"font-weight: 400;\">\u00a0No defects should be ignored even if they are minor. Minor defects are also capable to affect the quality of the product adversely. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>References:<\/b><span style=\"font-weight: 400;\"> A Guide to the Project Management Body of Knowledge, PMBOK\u00ae Guide Sixth Edition, Page 293.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option B is correct whereas options A, C, and D are incorrect.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>15. You are an agile coach leading a complex knowledge work project in an organization. To document and share the knowledge work created by the project, you have to select a tool. There are a number of options, and as the agile coach, you considered two options that seem equally good. What will you do next to select the final right tool? <\/strong><\/p>\n<p style=\"text-align: justify;\">A. Organize a planning poker event and study both the options to choose the best one<\/p>\n<p style=\"text-align: justify;\">B. Use a fishbone diagram to find the best tool out of the two options<\/p>\n<p style=\"text-align: justify;\">C. Organize a spike event and study both the options to choose the best one<\/p>\n<p style=\"text-align: justify;\">D. Schedule a meeting with the product owner to make the final decision<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> <span style=\"font-weight: 400;\">Choice C is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Explanation:<\/b><span style=\"font-weight: 400;\"> Spikes are helpful for learning purposes and are generally used in circumstances like acceptance criteria definition, estimation, and understanding the flow and applicability of ideas or actions. The agile coach should<\/span> <span style=\"font-weight: 400;\">organize a spike event and study both the options to choose the best one. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option A is incorrect. <\/b><span style=\"font-weight: 400;\">Planning Poker is consensus-based planning and estimating technique in agile. \u00a0It is used by the agile teams for the estimation of their product backlogs. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option B is incorrect.<\/b> <span style=\"font-weight: 400;\">Fishbone analysis is a diagramming tool that categorizes the possible causes of the intended problem with the intention of identification of the root cause.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option C is correct.<\/b><span style=\"font-weight: 400;\"> The agile coach should<\/span> <span style=\"font-weight: 400;\">organize a spike event and study both the options to choose the best one. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Option D is incorrect. <\/b><span style=\"font-weight: 400;\">To<\/span> <span style=\"font-weight: 400;\">schedule a meeting with the product owner to make the final decision is not the best option. Agile teams are self-organized and involving product owner in these matters is not recommended.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>References<\/b><span style=\"font-weight: 400;\">: Agile Practice Guide, PMI Inc. 2017, Page 56; Spikes in Scrum: The Exception, Not the Rule, Scrum Alliance 2016, Available on: <\/span><a href=\"https:\/\/www.scrumalliance.org\/learn-about-scrum\/agile-atlas\/agile-atlas-commentaries\/may-2014\/spikes-in-scrum-the-exception,-not-the-rule\" target=\"_blank\" rel=\"noopener noreferrer\"><span style=\"font-weight: 400;\">https:\/\/www.scrumalliance.org\/learn-about-scrum\/agile-atlas\/agile-atlas-commentaries\/may-2014\/spikes-in-scrum-the-exception,-not-the-rule<\/span><\/a><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence option C is correct whereas options A, B, and D are incorrect.<\/span><\/p>\n<p><a href=\"https:\/\/www.whizlabs.com\/pmi-acp\/online-course\/\"><img decoding=\"async\" class=\"wp-image-69791 size-full aligncenter\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/sites\/2\/2019\/01\/Agile_Certified_Practitioner.gif\" alt=\"PMI-ACP Online Course\" width=\"728\" height=\"90\" \/><\/a><\/p>\n<p style=\"text-align: justify;\"><strong>16. John is a scrum master\/coach for an agile team. During a design discussion meeting, he was acting as the facilitator. He noticed that the team has made the wrong design choice. John tried to correct them by dropping some hints in the form of questions but these got un-noticed. This incorrect design choice might cause some extra work for the team. What John should do next?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. John should continue dropping hints until team understands what he is trying to highlight<\/p>\n<p style=\"text-align: justify;\">B. John should tell the team to change the design option. John can also explain the reasoning if required<\/p>\n<p style=\"text-align: justify;\">C. John should share his view about design option but leave the final decision on the team<\/p>\n<p style=\"text-align: justify;\">D. Do nothing. Let the team learn from mistakes<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice D is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Here the team has already made a decision. John also tried to correct them by providing enough hints in the form of questions and these got un-noticed. Whatever mentioned by choice C is already done by John and the next thing is to do nothing and make sure the team learned from their mistakes.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct since the team has already made a decision.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since John is a scrum master he needs to focus on facilitating exercise and should not direct the team.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since he has already shared his views and insisting on them, again and again, is not his role.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is correct since as a scrum master he does nothing. The team can learn from their mistakes if any and come back fast.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Coaching Agile Teams by Lyssa Adks inins, chapter 3.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>17. In iteration planning, the team committed for 3 stories. The story point estimate for these stories were &#8211; 5 points, 4 points, and zero points. The team was able to successfully deliver all of these stories. The story worth 5 points took 5 ideal days. The story worth 4 points took 3 ideal days. The story worth zero points took very little effort (hardly 1-2 hours). What should be the velocity based on this data?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. 3 stories.<\/p>\n<p style=\"text-align: justify;\">B. 8 story points.<\/p>\n<p style=\"text-align: justify;\">C. A number between 8 and 9 story points.<\/p>\n<p style=\"text-align: justify;\">D. 9 story points.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice D is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct since estimation has been done in story points so velocity should be Calculated in story points only.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, as estimation was done in story points, so it makes sense to express the velocity in the same unit. If a story worth X points take Y ideal days, another story of worth 2X points need not take exactly 2Y points. Slight variations in the estimate are alright. We need not to bother about such minor variations as velocity itself is a great equalizer for estimation errors.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is incorrect for the same reason as mentioned above. Moreover, zero story point estimate is for stories having trivial effort so these have no contribution in velocity calculation. If there are multiple zero points stories in the same iteration, it is better to club these so that they may have a finite estimate in story points.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is correct, and total story points worth work delivered = 5 + 4 + 0 = 9 story points.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference: <\/b><span style=\"font-weight: 400;\">Agile estimating and planning by Mike Cohn.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>18. An agile team is planning for its 9th iteration. So far, the velocity has been: Lowest= 12 story points; Average=18 story points; Highest=24. Following are the user stories in backlog in descending order of priority?<\/strong><\/p>\n<ol style=\"text-align: justify;\">\n<li style=\"font-weight: 400;\"><strong>Story 1-5 points<\/strong><\/li>\n<li style=\"font-weight: 400;\"><strong>Story 2-7 points<\/strong><\/li>\n<li style=\"font-weight: 400;\"><strong>Story 3-9 points<\/strong><\/li>\n<li style=\"font-weight: 400;\"><strong>Story 4-5 points<\/strong><\/li>\n<li style=\"font-weight: 400;\"><strong>Story 5-3 points<\/strong><\/li>\n<li style=\"font-weight: 400;\"><strong>Story 6-1 points<\/strong><\/li>\n<\/ol>\n<p style=\"text-align: justify;\"><strong>Which of the following stories should be chosen?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. 1,2<\/p>\n<p style=\"text-align: justify;\">B. 1,2,3<\/p>\n<p style=\"text-align: justify;\">C. 1,2,4,6<\/p>\n<p style=\"text-align: justify;\">D. 1,2,4,5<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Answer: <\/strong>Choice C is the correct answer. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Generally, it is best to use average velocity for planning. Large velocity variations are possible due to a number of reasons. For e.g. in an iteration team picked 8 points worth story but could not finish it due to the last minute bud found. This didn\u2019t any anything in velocity calculation for that iteration. However, in next iteration, will small amount of effort team have got 8 points added in velocity. There could be a good amount of variation in velocity calculated for both iterations so taking average velocity for planning is a balanced approach. \u00a0\u00a0\u00a0<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">To select stories, the team will go through the backlog in priority order from the top, towards the bottom. \u00a0Now assuming 18 story points velocity, the team could easily pick stories 1 and 2. The team can\u2019t pick story 3 as that would mean committing for 21 story points. After skipping 3, the team could pick 4 so now their total commitments are 17 story points. Going further down, the team can\u2019t pick story 5 but can pick story 6. \u00a0\u00a0<\/span> <span style=\"font-weight: 400;\"> \u00a0<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct\u00a0since the number of story points is equal to 12 story points only.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct\u00a0since the number of story points is greater than 18 (Average velocity).<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct\u00a0since the number of story points is equal to the average velocity.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct\u00a0since the number of story points is greater than 18 (Average velocity).<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference: <\/b><span style=\"font-weight: 400;\">Agile estimating and planning by Mike Cohn.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>19. You are leading a large agile project for a health insurance company. You have decided to outsource one of the major functional modules. You received three bids. Seller A has the most experience of working on agile projects. Seller B has the most experience of delivering health insurance projects. Seller C has the lowest bid. Which seller you would choose?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Seller A: Understanding of agile methodology is most important. Agile incremental &amp;iterative delivery can cover for limited functional experience and will ultimately save the cost.<\/p>\n<p style=\"text-align: justify;\">B. Seller B: In agile, functional expertise is most important. If the contract is fixed price, it doesn\u2019t matter whether the vendor uses agile iterative delivery or waterfall.<\/p>\n<p style=\"text-align: justify;\">C. Seller C: Lowest bid, wins the contract.<\/p>\n<p style=\"text-align: justify;\">D. Any seller can win the contract depending on the weighing system. The weighing system considers all important factors.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Answer: <\/strong>Choice D is the correct answer. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> The PMBOK 5<\/span><span style=\"font-weight: 400;\">th<\/span><span style=\"font-weight: 400;\"> Edition guide recommends creating a weighting system for sellers; that is, rating sellers along with a set of weighted criteria so that the most appealing rise to the top. The weights then create a \u201cnegotiating sequence\u201d that determines the selection order of sellers.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct since the given statement is not correct with respect to the sellers&#8217; selection.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since the given statement is not correct with respect to the sellers&#8217; selection.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since the given statement is not correct with respect to the sellers&#8217; selection.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is correct, and any seller can win the contract depending on the weighing system. The weighing system considers all important factors.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference<\/b><span style=\"font-weight: 400;\">: The Software Project Manager\u2019s bridge to agility by Michele Slinger &amp; Stacia Broderick, Chapter 12.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>20. What agile team should do to mitigate the risks associated with intrinsic schedule flaw?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Add Local safety in the estimate.<\/p>\n<p style=\"text-align: justify;\">B. Add extra resources increases team productivity.<\/p>\n<p style=\"text-align: justify;\">C. Re-evaluate the release plan at the end of each iteration.<\/p>\n<p style=\"text-align: justify;\">D. Re-evaluate the release plan at the end of the release.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct, as first of all there should not be any local safety added in estimates. Any slack to handle schedule risk should be added at release level (like adding extra iteration). Secondly, slack is useful for general schedule risk but will not work for intrinsic schedule flaw.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, as adding extra resources will not help in meeting intrinsic schedule flaw. Beyond an optimum team, size having extra resources doesn\u2019t help in productivity gain. Moreover, intrinsic schedule flaw doesn\u2019t always mean project taking long. It may be opposite case.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct since the agile team should re-evaluate the release plan after the end of each iteration to mitigate risks associated with intrinsic schedule flaw.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, as re-evaluating at the end of release will not allow the teams to mitigate.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference<\/b><span style=\"font-weight: 400;\">: The Software Project Manager\u2019s bridge to agility by Michele Slinger &amp; Stacia Broderick.<\/span><\/p>\n<blockquote><p>Also Read: <a href=\"https:\/\/www.whizlabs.com\/blog\/agile-interview-questions-answers\/\" target=\"_blank\" rel=\"noopener noreferrer\">Top 25 Agile Interview Questions<\/a><\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>21. An agile team is tracking the progress using release burn-down chart. While the chart was moving down till 5th iteration then it went up slightly and then again moved down till it touched the horizontal line. What could have been the reason for burn-down chart going down?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. In the testing of 6th iteration, there were bugs found in stories that were accepted as \u201cdone\u201d in 5th iteration.<\/p>\n<p style=\"text-align: justify;\">B. It was simply a plotting error. The team requires training on agile tracking tool.<\/p>\n<p style=\"text-align: justify;\">C. There was more work added that team finished in the sixth iteration.<\/p>\n<p style=\"text-align: justify;\">D. The team could not finish any story in the sixth iteration.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:\u00a0<\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct, because if there are bugs found later in the accepted work, these should be treated as new stories but it is a priority call taken by product owner whether to add these in current iteration or later.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, as the burn-down chart is a very simple chart so it is highly unlikely to have such plotting errors.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct, there must have been more work added than team finished in 6<\/span><span style=\"font-weight: 400;\">th<\/span><span style=\"font-weight: 400;\"> iteration so work finished was negative. This is a known limitation of the burn-down chart that it doesn\u2019t show the work added separately.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, because if work wasn\u2019t finished then 6<\/span><span style=\"font-weight: 400;\">th<\/span><span style=\"font-weight: 400;\"> iteration should have horizontal line rather than chart moving upwards, it moved upwards because of additional work.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference: <\/b><span style=\"font-weight: 400;\">Agile estimating and planning by Mike Cohn, Chapter 19.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>22. An agile team working on new software for a bookstore. In 1st iteration top priority story in book maintenance (adding books, modifying information about books, deletion of books)<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>During the iteration planning, the team realized that this story is quite big and may not be delivered completely in a single iteration.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>What should the team do?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. divide into smaller stories based on the layers on an architecture such as the creation of screens, \u00a0user interface layer, back-end, middle tier connecting back-end and user interface.<\/p>\n<p style=\"text-align: justify;\">B. Divide it into smaller stories based on functions such as one story for adding books, another for modifying information about books, and the 3rd one for deletion of books.<\/p>\n<p style=\"text-align: justify;\">C. Do nothing as it\u2019s normal to have the initial few iterations delivering no business value. The team can continue working on remaining tasks in 2nd iteration.<\/p>\n<p style=\"text-align: justify;\">D. Modifying the iteration length so that the team is able to finish this story in one single iteration.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice B is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct, because dividing the story based on architecture is not recommended. It this case, smaller stories would not be valuable for business. Moreover, the team would not be able to deliver any business value until all the tasks are complete.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is correct, as it is advisable to split the stories based on operational boundaries.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct, it is true that often agile team don\u2019t deliver any real business value in initial iterations as entire effort goes into foundation laying activities. However, this doesn\u2019t mean that the team should not make an attempt to deliver business value when this is entirely possible.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, as iteration length is decided during release planning i.e. before iteration planning. Moreover, it is not advisable to tweak the iteration length just because a particular story can\u2019t be fit into an iteration. It is highly recommended to have all iterations of the same length. \u00a0\u00a0\u00a0<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference: <\/b><span style=\"font-weight: 400;\">Agile estimating and planning by Mike Cohn, Chapter 12.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>23. Which of the following is best to call a good user story?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. The administrator can manage the books she has added.<\/p>\n<p style=\"text-align: justify;\">B. The administrator can update the book availability text.<\/p>\n<p style=\"text-align: justify;\">C. The administrator can add, edit and delete multiple books.<\/p>\n<p style=\"text-align: justify;\">D. The code should be written in JAVA.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice B is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct since it is not a closed story because managing something is an ongoing activity and it does not tell what managing books involve.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is correct, and an administrator can update the book availability text. This can particularly useful if the book is out of stock so that users can get the correct information. It may also tell if the book was out of stock but now has become available.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct, but it is a compound story, which should be split into multiple small stories.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, as it is a technical requirement or constraint, not a user story.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> User Stories Applied: For Agile Software Development by Mike Cohn.<\/span><\/p>\n<blockquote><p>Also Read:\u00a0<a href=\"https:\/\/www.whizlabs.com\/blog\/agile-career\/\" target=\"_blank\" rel=\"noopener follow noreferrer\" data-wpel-link=\"internal\">Why Agile Career is a Good Option?<\/a><\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>24. As an agile lead\/manager, what should you do if you see a committed story can\u2019t be finished by end of the iteration and it would take another 2 days?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. As it is just a matter of two days, extend the iteration length this time to finish what was committed. Meeting commitment is more important than having a fixed iteration length.<\/p>\n<p style=\"text-align: justify;\">B. Ask the team to stop working on the story as it can\u2019t be finished. Schedule this as top priority story for next iteration.<\/p>\n<p style=\"text-align: justify;\">C. Discuss with the product owner about the situation and available options without changing iteration end date. Determine if and when it should be completed.<\/p>\n<p style=\"text-align: justify;\">D. Let the team continue working and finish as much as you can. Pick the unfinished part in next iteration<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer. \u00a0\u00a0\u00a0<strong>\u00a0\u00a0\u00a0<\/strong><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct, as no matter what, iteration end date should not be changed. That is against agile principles.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, as an agile manager can\u2019t just assume that this is the top priority item for the next iteration. The product priorities are best decided by the product owner.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct, as a product owner is best placed to decide about priorities. One of the opinions could be to divide the story into smaller stories (if feasible) or have an agreement about reduced scope. If the story has to be deferred to future iterations, it needs to be taken up in the iteration planning meeting of next iterations. There is a high probability that this would be picked in next iteration but we can\u2019t just assume that.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, for the reason mentioned above. It might be wasteful to continue the work and half-done work at the end of the iteration. The decision whether to continue or stop needs to be taken care after discussion with the product owner and team. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Agile Estimating and Planning by Mike Cohn, Chapter 19.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>25. There is a new person joined the team. You see him doing copy paste from one module to other. What do you think is right here?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. There is nothing wrong here as in a team, it\u2019s okay to reuse team members work<\/p>\n<p style=\"text-align: justify;\">B. This is the violation of intellectual property. People should use their knowledge and creativity rather than copying others work<\/p>\n<p style=\"text-align: justify;\">C. Violation of design principle called \u2018DRY\u2019 (Don\u2019t Repeat Yourself)<\/p>\n<p style=\"text-align: justify;\">D. No need for this person to ask permission from the original author of the code<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct, and it is not a valid practice in agile.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, because generally work produced by IT staff is the intellectual property of the organization and it is okay to reuse other\u2019s work.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct, as this violation of design principle DRY. DRY concept recommends removing\/avoiding duplicate code. Ideally, if we need to reuse some logic, the best thing is to make it a common routine, which can be called \/referenced from multiple places. This issue with such copy paste is, the code becomes un-necessarily lengthy and clumsy. If there is a change in that logic, changes will have to be made at multiple places so this impacts the scalability.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since the given statement is not correct with respect to the given situation.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> The Art of Agile Development by James Shore.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>26. Which of the following are the TRUE statements about velocity?<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>1) If a story is not complete, based on % complete, it can contribute towards velocity calculation.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>2) \u00a0Velocity corrects estimate errors.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>3) \u00a0Velocity helps in customer satisfaction.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>4) \u00a0Velocity helps in predicting end date of release.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. 4 only.<\/p>\n<p style=\"text-align: justify;\">B. 1 and 3.<\/p>\n<p style=\"text-align: justify;\">C. 2,3 and 4.<\/p>\n<p style=\"text-align: justify;\">D. All four.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Statement 1 is not correct as we should only consider done-done stories towards velocity calculation.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Statement 2, 3 and 4 are correct with respect to the velocity.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is true as velocity helps in predicting the end date of release. However, statement 2 and 3 are also true with respect to the velocity of the team. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since statement 1 is not correct.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct since all the given statements 2, 3 and 4 are correct related to the velocity of the team.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since statement 1 is not correct.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Agile estimating and planning by Mike Cohn.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>27. During iteration planning, the amount of slack that you build depends on the ______________of the problems that your team experiences in each iteration.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Complexity.<\/p>\n<p style=\"text-align: justify;\">B. Number.<\/p>\n<p style=\"text-align: justify;\">C. Randomness.<\/p>\n<p style=\"text-align: justify;\">D. Impact<\/p>\n<p style=\"text-align: justify;\"><strong>Answer:<\/strong> Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Amount of slack really depends on the randomness of the problem.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">For example, if roughly we face 20 hours of problems each release then that should have automatically come within velocity calculation. However, if we are facing 20 to 30 hours of the problem each iteration then you may consider having 10 hours of slack.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct since complexity is not the factor we consider to build the amount of slack in iteration planning.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since Number is not the factor we consider to build the amount of slack in iteration planning.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct since Randomness is the factor we consider to build the amount of slack in iteration planning.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since Impact is not the factor we consider to build the amount of slack in iteration planning.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> The Art of Agile Development by James Shore, Chapter 8.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>28. An agile team needs to build a new website to sell few retail products through the internet. In which order you would perform various activities related to user role modeling.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Create a persona, Identify user roles, Refine roles, Consolidation and narrowing.<\/p>\n<p style=\"text-align: justify;\">B. Identify customer, Brainstorm on initial roles, Organize roles, Consolidate roles, refine roles (add persona, consider an attribute).<\/p>\n<p style=\"text-align: justify;\">C. Identify customer, create personas, Identify initial roles, Refine roles, consolidated roles.<\/p>\n<p style=\"text-align: justify;\">D. Identify initial roles, refine roles (add persona, consider and attributes), Identify customer, consolidation and narrowing.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice B is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct, since create personas is given even before creating initial business roles. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is correct since the statement is given in the correct sequences.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct, since create personas is given even before creating initial business roles. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, as first, we need to identify the customer who could help in role identification. Also, role refinement typically happens after consolidation and narrowing. <\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> User Stories Applied: For Agile Software Development by Mike Cohn, Chapter 3. <\/span><\/p>\n<p style=\"text-align: justify;\"><strong>29. Which of the following is correct about terms product knowledge and project knowledge?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Product knowledge is knowledge about what will be developed while project knowledge is about how the product will be created.<\/p>\n<p style=\"text-align: justify;\">B. Project knowledge is knowledge about what will be developed while product knowledge is about how the product will be created.<\/p>\n<p style=\"text-align: justify;\">C. Project knowledge is knowledge about what will be developed while product knowledge is about features to be developed.<\/p>\n<p style=\"text-align: justify;\">D. Both project knowledge and product knowledge terms are used interchangeably in agile development and relate to knowledge about how the product should be developed.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice A is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Product knowledge is knowledge about what will be developed. It is knowledge about the features that will be included and about those that will not be included. The more product knowledge a team has, the better able they will be to make a decision about the nature and features of the product.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Project knowledge, by contrast, is the\u00a0knowledge about how the product will be created. Examples include knowledge about the technologies that will be used, about the skills of the developers, about how well the team functions together and so on.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is correct since the explanation for the product knowledge and project knowledge are correct.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since the explanation for the product knowledge and project knowledge are wrong. \u00a0\u00a0\u00a0\u00a0<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since the explanation for the product knowledge and project knowledge are wrong.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, and the terms project knowledge and product knowledge are not used interchangeably.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Agile Estimating and Planning by Mike Cohn, Chapter 9.<\/span><\/p>\n<blockquote><p><strong>Also Read:<\/strong>\u00a0<a href=\"https:\/\/www.whizlabs.com\/blog\/agile-development-method\/\" target=\"_blank\" rel=\"noopener noreferrer\">Factors to Choose the Right Agile Development Method<\/a><\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>30. Which of the following allows the team to make and meet long-term commitments?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Release planning.<\/p>\n<p style=\"text-align: justify;\">B. Project Chartering.<\/p>\n<p style=\"text-align: justify;\">C. Risk management.<\/p>\n<p style=\"text-align: justify;\">D. Slack.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct since release planning helps us in making long terms commitments. However, there can be the number of uncertainties that a team needs to manage throughout the project. Release planning happens once so it can\u2019t help much in meeting the long-term commitments.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since project charactering is for setting up initial direction, it typically happens before the team makes any commitments.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct since every project has a number of uncertainties. Despite these uncertainties, your stakeholders need schedule commitments that they can rely upon. Risk management allows us to make and meet these commitments.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since slack helps us in mitigating schedule risk. However, there are many other kinds of risk so the better answer is risk management.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> The Art of Agile Development by James Shore, Chapter 8.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>31. Following are few statements about story writing workshop. Which of the following statements are correct with respect to a story writing workshop? <\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>1. During a story writing workshop, the focus should be on quality rather than quantity.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>2. A Good story-writing workshop combines the best elements of brainstorming with low-fidelity prototyping.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>3. No priorities are associated with stories during story writing workshop.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>4. A story writing workshop includes developers, users, the product customer and other parties who can contribute by writing stories.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. 1 and 4<\/p>\n<p style=\"text-align: justify;\">B. 2 and 3<\/p>\n<p style=\"text-align: justify;\">C. 2, 3 and 4<\/p>\n<p style=\"text-align: justify;\">D. All four<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Statement 1 is incorrect as the aim of the story writing workshop is to produce as many stories as possible so key focus in on quantity (rather than quality)<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Statement 2 is correct as low fidelity prototypes are used during story-writing. There is brainstorming to come up with stories.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Statement 3 is correct as, during a story writing workshop, the complete focus is on writing stories. No priorities are associated at this time.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Statement 4 is correct as story-writing workshop does include developers, users and all other people who can contribute.<\/span><\/p>\n<p style=\"text-align: justify;\"><img decoding=\"async\" class=\"size-full wp-image-69184 aligncenter\" src=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/sites\/2\/2019\/01\/Story-Writing-Workshop.png\" alt=\"Story Writing Workshop\" width=\"595\" height=\"443\" srcset=\"https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop.png 595w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop-300x223.png 300w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop-564x420.png 564w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop-80x60.png 80w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop-100x75.png 100w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop-180x135.png 180w, https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/Story-Writing-Workshop-238x178.png 238w\" sizes=\"(max-width: 595px) 100vw, 595px\" \/><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct, as statement 1 is incorrect about story writing workshop.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since all the three statements which are correct 2, 3 and 4 are not given as options. Only statement 2 and 3 are given here.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct since all the three statements which are correct 2, 3 and 4 are given as options.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since statement 1 is incorrect about story writing workshop.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> User Stories Applied: For Agile Software Development by Mike Cohn.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>32. What is the best time for a product owner to groom the backlog?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. During release planning.<\/p>\n<p style=\"text-align: justify;\">B. During iteration planning.<\/p>\n<p style=\"text-align: justify;\">C. Exactly before iteration planning.<\/p>\n<p style=\"text-align: justify;\">D. This can happen throughout the iteration or in a meeting a few days prior to iteration planning.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice D is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Backlog grooming is a process of estimating the existing backlog using effort\/points, refining the acceptance criteria for individual stories, and breaking large stories into smaller stories. It can either happen in a meeting or can happen throughout the sprint on a more continuous basis. One of the commonly used methods is planning poker.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct, as backlog grooming is a process that happens throughout the release.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, as iteration planning is a short meeting so backlog grooming should better be avoided.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct, as backlog grooming need not happen just before iteration planning. Typically, we do grooming on a continuous basis to ensure that backlog has sufficient information for the next 2-3 iterations.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is correct, as grooming of backlog can happen anytime during the iteration. The idea is to have sufficient information in place before iteration planning.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Coaching Agile Teams by Lyssa Adksins, Chapter 6.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>33. When it is best to do Risk Audit (examine the effectiveness of risk responses)?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. As part of iteration planning.<\/p>\n<p style=\"text-align: justify;\">B. As part of iteration review.<\/p>\n<p style=\"text-align: justify;\">C. As part of the retrospective meeting.<\/p>\n<p style=\"text-align: justify;\">D. As part of risk management review meeting.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice C is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Explanation: Choice A is not correct, as iteration planning happens at the beginning of the iteration. Risk Audit should happen towards the end of iteration rather than the beginning (Risk Audit should be after doing some risk management)<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, as a purpose of iteration review is to provide a demo to stakeholders so risk audit is not in line with the key purpose of the iteration review meeting.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct, as the purpose of the retrospective is to understand what went well and what did not go well. Examining the effectiveness of risk response\u00a0<\/span><span style=\"font-weight: 400;\">plan (risk audit) should be best done as part of the retrospective meeting.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, as agile provides a mechanism for risk audit in the form of retrospectives so there is no need to have another separate meeting.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> The Software Project Manager\u2019s Bridge to Agility by Michele Sliger, Stacia Broderick, Chapter 11.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>34. An agile team is following burn down bar chart to track the progress. Following is the sequence of events:<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>1. In the beginning, there were 240 story points worth work.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>2. In iteration 1, the team finished 20 stories work.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>3. In iteration planning meeting of the second iteration, a new story high priority story of 15 story points was added and same was selected as part of iteration scope.<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>4. The team\u00a0did finish the newly selected story and another story of 5 points (total 20 points of worth work).<\/strong><\/p>\n<p style=\"text-align: justify;\"><strong>How should bar chart now look like for iteration progress?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Top of the bar is at 200 points, the bottom is at -15.<\/p>\n<p style=\"text-align: justify;\">B. Top of the bar is at 215 points, the bottom is at zero.<\/p>\n<p style=\"text-align: justify;\">C. Top of the bar is at 200 points, the bottom is at zero.<\/p>\n<p style=\"text-align: justify;\">D. Top of the bar is at 215 points, the bottom is at -15.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice A is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Top of the bar is lowered based on the amount of work finished. Total 40 points worth work finished so that means the top of the bar should be at 200 points. Bottom of the bar is lowered when additional work is added so the bottom was brought down to -15. It doesn\u2019t matter when this additional work finishes, the bottom of the bar will be raised only when some scope is removed.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is correct, and the calculated value is equal to the given value.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct, and the calculated value is not equal to the given value.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct, and the calculated value is not equal to the given value.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct, and the calculated value is not equal to the given value.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Agile Estimating and Planning by Mike Cohn, Chapter 19.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>35. Mark is working on a product development project using Agile methodologies. There are many features in the product which are available to the end user. Which one of the below is not a Minimum Viable Product (MVP)?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. An explainer video which explains your product in a few seconds.<\/p>\n<p style=\"text-align: justify;\">B. A nicely designed landing page which communicates the value of offerings in the product.<\/p>\n<p style=\"text-align: justify;\">C. A single most valuable feature ready for use online for free to judge investor interest.<\/p>\n<p style=\"text-align: justify;\">D. A product display of fifty features working nicely and developed\/tested for six months thoroughly.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice D is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Explanation: Minimum Viable product is that version of a new product while allows a team to collect the maximum amount of validated learning about customers with the least effort.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct since the explainer video which explains your product in a few seconds is an example of MVP.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since a nicely designed landing page which communicates the value of offering in the product is an example of MVP.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since a single most valuable feature ready for use online free to judge investor interest is an example of MVP.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is correct since a product display of fifty features working nicely and developed \/tested for a six month thoroughly is not an example of MVP.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence choice D is correct, whereas choices A, B, and C are incorrect. <\/span><\/p>\n<p style=\"text-align: justify;\"><strong>36. Daily stand-up is an important practice used in agile methodologies in different variants. Which of the below statement describes the difference between daily stand-up between Kanban &amp;scrum methodologies. Assuming a big project with multiple teams.<\/strong><\/p>\n<p style=\"text-align: justify;\">A. In both Kanban &amp; Scrum senior-level meeting happens first.<\/p>\n<p style=\"text-align: justify;\">B. In both Kanban &amp; Scrum team level meeting happens first.<\/p>\n<p style=\"text-align: justify;\">C. In Kanban, higher level (in authority) meeting happens first whereas in Scrum the team\u2019s first meet and then send a delegate to a Scrum-of-Scrums.<\/p>\n<p style=\"text-align: justify;\">D. In Scrum, higher level (in authority) meeting happens first whereas in Kanban the team\u2019s will meet first.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Answer: <\/strong>Choice C is the correct answer. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> In Kanban, all the features are taken at once and pulling of work items happens based on WIP. This is controlled first at senior level on daily basis and then further calls are taken. Whereas in Scrum, a set of features are taken and daily stand up happens within the individual team first and then they send representatives for the scrum of scrums.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct since the given statement is not a valid statement.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since the given statement is not a valid statement.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is correct since, in Kanban, higher level (in authority) meeting happens first whereas in Scrum the team\u2019s first meet and then send a delegate to a Scrum-of-Scrums is true.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since the given statement is not a valid statement.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Hence choice C is correct, whereas choices A, B and D are incorrect.<\/span><\/p>\n<blockquote><p>Going to handle an Agile project?? You need to get familiar with the term Agile Contracts. To help you out, here we bring <a href=\"https:\/\/www.whizlabs.com\/blog\/agile-contracts\/\" target=\"_blank\" rel=\"noopener noreferrer\">an overview of Agile Contracts<\/a>!<\/p><\/blockquote>\n<p style=\"text-align: justify;\"><strong>37. You are managing a large project. As you don\u2019t have internal capacity, you decided to outsource a major part of your project. You have prepared and sent the RFP to key suppliers. You get a call from your cousin who is an account manager in one of the supplier firm. He wants to bid on your project. You know his company has done good work in the past so may be a good fit. How do you proceed?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. You disclose the conflict of interest to your company and disqualify your cousin\u2019s company<\/p>\n<p style=\"text-align: justify;\">B. You disclose the conflict of interest to your company and provide your cousin with information that can improve his chances of winning the contract<\/p>\n<p style=\"text-align: justify;\">C. You do not disclose the conflict of interest and give your cousin the bid<\/p>\n<p style=\"text-align: justify;\">D. You disclose the conflict of interest to your company and make the selection based on objective criteria<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice D is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Any time there\u2019s a conflict of interest, it is your duty to disclose it to your company. After that, you should always proceed based on your company\u2019s policies. If there are no specific policies about that, then make sure that the conflict does not affect your decisions. When bidders are competing for a contract, you must make sure they all have some level of information so that no one bidder is given an unfair advantage.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice A is not correct since the given statement is against the PMI\u2019s code of professional ethics.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since the given statement is against the PMI\u2019s code of professional ethics.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since the given statement is against the PMI\u2019s code of professional ethics.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is correct since the given statement is correct with respect to the PMI\u2019s code of professional ethics.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> PMI\u2019s Code of professional ethics.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>38. John is a scrum master\/coach for an agile team. Tom came to him with a complaint about Jack. John as a good coach tried three-step intervention method but Tom rejected all three options. What John should be Next?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Do nothing. Cease to consider it a problem.<\/p>\n<p style=\"text-align: justify;\">B. Set-up a meeting with both Tom and Jack to sort out differences.<\/p>\n<p style=\"text-align: justify;\">C. Talk to Jack and make him aware of the complaint but without telling him the name of the complainer.<\/p>\n<p style=\"text-align: justify;\">D. Warn Tom that complaining about colleagues is not acceptable in agile teams so there should not be repetition.<\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice A is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is correct, do nothing and cease to consider it a problem. If complainer is not willing to accept options given in three-step intervention, that might mean complainer doesn\u2019t want to resolve the complaint. Sometimes, people just want to vent. Other times, people try to add coach into their gossip chain. If the conflict looks too serious to ignore, then the coach should ask \u201cAre you ready to solve this without blaming?\u201d This is not given a choice and hence the best choice is A.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since this is against agile concept and coach should make sure that team members are resolving the conflicts themselves. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since this is against agile concept and coach should make sure that team members are resolving the conflicts themselves. <\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct unless the complainer is a chronic complainer, the coach should listen to all complains. Even for the chronic complainer, it is important to make the complainer realize about the destructive influence that harboring resentments has on the team and on him as an individual.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> Coaching Agile Teams by Lyssa Adksins, Chapter 9.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><b>39.<\/b><\/span><span style=\"font-weight: 400;\">\u00a0<\/span><span style=\"font-weight: 400;\">Which of the following is a one-page summary of key business and quality objectives, product capabilities and project management information?<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">A. Vision.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">B. Project Datasheet.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">C. Business case.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">D. Requirement specification.<\/span><\/p>\n<p style=\"text-align: justify;\"><strong>Answer: <\/strong>Choice B is the correct answer.<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is not correct since a vision statement tells what is to be achieved. It may not provide a full picture of why a project should be undertaken.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is correct since a project data sheet (PDS) is a single page summary of key business and quality objectives, product capabilities and project management information.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since a business case is a more detailed document, which provides a high-level view of why an initiative should be undertaken from the business point of view and related market research data.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since in agile there are no requirement specifications. Moreover, requirements specifications are rarely a one-page document.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference<\/b><span style=\"font-weight: 400;\">: Agile Project Management: Creating Innovative Products \u2013 2<\/span><span style=\"font-weight: 400;\">nd<\/span><span style=\"font-weight: 400;\"> Edition by Jim Highsmith, Chapter 6. <\/span><\/p>\n<p style=\"text-align: justify;\"><strong>40. Which of the following is incorrect about acceptance tests?<\/strong><\/p>\n<p style=\"text-align: justify;\">A. Acceptance tests should be written as late as possible, generally just before the start of testing as that avoids rework<\/p>\n<p style=\"text-align: justify;\">B. Acceptance tests are helpful in communicating assumptions of the customer team<\/p>\n<p style=\"text-align: justify;\">C. Acceptance tests are tests that validate that the functionality to be delivered meets customer expectation<\/p>\n<p style=\"text-align: justify;\">D. Acceptance tests are often written on the back of story card<\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Answer: <\/strong>Choice A is the correct answer.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\"><strong>Explanation:<\/strong> Choice A is correct and the given statement about acceptance test is false.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice B is not correct since the given statement \u201cacceptance tests are helpful in communicating assumptions of customer team\u2019 is true.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice C is not correct since the given statement \u201cAcceptance tests are tests that validate that the functionality to be delivered meets customer expectation\u2019 is true.<\/span><\/p>\n<p style=\"text-align: justify;\"><span style=\"font-weight: 400;\">Choice D is not correct since the given statement \u201cAcceptance tests are often written on the back of the story card\u2019 is true.<\/span><\/p>\n<p style=\"text-align: justify;\"><b>Reference:<\/b><span style=\"font-weight: 400;\"> User Stories Applied: For Agile Software Development by Mike Cohn, Chapter 6.<\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">So, have you gone through all the free PMI ACP practice questions given above? How many of these questions could you solve? Hope this set of 25 free PMI\u00a0<\/span><span class=\"s1\">ACP practice questions would have helped you to check your preparation level. <\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">Whizlabs is dedicated to helping you in your certification exam preparation. So, to assist you in your PMI ACP exam preparation, we offer 120 more <a href=\"https:\/\/www.whizlabs.com\/pmi-acp\/free-test\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span class=\"s2\">PMI-ACP Free Questions<\/span><\/a> and set of <a href=\"https:\/\/www.whizlabs.com\/pmi-acp\/practice-tests\/\" target=\"_blank\" rel=\"noopener noreferrer\"><span class=\"s2\">PMI-ACP practice tests<\/span><\/a> with the 600 unique practice questions. <\/span><\/p>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\">We recommend you to check your preparation level with the PMI ACP practice questions before taking the real exam. Trying practice tests boost your confidence and make you confident enough to pass the real exam. <\/span><\/p>\n<blockquote><p>Get Whizlabs&#8217;\u00a0<strong><a href=\"https:\/\/www.whizlabs.com\/pmi-acp\/practice-tests\/\" target=\"_blank\" rel=\"noopener noreferrer\">PMI ACP\u00ae Practice Tests<\/a>\u00a0(600 unique questions)<\/strong>\u00a0<strong>Free<\/strong>. Share this article on Twitter and Send us a mail to <a href=\"mailto:pmexperts@whizlabs.com\" target=\"_blank\" rel=\"noopener noreferrer\">support@whizlabs.com<\/a> with your Tweet.<\/p>\n<p><a href=\"https:\/\/twitter.com\/intent\/tweet?via=whizlabs&amp;text=Free%20Agile%20Certified%20Practitioner%20%28PMI%20ACP%29%C2%AE%20Exam%20Questions&amp;url=https%3A%2F%2Fwww.whizlabs.com%2Fblog%2Ffree-pmi-acp-exam-questions%2F\" target=\"_blank\" rel=\"noopener noreferrer\"><strong><span class=\"td_btn td_btn_sm td_default_btn\">Share it Now<\/span><\/strong><\/a><\/p><\/blockquote>\n<p class=\"p1\" style=\"text-align: justify;\"><span class=\"s1\"><i>Seeking any help in your PMI-ACP exam preparation? Just write in the comment below or submit at <\/i><a href=\"https:\/\/help.whizlabs.com\/hc\/en-us\/requests\/new\" target=\"_blank\" rel=\"noopener noreferrer\"><span class=\"s2\"><i>Whizlabs Helpdesk<\/i><\/span><\/a><i>, we\u2019ll respond to you in no time.<\/i><\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Preparing for PMI Agile Certified Practitioner (PMI ACP) certification exam? Looking for some free PMI ACP practice questions to help in your preparation? Here we bring the top free PMI ACP exam questions for you so that you can prepare well for the PMI ACP certification exam. PMI Agile Certified Practitioner (PMI ACP) certification exam is for the project management professionals who follow Agile principles and use Agile methodologies in their projects. With the experience of using Agile methodologies, the candidate must have some required experience such as 1 year (or 2000 hours) of general project management experience 8 months [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":69276,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_uag_custom_page_level_css":"","site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[3],"tags":[81,1196,1197,1199,1209],"class_list":["post-69183","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-agile-and-scrum","tag-agile-certified-practitioner-acp-exam-questions","tag-pmi-acp-exam-questions","tag-pmi-acp-exam-questions-and-answers","tag-pmi-acp-practice-questions","tag-pmi-acp-exam"],"uagb_featured_image_src":{"full":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",600,315,false],"thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions-150x150.png",150,150,true],"medium":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions-300x158.png",300,158,true],"medium_large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",600,315,false],"large":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",600,315,false],"1536x1536":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",600,315,false],"2048x2048":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",600,315,false],"profile_24":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",24,13,false],"profile_48":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",48,25,false],"profile_96":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",96,50,false],"profile_150":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",150,79,false],"profile_300":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",300,158,false],"tptn_thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions-250x250.png",250,250,true],"web-stories-poster-portrait":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",600,315,false],"web-stories-publisher-logo":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",96,50,false],"web-stories-thumbnail":["https:\/\/www.whizlabs.com\/blog\/wp-content\/uploads\/2019\/01\/pmi-acp-exam-questions.png",150,79,false]},"uagb_author_info":{"display_name":"Dharmalingam N","author_link":"https:\/\/www.whizlabs.com\/blog\/author\/dharmalingam\/"},"uagb_comment_info":28,"uagb_excerpt":"Preparing for PMI Agile Certified Practitioner (PMI ACP) certification exam? Looking for some free PMI ACP practice questions to help in your preparation? Here we bring the top free PMI ACP exam questions for you so that you can prepare well for the PMI ACP certification exam. PMI Agile Certified Practitioner (PMI ACP) certification exam&hellip;","_links":{"self":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/69183","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/comments?post=69183"}],"version-history":[{"count":13,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/69183\/revisions"}],"predecessor-version":[{"id":71840,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/posts\/69183\/revisions\/71840"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media\/69276"}],"wp:attachment":[{"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/media?parent=69183"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/categories?post=69183"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.whizlabs.com\/blog\/wp-json\/wp\/v2\/tags?post=69183"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}