Chapter 6 Flashcards
(18 cards)
Acceptance Criteria
The conditions that must be met before a project can be considered complete and the project deliverables are accepted by the client. In business analysis, a set of conditions or criteria that a product or solution must meet to be accepted by the customer or stakeholders. They are used to define the requirements and expectations for the product or solution, and to ensure that it meets the needs of the business end users.
Business Analyst (BA)
An individual who works as a liaison among stakeholders to understand the structure, policies, and operations of an organization, and to recommend solutions that enable the organization to achieve its goals.
Business Requirements
The high-level objectives or goals that a business seeks to achieve through a proposed project or initiative. Business requirements are used to define the overall purpose and scope for the project, and to establish a clear and measurable set of outcomes for the business.
Definition of Done (DoD)
The qualifications that are needed and defined for a product, user story, or increment of a product to be considered done. It’s important to define what constitutes “done” for each item in the product backlog, such as passing a specific test.
Definition of Ready (DoR)
A set of criteria that a user story or backlog item must meet before it can be considered ready to be worked on by the development team during the upcoming sprint or iteration. In the scrum framework, the DoR is a perspective in which a task can get directly taken up for a sprint without further clarifications or revisions.
Process Manager
The person who evaluates current business processes and designs, tests, and implements new processes to improve efficiency, profitability, and performance.
Process Owner
Anything that can be offered to a market to solve a problem or to satisfy a want or need. Products can be physical, like furniture or clothing, or digital, like an app or a video feature on a website.
Product Manager
A role on a Scrum team that is responsible for the product’s success. The product owner seeks to maximize a product’s value by managing and optimizing the product backlog. They are responsible for ensuring that the product meets the needs of the customer, and that the development team is working on the right features.
Product Roadmap
A high-level strategic plan that outlines the vision, direction, priorities, and progress of a product over time. It’s a plan of how the project will move from start to finish, with intermittent deliverables to the stakeholders. It answers what conditions must be met to allow the product owner to do a release, what the components of a release are, and the result of the project. It’s a plan of action that aligns the organization around short- and long-term goals for the product or project and how they will be achieved. The product roadmap is a big picture of the functionality of deliverables and the product vision. The product roadmap is a way of keeping your team and your stakeholders involved and keeps focus on the project result.
Prototyping
A technique of producing an example of the finished product, service, or result to seek feedback from stakeholders.
Rolling Wave Planning
A project planning technique that breaks down the project into smaller, more manageable increments. Each increment is planned in detail, but the details of later increments are only planned to a high level. This allows the project team to adapt to changes as the project progresses. Rolling wave planning uses waves of planning, then executing, and is a characteristic of adaptive projects.
Simulation
Imitating the operation of real-world processes or systems with the use of models to represent the key behaviors and characteristics of the selected process or system.
Solution Requirements
Specific characteristics that a product must have to meet the needs of the stakeholders and the business itself. For example: The solution must be able to process 1000 transactions per second.
Transition Requirements
A classification of requirements that facilitate transition from the current state (as is) to the desired future state (to be), but that will not be needed once the transition is complete. For example, the previous year’s data must be migrated to the new system to generate a comparative report.
Elicitation
The process of gathering and documenting requirements from stakeholders and subject matter experts. Elicitation involves using a variety of techniques and tools to identify, clarify, and document the needs and expectations of stakeholders.
Outcome
An end result or consequence of a process or project. Outcomes can include outputs and artifacts but have a broader intent by focusing on the benefits and value that the project was undertaken to deliver.
Value
The worth, importance, or usefulness of something. Different stakeholders perceive value in different ways. Customers can define value as the ability to use specific features or functions of a product. Organizations can focus on business value as determined with financial metrics, such as the benefits less the cost of achieving those benefits. Societal value can include the contribution to groups of people, communities, or the environment.
DEEP
An acronym for detailed, estimable, emergent, and prioritized, a concept used in business analysis to describe the characteristics of a well-defined requirement.
