Agile Business Analyst: An Agile business analyst is one who elicits, gathers, structures, documents and interprets complex business requirements in line with set agile principles and practice required to drive business solutions. The Agile business analyst supports the product owner and the scrum team throughout the project.
Agile Coach: An agile coach is a person with a deep understanding of agile principles and practice who helps teams and individuals with the adoption of agile.
Business Owner: A business owner is an individual with vested interest and knowledge of a system or process within a business unit or organization.
Business Analyst: A business analyst (BA) is someone who analyzes an organization or business domain (real or hypothetical) and documents its business or processes or systems, assessing the business model or its integration with technology.
From A to Z, our extensive agile terminology guide will help you navigate the world of agile project management with ease.
Agile Business Analyst: An Agile business analyst is one who elicits, gathers, structures, documents and interprets complex business requirements in line with set agile principles and practice required to drive business solutions. The Agile business analyst supports the product owner and the scrum team throughout the project.
Agile Coach: An agile coach is a person with a deep understanding of agile principles and practice who helps teams and individuals with the adoption of agile.
Business Owner: A business owner is an individual with vested interest and knowledge of a system or process within a business unit or organization.
Business Analyst: A business analyst (BA) is someone who analyzes an organization or business domain (real or hypothetical) and documents its business or processes or systems, assessing the business model or its integration with technology.
Agile Business Analyst: An Agile business analyst is one who elicits, gathers, structures, documents and interprets complex business requirements in line with set agile principles and practice required to drive business solutions. The Agile business analyst supports the product owner and the scrum team throughout the project.
Agile Coach: An agile coach is a person with a deep understanding of agile principles and practice who helps teams and individuals with the adoption of agile.
Acceptance criteria: A set of conditions a software feature must meet to be considered complete and acceptable by stakeholders.
Acceptance Test: Acceptance tests are conducted after development to ensure that the software features meet the acceptance criteria.
Agile : A software development approach that emphasizes iterative and incremental development, teamwork, and customer satisfaction.
Agile manifesto: The Agile Manifesto is a document that outlines the 12 principles that guide the Agile framework.
Agile Mindset : The Agile mindset is a set of attitudes that an Agile or Scrum team should have towards their work.
Agile Principle : Agile principles are guiding practices that help teams understand and adopt an Agile approach.
Agile transformation: Agile transformation involves transitioning an entire organization to adapt to the Agile mindset.
Business Owner: A business owner is an individual with vested interest and knowledge of a system or process within a business unit or organization.
Business Analyst: A business analyst (BA) is someone who analyzes an organization or business domain (real or hypothetical) and documents its business or processes or systems, assessing the business model or its integration with technology.
Bottleneck/Blockers : Bottlenecks/Blockers are issues that can completely slow down the development process.
Burndown Chart : A burndown chart is an essential tool for Agile project managers to track the progress of the work done by the scrum team.
Change Manager: A change manager plays a key role in ensuring projects meet objectives on time and on budget by increasing employee adoption and usage. This person focuses on the people side of change, including changes to business processes, systems and technology, job roles and organization structures
DBA: A DBA (Database Administrator) is a person charged with the role of creating, maintaining, backups, querying, turning, user rights assignment and security of an organization’s database.
Developer: A person who writes code, builds applications, systems and subsystems.
Daily Scrum : The daily scrum is a daily meeting where the team discusses their plans for the day. The Scrum master usually hosts it for 15 minutes to discuss the day ahead.
Enterprise Coach: An Enterprise Coach is a person with several years of experience in modern agile practices related to non-IT functions such as human resources (also called People Management or People Operations), finance, and control.
Epics : Epics are large features that can be broken down into smaller user stories. Much like how Novels are splitted into Trilogies.
Feature:
This is an attribute of a system, software product, or a logical business function. It may entail a unit or several requirements.
A single unit feature is usually executed through several stories. It may be a non-function or functional. It offers the basis for organizing stories.
Fibonacci sequence:
This is a sequence of numbers that the following number can be derived from by adding the previous two, (for instance1, 2, 3, 5, 8, 13, 21, 34, 55….). This sequence is used in agile estimation methodologies while planning stories.
Genba:
This is a Japanese term that means a real place. It is the location whereby value is being created. It is the place you go as it is where the real work is done. You can get first-hand information about what is really going on. It can be an office, workshop, etc.
Grit:
Means passion or perseverance of the long-term goals of an organization
Group:
This is a collection of people who share the same label (name) and haven’t formed a team that the members learn to work and trust each other.
How:
The term “how” is used to describe the domain of a team; it’s used as the role of a product owner. It can be used to describe static, for instance (how to do something)
Hybrid Development Processes Development:
This is a process used in both agile and non-agile practices. It can be used in conjunction with each other and has been proven amazingly effective in development teams.
Impediment: Impediments are obstacles that can reduce team productivity.
Iteration: An iteration is a period during which the team develops working software. An iteration generally lasts 2-4 weeks for Kanban and Scrum teams.
Just in time (JIT):
This is a feature of an agile process whereby all the activities of work and the assets required for a task became available just as they are required.
Kanban:
This is a tool that is derived from lean manufacturing. It’s linked to a branch of agile practices that is known as Lean Software Development. Kanban limits the work in progress that can be done at the same time.
The difference between scrum and kanban is that scrum limits work in progress using prints. Kanban limit work in progress, orhow much work can be done at the same time.
Kanban board:
This allows workflow. It is used as a visualization tool that summarizes the status, work in progress or any other issue related to work and workflow. It summarizes the status, progress, and issues related to the work.
Lean Software Development:
This is software that is used to reduce wastages as well as optimizing software production.
Lean : A set of principles and practices that aims to eliminate waste and increase efficiency in the development process. It was inspired by the lean manufacturing approach introduced by Toyota in the 50s.
Minimum Viable Product (MVP):
This is the smallest product that can be developed, tested, and delivered at a given time, and will offer value to its users
Network Administrator: A network administrator is a person responsible for keeping an organization’s computer network up-to-date and operating as intended.
Network Analyst: Network analyst is a somewhat broad term that is used to describe several fields of work related to computer networks. Those who work in this field might be referred to as network architects, web administrators and developers, and telecommunication specialists.
Network Engineer: A network engineer, also known as network architect, designs and implements computer networks. Unlike network administrators, who perform day-to-day support, the network engineer focuses on high-level design and planning.
Nonfunctional Requirements (NFR):
This describes system characteristics such as reliability, security, maintainability, usability, and scalability. They are restrictions or constraints that are used to design a system. They are typically re-examined every time. They exist in programs, backlogs as well as in the team.
Nice-to-have features:
These are the targeted features for an upcoming release. They can be excluded in case there are insufficient funds to finalize the project.
Operations Analyst: The operations analyst is a key member of the operations team supporting data management, client reporting, trade processes, and problem resolution. This person works closely with the Client Support Services manager and the operations team to ensure integrity of the data systems.
0utput measure:
This describes the number/ quantity that has been produced or created (for instance, the number of mobile devices produced in a certain period of time) or service that have been delivered(number of clients served)
Output measures don’t address the impact or value of work to external or either stakeholders. An example of O.M is velocity
(OpEx)
Operational expense:
This is the expenditure that a company incurs as it performs its daily/routine business operations.
It is the full cost of building/developing a product or a service or the costs incurred by buying something the same year that you incurred the cost.
Product Backlog : A prioritized list of features or items that the team plans to develop in the future, maintained by the product owner.
Product Manager : A product manager assists the Agile team with the development process from start to finish.
Product owner : The product owner decides the final software’s vision and features by carefully considering the customer’s needs and requirements.
Quality Analyst: A software quality analyst is responsible for applying the principles and practices of software quality assurance throughout the software development life cycle.
Queue:
This is a holding place for the item/ stock as they wait for the next cause of action in the process.
Refactoring:
This is changingthe codes of the existing software so as to improve the design. This doesn’t change the observable features but the internal structure of the software.
Release Plan:A release plan showcases all the features to be included in the next release and the estimated release date.
Retrospective:
This is the meeting that is held after every sprint. The scrum team examines all its processes to determine what succeededand any other improvement that can be done.
A retrospective meeting is a major factor for continuous improvement.During a retrospective meeting, the team must identify positive outcomes and that the team may work on in the next sprint, release, or iteration.
System Analyst: A systems analyst is a person who uses analysis and design techniques to solve business problems using information technology. Systems analysts may serve as change agents who identify the organizational improvements needed, design systems to implement those changes, and train and motivate others to use the systems
Systems Engineer: A person who focuses on how to design and manage complex systems over their life cycles.
Software Engineer: A software engineer is a person who applies the principles of software engineering to the design, development, maintenance, testing, and evaluation of a computer software
Sashimi:
This is a concept used in agile that means delivering value in slices rather than that stage or layers. For instance, agile story/sprint is sashimi since it can be proven that it’s done, while it’s not possible to prove requirement in a document when it is done.
Scrum:
This is a framework usedin developing complex software products during the iteration orincremental fashion. It is widely used in anagile framework. It is comprised of several series of iteration known as sprints.Each sprint ends after the delivery of an increment of working software.
Scaled Agile Framework : The Scaled Agile Framework (SAFe) is a methodology that enables large organizations to implement Lean and Agile practices across their software development teams. This approach unites teams to work on enterprise-scale software development.
Scrum : A framework for Agile software development that emphasizes teamwork, accountability, and iterative progress toward a well-defined goal. The team works in short bursts called sprints, typically lasting 2-4 weeks.
Scrum board : A Scrum board is a virtual or physical display that shows the tasks that must be completed within a sprint. This board is similar to a Kanban board.
Scrum master : The Scrum master is the leader of the Scrum, organizing meetings, removing impediments, and working with the product owner to ensure that the product backlog is up to date.
Scrum meeting : Scrum meetings are crucial for providing structure and a project plan for sprints.
Scrum of Scrums : The Scrum of Scrums is a special meeting for large Scrum teams. The ambassadors from smaller Scrum teams meet daily to discuss their progress and resolve issues.
Scrum team : The Scrum team is a cross-functional team of 5-10 individuals with different skill sets who work together to develop a product under the Scrum framework.
Sprint : A time-boxed period (usually 1-4 weeks) during which the development team works on a set of prioritized features and produces a potentially shippable product increment.
Sprint backlog : A sprint backlog is a list of features, bug fixes, user requirements, and tasks the Scrum team needs to work on during the sprint. During the sprint planning meeting, the product owner decides the backlog items that need to be added to the sprint backlog.
Sprint goal : the sprint goal is the desired result the Scrum team wants to achieve during the sprint.
Sprint planning : Sprint planning is a meeting where the team decides what work is necessary during the sprint. This includes breaking down items from the sprint backlog into smaller tasks. During the sprint retrospective, the team uses Agile metrics, charts, and reports to analyze their performance. In the sprint review, the Scrum team presents a working software model to stakeholders and receives feedback for the next sprint.
Sprint Retrospective: A meeting is held at the end of a sprint or project to reflect on what went well, what didn’t, and how the team can improve. The team uses Agile metrics, charts, and reports to see where they excel and where they need to improve.
Sprint review: A sprint review is a Scrum meeting where the Scrum team demonstrates a working software model to the stakeholders. Along with the product demo, the Scrum team prepares a presentation outlining the new features, bug fixes, and other changes.
At the end of the review, the stakeholder provides valuable feedback, which is implemented in the next sprint.
Stakeholder: Stakeholders are anyone outside the Agile team connected to the project, such as investors, account managers, sales teams, or clients.
Story points : Story points are a measure of effort required by the team to complete a project task, while a task board can refer to either a Kanban board or Scrum board.
Task:
This is the description of the actual job that is to be done by an individual or a teamto complete the story or the feature. Tasks are manageably doable and measurable pieces of work. Generally, there are severaltasksto be performed per story.
Timebox:
This is a fixed time length that is to be taken to achieve a certain objective.A timebox is time taken or a fixed time all given toaccomplishan objective. This is used in iterations, agile development, and sprints.
Task board : A generic Agile term that can refer to either a Kanban board or Scrum board
User Acceptance Tests:
These are tests done, and they must be executed to validate the specific function, meet the minimum requirements as outlined by clients. Several agile methods support the use of defined requirements that are specific to the user’s perspective, that is, user stories.
It is recommended that user acceptance have similar and definite validation steps as those used in the user perspective. They are essential requirements that clearly define acceptance criteria.
User Experience (UX):
It is the responsibility of agile teams to implement codes. This includes the user interface. User experience design is done at the program level that helps to offer a consistent user experience to the users.
Unit Testing :
This is the smallest part of the software that can be tested. In the process of programming, a unit can be a distinctive function or a process. Unit testing is vital in software development, and it should be automated to support incremental delivery of all requirements in agile software development teams. In most cases, it is the responsibility of the developer to do unit testing.
User story : A brief, simple description of a software feature from the user’s perspective that helps the team understand the user’s needs and expectations.
Velocity : It’s a unit of measurement that determines the amount of work your team can handle during an iteration.
Vision Statement :
This is a high-level description of products that includes the owner or to whom it belongs, as well as why it is important and what difference it has from other similar products.
What :
“What” is used to describe the domain of a product owner. It can be used to describe strategies that the product owner needs to do to achieve a certain goal, for instance, “What is the best way to do something.
Waterfall:
This is a project management technique that searches for detailed provisions upfront.
Work-in- Progress:
This is any work that is haven’t been completed and has already incurred some cost to the business. Any task that has already been deployed is considered a work in progress.
Work item : A work item is an Agile term that refers to the different types of work that need to be done within the project.
XP (eXtreme Programming):
This is an agile development approach that is used in software development. It allows programmers to make decisions on the scope and deliveries.
XP (eXtreme Programming):
This is an agile development approach that is used in software development. It allows programmers to make decisions on the scope and deliveries.
Zen:
This is a state of a meditative and absorbing mind.
Zombie Agile:
This is a blind devotion to agile practices, even without the adoption of a mindset needed to make them work.