Agile Events, (formerly Agile Ceremonies), are several types of meetings prescribed within Agile frameworks.
Apache Kafka is used as a high-available messaging queue.
Automated Deployment is a practice that allows you to ship code fully or semi-automatically across several stages of the development process - from initial development right through to production.
Code Coverage (CC) measures how many, and which specific source code lines are being tested by automated tests (for example, unit or integration test).
A Code Review is a software quality assurance practice in which developers check each other’s code, usually before merging the code.
Commit Naming Rules
Commit messages have become a crucial part of the development process.
Continuous Delivery is a practice that enables you to release new product changes to your customers at any given time.
Continuous Integration (CI) is a practice of integrating code changes on a daily basis.
DevOps is a set of practices that combines the work of two teams: software development (Dev) and information technology operations (Ops).
Dockerizing is the process of packing, deploying, and running applications using Docker containers.
Documentation in a software project is a manual that describes the architecture of the software and provides helpful instructions to the users.
Documentation testing is a few processes of continuous feedback gathering and documentation improvements based on feedback.
Git is one of many VCS that are there in the market but it simply is the most popular among the developers.
Git Flow is one of many styles of Git workflows - a branching model set for Git.
Good Developer Experience
The Developer Experience (DX) describes the experience developers have while using or working on your product.
A handover is a process of transferring the roles and responsibilities of a project from one team/individual to another.
An icebreaker is an activity or game designed to "break the ice" between attendees in a meeting.
Infrastructure as Code
IaC is a principle (or process) of provisioning and managing your infrastructure through machine-readable definitions instead of using physical hardware configuration.
Kanban is an agile method similar to Scrum but it is less structured (no specific timeframe) and it is based on a list of items to do.
License in Repository
When you publish your source code repository, make sure to include a license.
Lint, or a Linter, is a very useful tool for automated analyzing of your source code to look for bugs and stylistic errors.
Many people decide to ignore the lock files and they do not commit it to Git.
Meaningful Meetings are spin-off on the classical, endless, and pointless meetings all people know and dislike.
Operations Logbook allows you to collect, store, and share data in real time and dig your historical data easily.
Package Managers are tools for automating the installation, upgrading, configuring, or removing of programs in a consistent manner.
Pair programming is a practice of two programmers working together on the same task at a single computer.
A Product Backlog is a prioritized list of work.
Product Backlog Refinement
Product Backlog Refinement is an act when the Product Owner (PO) in collaboration with the Development Team prioritizes the backlog items and adds details and estimates.
Proper Bug Reporting
Bug reports are descriptions of bugs found by testers - they help to understand where the product lacks its functionality or performance.
A pull request is a practice of getting feedback from other programmers and deciding to "merge" or "do not merge" the code before it is merged into the main codebase.
A README is a text file that introduces a product to a user.
You can see Refactoring as a controlled technique used for improving the design of existing code.
Release management is the process of going through the necessary steps to deploy a software build through different stages and environments; in preparation for its release.
Respectful Code Reviews
Code review helps you to improve the quality of software projects.
Response + ability, these two words combine to form a well known word Responsibility.
A retrospective is an opportunity for the team to inspect itself and create a plan for improvements to be included in the next Sprint.
Risk analysis is the process of defining your risks, analyzing their probabilities, and determining what impact they could have on your project.
A Runbook (also referred to as a playbook) is a compilation of procedures and operations that describe how to run a computer system or network.
SMART Goals is a tool that can be used to plan and achieve your goals – both personal and work ones.
Scrum is a framework focused on a productive and creative delivery of complex products with an emphasis on the highest possible value.
Semantic Versioning (SemVer) is the most popular system of versioning unique states of the project.
Software Development Kit (SDK)
A Software Development Kit (SDK) is an organized collection of software development tools that make it easier to create applications for a specific software or hardware platform.
The software documentation is a written text or an illustration that covers comprehensive information of the product.
Portability in high-level computer programming is the usability of the same software in different environments.
A Staged Rollout is a method of updating your application, while reaching only a certain percentage of users.
Some work has to go to every story in the product backlog.
As mentioned above it's a model, a simplified version of a system meant to test or present specific aspects of it.
A UX Strategy is a plan that supports the overall Business Strategy.
Unit testing is a way to test units - the smallest components of your software, the smallest piece of code.
Updating the Dependencies
Updating dependencies should be a regular part of your job.
A User Story (US) is the smallest chunk of work in an agile framework.
The Waterfall methodology is a linear project management approach where customer's requirements are collected at the beginning of the project.
YAGNI is an extreme programming principle (XP) which states that you must not implement features that you assume as significant in the future.