Agile Bullets

See our list of terminologies  

A

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.

B

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.

C

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

D

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.

E

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.

F

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.

G

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.

H

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.

I

Impediment:
This is anything that inhibits or prevents a member of the scrum team from performing or delivering his or her task efficiently and effectively. Every member has a chance to say his or her impediment (obstacle) during their daily stand-up meeting.

The work of the Scrum Master is to ensure that all impediments/ obstacles are removed as soon as possible so as the team member can continue with the tasks assigned.

Iteration:
This is the time taken by agile scrum team members produce an increment of work done. This mostly takes 1week to 2 months.

All the phases of the product life cycle should be completed within this period. That is planning, design, coding testing, among others.

J

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.

K

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.

L

Lean Software Development:
This is software that is used to reduce wastages as well as optimizing software production.

M

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.

N

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.

O

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.

P

Portfolio Manager: A Portfolio Manager is a professional responsible for making investment decisions and carrying out investment activities on behalf of vested individuals or institutions.

Product Owner:
A product owner is one of the major roles in the scrum. The product owner has several roles.
 Setting up, fostering, and communicating the vision of scrum
 Creates and leads developers to offer the best value to clients
 Helps in monitoring and evaluation of projects regarding ROI as well as the vision
 Responsible for making all decision when todevelop and release work done

Product Backlog:
This is a list of work or the features that an organization wants to be done in the long run. It is a collection of tasks or stories that the scrum team would like to be done at a given time in the future.
It is the product owner’s role to retain this list of product backlogs according to the priorities of the business. All the items in the backlog ought to reflect the business goals and objectives.

Q

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.

R

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:
This is the planned schedule for releasing the software into production. Thisincludes the key characters to be delivered along with the date to be released.

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.

S

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.

Scrum Master:
Scrum Master oversees all the processes that the scrum team does, in addition to the overall health of the team. Scrum Master ensures that the team is fully functional and removes all the impediments that the team may be experiencing. The Scrum Master organizes the Scrum meetings and ceremonies.

Scrum Team:
This is a cross-functional team that is self-organizing and is responsible for the delivery of increment or software. It consists of multi-skilled individuals whounderstand the requirement for the customer and thenconduct softwaredesign, coding, and afterward testing.
Agile scrum team includes skilled individuals who understand customer needs. Theydesign, code, and test software. The scrum team oversees all work thatis doneand the outcomes.

Sprint:
In the product development cycle, a sprint is the time set during which specific work must be done and completed and made ready for release and review. Typically, a sprint length should be from two weeks and not more than four weeks.

Sprint Backlog:
Thisis a list of tasks, stories, or features that are split from the product backlog. It is done and completed in the next sprint.
Product backlog stories, features are broken down into smaller tasks for sprit backlog. This is done during a sprint planning meeting.

SCALED AGILE FRAMEWORK ENTERPRISE (SAFe):
This is an agile technique or methodology that is usedduring software development.

T

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.

U

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.

V

Velocity:
This is the measure of how much work a team can complete each interaction. Velocity is measured in story points. It is also measured in hours or an equivalent. It is time taken that the team can deliver outcomes.

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.

W

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.

X

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.

Y

YAGNI (You Aren’t Going to Need It) :
One of the XP principles is to avoid adding functionalities until they are needed, or it’s necessary. Always apply things whenever you require them, and not when you foresee that you require them.

Z

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.