Agile: A project management approach in which project phases overlap and tasks are completed in iterations
Authority: Refers to one's ability to make decisions for the project that impact the organization
Adoption: Refers to how the customer uses and adapts a product or service without any issues
Asana: A work management platform that helps teams plan and coordinate their work; useful for building project plans, assigning tasks, automating workflows, tracking progress, and communicating with stakeholders
Abandoned project: A project in which inadequate handoff or transition on the project deliverables occurs
Acceptance criteria: Pre-established standards or requirements that a product, service, or process must meet
Accessible: Something that is easily used, accessed, or adapted for use by people experiencing disabilities
Action item: A task that needs to be completed
Adoption metrics: Metrics that indicate whether or not a product, service, or process is accepted and used
Air cover: Support for and protection of a team in the face of out-of-scope requests or criticism from leadership
Analytics: The process of answering business questions, discovering relationships, and predicting outcomes based on the analysis of data
Acceptance criteria: The checklist the project manager uses to decide whether a story is done
Adaptation: Adjusting project, product, or processes to minimize any further deviation or issues; one of the three pillars of Scrum
Agile Manifesto: A collection of four values and 12 principles that define the mindset that all Agile teams should strive for
Agile project management: An approach to project and team management that embodies “agility” based on the Agile Manifesto
Ambiguity: A state where conditions and root causes of events or circumstances are unclear, leading to the possibility of misunderstanding
Accountability: Refers to being responsible for decisions associated with a project or ****task ****
Alignment: Reaching agreement between two or more parties ****