ACP Exam 2024 with 100% Correct Answers
non-value-added work - ANSWERSAny activity that, in the eyes of the customer, does not increase the usefulness or worth of a product or service; non-value-added activities may be necessary for business purposes (such as invoicing) but are not something that customers value enough to pay for.
burndown chart - ANSWERSA line chart (with a decreasing slope) that shows the amount of work remaining in an iteration or release. The point at which the downward trend of the line intersects with the x-axis indicates the probable completion date.
minimally marketable features - ANSWERSPotentially shippable increments of features or functions that result from iterations and that have value in the marketplace.
work in progress - ANSWERS(WIP) Any work that has been started but has not been finished.
Five Whys - ANSWERSA technique in which practitioners ask "why" several times to uncover the root cause of a problem or issue. The answer to each question provides the stimulus for additional questions that help team members dig deeper into the problem.
exploratory testing - ANSWERSA testing strategy that checks to see if a product will do things that it is not supposed to do.
return on investment - ANSWERSComparison of money earned to money spent. Usually calculated for a given time period as (money earned minus money spent) divided by money spent.
release planning - ANSWERSProcess in which an organization decides when it will release products to customers.
backlog grooming - ANSWERSThe process of adjusting and refining the product backlog to ensure that it is appropriately prepared for use. Wideband Delphi - ANSWERSAn estimating technique in which team members jointly discuss user stories, then individually estimate the amount of work needed to complete the stories. If discrepancies occur, teams continue to develop work estimates until a consensus is reached.
earned value management - ANSWERSA comparison of work planned to work completed and to costs incurred, at any specific point in time. EVM helps teams track project schedule and budget performance and provides insight into project trends.
Kanban board - ANSWERSA story board that shows how many user stories are included in each phase of a project. Also known as a task board.
emotional intelligence - ANSWERSAn individual's ability to recognize, understand, and control his emotions, and to understand and relate to the emotions of others.
negotiation - ANSWERSDiscussions to explore options and reach an agreement.
escaped defects - ANSWERSErrors that are not corrected or user stories that are not completed in an iteration.
wireframes - ANSWERSVisual mock-ups of a product that developers use to verify design concepts and test functionality with users.
customer-valued prioritization - ANSWERSOrdering process that places a higher priority on user stories that provide the most value to customers (as opposed to assigning higher priority to stories that address cost, compliance, or market conditions).
timeboxing - ANSWERSThe process of setting time constraints or deadlines for iterations or projects. Timeboxing helps control a project's scope and schedule.
variance analysis - ANSWERSAn assessment to uncover any differences between what was expected and what was achieved. team space - ANSWERSAn area set aside to house the team while it works on a project. A team space generally includes individual work areas and a common area where team members can collaborate and post pertinent information.
affinity estimating - ANSWERSAn estimating technique that asks team members to silently order user stories before estimating the amount of work they could complete in an interation.
minimal viable product - ANSWERS(MVP) An early-but-complete version of a product that is released to a target audience to ensure that the product contains the features that customers will value most.
statement of work - ANSWERS(SOW) A narrative description of products, services, or results to be supplied [PMI project management definition]
Agile tooling - ANSWERSThe tools and techniques unique to Agile practices that help teams complete work and satisfy project objectives.
brainstorming - ANSWERSAn idea-generation technique in which participants develop and filter suggestions for new products or solutions to problems.
personas - ANSWERSFictional characters that represent the users of a product. Personas generally include information and assumptions about these users so teams can plan their work to satisfy these types of users.
requirements review - ANSWERSAn evaluation to clarify or gather detail about existing requirements. The information gathered in the review will help in prioritizing work for upcoming iterations.
kaizen - ANSWERSA continuous improvement approach that helps to uncover and correct problems and inefficiencies.
user story - ANSWERSAn initial requirement stated as one or more sentences in the routine or business language of the user; often placed on an index card.
non-value-added work - ANSWERSAny activity that, in the eyes of the customer, does not increase the usefulness or worth of a product or service; non-value-added activities may be necessary for business purposes (such as invoicing) but are not something that customers value enough to pay for.
burndown chart - ANSWERSA line chart (with a decreasing slope) that shows the amount of work remaining in an iteration or release. The point at which the downward trend of the line intersects with the x-axis indicates the probable completion date.
minimally marketable features - ANSWERSPotentially shippable increments of features or functions that result from iterations and that have value in the marketplace.
work in progress - ANSWERS(WIP) Any work that has been started but has not been finished.
Five Whys - ANSWERSA technique in which practitioners ask "why" several times to uncover the root cause of a problem or issue. The answer to each question provides the stimulus for additional questions that help team members dig deeper into the problem.
exploratory testing - ANSWERSA testing strategy that checks to see if a product will do things that it is not supposed to do.
return on investment - ANSWERSComparison of money earned to money spent. Usually calculated for a given time period as (money earned minus money spent) divided by money spent.
release planning - ANSWERSProcess in which an organization decides when it will release products to customers.
backlog grooming - ANSWERSThe process of adjusting and refining the product backlog to ensure that it is appropriately prepared for use. Wideband Delphi - ANSWERSAn estimating technique in which team members jointly discuss user stories, then individually estimate the amount of work needed to complete the stories. If discrepancies occur, teams continue to develop work estimates until a consensus is reached.
earned value management - ANSWERSA comparison of work planned to work completed and to costs incurred, at any specific point in time. EVM helps teams track project schedule and budget performance and provides insight into project trends.
Kanban board - ANSWERSA story board that shows how many user stories are included in each phase of a project. Also known as a task board.
emotional intelligence - ANSWERSAn individual's ability to recognize, understand, and control his emotions, and to understand and relate to the emotions of others.
negotiation - ANSWERSDiscussions to explore options and reach an agreement.
escaped defects - ANSWERSErrors that are not corrected or user stories that are not completed in an iteration.
wireframes - ANSWERSVisual mock-ups of a product that developers use to verify design concepts and test functionality with users.
customer-valued prioritization - ANSWERSOrdering process that places a higher priority on user stories that provide the most value to customers (as opposed to assigning higher priority to stories that address cost, compliance, or market conditions).
timeboxing - ANSWERSThe process of setting time constraints or deadlines for iterations or projects. Timeboxing helps control a project's scope and schedule.
variance analysis - ANSWERSAn assessment to uncover any differences between what was expected and what was achieved. team space - ANSWERSAn area set aside to house the team while it works on a project. A team space generally includes individual work areas and a common area where team members can collaborate and post pertinent information.
affinity estimating - ANSWERSAn estimating technique that asks team members to silently order user stories before estimating the amount of work they could complete in an interation.
minimal viable product - ANSWERS(MVP) An early-but-complete version of a product that is released to a target audience to ensure that the product contains the features that customers will value most.
statement of work - ANSWERS(SOW) A narrative description of products, services, or results to be supplied [PMI project management definition]
Agile tooling - ANSWERSThe tools and techniques unique to Agile practices that help teams complete work and satisfy project objectives.
brainstorming - ANSWERSAn idea-generation technique in which participants develop and filter suggestions for new products or solutions to problems.
personas - ANSWERSFictional characters that represent the users of a product. Personas generally include information and assumptions about these users so teams can plan their work to satisfy these types of users.
requirements review - ANSWERSAn evaluation to clarify or gather detail about existing requirements. The information gathered in the review will help in prioritizing work for upcoming iterations.
kaizen - ANSWERSA continuous improvement approach that helps to uncover and correct problems and inefficiencies.
user story - ANSWERSAn initial requirement stated as one or more sentences in the routine or business language of the user; often placed on an index card.
