"A" Terms & Definitions Flashcards
Abusive manner
Treating others with conduct that may result in harm, fear, humiliation, manipulation, or
exploitation. For example, berating a project team member because they have taken longer than
expected to complete a project assignment may be considered humiliation.
Acceptance
A risk response appropriate for both positive and negative risks, but often used for smaller risks
within a project.
Acceptance test driven development
A method used to communicate with business customers, developers, and testers before coding
begins.
Acknowledgment
The receiver signals that the message has been received. An acknowledgment shows receipt of
the message, but not necessarily agreement with the message.
Active listening
The message receiver restates what has been said to understand and confirm the message fully,
and it provides an opportunity for the sender to clarify the message if needed.
* The receiver confirms that the message is being received through feedback, questions, prompts
for clarity, and other signs of confirmation.
Active observation
The observer interacts with the worker to ask questions and understand each step of the work
being completed. In some instances, the observer could serve as an assistant in doing the work.
Active problem solving
Active problem solving begins with problem definition. Problem definition is the ability to discern
between the cause and effect of the problem. Root-cause analysis looks beyond the immediate
symptoms to the cause of the symptoms—which then affords opportunities for solutions.
Activity list
The primary output of breaking down the WBS work packages.
Activity network diagram
These diagrams, such as the project network diagram, show the flow of the project work.
Actual Cost (AC)
The actual amount of monies the project has spent to date.
Adjourning
Once the project is done, either the team moves onto other assignments as a unit, or the project
team is disbanded, and individual team members go on to other work.
Adaptive leadership
A leadership style that helps teams to thrive and overcome challenges throughout a project.
Affinity diagram
This diagram breaks down ideas, solutions, causes, and project components and groups them
together with other similar ideas and components.
* When stakeholders create a large number of ideas, you can use an affinity diagram to cluster
similar ideas together for further analysis.
Affinity estimation
A method used to quickly place user stories into a comparable-sized group.
Agile
To develop a goal through periodic experimentation in order to fulfill the need of a complex
decision.
Agile adaptation
To adapt the project plan continuously through retrospectives in order to maximize value
creation during the planning process.
Agile coaching
To help achieve goals that is either personal or organizational.
Agile experimentation
To use the empirical process, observation, and spike introduction while executing a project to
influence planning.
Agile manifesto
A statement that reflects agile philosophy that includes:
* Individuals and interactions over processes and tools
* Working software over comprehensive documentation
* Customer collaboration over contract negotiation
* Responding to changes over following a plan
Agile manifesto principles
A document that describes the twelve principles of the Agile Manifesto.
Agile manifesto: Customer satisfaction
To satisfy customers through early and continuous delivery of products, to test and receive
feedback, to inform customers on progress, and to fulfill the customer’s value by completing
priority requirements.
Agile manifesto: Welcome changes
To allow quick responses to changes in the external environment, and late in development to
maximize the customer’s competitive advantage.
Agile manifesto: Frequent delivery
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: Collocated team
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: Motivated individuals
To give individuals the empowerment, environment, support, and trust needed to complete a
task successfully.
Agile manifesto: Face-to-Face conversation
- The most efficient and effective way to communicate in order to receive direct feedback and
influence osmotic communication.
Agile manifesto: Working software
Working software enables the measurement of progress, enhance customer satisfaction, and
maintain and improve the quality of the software to help support project goals.
Agile manifesto: Constant pace
To help team members establish a healthy work-life balance, remain productive, and respond to
changes swiftly for progress during a project.
Agile manifesto: Continuous attention
To enhance agility and time spent on work requirements in order to retain a well-balanced work
environment.
Agile manifesto: Simplicity
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: Self-organization
A team that knows how to complete tasks effectively, has dedication to the project, and is expert
on the process and project.
Agile manifesto: Regular reflection
This allows a team to learn how to become more effective, what changes need immediate
implementation, and behavior that needs adjustment.
Agile mentoring
To pass on and teach based on experience, knowledge, and skills to other individuals in the team
or that work for the organization.
Agile methodologies
A way to complete a goal effectively and efficiently. Examples of Agile Methodologies include XP,
Scrum, and Lean.
Agile modeling
A workflow depiction of a process or system a team can review before it is turned into code.
Stakeholders should understand the model.
Agile planning
The most important aspect of the Agile project. Planning happens at multiple levels such as
strategic, release, iteration, and daily. Planning must happen up-front and can change
throughout the project.
Agile practices
To make use of the Agile principles through activities.
Agile smells
Symptoms or indicators of problems that affect Agile teams and projects.
Agile space
A space that allows team members to establish collaboration, communication, transparency, and
visibility.
Agile themes
Themes used to help the team focus on the functions of iteration.
Agile tooling
To increase team morale with software or artifacts.
Alternative analysis
The identification of more than one solution. Consider roles, materials, tools, and approaches to
the project work.
Alternative dispute resolution
When there is an issue or claim that must be settled before the contract can be closed, the
parties involved in the issue or claim will try to reach a settlement through mediation or
arbitration.
Alternatives generation
A scope definition process of finding alternative solutions for the project customer while
considering the customer’s satisfaction, the cost of the solution, and how the customer may use
the product in operations.
Ambiguity risks
Risks that have an uncertain, unclear nature, such as new laws or regulations, the marketplace
conditions, and other risks that are nearly impossible to predict.
Analogous estimating
- An approach that relies on historical information to predict the cost of the current project.
- Analogous estimating is more reliable, however, than team member recollections.
- Analogous estimating is also known as top-down estimating and is a form of expert judgment. It
is the least reliable of all estimating approaches.
Analysis
To develop possible solutions by studying the problem and its underlying need and to
understand the information provided.
Application areas
The areas of expertise, industry, or function where a project is centered. Examples of application
areas include architecture, IT, health care, and manufacturing.
Approved Iterations
After the deadline of iteration is reached, the team and stakeholders conduct a meeting for
approval. Stakeholders approve the iteration if the backlog used supports the product increment.
Artifact
A process or work output; e.g., documents, code
Assumption log
- An assumption is something that is believed to be true or false, but it has not yet been proven to
be true or false. Assumptions that prove wrong can become risks for the project. All identified
project assumptions are recorded in the assumption log for testing and analysis, and the
outcomes are recorded.
Authority power
Project management team members may have authority over other project team members, may
have the ability to make decisions, and perhaps even sign approvals for project work and
purchases.
Autocratic
A decision method where only one individual makes the decision for the group.
Automated testing tools
- These tools allow for efficient and strong testing. Examples: Peer Reviews, Periodical Code-
Reviews, Refactoring, Unit Tests, Automatic and Manual Testing.
Avoidance
A risk response to avoid the risk.
Avoiding power
The project manager refuses to act, get involved, or make decisions.
