PMI-ACP Term Quiz 2020
Course Glossary from Instructing.com
🇬🇧
In English
In English
Practice Known Questions
Stay up to date with your due questions
Complete 5 questions to enable practice
Exams
Exam: Test your skills
Test your skills in exam mode
Learn New Questions
Manual Mode [BETA]
The course owner has not enabled manual mode
Specific modes
Learn with flashcards
multiple choiceMultiple choice mode
SpeakingAnswer with voice
TypingTyping only mode
PMI-ACP Term Quiz 2020 - Leaderboard
PMI-ACP Term Quiz 2020 - Details
Levels:
Questions:
266 questions
| 🇬🇧 | 🇬🇧 |
| A method used to communicate with business customers, developers, and testers before coding begins. | Acceptance Test Driven Development |
| A leadership style that helps teams to thrive and overcome challenges throughout a project. | Adaptive Leadership |
| A method used to quickly place user stories into a comparable-sized group. | Affinity Estimation |
| To adapt the project plan continuously through retrospectives in order to maximize value creation during the planning process. | Agile Adaption |
| To use the empirical process, observation, and spike introduction while executing a project to influence planning. | Agile Experimentation |
| A document that describes the twelve principles of the Agile Manifesto. | Agile Manifesto Principles |
| To have individuals work together daily on a project to implement osmotic communication, focus, and receive instant feedback to achieve a common goal. | Agile Manifesto: Collocated Team |
| To help team members establish a healthy work-life balance, remain productive, and respond to changes swiftly for progress during a project. | Agile Manifesto: Constant Pace |
| To enhance agility and time spent on work requirements in order to retain a well-balanced work environment. | Agile Manifesto: Continuous Attention |
| To deliver software frequently to the customer, allowing for a quicker product release, faster provision of value to the customer and shorter delivery timeframe. | Agile Manifesto: Frequent Delivery |
| To give individuals the empowerment, environment, support, and trust needed to complete a task successfully. | Agile Manifesto: Motivated Individuals |
| This allows a team to learn how to become more effective, what changes need immediate implementation, and behavior that needs adjustment. | Agile Manifesto: Regular Reflection |
| A team that knows how to complete tasks effectively, has dedication to the project, and is expert on the process and project. | Agile Manifesto: Self-Organization |
| Allows team members to focus on what is necessary to achieve the requirements needed to create and deliver value to the project and customer. | Agile Manifesto: Simplicity |
| To allow quick responses to changes in the external environment, and late in development to maximize the customer’s competitive advantage. | Agile Manifesto: Welcome Changes |
| To pass on and teach based on experience, knowledge, and skills to other individuals in the team or that work for the organization. | Agile Mentoring |
| The most efficient and effective way to communicate in order to receive direct feedback and influence osmotic communication. | Agile Manifesto: Face-to-Face Conversation |
| A way to complete a goal effectively and efficiently. Examples of Agile Methodologies include XP, Scrum, and Lean. | Agile Methodologies |
| To make use of the Agile principles through activities. | Agile Practices |
| To increase team morale with software or artifacts. | Agile Tooling |
| Spikes that relate to any area of a system, technology, or application domain that is unknown. | Architectural Spikes |
| These tools allow for efficient and strong testing. Examples: Peer Reviews, Periodical Code-Reviews, Refactoring, Unit Tests, Automatic and Manual Testing. | Automated Testing Tools |
| An effective and efficient way of gathering ideas within a short period of time from a group. | Brainstorming |
| The entire team together is responsible for 100% of the code. | Collective Code Ownership |
| Decisions created by higher up individuals in the organization and handed over to the team. | Command & Control |
| An agreement made after a conflict. | Conflict Resolution |
| To ensure that self-assessment and process improvement occurs frequently to improve the product. | Continuous Improvement |
| To consistently examine a team member’s work. To build, and test the entire system. | Continuous Integration |
| To measure the cost spent on a project and its efficiency. Earned Value / Actual Cost = CPI | Cost Performance Index (CPI) |
| Teams that consist of members who can complete various functions to achieve a common goal. Team members are able to do more than one role in a project. | Cross-Functional Team |
| A chart that displays feature backlog, work-in-progress, and completed features. | Cumulative Flow Diagram |
| To deliver the maximum customer value early in order to win customer loyalty and support. | Customer-Valued Prioritization |
| To postpone decisions to determine possibilities and make the decision when the most amount of knowledge is available. | Decide As Late As Possible |
| A tangible or intangible object delivered to the customer. Ex. Document, Pamphlet, Report | Deliverables |
| To separate epics or large stories into smaller stories. | Disaggregation |
| To reach a deal through tactics so both parties receive the highest amount of value possible. | Distributive Negotiation |
| A system of voting where people receive a certain number of dots to vote on the options provided. | Dot Voting |
| Earned Value Management, works well at iteration. It is a method to measure and communicate progress and trends at the current stage of the project. | Earned Value Management (EVM) |
| An individual’s skill to lead and relate to other team members. | Emotional Intelligence |
| Defects reported after the delivery by the customer. | Escaped Defects |
| An individual chooses to behave in a particular way over other behaviors because of the expected results of the chosen behavior. | Expectancy Theory |
| To inquire how software works with the use of test subjects using the software and asking questions about the software. | Exploratory Testing |
| A team-manufactured persona that exaggerates to induce requirements a standard persona may miss. | Extreme Persona |
| A methodology in Agile with one-week iterations and paired development. | EXtreme Programming (XP) |
| A comprehensive model and list of features included in the system before the design work begins. | Feature-Driven Development (FDD) |
| A sequence of numbers used in Agile estimating, 0, 1, 2, 3, 5, 8, 13, 20, 40, 100. | Fibonacci Sequence |
| Tasks must be finished in all iterations to meet the “Definition of Done” requirements as a way to track progress and allow frequent delivery. | Finish Tasks One by One |
| A root cause diagram. | Fishbone Diagram |
| Assigned tasks prioritized for completion based on an estimated number of days. Top priorities are usually completed first. | Fixed Time Box |
| To analyze forces that encourages or resists change. | Force Field Analysis |