[{"title":"Agile","question":"What is Agile?","description":"A software development approach that values adaptability and continuous delivery.","date":"2024-11-10","categories":["agile"],"published":true,"slug":"agile","content":"

🔍 Definition

Agile is a software development philosophy focused on continuously delivering value to customers through adaptability, collaboration, and quick response to change.

🚀 Origin

The origin of Agile dates back to the early 2000s, marked by a crucial event in 2001: the creation of the Agile Manifesto.

🧠 Movement

It started as a response to the limitations and challenges faced by traditional project-based software development methods, known as waterfall methodologies, which were sequential and inflexible.

🔁 Approach

Agile is based on an iterative and incremental development approach where the scope is divided into small parts with frequent deliveries, allowing for adaptation to changing requirements.

🤝 Collaboration

Agile focuses on team collaboration and customer involvement throughout development.

📈 Benefits

It is known for improving product quality, employee and customer satisfaction, and development speed.

📚 Agile Frameworks

Agile encompasses and is related to various methods and frameworks such as Scrum, Kanban, and Lean.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Agile Coach","question":"What is an Agile Coach?","description":"It's someone who guides teams and organizations in agility.","date":"2024-11-10","categories":["role","agile"],"published":true,"slug":"agile-coach","content":"

🔍 Definition

An Agile Coach is an expert in agility who guides individuals, teams, and organizations in adopting agile principles and practices.

📅 Origin

The role of Agile Coach was coined by Kent Beck in 1999 in his book 'Extreme Programming Explained: Embrace Change'.

📈 Historical Development

The role initially focused on guiding teams in adopting agile practices and has evolved to include broader organizational transformation.

🪓 Responsibility

They facilitate the adoption of agile frameworks such as Scrum or Kanban, promote self-organization, and lead the organization's agile transformation.

🔑 Competencies

An Agile Coach must possess skills in facilitation, training, mentoring, communication, and change management.

🌐 Importance

Their role is crucial in helping organizations navigate the complexity of agile transformation and achieve sustainable change.

👤 Key Figures

Lyssa Adkins is one of the most notable figures in the development of the Agile Coach profession.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Agile Manifesto","question":"What is the Agile Manifesto?","description":"It is a statement of 4 values and 12 principles on new ways of developing software.","date":"2024-11-10","categories":["agile","scrum","kanban","manifesto","values","principles"],"published":true,"slug":"agile-manifesto","content":"

📜 Definition

The Agile Manifesto is a document created on February 12, 2001, by 17 software development experts, outlining a new approach to software development that prioritizes flexibility and customer collaboration.

🌐 Context

It was a response to the limitations of traditional software development methodologies, aiming to better meet the rapidly changing needs of users in the digital age.

🏔️ Location

The document was formulated at the Snowbird ski resort in Utah, USA. From this in-person session, the 4 values were born, and later the 12 principles were developed remotely.

💎 Values

First, it values human interactions over processes; second, it prioritizes working software over extensive documentation; third, it prefers direct collaboration with the client over contractual negotiations; and fourth, it emphasizes the importance of adapting to changes over following a plan.

🛠 Principles

The 12 principles of the Agile Manifesto complement its values, promoting frequent deliveries, change as a competitive advantage even in late stages, and building projects around motivated individuals. These principles aim at customer satisfaction, sustainability in development, and technical excellence.

📄 Accessing the Agile Manifesto

For a deep understanding of these values and principles that have revolutionized software development, it is recommended to read the Agile Manifesto directly. Access the complete document for free through this link to the Agile Manifesto.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"ALM","question":"What does ALM stand for?","description":"Stands for Application Lifecycle Management.","date":"2024-11-10","categories":["ALM","development","software","DevOps"],"published":true,"slug":"alm","content":"

📜 Definition

ALM, or Application Lifecycle Management, refers to the process of managing a software application from its initial design and development to its eventual retirement.

🔑 Key Aspects

It involves various stages such as the conception of the idea, design, development, testing, production, support, and eventual decommissioning.

📈 Importance

Understanding ALM is crucial for efficient software development, ensuring that the application meets business objectives and is successfully managed throughout its lifecycle.

🎯 Ideation

The initial phase where stakeholders define what they need from the application, often through user stories.

🛠️ Development

Teams work together to turn requirements into a functional application, including tasks like design, coding, and quality analysis.

🧪 Testing

The application is rigorously tested to ensure it meets the specified requirements and is free of defects.

🚀 Deployment

The developed and tested application is released to end-users, often involving version management and deployment planning.

🔧 Maintenance

An ongoing phase where support and development teams work together to address issues, plan updates, and improve the product.

🤖 Automation

Following the principles of the DevOps approach, many of the routine tasks of ALM should be automated to ensure their quality and establish them as a standard that ensures quality.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Antipattern","question":"What is an antipattern?","description":"A bad practice that reduces productivity, communication, or quality.","date":"2024-11-10","categories":["best practice","agile"],"published":true,"slug":"antipattern","content":"

🎯 Definition

An \"antipattern\" refers to a common problem or bad practice that hinders the successful implementation of an agile framework.

🚫 Impact

Antipatterns can lead to decreased productivity, low-quality deliverables, and failure to fully realize the benefits of agile practices.

🔍 Example

A common agile antipattern is the \"feature factory\", which focuses on delivering features without considering their real value.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","fi","fr","he","hi","hu","it","ja","ko","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"API","question":"What is an API?","description":"Stands for Application Programming Interface.","date":"2024-11-10","categories":["it","dev"],"published":true,"slug":"api","content":"

🤖 Definition

An API, or Application Programming Interface, is a set of rules and protocols that allows different software applications to communicate with each other.

## 🔗 Purpose\nAPIs act as a bridge between applications, enabling data and functionality exchange, and are essential for modern software and web applications.

## 🔄 Function\nAPIs function by defining how software modules interact: one application makes a request, and another provides a response, all following the rules set by the API.

🤝 Contract

To ensure consistency and security in communication, a services contract is defined between applications, outlining how requests and responses should be structured.

🌐 Web Services

All web services are APIs, but not all APIs are web services, as APIs can also be used for communication between local applications.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Asana","question":"What is Asana?","description":"It is a project management software that enables the implementation of the Kanban method.","date":"2024-11-10","categories":["tool","kanban","information radiator"],"published":true,"slug":"asana","content":"

## 🔍 Definition\nAsana is a project management software that helps teams organize, track, and manage their work.

🚀 Origin

Asana was co-founded by Dustin Moskovitz and Justin Rosenstein, both involved in leading engineering teams at Facebook. The beta version of Asana was officially launched in November 2011.

🧘‍♂️ Connection to Yoga

The word \"asana\" comes from Sanskrit and is used in yoga to refer to a posture or position.

## 📊 Functionality\nIt allows for task and project management, team collaboration, and goal tracking.

🌐 Accessibility

Asana is available online, making it convenient for remote and distributed teams.

🔄 Relation to Kanban

Asana facilitates the implementation of the Kanban method, acting as an information radiator by allowing tasks to be visualized on boards. These boards provide a clear view of the workflow and the progress of each task.

🔗 Access

To access Asana, visit their website

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"ASAP","question":"What does ASAP mean?","description":"As soon as possible.","date":"2024-11-10","categories":["expression"],"published":true,"slug":"asap","content":"

🔍 Meaning

ASAP means \"As Soon As Possible\" and is an acronym used to indicate the urgency of a request or task.

📧 Usage

Commonly used in emails to signal that something needs attention or completion urgently.

💬 Informal Context

It's also used in informal communication, such as text messages and chats, to convey the need for a quick response or action.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Backlog","question":"What is a Backlog?","description":"It is an ordered list of tasks.","date":"2024-11-10","categories":["scrum","agile","product"],"published":true,"slug":"backlog","content":"

## 📋 Definition\nA backlog is an ordered list of work for a development team that is derived from the roadmap and its requirements.

## 🔑 Importance\nIt serves as a list of a project's work items, helps plan iterations, and facilitates collective prioritization.

## 🎯 Prioritization\nBacklog items should be prioritized based on criteria such as customer value or the difficulty of implementation.

📝 Detailing

The most important items are detailed more, while less priority ones have fewer details and are typically at the bottom of the Backlog.

🔄 Living List

It is a living list that should change as development progresses on its items.

🏉 Scrum

In Scrum, there are two types of artifacts that employ the concept of Backlog: Product Backlog and Sprint Backlog.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"BDD","question":"What is BDD?","description":"BDD stands for Behavior Driven Development.","date":"2024-11-10","categories":["dev","it","bdd","software development","testing","gherkin","collaboration"],"published":true,"slug":"bdd","content":"

📜 Definition

Behavior Driven Development (BDD) is a software development process that aims to improve collaboration. It focuses on defining the behavior of the system from the user's perspective, using specifications written in natural language.

🌐 Context

BDD evolved from Test Driven Development (TDD), with a more user-oriented approach towards the requirements and system behavior. This approach helps ensure that software development is better aligned with the expectations and needs of the end user.

🏔️ Evolution from TDD

The transition from TDD to BDD is characterized by a shift in focus from tests based solely on code to tests based on the system's behavior from the user's perspective. This facilitates a deeper understanding of the user's needs and how the system should behave to meet them.

💎 Gherkin Language

BDD uses the Gherkin language to write specifications in a way that is understandable to both technical and non-technical team members. This allows the specifications to act as a shared source of truth, improving communication and reducing misunderstandings.

📄 Alignment

BDD promotes a shared understanding of the expected software behavior, ensuring that everyone involved, including non-technical stakeholders, has a clear understanding of the project's goals. This approach helps to avoid discrepancies between what the business needs and what the development team delivers.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Beta","question":"What is a beta version?","description":"It is a pre-release version of software made available to a select group of users for testing.","date":"2024-11-10","categories":["version","alpha","development","mvp","software","feedback"],"published":true,"slug":"beta","content":"

🔬 Definition

A beta version, also known as a preview, is a pre-release version of software made available to a select group of users for testing.

🛠️ Purpose

It allows developers to gather feedback, identify and fix bugs, and ensure the stability and functionality of the software before its official release to the public.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Backend for Frontend - BFF","question":"What is Backend for Frontend BFF?","description":"An architectural pattern that creates specific backend services for each type of frontend interface.","date":"2024-11-10","categories":["BFF","architectural pattern","backend services","user experience"],"published":true,"slug":"bff","content":"

🔄 Definition

Backend for Frontend (BFF) is an architectural pattern that involves creating specific backend services for each type of frontend interface, optimizing and adapting the backend to the unique needs of each frontend.

📱 Purpose

BFF is used to improve the user experience by customizing backend services to the requirements of different frontend interfaces, such as web, mobile, or third-party applications.

🔧 Implementation

BFF is implemented by introducing a layer of backend services that act as intermediaries between the main backend and the frontends, managing specific requests and responses for each frontend.

🚀 Benefits

BFF enhances adaptability, independence of frontend and backend teams, performance, and ease of evolution in software applications.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Blended Learning","question":"What is blended learning?","description":"It is an educational approach that integrates face-to-face instruction with online learning activities.","date":"2024-11-10","categories":["blended learning","b-learning","education","online learning","educational technology"],"published":true,"slug":"blended-learning","content":"

🔍 Definition

Blended Learning, also known as B-learning, is an educational approach that combines face-to-face instruction with online learning activities.

🎯 Purpose

This method aims to integrate the best of both educational worlds to enrich the learning experience of students.

💻 Online Component

The online part of the training does not replace in-person classes but complements them, providing a more flexible and interactive learning experience.

🔄 Flipped Classroom

The term Flipped Classroom refers to the learning approach where students learn new content at home through online resources and then apply it in class with the teacher's guidance.

📈 Benefits

Some of the benefits of Blended Learning include interaction, flexibility, student engagement, and accessibility.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Blue / Green","question":"What is Blue / Green deployment?","description":"It is a software deployment method that involves maintaining two identical production environments.","date":"2024-11-10","categories":["deployment","CI","CD","DevOps","ALM"],"published":true,"slug":"blue-green","content":"

🔄 Definition

It is a software deployment method that involves maintaining two identical production environments, with one environment (blue) running the current version of the application and the other (green) running the new version.

🚦 Traffic Switching

Only one environment is receiving live traffic at any given time, with all production traffic directed to it, while the inactive environment is used for testing and rolling out new changes.

🔁 Rollback

If issues arise with the new version, traffic can be instantly switched back to the previous live environment, minimizing downtime and risk.

🌐 Goal

The method aims to reduce downtime during deployments by instantly redirecting requests from one environment to the other.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Bottom-Up","question":"What is the Bottom-Up transformation approach?","description":"It involves transformation coming from the teams up to the higher layers of the organization.","date":"2024-11-10","categories":["transformation","agile","approach","empowerment"],"published":true,"slug":"bottom-up","content":"

⬆️ Definition

In Agile transformation, the Bottom-Up approach means that teams and individuals initiate Agile practices, with the transformation gradually permeating upwards, usually through management layers, across the organization.

👥 Empowerment

This method emphasizes empowerment and change at the team level, allowing for self-organization and the organic adoption of Agile principles.

📈 Progress

Bottom-up transformations often start with one or more pilot teams, allowing a step-by-step pollination approach to Agile implementation and the ability to adjust the process before scaling.

🚀 Flexibility

Teams can tailor the Agile approach to suit the specific needs of the organization, potentially leading to a more customized and effective transformation.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Bug","question":"What is a bug?","description":"It is an error in the code that causes a malfunction in the program.","date":"2024-11-10","categories":["bug","development","software","qa","test"],"published":true,"slug":"bug","content":"

🐛 Definition

In the context of software, a bug refers to an error or flaw in the code that causes a malfunction in the program.

💻 Origin

The term 'bug' was first used in 1889 by Thomas Edison to describe a technical problem, and since then has been adopted in computing to describe software issues.

🔍 Debugging

The process of finding and fixing bugs is called debugging, and tools known as debuggers are used by developers for this purpose.

💡 Importance

Bugs can have significant implications, from minor inconveniences to major security vulnerabilities.

🪲 Literal Meaning

The word bug literally means insect, and was humorously used to describe a technical problem when a moth caused an issue in a computer relay in 1947.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Build","question":"What is a build?","description":"It is the process of creating and compiling software, resulting in an executable version of the program.","date":"2024-11-10","categories":["software development","build","automation","software quality"],"published":true,"slug":"build","content":"

📜 Definition

In the field of software development, a build refers to the process of creating and compiling software, which results in an executable version of the program. This process is fundamental for the testing and debugging of software before its release.

📦 Outcome

The term 'build' also refers to the software version that is the outcome of the build process. This outcome is essential for different stages of testing and the final implementation of the software.

🔄 Automation

Builds can be automated using tools like Make, Gradle, Ant, or Maven, facilitating repetitive and reliable software construction. Build automation is crucial for maintaining efficiency and quality in software development.

🔍 Types

There are different types of builds, including development builds, test builds, and production builds, each serving specific purposes in the software development lifecycle.

👩‍💻 Importance

Builds are crucial for testing and debugging software before its release, ensuring its quality and functionality. They allow developers to identify and fix issues in the software before it is released to users.

🔍 Quality Assurance

Test builds are particularly important for QA (Quality Assurance) teams to ensure the software meets the required quality standards.

📈 Continuous Integration

The use of build automation tools in continuous integration (CI) processes helps maintain software quality and reliability, allowing for faster and more efficient delivery of updates and new features.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Burndown Chart","question":"What is a burndown chart?","description":"It is a visual representation of the amount of work remaining to be done over time.","date":"2024-11-10","categories":["scrum","metric","progress tracking"],"published":true,"slug":"burndown-chart","content":"

📜 Definition

A burndown chart is a visual representation that shows the amount of work remaining to be done over time, commonly used in Scrum to track the progress of a project.

⏳ Time vs. Work

This chart demonstrates the relationship between the amount of pending work and the time available to complete it, helping teams manage their work and meet established deadlines. The horizontal axis of the chart represents time, while the vertical axis represents the amount of work remaining.

🔄 Iterative Tracking

The chart is updated regularly, throughout the sprint, to reflect actual progress.

🎯 Ideal Trend

It includes a line representing the ideal progress, showing how the work should decrease over time if everything goes as planned.

📈 Actual Trend

The actual remaining work is plotted against the ideal trend, providing a clear visualization of the expectation to finish the planned scope.

🔧 Performance Analysis

The chart also serves as a tool to evaluate team performance and identify areas for improvement.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Burnup Chart","question":"What is a burnup chart?","description":"It is a visual representation of the amount of work completed over time.","date":"2024-11-10","categories":["agile","scrum","metrics"],"published":true,"slug":"burnup-chart","content":"

📜 Definition

A burnup chart is a visual representation that shows the amount of work completed over time, illustrating the cumulative progress towards the scope or goals of the project.

🔍 Interpretation

The x-axis represents time, typically in sprints or weeks, while the y-axis represents the amount of work completed, often in story points or other relevant metrics.

🎯 Purpose

It is used by teams to track and forecast progress, manage scope changes, and make data-driven decisions.

⬇️ Contrast with Burndown Chart

Unlike the burnup chart, the burndown chart tracks the remaining work instead of completed work, with the ideal scope line decreasing over time.

🔄 Scrum

The burnup chart is a tool commonly used in agile frameworks like Scrum to monitor and manage delivery.

🔢 Ideal Line

A straight line is drawn to represent the ideal scope, indicating the total work that needs to be completed.

♻️ Scope Changes

The chart is updated to reflect any changes in scope, adjusting the ideal scope line accordingly.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Business Agility","question":"What is Business Agility?","description":"It is the ability of an organization to adapt and respond to change.","date":"2024-11-10","categories":["business agility","adaptation","innovation","leadership","digital transformation"],"published":true,"slug":"business-agility","content":"

📜 Definition

Business Agility, or Corporate Agility, refers to an organization's ability to adapt and respond to change in a rapid, continuous, and systematic manner, staying profitable and outperforming its competition.

🔄 Adaptation

It involves creating and delivering new value to customers, successfully meeting their evolving needs, and thereby gaining a competitive advantage.

📈 Importance

Business Agility is crucial in today's digital age, where rapid and radical changes in the business environment require organizations to be flexible and resilient.

🎯 Customer-Centric

Business Agility involves a deep consideration of customer needs and a commitment to delivering value to them (Customer Centricity).

📊 Data

Recognizing the importance of data and leveraging it as a strategic asset is a key element of Business Agility.

🌐 Market Observation

Constant monitoring of the market is necessary to adapt to changing conditions and customer demands.

🔄 Decision Processes

Implementing agile decision-making processes that continuously assess business opportunities and initiatives.

📈 Portfolio Adjustment

A key to Business Agility is quickly adapting the portfolio of business initiatives to meet organizational objectives.

🛠️ Organizational Structure

An important part of the approach is the need to adapt the organizational structure to be more flexible and responsive to change.

💼 Leadership Focus

Business Agility emphasizes leadership in the context of digital transformation and the importance of agility in modern business.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Canary Release","question":"What is a Canary Release?","description":"It is a deployment strategy used to minimize risk.","date":"2024-11-10","categories":["release","DevOps","deployment","risks"],"published":true,"slug":"canary-release","content":"

🐤 Definition

A Canary Release is a deployment strategy used in software development to reduce the risk of introducing a new version by initially rolling it out to a small subset of users.

📅 Origin

The name originates from miners who would carry a canary in a cage down coal mines. If toxic gases leaked into the mine, the canary would die before the miners..

🔍 Monitoring

The system is carefully monitored for issues, and if the new version performs well, it is gradually released to more users.

🔄 Rollback

If issues are detected, the release can be rolled back, and the old version reinstated for all users.

👥 Selection

Different strategies are used to select which users will be exposed to the new version, such as random sampling or selection based on demographics.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"CD","question":"What is CD?","description":"Stands for continuous deployment.","date":"2024-11-10","categories":["release","deploy","DevOps","automation","alm","ci"],"published":true,"slug":"cd","content":"

🔄 Definition

Continuous Deployment, or Continuous Delivery, is a software engineering approach where code changes are automatically released to the production environment through a series of automated tests.

🛠️ Process

New code changes go through a test and inspection pipeline, and if they are approved, are directly deployed to the production environment.

🚀 Benefits

Continuous deployment accelerates the delivery of software, reduces the time to market for new features, and allows for faster feedback cycles.

🐞 Correction

Frequent deployments facilitate the finding and fixing of bugs, as bugs are more recent and easier to trace.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"CFD","question":"What is a CFD?","description":"Stands for Cumulative Flow Diagram.","date":"2024-11-10","categories":["kanban","CFD","metric","continuous improvement","kaizen"],"published":true,"slug":"cfd","content":"

📜 Definition

A Cumulative Flow Diagram (CFD) is a visual tool used in Kanban to track the performance of a system or team, showing the flow of work items through different stages over time.

🔍 Purpose

It provides insights into the stability and efficiency of the workflow, highlighting areas for improvement and helping to identify bottlenecks.

📈 Elements

The diagram consists of bands that represent different stages of the workflow, with the width of each band indicating the number of work items in that stage at any given time.

🔄 CFD Analysis

Trends in the CFD can be analyzed to understand delivery time, cycle time, work in process (WIP), and to identify irregularities or performance issues.

📏 Axes

The horizontal axis represents time, showing the progression of work items through the workflow while the vertical axis measures the quantity of work items, typically representing the WIP at each stage.

🔄 Lead Time

The CFD can be used to analyze Lead Time, which is the time it takes for a work item to move from start to finish.

🔄 Cycle Time

It also helps to understand Cycle Time, which is the time it takes to complete a single iteration of a work item.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"CI","question":"What does CI mean?","description":"Stands for Continuous Integration.","date":"2024-11-10","categories":["development","CI","automation","quality","ALM","DevOps"],"published":true,"slug":"ci","content":"

📜 Definition

Continuous Integration (CI) is a software development practice where developers regularly merge their code changes into a central repository, followed by automated builds and tests. It's a core practice of the DevOps philosophy.

🔨 Automation

CI involves both a cultural component, promoting frequent integration, and an automation component. Code changes trigger automated build processes to create executable software.

🚀 Goals

The key goals of CI are to find and fix errors quickly, improve software quality, and reduce the time it takes to validate and release new software updates.

🔄 Confidence

Frequent integration generates confidence that the code base is always in a functional state.

🔬 Test Coverage

CI should include a comprehensive set of automated tests to cover different aspects of the software and ensure its QA level.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"CI/CD","question":"What are Continuous Integration (CI) and Continuous Deployment (CD)?","description":"They are key practices in software development and central pillars of the DevOps approach.","date":"2024-11-10","categories":["CI","CD","DevOps"],"published":true,"slug":"ci-cd","content":"

🔄 Continuous Integration (CI)

CI involves the frequent integration of code changes into a shared repository and automating tests to ensure code reliability.

📦 Continuous Delivery (CD)

CD automates the process of testing and delivery of code changes, stopping just short of automatic deployment to production.

🔁 CI/CD Pipeline

A pipeline is a connected set of tests, processes, and checks that includes CI, CD, supported by the Agile mindset, DevOps approach, and SRE practices.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"CoE","question":"What is a CoE?","description":"Stands for Center of Excellence.","date":"2024-11-10","categories":["agile","center of excellence","Kaizen"],"published":true,"slug":"coe","content":"

📜 Definition

A Center of Excellence (CoE) is a strategic unit within an organization that provides expertise and specialized skills to promote and ensure excellence in the practices of its discipline.

🎯 Purpose

The primary purpose of a CoE is to drive the adoption, optimization, and governance of best practices. CoEs play a crucial role in influencing organizational culture towards continuous improvement.

🤝 Collaboration

CoEs collaborate with teams to disseminate knowledge and best practices, with the aim of improving the quality and consistency of the organization.

👩‍🏫 Services

Among the services of a CoE are training, process creation, playbooks, and mentoring.

📝 Governance Frameworks

CoEs establish governance frameworks to ensure proper implementation and adherence to best practices.

📈 Metrics

Often, CoEs measure the correct performance of their discipline's practices within the organization and identify areas for improvement.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Commitment Point","question":"What is the Commitment Point?","description":"It is the stage in the workflow where a work item is ready to be incorporated into the system.","date":"2024-11-10","categories":["kanban","commitment","efficiency","flow"],"published":true,"slug":"commitment-point","content":"

📜 Definition

A commitment point in Kanban is the stage in the workflow where a work item is ready to be incorporated into the system and flow through it, representing a commitment to work on and deliver the item.

🔄 Significance

It is a key concept for managing work in progress and ensuring that teams can release their committed work with greater predictability.

📊 Visual Representation

Commitment points are typically visualized as the dividing line between two columns on a Kanban board to provide clarity on the status of work items and help manage the workflow.

🛠️ Efficiency

By defining commitment points, teams can avoid overloading with too many items and maintain a balance between demand and capacity.

📝 Explicit Confirmation

Commitment points require explicit confirmation by the team that a work item is ready to be started and delivered.

🏉 Scrum

In Scrum, the equivalent of a Kanban commitment point is the creation of the Sprint Backlog.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Community of Practice - CoP","question":"What is a Community of Practice?","description":"It is a group of people who share a concern, a set of problems, or a passion about a topic.","date":"2024-11-10","categories":["CoP","learning","knowledge"],"published":true,"slug":"cop-comunidad-de-practicas","content":"

📜 Definition

A CoP (Community of Practice) is a group of people who share a concern, a set of problems, or a passion about a topic, and who deepen their knowledge and expertise in this area by interacting on an ongoing basis.

🔍 Purpose

CoPs are formed to facilitate learning, problem-solving, and the exchange of best practices within a professional or organizational context.

👥 Members

CoPs typically consist of members who are practitioners in a specific field and collaborate to develop a shared repertoire of resources, experiences, and tools.

📚 Origin

The concept of CoPs was first proposed by cognitive anthropologist Jean Lave and educational theorist Etienne Wenger in the 1990s.

👩‍🏫 Natural Formation

CoPs often emerge organically within organizations as practitioners with similar interests and challenges come together to collaborate.

📅 Evolution

Over time, CoPs develop their own identity, practices, and ways of working, often becoming an integral part of an organization's knowledge management.

🔧 Facilitation

Some organizations actively support the formation of CoPs by providing resources, leadership, and a platform for communication and collaboration.

📈 Practice

CoPs focus on the development and sharing of best practices and practical knowledge within their domain.

📚 Knowledge Management

CoPs are effective in capturing and disseminating tacit knowledge within an organization.

\n","language":"en","alternativeLangs":["ar","da","el","es","fi","fr","he","hi","hu","it","ja","ko","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Cost of Delay","question":"What is Cost of Delay?","description":"Represents the economic impact of a delayed delivery over time.","date":"2024-11-10","categories":["kanban","lean","SLA","metric","prioritization"],"published":true,"slug":"cost-of-delay","content":"

📜 Definition

The Cost of Delay (CoD) represents the economic impact of a delay in the delivery of a product or service.

📊 Significance

It is a key metric in lean management and the kanban method for prioritizing work, reducing waste, and understanding the impact of delays.

🎯 Purpose

To raise awareness of the financial impact of delays.

🔢 Calculation

Involves estimating the weekly revenue that the delivery would generate and dividing it by the project's duration.

➗ Technique

CD3 is a technique that helps prioritize a backlog. It is calculated by dividing the Cost of Delay by the project duration to obtain the order of magnitude for ordering each PBI (Product Backlog Item).

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Crystal Method","question":"What is Crystal Method?","description":"It is a framework that prioritizes people and their interactions over processes and tools.","date":"2024-11-10","categories":["framework","agile"],"published":true,"slug":"crystal-method","content":"

🔍 Definition

Crystal Method is a project management framework that prioritizes people and their interactions over processes and tools.

👨‍💻 Creator

Alistair Cockburn developed the Crystal method for IBM in 1991, in response to the need for a more flexible and adaptable project management approach.

🌐 Approach

Crystal is part of the Agile mindset, emphasizing adaptability and team collaboration.

📊 Color Coding

Crystal is divided into several color-coded groups based on team size, with each group having its own set of guidelines.

📜 Traits

The Crystal method is human-driven, adaptable, and ultra-lightweight, requiring minimal documentation and emphasizing flexibility.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Customer Centricity","question":"What does Customer Centricity mean?","description":"It is placing the customer at the center.","date":"2024-11-10","categories":["strategy","ux","culture"],"published":true,"slug":"customer-centricity","content":"

📜 Definition

Customer Centricity is a business strategy that prioritizes placing the customer at the center of all operations, with the goal of providing a positive experience and building long-term relationships.

📈 Importance

It is crucial for businesses as it can increase customer loyalty, improve retention rates, and ultimately achieve greater profitability.

📊 Use of Data

A key part of this approach is using customer usability and engagement data to understand their behaviors and preferences.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","no","pl","pt","ru","th","tr","zh"]},{"title":"Cycle Time","question":"What is Cycle Time?","description":"It is the duration it takes for an item to be completed in a given process.","date":"2024-11-10","categories":["kanban","metrics","cycle time","delivery rate","throughput","lead time"],"published":true,"slug":"cycle-time","content":"

📜 Definition

Cycle time refers to the time it takes for an item to go through the production or development process from start to finish. That is, from when active work begins on the item until it is ready to be delivered.

🆚 Difference with Lead Time

The main difference between Cycle Time and Lead Time lies in the scope of measurement.

📅 Measurement

Cycle time is measured by recording the start and finish dates and times of each item as it progresses through the board.

🔢 Calculation

The Cycle Time formula is (Completion Date - Start Date) + 1, to account for items finished on the same day they started.

🎯 Improvement

Strategies to improve Cycle Time include limiting work in progress and addressing bottlenecks.

📈 Average Cycle Time

Teams can use historical data to calculate the average cycle time of their process, aiding in future predictions.

📈 Performance Analysis

Regularly analyzing Cycle Time data can help identify improvement areas and validate the effectiveness of changes.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Disciplined Agile Delivery - DAD","question":"What is Disciplined Agile Delivery?","description":"It is a flexible approach to applying Agile.","date":"2024-11-10","categories":["agile","disciplined agile delivery","PMI","scaling"],"published":true,"slug":"dad---disciplined-agile-delivery","content":"

📜 Definition

Disciplined Agile Delivery (DAD) is a toolkit that provides a flexible approach to applying agile within organizations.

📅 Origin

Scott Ambler and Mark Lines are the co-creators of Disciplined Agile Delivery.

🔄 Evolution

Originally known as DAD, it has evolved into Disciplined Agile (DA) and is now considered a toolkit rather than a framework.

🔧 Flexibility

It is designed to be agnostic and pragmatic, allowing organizations to choose the best tools and approaches based on their specific context.

📚 Integration

Integrates various frameworks like Scrum, Kanban, XP, DevOps, and SAFe, while providing guidance on how to adapt and effectively use these practices.

📈 Acquisition by PMI

The Project Management Institute (PMI) acquired Disciplined Agile in 2019, aiming to enhance and promote its use.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"DDD","question":"What is DDD?","description":"It stands for Domain-Driven Design.","date":"2024-11-10","categories":["DDD","TDD","BDD"],"published":true,"slug":"ddd---domain-driven-design","content":"

📜 Definition

Domain-Driven Design (DDD) is a software development approach focused on creating high-quality software that meets business needs.

🎯 Primary Focus

DDD emphasizes placing the main focus of a project on the core logic and concepts of the business domain.

🤝 Collaboration

DDD promotes creative collaboration between technical and domain experts to ensure the model accurately reflects the business.

📚 Reference Material

The model serves as a reference for both business and technical teams, using a common 'Ubiquitous Language' to describe concepts.

🗂️ Model Artifacts

The model consists of various artifacts such as diagrams, documents, and prototypes that represent the business domain.

🔄 Synchronization

The model and the software design must be kept synchronized, with any changes in the design validated against the model.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Delivery","question":"What is Delivery?","description":"It is the delivery of software.","date":"2024-11-10","categories":["development","alm"],"published":true,"slug":"delivery","content":"

🔄 Definition

Delivery refers to the delivery of software by a team.

🎯 Focus on Value

For the Agile mindset, the frequent and early delivery of valuable software is crucial to obtain immediate feedback that allows taking advantage of adaptation as a competitive edge.

📈 Metrics

Some of the metrics used to measure a team's delivery capability are: Lead Time, Cycle Time, and Throughput.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Design Sprint","question":"What is Design Sprint?","description":"It is a process that allows the creation and testing of a prototype in just five days.","date":"2024-11-10","categories":["MVP","Product","innovation","Agile","Prototype","design sprint","validation"],"published":true,"slug":"design-sprint","content":"

🚀 Definition

Design Sprint is an agile product development process that allows the creation and testing of a prototype in just five days.

🔍 Origin

Design Sprint was developed by Jake Knapp and his colleagues at Google Ventures. Its origin dates back to an effort to accelerate the design and validation of ideas within startups and product development teams.

🗓️ Schedule

The process is typically divided into five key stages, each corresponding to a day of the workweek.

👩‍💻 Team

A small cross-functional team is required to work on the project, with roles such as the facilitator and decision maker being crucial.

📅 Monday — Understanding and Planning

Define the product goal and set realistic objectives.

🖊️ Tuesday — Sketching

Generate a variety of solutions and ideas through individual and group sketching sessions.

🔍 Wednesday — Decision Making

Evaluate and select the best ideas to follow, creating a storyboard for the chosen solution.

🛠️ Thursday — Prototyping

Build a high-quality prototype that can be tested with users.

🧪 Friday — Testing

Present the prototype in front of real users to collect feedback and validate the concept.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Design Thinking","question":"What is Design Thinking?","description":"It is a process for solving problems that focuses on understanding human needs and creating innovative solutions.","date":"2024-11-10","categories":["process","design thinking","innovation"],"published":true,"slug":"design-thinking","content":"

🎨 Definition

Design Thinking is a process for solving problems that focuses on understanding human needs and creating innovative solutions developed with a Customer Centricity alignment.

📚 Origin

Design Thinking originated at Stanford's d.school, with early works by John E. Arnold and Herbert Simon.

💡 Ideation

The process includes a brainstorming phase and idea generation to explore a wide range of possibilities.

🏗️ Prototyping

Ideas are quickly turned into tangible prototypes for testing and refinement.

📊 Testing and Feedback

Prototypes are tested with users to gather feedback and iterate on the design.

📈 Business Impact

Design Thinking is used not only for product design but also for innovation in business models and organizational change.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Developers","question":"What is a Developer?","description":"They are responsible for writing code to create, design, and maintain software applications.","date":"2024-11-10","categories":["development","scrum","role"],"published":true,"slug":"developer","content":"

💻 Definition

A Developer, also known as a software developer, is an expert in writing code to create, design, and maintain software applications, websites, or games for various devices.

📱 Importance

Developers are crucial in the digital era, with their skills being in high demand due to the rapid digitalization of markets and the need for innovative digital solutions.

🥷 Skills

They require advanced knowledge in programming languages, design technologies, and the ability to work on complex technical projects.

👨‍💻 Scrum

Developers in Scrum are the team members responsible for creating, designing, implementing, and delivering the software product.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"DevOps","question":"What is DevOps?","description":"It is a combination of the English terms development and operations.","date":"2024-11-10","categories":["DevOps","agile","development","operations","CI","CD"],"published":true,"slug":"devops","content":"

🛠️ Definition

DevOps is a software development philosophy that focuses on communication, collaboration, and integration between software developers and IT operations professionals.

🌐 Origin

The term DevOps was coined in 2009 with the presentation \"10 deploys per day\" by John Allspaw and Paul Hammond at the O'Reilly Velocity 09 event, but the movement actually began in 2007 when Patrick Debois, an independent consultant, experienced conflicts between development and operations teams.

📈 Evolution

DevOps has evolved to include practices like continuous delivery and continuous deployment, aiming to improve the quality, speed, and profitability of software.

🤝 Cross-functional Collaboration

DevOps requires a cultural shift towards collaboration and integration between traditionally isolated development and operations teams.

🔁 Continuous Integration

Continuous Integration (CI) is a key practice in DevOps involving automatic updates of code in a shared repository. Its goal is to quickly detect and fix errors, improve software quality, and accelerate delivery time.

🚀 Continuous Deployment

Another evolution of the DevOps paradigm is Continuous Deployment (CD), where code changes are automatically released into the production environment.

\n","language":"en","alternativeLangs":["cs","da","de","el","es","fi","fr","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Discovery","question":"What is Discovery?","description":"It is the process of determining what product or service to build.","date":"2024-11-10","categories":["innovation","agile","upstream","product","product backlog"],"published":true,"slug":"discovery","content":"

🔍 Definition

Discovery is the process of determining what product or service to build, focusing on validating user needs and identifying risks and opportunities.

🔄 Agile

Discovery is often used in conjunction with agile methodologies to ensure that the correct product is being built efficiently.

👥 Team Collaboration

It involves a cross-functional team working together to understand user contexts and challenges, and to create innovative and valuable solutions.

📈 Continuous Process

Discovery is not a one-time activity, but a continuous process that helps mitigate risks and make informed decisions.

🔄 Dual Track Approach

Discovery can be used in a Dual Track approach, integrating with agile practices such as Scrum to ensure that the developed product aligns with user needs.

📅 Initial Stage

It is typically performed in the early stages of the product development lifecycle, allowing for the validation of product ideas before significant resources are invested.

🛠 Lean Methodologies

Discovery often leverages lean methodologies to quickly test and iterate on ideas, aligning with the iterative nature of agile development.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"DoD - Definition of Done","question":"What is the Definition of Done?","description":"It is a set of criteria that determines when a user story has been completed.","date":"2024-11-10","categories":["scrum","user story","quality","agile"],"published":true,"slug":"dod-definition-of-done","content":"

🎯 Definition

The Definition of Done, DoD, is a set of criteria that determines when a user story is considered complete within the Scrum framework.

🛠️ Importance

It ensures that all work is finished according to a consistent standard for the team and is ready for release, providing transparency and ensuring quality.

🤝 Creation

If the organization does not have a defined DoD, it is the developers' responsibility to create it.

📈 Measurement

Allows for an objective assessment of completed work and helps manage team capacity and expectations.

📋 Visible Criteria

The DoD is typically documented as a checklist or list of criteria that is visible to the entire team and can be referenced throughout the sprint.

🌱 Evolution

The DoD is a living element that should improve and expand as more is learned.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"DoR - Definition of Ready","question":"What is the Definition of Ready?","description":"It is a set of criteria that defines the requirements an item must meet before being developed.","date":"2024-11-10","categories":["scrum","agreement","antipattern","DoD"],"published":true,"slug":"dor-definition-of-ready","content":"

🔍 Definition

The Definition of Ready, DoR, is a set of criteria agreed upon by the Product Owner and the Developers in Scrum, which outlines the requirements a Product Backlog item must meet before being selected for a Sprint Backlog.

📝 Criteria for Readiness

The DoR ensures that items are sufficiently refined, understood, and feasible for implementation, reducing the risk of delays and misunderstandings during Sprint Planning.

📝 Not Part of Scrum

Although not a formal part of the Scrum framework, the DoR serves, in some cases, as a collaborative tool, promoting communication and shared understanding between the Product Owner and the Development Team.

🚫 Antipattern

The DoR is considered an antipattern because it goes against the principles of empiricism in Scrum, hindering a team's ability to follow empirical process control and can become a barrier to communication and autonomy for the team.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Downstream","question":"What is downstream?","description":"Activities from the receipt of a request to its delivery.","date":"2024-11-10","categories":["lean","kanban","agile","upstream","cycle time","lead time"],"published":true,"slug":"downstream","content":"

⬇️ Downstream

Refers to the activities from the receipt of a request to the completion of the service for a customer in Agile and Lean philosophies.

🔄 Upstream

In contrast, upstream involves everything that happens before the actual execution, such as product discovery or backlog definition.

🔀 Kanban

Uses the concept of downstream to manage workflow, with a focus on visualizing and optimizing the entire process.

📈 Metrics

Some metrics used to observe the efficiency of upstream are Lead Time and Cycle Time.

📦 Scrum

Although not explicitly named, Scrum also implies upstream activities through the management of the Product Backlog by the Product Owner.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"DRY","question":"What does DRY mean?","description":"DRY stands for Don't Repeat Yourself.","date":"2024-11-10","categories":["DRY","development","principles","maintainability","scalability"],"published":true,"slug":"dry---dont-repeat-yourself","content":"

📚 Principle Definition

DRY stands for 'Don't Repeat Yourself' and is a software development principle that emphasizes reducing repetitive patterns and duplicated code in favor of modular and referable code.

👨‍💻 Origin

Coined by Andy Hunt and Dave Thomas in 'The Pragmatic Programmer', DRY aims to ensure that each piece of knowledge has a single, unambiguous representation within a system.

⚙️ Importance

Writing DRY code is essential for maintainability, scalability, and to avoid the opposite, WET code ('Write Everything Twice').

🔍 Rule of Three

A good general rule for DRY code is the 'Rule of Three', which suggests abstracting code into a reusable unit the third time a certain pattern is encountered.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Dual Track","question":"What is Dual Track?","description":"It is an approach that combines product discovery with its delivery simultaneously.","date":"2024-11-10","categories":["discovery","delivery","upstream","downstream","scrum","agile"],"published":true,"slug":"dual-track","content":"

🔍 Definition

A project management approach that combines the iterative and flexible nature of Agile by separating upstream and downstream activities.

🔄 Origin

The concept of Dual Track was first mentioned in 2005 by Lynn Miller, with further elaboration by Desirée Sy in 2007, and formalized as 'Dual-Track Agile' by Marty Cagan and Jeff Patton in 2012.

👁️ Discovery

During the upstream phase, a part of the team, generally including the Product Owner and team members with User Experience (UX) roles, focuses on understanding user needs, prototyping, and testing solutions before proceeding with development.

🚀 Execution

During the downstream, developers materialize the ideas from discovery into product increments.

🤝 Synchronization

Both tracks work in parallel, aiming to synchronize their efforts to ensure a sustainable and efficient workflow.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Engineer Manager","question":"What is an Engineer Manager?","description":"They are experienced engineers who lead technical activities and manage teams of engineers.","date":"2024-11-10","categories":["collaboration","leadership"],"published":true,"slug":"engineer-manager","content":"

👩‍💼 Role Definition

An Engineer Manager is an experienced engineer who leads technical activities and manages teams of developers.

🔧 Technical Leadership

They are responsible for making data-based technical decisions and overseeing the execution of technical and design operations.

👥 Team Management

In addition to technical tasks, they oversee and guide several engineering teams, ensuring projects are completed efficiently and according to schedule.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Expedite","question":"What does expedite mean?","description":"These are high-priority work items that require immediate attention.","date":"2024-11-10","categories":["kanban","urgency"],"published":true,"slug":"expedite","content":"

⏱️ Definition

In Kanban, expedite refers to work items that require immediate attention due to their urgency, often interrupting the normal flow of work.

🚀 Board

Teams can use an expedite lane in their Kanban Board to visually separate and prioritize urgent work items, allowing them to be worked on outside the regular process constraints.

📈 Impact

An excess of urgent items can negatively affect the team's delivery capacity.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Extreme Programming - XP","question":"What is Extreme Programming?","description":"It is an agile software development framework that focuses on frequent feedback and continuous improvement.","date":"2024-11-10","categories":["downstream","agile","kaizen","tdd"],"published":true,"slug":"extreme-programming---xp","content":"

🔍 Definition

Extreme Programming or XP is an agile software development framework that focuses on frequent feedback and continuous improvement, involving practices such as pair programming and collective code ownership.

📅 Origin

Extreme Programming (XP) was developed by Kent Beck, a promoter and signer of the Agile Manifesto, in the 1990s as a response to the challenges of software projects with tight deadlines. Beck introduced XP in his book \"Extreme Programming Explained: Embrace Change\" in 1999, an agile framework focused on continuous improvement, adaptability, and team collaboration.

📈 Quality

XP aims to deliver high-quality software through testing and simplicity.

🔍 Simplicity

XP advocates for the simplest solutions that work, avoiding unnecessary technical complexity.

💎 Courage

Encourages team members to take risks and make necessary changes without fear.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"FDD","question":"What is FDD?","description":"FDD stands for Feature Driven Development.","date":"2024-11-10","categories":["FDD","BDD","DDD","TDD","feature"],"published":true,"slug":"fdd---feature-driven-development","content":"

🔍 Definition

Feature Driven Development, or Development Guided by Features, is an agile software development approach that focuses on customer-valued features, emphasizing short iterations and frequent releases.

🎯 Key Principle

FDD requires the delivery of a feature every 2-10 days, ensuring that customer needs are continually met.

🔄 Iterative Process

FDD involves a series of five key processes, including creating the feature list, planning, design, and build, all within a customer-centered framework.

🛠️ Team Roles

FDD defines specific roles such as the Chief Architect, Chief Programmer, Domain Expert, Development Manager, Deployer Technical Writer, Domain Manager, Language Guru, Tester, and other support roles emphasizing individual and team responsibilities in feature development.

🔀 Differentiation from Scrum

FDD is feature-centered, whereas Scrum focuses on delivering a product increment.

📈 Customer Involvement

FDD requires active participation from the customer.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Features","question":"What is a feature?","description":"It is a distinctive portion of functionality that delivers value.","date":"2024-11-10","categories":["agile","mvp","scrum","product backlog","FDD","feature flag"],"published":true,"slug":"feature","content":"

🔍 Definition

A feature, or characteristic, is a portion of functionality that delivers value to the user. It is a high-level requirement that can be broken down into smaller user stories.

📈 Importance

Features help to organize and prioritize development work, allowing teams to focus on delivering concrete functional value.

👨‍💼 Ownership

The Product Owner is typically responsible for defining, managing, and ordering features within the product backlog.

🔄 Relationship

Features are often composed of multiple user stories, which are the more granular units of work within agile development.

🚀 Release

The Product Owner is responsible for deciding which features to include in each release based on business value and customer needs.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Feature Flags","question":"What is a Feature Flag?","description":"It is a technique that allows enabling or disabling functionalities.","date":"2024-11-10","categories":["development","CI","CD","A/B Testing"],"published":true,"slug":"feature-flag","content":"

🚩 Definition

Feature Flags, also known as Feature Toggles, are a technique that allows developers to enable or disable certain functionalities in a software application without changing the codebase.

🔧 Implementation

They can be implemented using boolean values in configuration files that are conditionally checked to determine whether a functionality should be visible and active or not.

🎯 Use Cases

They are used in Continuous Deployment (CD) approaches, Canary Releases, A/B Testing, and to manage the visibility of functionalities for different user segments.

💡 Benefits

Feature Flags allow for safer and more efficient development, enabling teams to deploy and test new features without impacting the entire user base.

📈 Growth

The use of Feature Flags has grown in popularity with the rise of Agile, DevOps, and continuous delivery practices in software development.

📝 Configuration

They can be defined using a service like Bullet Train or Launch Darkly, creating a custom backend service, or using local files within the application.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Feedback","question":"What is feedback?","description":"Feedback is a response given to some stimulus as a way to evaluate it.","date":"2024-11-10","categories":["feedback","communication"],"published":true,"slug":"feedback","content":"

🔊 Definition

Feedback is a response given to some stimulus as a way to evaluate it.

♻️ Relation to Agile

Agile promotes early feedback acquisition to use it as a competitive advantage through adaptation to change.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Fibonacci Sequence","question":"What is the Fibonacci Sequence?","description":"It is an infinite series of natural numbers.","date":"2024-11-10","categories":["estimation","effort","complexity","planning poker"],"published":true,"slug":"fibonacci","content":"

🔢 Definition

The Fibonacci Sequence is an infinite series of natural numbers where each term is the sum of the two preceding ones, starting with 0 and 1 or 1 and 1.

🌿 Design in Nature

The sequence is observed in natural phenomena such as the spiral patterns of shells and the arrangement of leaves on plants.

🎯 Agile Estimation

The Fibonacci Sequence is commonly used in agile techniques for estimating effort and complexity, such as planning poker.

🧮 Example

0, 1, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89...

💻 Applications

It has practical applications in fields like computing, game theory, and is used as a tool in the analysis of financial markets.

📏 Golden Ratio

The ratio of consecutive Fibonacci numbers approximates the Golden Ratio, a mathematical concept often associated with aesthetic beauty.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Figma","question":"What is Figma?","description":"It is a graphic design and prototyping tool.","date":"2024-11-10","categories":["collaboration","design","UX","UI"],"published":true,"slug":"figma","content":"

🎨 Design Tool

Figma is a graphic design and prototyping tool widely used in the design and development of user interfaces (UI).

🤝 Collaboration

Figma allows for real-time collaborative work, enabling team members to work together.

💻 Usability

Known for its intuitive and user-friendly interface, Figma is popular among UX/UI designers and design agencies for creating prototypes and mockups.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"FOMO","question":"What is FOMO?","description":"It stands for Fear of Missing Out.","date":"2024-11-10","categories":["psychology","product","innovation"],"published":true,"slug":"fomo","content":"

🔍 Definition

'FOMO' stands for 'Fear of Missing Out' and is a psychological condition characterized by a constant desire to stay connected with what others are doing, particularly through social media.

😟 Consequences

The condition can lead to anxiety, depression, and sleep disorders as individuals feel compelled to constantly check for updates and interactions.

📚 Origin

The term 'FOMO' was first used in the late 90s and originally referred to the fear of missing out on social plans.

🌐 Evolution

With the rise of social media and digital connectivity, FOMO has evolved into a broader anxiety related to feeling left out of experiences others are having.

👥 Social Connection

FOMO is now understood as a form of social anxiety, where individuals seek constant connection to avoid feeling excluded.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Forecast","question":"What is a Forecast?","description":"It is the estimation and tracking of future sales.","date":"2024-11-10","categories":["metrics","forecast","predictability"],"published":true,"slug":"forecast","content":"

📈 Definition

A Forecast is the estimation and tracking of future sales of a product, typically using historical sales data and inputs from sales and marketing teams.

🔍 Purpose

To predict short and medium-term sales, detect problems early, find solutions quickly, reduce inventory, and improve customer service.

📊 Methods

Forecasting can be done using both quantitative and qualitative data.

📊 Quantitative Data

Uses historical sales data as a basis for predicting future sales, but does not guarantee future performance.

🧮 Qualitative Data

Relies on subjective assessments within the company, such as from sales and marketing teams, to inform the forecast.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Framework","question":"What is a framework?","description":"It is a system of rules, ideas, or beliefs used for planning, agreeing, or deciding something.","date":"2024-11-10","categories":["scrum","agreements","team","shared understanding"],"published":true,"slug":"framework","content":"

🏗️ Meaning

A Framework, or work frame, is a supporting structure around which something can be built, or a system of rules, ideas, or beliefs used for planning or deciding something.

💻 Context

In computer systems, a framework is an actual or conceptual structure intended to serve as a support or guide for the construction of software applications.

📚 Conceptual Structure

A framework can be a basic conceptual structure of ideas or a set of rules used for planning.

📝 Examples

Scrum is an Agile framework and Laravel is a framework for the PHP programming language.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"FYI","question":"What does FYI mean?","description":"It stands for For Your Information.","date":"2024-11-10","categories":["communication","acronyms"],"published":true,"slug":"fyi","content":"

📝 FYI

For Your Information, or para tu información, is a common acronym used in both professional and informal communications to signal information that is relevant to the recipient.

🗨️ Use

It is often used to prefix a message or subject line to indicate that the content is provided for the recipient's knowledge.

📧 Email

In email communication, FYI is often included in the subject line or body of the email to indicate that the content is informative and does not require a response.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Gemba","question":"What is Gemba?","description":"It's a Japanese term that refers to the 'real place' or the 'place where action happens'.","date":"2024-11-10","categories":["gemba","lean","kaizen"],"published":true,"slug":"gemba","content":"

🏭 Definition

Gemba is a Japanese term that refers to the 'real place' or the 'place where action happens' in a business context.

💼 Application

In business, Gemba is where value is created, such as where the operators are in a factory or the sales area in a retail environment.

🔄 Lean Management

Within Lean Management, Gemba is the focus of continuous improvement efforts, with the belief that problems are best understood and solved at the place where they occur.

📈 Connection to Kaizen

Gemba is closely related to the concept of Kaizen, which is the philosophy of continuous improvement.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Gherkin","question":"What is Gherkin?","description":"Gherkin is a language used to specify the behavior of software systems in a way that is easy to understand for non-technical stakeholders.","date":"2024-11-10","categories":["gherkin","behavior-driven development (BDD)","test automation"],"published":true,"slug":"gherking---given-when-then","content":"

📝 Definition of Gherkin

Gherkin is a language used to specify the behavior of software systems in a way that is easy to understand for non-technical stakeholders.

🧪 Testing Method

It is particularly associated with Behavior-Driven Development (BDD) and is used to design test cases.

➡️ Syntax

Gherkin has a specific syntax with keywords like Feature, Scenario, Given, When, and Then, which are used to structure test descriptions.

🔄 Automation

Gherkin is often used in conjunction with tools like Cucumber for test automation.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Git","question":"What is Git?","description":"It is a distributed version control system.","date":"2024-11-10","categories":["git","development","ALM"],"published":true,"slug":"git","content":"

🔄 Definition

Git is a distributed version control system that allows for efficient tracking of changes in files, particularly in software development.

🔗 Repository

Each developer's local copy of a project is a complete repository, allowing for offline work and facilitating remote collaboration.

🔀 Merging

Git provides tools for merging different branches, resolving conflicts, and maintaining a clean repository history.

🌐 Flexibility

Git's design supports non-linear development, with powerful branching and merging capabilities.

🔒 Data Integrity

Git uses cryptographic hashes to ensure the integrity of the stored data, making it difficult to alter or lose information.

📈 Popularity

Git has become the global standard for version control, widely used in both open source and commercial software projects.

📝 Commits

Git creates a snapshot of all files with each save, called a commit, forming a graph of the development history.

🌿 Branches

Developers can work on separate branches and then merge their work back into the project's main branch.

🔍 Revert

It is possible to revert code to a previous commit, inspect changes in files, and review information like when and where changes were made.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"GitFlow","question":"What does GitFlow mean?","description":"It is a branching model for Git.","date":"2024-11-10","categories":["gitflow","git","branches"],"published":true,"slug":"gitflow","content":"

🔄 GitFlow

GitFlow is a branching model for Git that assists in managing project branches and releases.

🚀 Origin

GitFlow was developed by Vincent Driessen and has become a widely adopted workflow for software development.

🔗 Branch Organization

Branches are organized into main (e.g., 'main') and development (e.g., 'develop') branches, along with feature branches, release branches, and hotfixes.

🔄 Initial Proposal

Initially proposed as a branching model, GitFlow has evolved into a supported tool with specific commands.

📜 Refinement and Adaptation

Over time, GitFlow has been refined and adapted by development teams to meet their specific needs and workflows.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"GitHub","question":"What is GitHub?","description":"It is a platform for hosting and managing code.","date":"2024-11-10","categories":["github","git","gitflow","collaboration","development","version control"],"published":true,"slug":"github","content":"

🖥️ Definition

GitHub is a platform for developers to host and manage their code, offering both public and private repositories.

🤝 Collaboration

It provides tools for collaborative development, allowing multiple users to work on the same codebase.

🔍 Version Control

GitHub uses Git, a version control system, to track changes in code and manage different versions of the project.

💻 Services

GitHub offers additional services like issue tracking, code review, and software management tools.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Hype","question":"What is Hype?","description":"It is a strong expectation for something new.","date":"2024-11-10","categories":["hype","marketing","product"],"published":true,"slug":"hype","content":"

🔊 Hype

Hype refers to excessive or exaggerated excitement, often used in the context of marketing by the public about a feature, product, or novelty.

📈 Example

A product being heavily hyped may have its features or benefits overstated to generate interest and sales.

📚 Origin

The term derives from the English word 'hyperbole', which is a literary figure that exaggerates or overvalues something.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Impact Map","question":"What is Impact Mapping?","description":"It is a technique used to focus on the goals and how to achieve them.","date":"2024-11-10","categories":["impact mapping","design thinking","strategy","product","roadmap"],"published":true,"slug":"impact-mapping","content":"

🎯 Definition

Impact Mapping is a visual technique used to help teams focus on the goals they want to achieve and how to achieve them.

🔄 Iterative Process

It is often applied in the early stages of development to create a strategic plan and a product roadmap.

🧠 Collaborative Tool

Impact Mapping involves all stakeholders in a collaborative discussion to prioritize actions that will have the most significant impact.

📈 Four Levels

The technique is structured around four levels - Goals, Actors, Impacts, and Deliverables - to map the connections between the 'Why', 'Who', 'How', and 'What'.

🎯 Goals

The first step in Impact Mapping is defining the overall goal, ensuring it is Specific, Measurable, Actionable, Realistic, and Time-bound (SMART).

👥 Actors

Identify key actors or stakeholders who can influence the success of the project, avoiding generic terms like 'users' and being specific about user categories or roles.

💥 Impacts

Determine how the identified actors can help achieve the project goals and the specific impacts that will contribute to success.

📦 Deliverables

List the high-level features or characteristics that need to be developed, which can serve as an initial product roadmap.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Ishikawa","question":"What is an Ishikawa diagram?","description":"It is a tool used to identify the possible causes of an event or problem.","date":"2024-11-10","categories":["Ishikawa diagram","kaizen","retrospective","post-mortem"],"published":true,"slug":"ishikawa","content":"

📊 Definition

An Ishikawa diagram, also known as a fishbone diagram, is a visualization tool commonly used in post-mortem or retrospective sessions to identify and categorize the possible root causes of a specific event or problem.

🐟 Origin

The diagram is named after its creator, Kaoru Ishikawa, and is called a fishbone diagram due to its resemblance to the skeleton of a fish.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Jira","question":"What is Jira?","description":"It is an application for project management.","date":"2024-11-10","categories":["jira","tool","project"],"published":true,"slug":"jira","content":"

🔍 Definition

Jira is a proprietary software application developed by Atlassian for issue tracking and project management.

📈 Purpose

It is used by teams to plan, track, and support software, providing a single source of truth for the entire development lifecycle.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Junior","question":"What is a junior?","description":"It is a developer with some knowledge of the language and the technology stack.","date":"2024-11-10","categories":["senior","junior","developer","role"],"published":true,"slug":"junior","content":"

👨‍💻 Role Definition

A junior developer typically has 0 to 3 years of experience, with some knowledge of the language and the technology stack used. However, years of experience are not determinative in defining a developer's expertise.

💼 Responsibilities

Junior developers often work on smaller, less critical tasks under the guidance of more experienced or senior team members.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"JIT - Just In Time","question":"What is Just In Time?","description":"It is a strategy that aims to align raw material orders with production schedules.","date":"2024-11-10","categories":["toyota","lean","jit"],"published":true,"slug":"just-in-time---jit","content":"

⏱️ Definition

Just In Time (JIT), or Just In Time, is a management strategy that aims to align raw material orders with production schedules, receiving goods as close as possible to when they are needed.

🏭 Origin

JIT was developed by the Japanese automobile manufacturer Toyota in the 1970s as part of its Toyota Production System.

💰 Benefits

JIT minimizes the need to store large inventories, leading to efficiency and cost savings, but can present risks during supply or demand shocks.

🔄 Process

JIT requires constant monitoring of demand and uses methods such as Kanban to facilitate continuous improvement in streamlining, efficiency, and quality.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Kaizen","question":"What is Kaizen?","description":"It means good change or improvement.","date":"2024-11-10","categories":["kaizen","continuous improvement","toyota","lean"],"published":true,"slug":"kaizen","content":"

📈 Definition

Kaizen is a Japanese term that translates as \"good change\" or \"improvement\", and it's a business philosophy focused on continuous improvement.

🏭 Origins

Developed in post-war Japan, kaizen was influenced by American teachings on quality management and was notably implemented by Toyota.

🔄 Methodology

Kaizen involves all employees in the gradual and continuous improvement of various areas of a company, aiming to eliminate waste and improve processes.

🔧 Tools

The kaizen philosophy utilizes various tools like 5S for workplace organization, JIT and Kanban for inventory control, and value stream mapping for waste elimination.

📚 Expansion

Management consultant Masaaki Imai introduced kaizen globally in 1986 through his book \"Kaizen: The Key to Japan's Competitive Success\".

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Kanban","question":"What is Kanban?","description":"It is a Lean method to optimize workflow processes.","date":"2024-11-10","categories":["kanban","agile","lean","services","pull system","flow","wip","kaizen"],"published":true,"slug":"kanban","content":"

🔖 Definition

Kanban is a lean method for managing and improving work flows in production and development processes. It focuses on continuous delivery without overloading the work team, using a visual system to monitor task progress.

🏭 Origin

Initially developed in the 1940s by Toyota, Kanban is part of the Lean Manufacturing system. Its goal is to optimize production processes by visualizing work and reducing waste.

🔄 Evolution

Originating in manufacturing, Kanban has spread to software development and other fields thanks to the promotion by David J. Anderson. Its focus on efficiency and continuous improvement highlights its adaptability and value across different environments.

🔍 Visual Management

Teams use Kanban boards to visualize their work and track progress, often with columns like \"To Do\", \"In Progress\", and \"Done\".

🔄 Continuous Improvement

Kanban promotes the identification and resolution of problems in the work process, allowing for continuous and efficient improvement, advocating the Kaizen philosophy.

🔒 Limitation of Work In Progress

One of the key practices of Kanban is limiting WIP (Work In Progress) to improve team focus and efficiency, reduce Lead Time, and increase the quality of the delivered work.

🔄 Pull System

The pull system in Kanban encourages finishing tasks before starting new ones, focusing on actual capacity and demand. This approach improves value delivery and efficiency by ensuring that one piece of work is completed before taking on another, simplifying workflow management from right to left.

🛠 Tools

Some of the most popular digital tools for implementing the Kanban method are: Trello, Asana, and JIRA.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Kanban Board","question":"What is a Kanban Board?","description":"Visually represents work at various stages of a process using cards and columns.","date":"2024-11-10","categories":["Kanban","Lean","Information Radiator"],"published":true,"slug":"kanban-board","content":"

📊 Definition

A Kanban Board, or Kanban board, is a tool that visually represents work at various stages of a process using cards and columns.

🔢 WIP Limit

It is designed to help teams maximize efficiency by setting limits on work in progress (WIP).

👥 Team Coordination

Kanban boards help coordinate teams by providing a clear view of the work that needs to be done, any blockages or impediments, and work that is in progress or completed.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"KISS","question":"What does KISS mean?","description":"It is an acronym for Keep It Simple, Stupid!","date":"2024-11-10","categories":["KISS","design principle"],"published":true,"slug":"kiss---keep-it-simply-stupid","content":"

🔤 Meaning

The KISS principle, which stands for Keep It Simple, Stupid! is an acronym used as a design principle.

🛠️ Design Principle

It advocates for simplicity in the design and development of systems.

📅 Origin

It is attributed to engineer Kelly Johnson of the U.S. Navy, in 1960.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"KPI","question":"What does KPI mean?","description":"It stands for Key Performance Indicator.","date":"2024-11-10","categories":["KPI","metric"],"published":true,"slug":"kpi---key-performance-indicator","content":"

🎯 Definition

Key Performance Indicator (KPI), or Key Performance Indicator, is a quantifiable measure of performance over time for a specific objective, used to track progress towards goals.

🔑 Importance

KPIs are crucial for aligning teams, providing business metrics, and increasing transparency within organizations.

💼 Examples

KPIs can include metrics such as revenue growth, customer retention rate, sales by region, and more, depending on the specific business objectives.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Lead Time","question":"What is Lead Time?","description":"It is the total duration from the start to the completion of an order.","date":"2024-11-10","categories":["lean","kanban","cycle Time","metric"],"published":true,"slug":"lead-time","content":"

⏳ Definition

Lead Time, or delivery time, is the total duration from the start to the completion of an order, often used to measure the efficiency of operations.

📅 Formula

Lead Time = Delivery Date - Order Date

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Lean","question":"What is Lean?","description":"Lean is the application of manufacturing principles to software development.","date":"2024-11-10","categories":["lean","kanban","agile"],"published":true,"slug":"lean","content":"

🔍 Definition

Lean is the application of manufacturing principles to the development and management of products and services.

🎯 Goal

To maximize value offered to customers and users while reducing costs and waste.

🔃 Pull System

Uses a Pull system where services are initiated by customer requests, reducing overproduction and waste.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Lean Inception","question":"What is Lean Inception?","description":"It is a collaborative workshop to align on building a minimum viable product.","date":"2024-11-10","categories":["lean inception","lean","design thinking","mvp"],"published":true,"slug":"lean-inception","content":"

🚀 Purpose

Lean Inception is a method designed to align a team around the development of a Minimum Viable Product (MVP) in a collaborative workshop through shared understanding.

🏢 Creator

Lean Inception was introduced by Paulo Caroli, with the first publication dating from 2011.

📅 Duration

Typically lasting one week, the Lean Inception workshop focuses on quickly defining the MVP and creating a plan for its launch.

🔄 Evolution

Lean Inception has undergone various modifications and adaptations, including how to conduct it remotely for distributed teams.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"LeSS","question":"What does LeSS mean?","description":"It stands for Large Scale Scrum.","date":"2024-11-10","categories":["LeSS","scaling","scrum"],"published":true,"slug":"less-large-scale-scrum","content":"

🔍 Definition

Large Scale Scrum (LeSS) is a framework for scaling the Scrum framework to multiple teams working on the same product.

🎯 Purpose

LeSS aims to apply the principles and practices of Scrum in a large-scale enterprise context as simply as possible, maintaining a focus on delivering value and reducing complexity.

📜 Key Principles

LeSS is guided by 10 principles, including empirical process control, transparency, customer focus, and continuous improvement.

🔄 Scaling

LeSS offers two configurations - Basic LeSS for two to eight teams and LeSS Huge for more than eight teams, providing a scalable approach for different organizational sizes.

👥 Teams

LeSS emphasizes that each team be cross-functional and highly self-managed.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Management 3.0","question":"What is Management 3.0?","description":"It is a leadership and management approach that focuses on the systemic view of organizations.","date":"2024-11-10","categories":["management 3.0","leadership","continuous improvement"],"published":true,"slug":"management-3-0","content":"

🎯 Definition

Management 3.0 is a leadership and management approach that focuses on the systemic view of organizations, emphasizing collective responsibility for worker performance and happiness.

🔄 Mindset

It is described as a mindset rather than a methodology or framework, with an evolving set of tools, games, and practices to help manage organizations.

👥 Collaborative Leadership

Management 3.0 promotes a leadership model where management is a group responsibility, aiming to create a work environment that is efficient and prioritizes employee happiness.

🔧 Practical Application

The approach provides actionable advice and tools that can be implemented in organizations, with a strong focus on agile management and continuous improvement.

🏢 Origin

Management 3.0 is a management model created by Jurgen Appelo, an IT manager, in 2010.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Market Fit","question":"What is Market Fit?","description":"When the product meets a strong market demand.","date":"2024-11-10","categories":["startup","product","lean startup"],"published":true,"slug":"market-fit","content":"

🎯 Definition

Market fit occurs when a company's product satisfies a strong market demand, with customers purchasing, using, and recommending it at a scale that sustains growth and profitability.

💼 Importance

It is crucial for startups and established companies as it reduces the risk of failure, facilitates product sales, and enables informed decisions about features, pricing, and market approach.

📈 Measurement

It is measured through a combination of qualitative and quantitative metrics, including customer surveys, retention rates, and market share.

🔍 Process

Achieving market fit involves understanding the target customer, identifying their needs, defining a value proposition, and testing the product with the market.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Mindset","question":"What does mindset mean?","description":"It is a set of established attitudes, beliefs, and perspectives.","date":"2024-11-10","categories":["mentality","mindset","philosophy","agile"],"published":true,"slug":"mindset","content":"

🧠 Definition

Mindset, or mentality, is a set of established attitudes, beliefs, and perspectives that shape how an individual interprets and responds to the world around them.

🌱 Types

Two common types of mindsets are the growth mindset, which believes that abilities can be developed through effort, and the fixed mindset, which believes that abilities are innate and immutable.

💡 Importance

Mindsets can significantly influence a person's behavior, motivation, and developmental capacity, impacting various areas of their life.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"MMF","question":"What does MMF mean?","description":"It stands for Minimum Marketable Feature.","date":"2024-11-10","categories":["MVP","Lean Startup","value","feature"],"published":true,"slug":"mmf---minimum-marketable-feature","content":"

🎯 Definition

Minimum Marketable Feature, or Característica Mínima Comercializable, is the smallest set of functionality in a product that must be delivered for a customer to perceive some value.

💡 Importance

Understanding whether a feature is an MMF is crucial in agile product development as they focus on delivering significant value to customers, reducing time to market, and increasing return on investment (ROI).

🔄 Iterative Approach

MMFs are part of the iterative process, allowing for the continuous delivery of customer-valued functionality while reducing risk and increasing adaptability.

📈 Commercialization

MMFs are marketable features that can be sold or shipped, providing tangible value to users and addressing specific needs or problems.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Mob Programming","question":"What is mob programming?","description":"It is a software development approach where a group of programmers works together at a single workstation.","date":"2024-11-10","categories":["pair programming","collaboration","development","Extreme Programming"],"published":true,"slug":"mob-programming","content":"

🏉 Team Collaboration

Mob Programming is a software development approach where a group of programmers works together at a single workstation.

🔄 Role Rotation

Similar to pair programming, in mob programming, the team frequently rotates the role of 'driver' who actively writes the code, while the rest of the team provides real-time feedback and guidance.

📈 Collective Intelligence

Mob programming leverages the collective knowledge and expertise of the whole team to solve problems and develop software, potentially leading to higher-quality code.

🔀 Distribution

Unlike pair programming, where only two programmers are involved, mob programming involves a larger group, typically three or more programmers working together simultaneously.

🌐 Remote Collaboration

It can also be performed remotely, with programmers in different locations using collaborative tools to work together, such as VSCode's \"Live Share\".

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Mockups","question":"What is a mockup?","description":"It is a static and visual representation of a product.","date":"2024-11-10","categories":["mockup","design","UX","UI"],"published":true,"slug":"mockup","content":"

🖼️ Definition

A mockup is a static representation of a product, often used in product design and development to show how the final product might look and be used.

🎨 Elements

It includes design elements such as typography, logos, images, color schemes, and navigation visuals that are part of the final user experience.

🔍 Purpose

Mockups are used to present and evaluate design concepts, UI, and UX, allowing for feedback and iteration before the product is fully developed.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Muda","question":"What is Muda?","description":"It is a Japanese term that translates as waste.","date":"2024-11-10","categories":["muda","kanban","lean","waste","waste"],"published":true,"slug":"muda","content":"

📉 Definition

Muda is a Japanese term that translates as waste and refers to any activity within a process that does not add value to the final product or service.

🏭 Lean

Muda is a central concept in lean, aiming to eliminate waste to improve efficiency and productivity.

🚫 Types of Muda

There are two main types of muda: those activities that do not add value but are necessary, and those activities that do not add value and are unnecessary and should be eliminated.

🔢 TIMWOOD

Besides the above types, based on their nature, they are further categorized into seven types of waste, known by the acronym TIMWOOD, which include: Inventory, Transportation, Motion, Waiting, Overproduction, Overprocessing, and Defects.

🏗️ Origin

The concept of muda originated within the Toyota Production System (TPS) and is a fundamental principle of lean management.

💰 Business Impact

By reducing muda, organizations can improve operational efficiency, reduce costs, and enhance overall quality.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Multitasking","question":"What does multitasking mean?","description":"It involves the concurrent performance of multiple tasks.","date":"2024-11-10","categories":["multitasking","wip","wip limit","kanban"],"published":true,"slug":"multitasking","content":"

🧠 Definition

Multitasking, or multitasking, involves the concurrent performance of multiple tasks, whether by a computer or a person.

💻 Machines

In computing, it refers to the simultaneous execution of multiple tasks by an operating system.

👩‍💼 Human Multitasking

For humans, it involves rapidly switching between tasks or performing several tasks in quick succession.

🚫 Productivity

Research in productivity and efficiency suggests that, although multitasking may seem efficient, it can actually reduce productivity and impair cognitive abilities due to the cost of context switching.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"MVP","question":"What does MVP mean?","description":"It is a version of a product with just enough features to be used by early customers.","date":"2024-11-10","categories":["MVP","MMF","lean startup","product"],"published":true,"slug":"mvp---minimum-viable-product","content":"

📊 Definition

A Minimum Viable Product (MVP) is a version of a product with the minimum necessary features required to be used by early adopters, who can provide feedback for future product development.

🚀 Purpose

The MVP is used to test a product hypothesis with minimal resources, speed up learning, and reduce engineering hours wasted on features that will not be used.

💡 Lean Startup

The concept is central in Lean Startup, emphasizing the importance of validated learning in the development of new products.

🔍 Iterative Development

MVPs allow for iterative development, where products are launched with basic features and then improved based on user feedback.

💰 Cost Savings

MVPs help to minimize the time and resources committed to building a product that may not succeed.

📈 Market Validation

They allow testing market demand for a product or business idea before a significant investment.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Nexus","question":"What is Nexus?","description":"It is a Scrum scaling framework.","date":"2024-11-10","categories":["Nexus","Scrum@Scaled","Scrum","Scaling"],"published":true,"slug":"nexus","content":"

🔗 Nexus Framework

Nexus is a framework developed by Ken Schwaber and scrum.org for scaling Scrum, minimizing and managing dependencies among multiple teams.

🎯 Objective

The goal of Nexus is to help teams deliver more value by reducing complexity and dependencies while preserving the fundamental principles of Scrum.

👥 Grouping

Nexus involves a group of approximately three to nine Scrum Teams working together to deliver a single product.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Niko-Niko","question":"What is Niko-Niko?","description":"It is a visual tool used to track the emotions of a team.","date":"2024-11-10","categories":["Niko-Niko","Team"],"published":true,"slug":"niko-niko","content":"

🗓️ Description

The Niko-Niko calendar is a visual tool used to track the emotions of a team, also known as the happiness index.

🔍 Origin

Originating from Japan, the term 'Niko-Niko' means 'smile' and was created in 2005 in Yokohama, by Mrs. Sachiko Kuroda at Fujitsu Software Technologies Limited.

⚒️ Use

Team members place colored stickers or emojis on the calendar to represent their mood at the end of each workday, along with a brief explanation.

📈 Benefits

The calendar helps to quantify morale, mental well-being, and team momentum, providing an overview of team performance over time.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"OKRs","question":"What does OKR mean?","description":"The acronym stands for Objective and Key Result.","date":"2024-11-10","categories":["OKR","KPI","Metric","Objectives"],"published":true,"slug":"okr","content":"

📅 Origin

OKRs were developed by Andrew Grove at Intel in the 1970s and later popularized by John Doerr, who introduced the concept to Google.

🎯 Meaning

OKRs (Objectives and Key Results) are a framework used to set and track objectives and their outcomes within an organization.

🎯 Objectives

The Objectives in OKRs should be clear, meaningful, and challenging. They should be formulated in a way that inspires and motivates the team. Furthermore, they should be aligned with the organization's mission and vision. A good objective is one that, although it may be difficult to achieve, is realistic and contributes to the growth and improvement of the organization.

🔑 Key Results

The Key Results in OKRs are the specific metrics used to measure progress towards achieving the Objectives. Key Results should be quantifiable, meaning they should be measurable in some way. For example, a Key Result could be \"Increase sales by 20%\".

🌐 Expansion

OKRs have been adopted by numerous large technology organizations, largely due to the influence of John Doerr.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Open Space","question":"What is an Open Space?","description":"It is an event format without a previous agenda and led by the participants themselves.","date":"2024-11-10","categories":["Agile","Law of Two Feet","self-organization","event"],"published":true,"slug":"open-space","content":"

🔄 Definition

An Open Space is a participant-driven event format that allows for self-organization and the exploration of specific questions or themes within an Agile context.

🎯 Purpose

To quickly gather the best ideas from a large group of people on a particular topic, often within a short period of time.

👥 Participant-Led

The content and structure of the event are determined by the participants, not the organizers.

🔀 Self-Organization

Participants propose and schedule meetings to discuss specific topics, with the freedom to move between sessions as they see fit.

📅 Duration

Open Spaces typically last from half a day to two full days, with multiple simultaneous meetings.

📝 Four Principles

Whoever comes is the right person; whatever happens is the only thing that could have; whenever it starts is the right time; when it's over, it's over.

🦶 Law of Two Feet

The Law of Two Feet encourages participants to take responsibility for their own learning and contribution by moving to sessions that interest them.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Pair Programming","question":"What is Pair Programming?","description":"It is a software development technique where two programmers work together at a single workstation.","date":"2024-11-10","categories":["Mob Programming","development","collaboration"],"published":true,"slug":"pair-programming","content":"

⚙️ Definition

Pair Programming is a software development technique where two programmers work together at a single workstation, with two roles: the 'driver' writing the code and the 'observer' or 'navigator' reviewing each line of code.

🔄 Roles

The two programmers frequently switch roles, with the observer also considering the strategic direction of the work while the driver focuses on the tactical aspects.

👥 Collaboration

Pair Programming is a collaborative technique involving a lot of communication, with the goal of producing higher quality code and sharing knowledge.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Parking Lot","question":"What is a Parking Lot?","description":"It is a technique to improve focus during meetings.","date":"2024-11-10","categories":["technique","timebox"],"published":true,"slug":"parking-lot","content":"

🅰️ Definition

A Parking Lot is a designated space, either physical or virtual, used to record and address topics, questions, or ideas that arise during meetings but are not relevant to the current discussion.

🚗 Purpose

It helps to keep the focus on the main agenda, prevents discussions from going off-topic, and ensures that all relevant matters are addressed at an appropriate time and within the agreed timebox.

📝 Usage

Participants can briefly jot down off-topic items in the Parking Lot, and the facilitator is responsible for revisiting and addressing these items after the main meeting.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"PBI","question":"What does PBI mean?","description":"It stands for Product Backlog Item.","date":"2024-11-10","categories":["backlog","product backlog","sprint backlog","scrum"],"published":true,"slug":"pbi---product-backlog-item","content":"

📝 Definition

Product Backlog Item, or Element of the Product Backlog, is a term used in Scrum to represent a single requirement or piece of work that needs to be completed.

🎯 Importance

PBIs are essential for organizing and prioritizing the work that needs to be done, providing visibility and transparency to the entire team.

🔄 Nature

The Product Backlog is a living document that evolves as development progresses, with PBIs being updated, added, or removed based on the team's needs and feedback.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"PI","question":"What does PI mean?","description":"It stands for Program Increment.","date":"2024-11-10","categories":["Release Train","SAFe"],"published":true,"slug":"pi---program-increment","content":"

⏱️ Definition

Program Increment, or Increment of Program, is a period of 8 to 12 weeks during which an Agile Release Train (ART) delivers incremental value to a product.

📈 Purpose

To provide a fixed cadence for planning, building, and validating a complete system increment.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"PI Planning","question":"What does PI Planning mean?","description":"It is an event for planning the Program Increment.","date":"2024-11-10","categories":["PI","SAFe","scaling"],"published":true,"slug":"pi-planning","content":"

📈 Definition

PI Planning, or Program Increment Planning, is an event within SAFe that aligns multiple teams to a shared mission and vision.

🤝 Purpose

It aims to create a shared understanding and commitment to the goals for the next Program Increment, which typically lasts from 8 to 12 weeks.

👥 Participants

The participating roles include the Product Manager, Product Owner, Release Train Engineer, Scrum Master, and Developer, who collaborate to plan and prioritize the work.

🗓️ Process

The event involves reviewing the Backlog, identifying dependencies, and setting clear goals for the Agile Release Train (ART).

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Planning Poker","question":"What is Planning Poker?","description":"It is a technique used to estimate effort.","date":"2024-11-10","categories":["scrum","estimation","user story","story points","XP"],"published":true,"slug":"planning-poker","content":"

🃏 Definition

Planning Poker is a technique used in Agile teams to estimate the effort required to complete a user story or task.

🤝 Estimation

The technique involves team members using a deck of cards to individually estimate the effort, then discussing and re-estimating until consensus is reached.

💬 Importance

The true significance of this technique lies not in the score reached, but in the dialogue it fosters within the team.

📈 Agile

It is commonly associated with Scrum and Extreme Programming - XP.

🔢 Fibonacci

The cards in the deck often follow the Fibonacci sequence to reflect the uncertainty in the estimation process and employ a relative measure that does not relate to time.

⭐ Introduction

The team member most familiar with a particular user story provides a brief overview, and the team may ask questions to clarify.

📝 Estimation

Each team member selects a card from their deck to represent their individual estimate without revealing it to the rest of the team to prevent swaying others.

💬 Discussion

The team discusses the estimates, aiming to understand any discrepancies or polarity and reach a consensus.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"PMBOK","question":"What is PMBOK?","description":"It stands for Project Management Body of Knowledge.","date":"2024-11-10","categories":["PMBOK","Projects","PMI"],"published":true,"slug":"pmbok","content":"

📘 Definition

PMBOK is the body of knowledge in project management developed by the Project Management Institute (PMI) that provides Project Managers with fundamental concepts, best practices, and processes for project management.

🌐 Importance

PMBOK serves as a standard reference for project management and is regularly updated to reflect changes in the industry, including the incorporation of agile frameworks and change management models.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"PMI","question":"What does PMI mean?","description":"It stands for Project Management Institute.","date":"2024-11-10","categories":["PMI","PMBOK","PMP","Project"],"published":true,"slug":"pmi","content":"

🏢 Organization

Project Management Institute, or PMI, is a non-profit organization focused on improving knowledge surrounding project management.

📜 PMP Certification

PMI offers the PMP certification, which is a globally recognized standard for project managers.

📚 Body of Knowledge

The organization is not only dedicated to development but also to the publication of PMBOK, which is the most prestigious and recognized body of knowledge in the field of project management.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"PMP","question":"What does PMP mean?","description":"It stands for Project Management Professional.","date":"2024-11-10","categories":["PMBOK","PMP","PMI","Project"],"published":true,"slug":"pmp","content":"

🎓 PMP Certification

PMP is a credential offered by the Project Management Institute (PMI).

🌍 Recognition

The PMP certification is recognized in 125 countries and is highly valued in the field of project management.

📚 Requirements

To earn the PMP certification, candidates must meet specific criteria for education, experience, and training, and pass a rigorous exam.

📖 PMBOK Guide

The certification is based on the PMBOK Guide, which compiles best practices in project management and is regularly updated to reflect industry standards.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Portfolio","question":"What is a portfolio?","description":"It is a strategic grouping of projects and programs.","date":"2024-11-10","categories":["project","program"],"published":true,"slug":"portfolio","content":"

📊 Definition

A portfolio refers to the collection of projects, programs, and other work elements that are managed as a group to achieve strategic business objectives.

🎯 Prioritization

Projects are reprioritized as business needs change, ensuring that the most valuable work is always addressed.

📈 Transparency

The portfolio management process should be designed to be transparent, with clear visibility into project progress and decision-making.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Product Backlog","question":"What is the Product Backlog?","description":"It is a prioritized list of all the work that needs to be done on a product.","date":"2024-11-10","categories":["PBI","scrum","Product Owner"],"published":true,"slug":"product-backlog","content":"

📝 Definition

The Product Backlog is a prioritized list of all the work that needs to be done on a product, and it is the main artifact of the Product Owner in Scrum.

🎯 Purpose

It helps define and maintain the overall direction and vision for the product and serves as the single source of work input for the Scrum Team.

🔄 Iterative Refinement

As the team learns more about how to achieve the goal, Product Backlog items are refined to align with the Product Goal.

🔍 Visibility

It provides transparency to the entire Scrum Team regarding the work that needs to be done, aiding in effectively addressing Sprint Planning and Sprint Review.

📈 Prioritization

PBIs should be prioritized to ensure that the most valuable and important work is completed first.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Product Goal","question":"What is the Product Goal?","description":"It is a long-term objective that describes a future state of the product.","date":"2024-11-10","categories":["sprint goal","scrum","Product Owner","Product Backlog"],"published":true,"slug":"product-goal","content":"

🎯 Definition

The Product Goal, also known as the Product Objective, is a long-term objective that describes a future state of the product, providing a clear path for the Scrum Team.

📈 Strategic Focus

It serves as a strategic focus for the team, guiding their work across multiple Sprints.

🔍 Transparency

The Product Goal is made visible through the Product Backlog, and the Product Owner is responsible for its development and explicit communication.

📘 Origin

In the 2020 version of the Scrum Guide, the concept of the Product Goal is introduced as a key element.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Product Owner","question":"What is a Product Owner?","description":"They are responsible for maximizing the value of the product.","date":"2024-11-10","categories":["product owner","scrum","product backlog"],"published":true,"slug":"product-owner","content":"

👩‍💼 Definition

The Product Owner (PO) is a key role in Scrum, responsible for maximizing the value of the product and the work of the Scrum Team.

📝 Artifact

The PO's artifact is the Product Backlog, which is a prioritized list of work to be done on the product.

📢 Communication

The Product Owner is responsible for communicating the vision and objectives of the product to the team and stakeholders.

📑 Refinement

They are responsible for refining the Product Backlog, ensuring that the top-layer items are clear and known so that Sprint Planning can be conducted effectively.

🎯 Objectives

Defines the Product Goal, which is the purpose of the product.

🔒 Authority in Prioritization

Has the exclusive authority to prioritize items in the Product Backlog based on the value they will deliver, according to the criteria deemed appropriate.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Pull System","question":"What is the Pull system?","description":"It is one where work is only initiated when there is demand for it.","date":"2024-11-10","categories":["kanban","jit","lean","wip","waste"],"published":true,"slug":"pull","content":"

🔄 Definition

In Kanban, a Pull system is one where work is only initiated when there is demand for it, as opposed to a Push system that relies on forecasts and can lead to overproduction.

📦 Just-in-Time

Pull systems are integral to the Just-in-Time (JIT) production model, where goods are produced to meet actual demand, reducing excess inventory and waste.

🚦 Kanban Signals

Kanban uses visual signals, such as cards and wip limits, to indicate when work should be started, linking production directly to customer demand.

📉 Waste Reduction

Pull systems help minimize waste by aligning production with actual demand, leading to more efficient use of resources.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"QA","question":"What does QA mean?","description":"It stands for Quality Assurance.","date":"2024-11-10","categories":["quality","development","testing","tester"],"published":true,"slug":"qa---quality-assurance","content":"

📏 QA Definition

Quality Assurance (QA) is the systematic process of ensuring that software meets specified requirements and is free of defects before being released to users.

🛠️ Importance

The QA process is crucial for identifying and correcting defects, bugs, and issues in software, helping to deliver a reliable and high-quality product to end-users.

👩‍💻 Role

A QA Analyst is the role responsible for testing the software, creating test plans, and working alongside the rest of the team to ensure that the software functions as intended.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"QBR","question":"What does QBR mean?","description":"It stands for Quarterly Business Review.","date":"2024-11-10","categories":["QBR","OKR","business","strategy"],"published":true,"slug":"qbr---quarterly-business-review","content":"

📊 Definition

Quarterly Business Review (QBR), or Business Quarterly Review, is a periodic meeting, usually held every quarter, to assess a company's performance and results over a specific period.

🔍 Focus

QBRs typically involve a strategic discussion about the company's performance, future plans, and any necessary adjustments to business strategies.

🤝 Participation

Key stakeholders from both sides, both the client and the company, are usually involved in QBR meetings.

🗓️ Regular Practice

QBRs are a standard business practice, helping to keep organizations aligned with their strategic goals and make informed decisions.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Release","question":"What is a release?","description":"It is a specific version of software that has been completed, tested, and made available for use.","date":"2024-11-10","categories":["release candidate","PRO","PRE","staging","software"],"published":true,"slug":"release","content":"

🚀 Definition

A release, or launch, refers to a specific version of software that has been completed, tested, and made available for use by end-users.

🎯 Objectives

The main goal is to ensure that the software is delivered in a controlled and predictable manner, meeting quality and service level requirements.

🔄 Importance

Releases are significant milestones in software development, often including new features, performance enhancements, and bug fixes.

🔖 Version Vs. Release

While a release is a version of software, not all software versions are considered releases; a release is a version that is made public for use.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Release Candidate","question":"What is a Release Candidate?","date":"2024-11-10","categories":["release","development","alm"],"published":true,"slug":"release-candidate","content":"

🚀 Definition

A Release Candidate (RC) is a version of a software program that is nearly complete and ready to be released, pending final testing.

🔍 Purpose

The RC phase is the last step before a software product is released to the public, serving as a final quality check.

🛠️ Testing

During the RC phase, rigorous testing is performed to identify and correct any critical issues that could affect the software's performance or stability.

📦 Naming Convention

Release candidates are often denoted with the term 'RC' followed by a version number, such as '3.0-RC1'.

👨‍💻 Stages of Development

🅰️ Alpha: The first complete or nearly complete version of a software program, often used for internal testing.\n🅱️ Beta: A more stable version than alpha, released to a wider group for testing and feedback.\n🆗 RC: The release candidate phase comes after beta and is the final step before a software product is officially released.\n🎯 RTM: Stands for 'Release to Manufacturing' or 'Release to Marketing', indicating that the software is ready for distribution.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"IT Roadmap","question":"What is an IT roadmap?","description":"In IT, a roadmap is a visual representation of a strategic plan that aligns the organization's technological resources with its short- and long-term business objectives.","date":"2024-11-10","categories":["roadmap","IT","strategic planning"],"published":true,"slug":"roadmap","content":"

🗺️ Roadmap Definition

In IT, a roadmap is a visual representation of a strategic plan that aligns the organization's technological resources with its short- and long-term business objectives.

🔗 Link to Strategy

It serves as a guide for technology-related initiatives, outlining the necessary technologies, development timelines, resource requirements, and potential challenges.

👩‍💻 Agile Tool

Roadmaps are commonly used in agile methodologies to communicate the technological strategy within the organization and to external stakeholders.

📈 Strategic Planning

They are a powerful tool for managing and communicating the evolution of technology within the organization.

📱 Product Roadmap

Focuses on the development and improvement of a specific product, often incorporating user feedback and market trends.

🖥️ Technology Roadmap

Aligns technological initiatives with business objectives, detailing the implementation of new technologies and their impact on the organization.

📊 Strategic Roadmap

Provides a long-term vision for the organization's technological landscape, guiding major technology-related projects over several years.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"ROI","question":"What does ROI mean?","description":"It stands for Return on Investment.","date":"2024-11-10","categories":["ROI","financial metrics","profitability"],"published":true,"slug":"roi---return-of-invest","content":"

🔍 Definition

Return on Investment, or ROI, is a financial metric used to evaluate the profitability of an investment relative to its cost.

📈 Calculation

ROI is calculated by subtracting the initial investment from the final value of the investment, dividing the result by the initial investment, and then multiplying by 100 to express the result as a percentage.

📊 Formula

ROI = [(Gain - Investment) / Investment] x 100

🧮 Example

If an investment of 10,000 euros generates 15,000 euros, the ROI would be (15,000 - 10,000) / 10,000 X 100 = 50%.

🔢 Interpretation

A 50% ROI means that for every dollar invested, there is a return of $1.50, including the initial investment.

📈 Importance

ROI is crucial for businesses as it aids in decision-making by providing a clear measure of the financial success of an investment.

🎯 Application

It is widely used in marketing to assess the performance of campaigns and generally in business to evaluate the efficiency of various investments.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"SAFe","question":"What does SAFe mean?","description":"It stands for","date":"2024-11-10","categories":["SAFe","scaling","agile"],"published":true,"slug":"safe---scaled-agile-framework","content":"

🔍 Definition

Scaled Agile Framework (SAFe) is a set of organizational patterns for implementing agile practices at enterprise scale.

🏢 Purpose

Its goal is to enable companies to apply an agile framework across the organization, fostering flexibility, innovation, and a rapid response to customer needs.

🎯 ART

One of the key elements of SAFe is the Agile Release Train (ART).

## 👎 Criticism\nSAFe is the most criticized scaling framework within Agile communities. One of the main criticisms it receives is not addressing the transformation from a cultural perspective and only focusing on techniques.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Scrum","question":"What is Scrum?","description":"It is a framework that helps generate value through adaptive solutions.","date":"2024-11-10","categories":["agile","scrum"],"published":true,"slug":"scrum","content":"

## 🔍 Definition\nScrum is an Agile framework designed to develop adaptive solutions to complex problems, emphasizing the delivery of value through iterative and incremental progress, team collaboration, and adaptability to changing requirements.

🤝 Collaboration

It is designed to facilitate a team's ability to self-organize and make rapid decisions in response to complex and changing needs.

📈 Incremental Iterative Focus

The solution scope is addressed through 'Sprints', short iterations of up to a month, commonly 2 weeks, where each iteration produces a deliverable product increment.

## 🎯 Focus on Value

Scrum prioritizes the delivery of the highest value features to the customer early and regularly, over the Product Owner's ordered Backlog.

## 🧭 Scrum Roles

Scrum establishes specific roles: the Scrum Master, who ensures adherence to Scrum practices; the Product Owner, who defines the product needs; and the Developers, responsible for materializing the solutions that make up the product.

📝 Scrum Artifacts

The main artifacts of Scrum are the Product Backlog, a list of everything that is needed for the product; the Sprint Backlog, the commitment to the solutions that will be developed in the next Sprint; and the Increment, the set of completed items, ready to be delivered.

🕒 Scrum Events

Scrum determines the following events: Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

💡 Scrum Values

Scrum is based on Commitment, Courage, Focus, Openness, and Respect. These key values foster an environment of collaboration and shared responsibility within the team.

🏛 Pillars of Scrum

Scrum rests on the pillars of Transparency, Inspection, and Adaptation. These pillars support the agile process, promoting visibility, continuous evaluation, and flexibility to adapt to changes.

📘 Scrum Guide

The Scrum Guide offers an essential and practical understanding of the agile framework in an accessible format. Ideal for those looking to implement Scrum, download the Scrum guide for free.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Scrum Master","question":"What is a Scrum Master?","description":"It is the role responsible for establishing Scrum within the organization or team.","date":"2024-11-10","categories":["scrum","role","framework","agile"],"published":true,"slug":"scrum-master","content":"

👨‍💼 Definition

The Scrum Master is one of the three key roles in the Scrum framework, responsible for establishing Scrum and ensuring that the team and organization understand its theory and adhere to its practices.

🔄 Impediments

The Scrum Master aids the team in continuous improvement by facilitating the removal of impediments and creating space for the team to self-manage and be cross-functional.

📊 Metrics and Reporting

Helps the team understand and use metrics to observe progress and identify areas for improvement.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Scrum of Scrums (SoS)","question":"What is Scrum of Scrums?","description":"It is a method for coordinating work among multiple Scrum teams.","date":"2024-11-10","categories":["Scrum","scaling","agile"],"published":true,"slug":"scrum-of-scrums","content":"

🔄 Definition

Scrum of Scrums (SoS) is a scaling technique for coordinating work among multiple teams practicing Scrum in an Agile software development environment.

📜 Context

The Scrum of Scrums was formalized by Jeff Sutherland in 2001 as a technique to address the need for coordination and alignment when multiple teams are working on a single product or a family of products within the Scrum framework.

👥 Representatives

Each team designates a representative/ambassador to participate in a sort of Daily Scrum only for sub-team representatives called Scrum of Scrums.

⏱ Time Limit

The meeting should not exceed 30 minutes, and the focus is on coordination and addressing any dependencies or impediments between teams.

🔗 Scalability

The SoS can be further scaled by having a Scrum of Scrums of Scrums, allowing coordination across multiple levels within the organization.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Scrumban","question":"What is Scrumban?","description":"It is a framework that combines the principles of Scrum and Kanban.","date":"2024-11-10","categories":["Scrum","Kanban","agile"],"published":true,"slug":"scrumban","content":"

🔄 Definition

Scrumban is a framework that combines the principles of Scrum and Kanban, offering a flexible approach to product management.

🔍 Origin

The term 'Scrumban' was coined by Corey Ladas, and the framework is designed to help teams transition between Scrum and Kanban or to operate in a hybrid manner.

🎯 Focus

The method emphasizes continuous improvement and efficiency while maintaining a balance between structure and flexibility.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Scrum@Scale","question":"What is Scrum@Scale?","description":"It is a framework for naturally extending the core of the Scrum framework.","date":"2024-11-10","categories":["Scrum","scaling","agile"],"published":true,"slug":"scrumscale","content":"

🔄 Definition

One of the biggest challenges for organizations using Scrum is expanding the core of the framework beyond individual teams. Scrum@Scale, developed by Dr. Jeff Sutherland, co-creator of Scrum, is a framework that allows for this natural expansion of the core framework to enhance coordination and results at an organizational level.

🏢 Organization

Its goal is to help organizations achieve business agility by providing a structure for systems and processes to grow organically from the unique conditions of the organization.

🔬 Empirical Control

The framework is based on the pillars of empirical process control and Scrum values, focusing on transparency, inspection, and adaptation.

📚 Guide

The official Scrum@Scale guide provides a comprehensive understanding of the framework and its components. You can access it for free through this link.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Senior","question":"What is a Senior?","description":"It is a developer with a high level of knowledge of the language and the technology stack.","date":"2024-11-10","categories":["senior","role","team"],"published":true,"slug":"senior","content":"

👨‍💻 Role Definition

A senior developer typically has more than 5 years of experience, with a high level of knowledge of the language and the technology stack used.

🕰️ Experience

The 'senior' title is not based solely on years of experience, but also on the natural aptitude and soft skills demonstrated by the individual.

📈 Leadership

Within organizations, senior developers are expected to actively advise and assist junior team members.

🧠 Problem Solving

They are responsible for turning ideas into well-thought-out and implementable solutions, often guiding others in the process.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Servant Leadership","question":"What is a Servant Leader?","description":"It is a philosophy where the main goal of the leader is to serve others.","date":"2024-11-10","categories":["leadership","agile","management 3.0"],"published":true,"slug":"servant-leadership","content":"

👥 Definition

Servant Leadership is a philosophy where the main goal of the leader is to serve others, focusing on their well-being and growth.

🌱 Key Principle

The servant leader shares power, puts the needs of their team first, and helps people develop and perform to their highest potential.

🔄 Contrast

Unlike traditional leadership, which often involves the accumulation and exercise of power, servant leadership emphasizes serving and empowering others.

📚 Origin

The phrase 'servant leadership' was first popularized by Robert K. Greenleaf in his 1970 essay 'The Servant as Leader'. Greenleaf credited his reading of 'Journey to the East' by Hermann Hesse as the inspiration for the term.

🏢 Application

Greenleaf applied the concept in an organizational context while working as an executive at AT&T.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"SLA","question":"What does SLA mean?","description":"It stands for Service Level Agreement.","date":"2024-11-10","categories":["service","kanban","metrics"],"published":true,"slug":"sla","content":"

📝 Definition

Service Level Agreement, or SLA, is a contract between a service provider and a client that defines the level of service the provider is committed to delivering. It includes metrics such as uptime, delivery time, response time, and resolution time.

🔍 Importance

SLAs are crucial for both parties as they establish clear expectations, provide a basis for measuring performance, and outline the course of action if the requirements are not met.

🤝 Creation

SLAs are typically created through negotiations, with both parties agreeing on the specific services, performance metrics, responsibilities, and potential penalties.

👥 Parties Involved

It usually involves a client (internal or external) and a service provider, but can also be between different business units within the same organization.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"SOLID","question":"What are the SOLID principles?","description":"They are a set of design guidelines for improving the maintainability and scalability of software.","date":"2024-11-10","categories":["principles","software","development"],"published":true,"slug":"solid","content":"

🏛️ Origin

The SOLID principles were introduced by Robert C. Martin, also known as Uncle Bob, in his work on object-oriented design in the early 2000s. These principles are a compilation of five design concepts that assist developers in creating software systems.

📕 Definition

SOLID is an acronym that stands for five design principles in object-oriented programming: Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion.

## 🔍 Purpose\nThese principles provide a framework for designing software that is easy to maintain, understand, and expand, allowing developers to avoid common design and architecture pitfalls.

🔨 Single Responsibility (SRP)

A class should have only one reason to change.

🔒 Open/Closed (OCP)

Software entities should be open for extension, but closed for modification.

🔄 Liskov Substitution (LSP)

Objects of a superclass should be replaceable with objects of its subclasses without affecting the functionality.

🔀 Interface Segregation (ISP)

Many client-specific interfaces are better than one general-purpose interface.

🔄 Dependency Inversion (DIP)

High-level modules should not depend on low-level modules; both should depend on abstractions.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Spike","question":"What is a Spike?","description":"It is a research or experimentation task to decrease uncertainty.","date":"2024-11-10","categories":["Extreme Programming - XP","Agile","User Story","Uncertainty"],"published":true,"slug":"spikes","content":"

🔍 Spike Definition

A 'spike' is a term used in Extreme Programming - XP to refer to a research or experimentation task. It is typically used to reduce uncertainty or gain knowledge to estimate or implement a user story.

🕒 Time-Boxed

Spikes are time-boxed, often within the duration of a single sprint, meaning they have a predefined maximum duration and are not intended to deliver a functional increment to the product.

🔧 Technical Spikes

Used to evaluate technical aspects such as performance, feasibility, or the impact of new technology within the project.

📐 Functional Spikes

Employed to understand user interactions or to prototype and test user interface elements for a specific feature.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Sprint","question":"What is a Sprint?","description":"It is a short, fixed period during which a Scrum team works to complete a set amount of work.","date":"2024-11-10","categories":["Sprint","Scrum","Agile"],"published":true,"slug":"sprint","content":"

🏃‍♂️ Definition

A sprint is a short, fixed period during which a Scrum Team works to complete a set amount of work.

📈 Incremental

Each sprint aims to deliver a potentially shippable product increment, adding value to the users.

🔄 Iterative

Sprints are part of an iterative process, with one sprint following another of the same duration, allowing for continuous improvement and adaptation to changes.

🗓️ Planning and Review

A sprint contains the other Scrum events, namely: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.

⏱️ Typical Duration

Sprints commonly last two weeks, with a maximum duration of no more than one month.

📅 Recommendation

Once the duration of sprints is established, it is fixed and should not be altered, maintaining a consistent rhythm for the team over time.

🌱 Analogy

The Scrum guide defines a Sprint as: \"Sprints are the heartbeat of Scrum, where ideas are turned into value.\"

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Sprint Backlog","question":"What is the Sprint Backlog?","description":"They are the Product Backlog items committed by the developers for completion in the next iteration.","date":"2024-11-10","categories":["Scrum","PBI","Product Backlog","Sprint Backlog"],"published":true,"slug":"sprint-backlog","content":"

📝 Definition

The Sprint Backlog is a set of items from the Product Backlog (PBI) chosen for the Sprint, plus a plan for delivering the product Increment and achieving the Sprint Goal.

🔄 Dynamic

It is a living plan that evolves during the Sprint as more is learned about the work needed to achieve the Sprint Goal.

👨‍💻 Ownership

The Developers are responsible for creating and maintaining the Sprint Backlog, ensuring it reflects the work needed to achieve the Sprint Goal.

🔍 Transparency

The Sprint Backlog is one of the Scrum artifacts that provides transparency on the work being done in the Sprint.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Sprint Planning","question":"What is Sprint Planning?","description":"It is the first event of a Sprint where the iteration's scope is planned.","date":"2024-11-10","categories":["Sprint","Scrum","event","Product Backlog","Sprint Goal","Sprint Backlog"],"published":true,"slug":"sprint-planning","content":"

📅 Event

Sprint Planning is the first event of a Sprint and lasts a maximum of eight hours for a one-month Sprint.

🎯 Purpose

This event serves to establish the Sprint Goal and plan the work necessary to deliver the Increment.

🔍 Focus

It involves the entire Scrum Team, with the Product Owner and Developers collaborating to select work from the Product Backlog that can be done in the next Sprint.

📝 Outcome

The outcome is a Sprint Backlog, a forecast of the functionality that will be developed during the Sprint, and a Sprint Goal.

⏱️ Timebox

The event has a limited duration to ensure it does not consume too much time.

🔄 Iterative

Sprint Planning occurs before the start of each Sprint, ensuring a regular cadence for planning and goal setting.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Sprint Retrospective","question":"What is the Sprint Retrospective?","description":"It is a meeting at the end of each sprint where the team reflects on what went well, what could be improved, and identifies actions for the next sprint.","date":"2024-11-10","categories":["Kaizen","Sprint","Scrum"],"published":true,"slug":"sprint-retrospective","content":"

🔄 Definition

The Sprint Retrospective, or Retro, is a meeting at the end of each sprint within the Scrum framework, where the team reflects on what went well, what could be improved, and identifies actions for the next sprint.

🎯 Purpose

The main goal is to continuously improve the Way of Working (WoW) and the team's performance by incorporating feedback and making adjustments for future sprints.

📩 Outcome

Once concluded, the Retrospective requires that at least one improvement action is incorporated into the work planned for the next Sprint.

👥 Participants

All members of the Scrum Team, including the Scrum Master, the Product Owner, and the Developers.

📈 Iterative Improvement

The retrospective is a key element of Scrum's empirical process control, allowing regular adaptation and refinement of the team's working methods.

📅 Timebox

The retrospective is limited to 3 hours for a monthly sprint, with shorter durations for shorter sprints.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Sprint Review","question":"What is the Sprint Review?","description":"It is a Scrum event that occurs at the end of the Sprint, where the product increment is inspected.","date":"2024-11-10","categories":["Increment","Product","Product Backlog","Scrum"],"published":true,"slug":"sprint-review","content":"

🔍 Definition

The Sprint Review is a Scrum event that occurs at the end of a Sprint, where the product increment is inspected and the Product Backlog is adapted based on the feedback received.

📈 Inspection

The team and stakeholders review what was accomplished during the Sprint and discuss any changes that may be needed.

🎯 Sprint Goal

The Scrum Team articulates the Sprint Goal and shows how each PBI contributed to it.

📈 Metrics

Quantitative data on the performance of the Increment may be discussed to inform decision-making.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Sprint Zero","question":"What is a Sprint Zero?","description":"It is an anti-pattern that introduces a preliminary phase before starting product development using the Scrum framework.","date":"2024-11-10","categories":["Empiricism","Sprint","Scrum","anti-pattern"],"published":true,"slug":"sprint-zero","content":"

🏃‍♂️ Definition

A Sprint Zero is a prelude to the formal sprint process in agile development, focused on initial setup, planning, and preparation.

🚫 Anti-pattern

Sprint Zero is considered an anti-pattern because it can lead to a lack of focus on delivering functional software and can be misused as an excuse for excessive planning without tangible outcomes, violating the principles of empirical process control.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Stakeholders","question":"What is a Stakeholder?","description":"It is any individual or group with an interest in a business or project.","date":"2024-11-10","categories":["Stakeholder","product","service","role"],"published":true,"slug":"stakeholder","content":"

👥 Definition

A stakeholder is any individual or group of individuals with an interest in a business or project, who can influence or be influenced by the project's outcomes and determine its success or failure.

🎯 Importance

Understanding the roles of stakeholders is crucial for managing their expectations and potential dependencies.

📊 Types

Stakeholders can be categorized as internal, external, or secondary, depending on their relationship with the project.

🏢 Internal Stakeholders

Typically include the team developing the product or service, and other members of the organization directly involved.

🌐 External Stakeholders

Consist of entities outside of the organization, such as customers, suppliers, and regulatory bodies, who have a direct interest in the project.

🔗 Secondary Stakeholders

Indirectly affected parties such as the media or the general public, who can influence or be influenced by the project's outcomes.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Swarming","question":"What is Swarming?","description":"It is a technique where the entire team focuses on a single task or user story.","date":"2024-11-10","categories":["User Story","PBI"],"published":true,"slug":"swarming","content":"

🔄 Swarming Definition

Swarming is a technique where the entire team focuses on a single task or user story, working collaboratively to solve it.

🏗️ Context

Swarming is often used in Scrum and other agile frameworks to tackle complex problems and ensure a continuous flow of work.

👥 Team Collaboration

The approach involves all team members working together, leveraging their collective strengths and experience to efficiently address the task at hand.

🔑 Challenge

Swarming is employed when a problem is particularly challenging and requires the collective effort of the team to overcome it.

🔄 Continuous Flow

Swarming helps to maintain a continuous flow of work by avoiding bottlenecks and delays in task completion.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"System Demo","question":"What is a System Demo?","description":"It's a practice within SAFe that provides a means to assess the current state of the solution.","date":"2024-11-10","categories":["SAFe","Scaling"],"published":true,"slug":"system-demo","content":"

🔍 System Demo

A System Demo is a practice within SAFe that provides a means to assess the current state of the solution by showcasing the integrated features of the software.

🔄 Process

Typically conducted at the end of each iteration, the System Demo is a regular event that allows stakeholders to evaluate progress and the value delivered by the teams.

👥 Participation

The System Demo involves key stakeholders and is an opportunity for them to provide feedback and assess the real value and velocity of the project.

⏱️ Timebox

SAFe recommends a timebox of approximately 60 minutes for the System Demo at the end of each iteration.

📋 Agenda

A predefined agenda is created to guide the demo, ensuring a well-organized flow of the event.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"T-Shaped Skills","question":"What are T-Shaped Skills?","description":"They are the combination of deep expertise in a specific area with broader interdisciplinary skills.","date":"2024-11-10","categories":["skills"],"published":true,"slug":"t-shaped","content":"

🔤 Definition

T-Shaped Skills refer to the combination of deep expertise in a specific area (the vertical bar of the T) with broader interdisciplinary skills that enable effective collaboration across different fields (the horizontal bar of the T).

👥 Significance

Professionals with T-Shaped Skills are highly valued for their ability to contribute both within their specialized area and in related fields, making them versatile and adaptable team members.

🎓 Origin

The concept was first introduced by David Guest in 1991 and popularized by Tim Brown, CEO of IDEO, as a way to build cross-disciplinary teams for creative processes.

🏢 McKinsey & Company

The concept was also used internally by McKinsey & Company in the 1980s, referred to as 'T-shaped man' for both men and women.

🌐 Application

T-Shaped Skills are particularly sought after in software development and are applicable to a wide range of industries where cross-disciplinary collaboration is essential.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"T-Shirt Sizing","question":"What is T-Shirt Sizing?","description":"It's an estimation technique that uses t-shirt sizes.","date":"2024-11-10","categories":["planning poker","estimating","story points","fibonacci"],"published":true,"slug":"t-shirt","content":"

👕 T-Shirt Sizing

T-Shirt Sizing is an estimation technique that uses t-shirt sizes (XS, S, M, L, XL) or other relative scales to estimate the size or effort required for tasks or user stories.

📊 Relative Estimation

It focuses on comparing the size or effort of one task to another, rather than providing specific time-based estimates.

👥 Team Collaboration

Involves the entire team in the estimation process, allowing for a shared understanding of the effort or complexity represented by each size.

📈 Story Points

Story Points are another common technique of relative estimation, where tasks are assigned points to indicate their complexity or effort.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"TDD","question":"What is Test Driven Development (TDD)?","description":"Test-Driven Development (TDD) is a programming approach that emphasizes writing tests before developing the code functionality.","date":"2024-11-10","categories":["BDD","development","software"],"published":true,"slug":"tdd---test-driven-development","content":"

🧪 Test Driven Development (TDD)

Test-Driven Development (TDD) is a programming approach that emphasizes writing tests before developing the code functionality. This method ensures that the code meets the intended requirements and helps prevent errors.

📚 Origin

Test-Driven Development (TDD) was developed by Kent Beck in the late 1990s as part of Extreme Programming.

🔄 Iterative Process

TDD follows a cycle of adding a test, failing the test execution, writing code to pass the test, and then refactoring the code.

🎯 Focus

TDD focuses on testing small units of code at a time, ensuring that the system is built incrementally and with high test coverage.

🔴🟢 Refactoring Cycle

Also known as the 'Red-Green-Refactor' cycle, where code is written to make the failed test pass and then refactored to improve its structure.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Team Leader","question":"What is a Team Leader?","description":"It's the role responsible for overseeing operations to setting goals and solving problems.","date":"2024-11-10","categories":["leadership","role"],"published":true,"slug":"team-leader","content":"

👥 Responsibility

The Team Leader is the role that acts as the bridge between management and team members. Their role includes overseeing daily operations, setting goals, measuring performance, and ensuring all team members are aligned with the organization's objectives. Additionally, an effective Team Leader provides guidance, support, and motivation to foster a positive and productive work environment.

📋 Organizer

Responsible for organizing the team's work, delegating tasks, and managing resources.

🎯 Strategist

Develops plans and strategies to achieve the company's and team's objectives, aligning with the organizational mission.

🗣️ Communicator

Facilitates internal and external communication, resolves conflicts, and promotes transparent dialogue.

💡 Problem Solver

Addresses challenges, makes informed decisions, and guides the team towards success.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Tech Lead","question":"What is a Tech Lead?","description":"A senior developer overseeing the technical aspects of a software team.","date":"2024-11-10","categories":["leadership","development","software"],"published":true,"slug":"tech-lead","content":"

👨‍💻 Leadership

A Tech Lead (TL), or technical leader, is a role assumed by a senior developer who oversees the technical aspects of a software team, making architectural and design decisions, and guiding team members on technical issues.

🏗️ Direction

They are responsible for setting the specifications and technical direction of the project, creating a framework of technical standards, and overseeing the quality of the software and system modifications.

🤝 Team Guidance

A technical leader plays a critical role in guiding the team, helping to solve technical problems, and analyzing existing operations to identify risks and redundancies.

📈 Professional Development

The role involves not only technical expertise but also leadership and mentorship, providing a launchpad for career advancement within the organization.

📐 Architecture

Technical leaders are involved in high-level architecture discussions and are responsible for the overall design and definition of the system's architecture.

🛠️ Guidance

Tech Leads guide team members through technical challenges and help to analyze and resolve operational risks.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Testing","question":"What is Testing?","description":"It is the process of verifying the quality, functionality, and performance of a software product.","date":"2024-11-10","categories":["testing","quality","qa","development","software"],"published":true,"slug":"test","content":"

🖥️ Definition

Testing, or test, is a procedure conducted to verify and validate the functionality, performance, security, and usability of a software product. This process is crucial for identifying and correcting errors, inconsistencies, or any other issues before the product is released to the market or delivered to the client.

🔄 Evolution

Testing activities have evolved with new techniques and approaches as applications become more complex.

🎯 Acceptance Testing

UAT (User Acceptance Testing) verifies if the entire system works as intended.

🔍 Code Review

Confirms that new and modified software adheres to coding standards and best practices.

🤝 Integration Testing

Integration tests ensure that software components or functions work together.

🧪 Unit Testing

Unit tests check that each unit of the software operates as expected.

📝 Functional Testing

Functional tests validate the system's functionalities by simulating user interaction scenarios based on specified requirements.

⚙️ Performance Testing

Performance tests evaluate the software's performance under different workloads.

🔁 Regression Testing

Regression tests check if new features break or degrade functionality.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"A/B Testing","question":"What are A/B Tests?","description":"They are a method for comparing two versions of a webpage or application.","date":"2024-11-10","categories":["marketing","product","ux"],"published":true,"slug":"test-a-b","content":"

🔬 Definition

A/B tests, also known as A/B split tests, are a method for comparing two versions of a webpage or application to determine which one performs better.

📊 Purpose

It is used to optimize the user experience (UX) and increase conversions by identifying which design or content variation is more effective.

🖥️ Process

A/B testing involves showing two or more versions (A and B) to different segments of website visitors at the same time and then analyzing the results to determine the better-performing version.

🧪 Implementation

The process is typically part of a broader Conversion Rate Optimization (CRO) strategy and is widely used in digital marketing and web design.

📈 Variants

A and B are the variants being tested, with A often being the current design (control) and B being a modified version (variation).

🔀 Random

Visitors are randomly assigned to either A or B, ensuring a fair comparison between the two variants.

📊 Analysis

Data on user behavior and conversions are collected and analyzed to determine which variant is more effective.

🖥️ Digital Elements

A/B testing can involve testing various digital elements such as webpage design, content, forms, and calls to action.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Tester","question":"What is a tester?","description":"Responsible for ensuring that software products are free of errors and meet quality standards.","date":"2024-11-10","categories":["testing","quality","development","software"],"published":true,"slug":"tester","content":"

🧪 Role

A tester, also known as a test engineer or QA (Quality Assurance), is primarily responsible for ensuring that software products function correctly, are free of errors, and meet specified quality standards.

📝 Responsibility

Testers analyze specifications, develop test cases, execute tests, report defects, and provide feedback to developers.

🔍 Skills

They need to be familiar with programming, understand system requirements, and have strong analytical and problem-solving skills.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Three Amigos","question":"What does Three Amigos mean?","description":"Refers to the primary perspectives of Business, Development, and Testing.","date":"2024-11-10","categories":["agile","product","development","business","software development"],"published":true,"slug":"three-amigos","content":"

👥 Definition

\"Three Amigos\" refers to a term used in agile software development to describe the collaboration and dialogue among three key roles: Business, Development, and Testing. This collaboration focuses on defining and agreeing on the product features' acceptance criteria from these three perspectives.

🎯 Goal

The goal is to ensure a shared and complete understanding of the requirements, resulting in a high-quality product that meets business needs and provides an excellent user experience.

📊 Business Perspective

Focuses on the problem being solved and the needs of the user.

🛠️ Development Perspective

Concerns how to create a solution for the identified problem.

🧪 Testing Perspective

Considers possible outcomes and ensures the solution meets the required criteria.

🤝 Building a Shared Understanding

The collaboration of the Three Amigos leads to a shared understanding of the product increment.

🔍 Early Problem Identification

Helps identify misunderstandings and confusion early in the development process.

🚀 Faster Delivery

The clarity from Three Amigos meetings can lead to quicker product delivery.

📈 Quality Assurance

Ensures the product meets both functional and non-functional requirements.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","hi","hu","it","ja","ko","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Throughput","question":"What is throughput?","description":"It is the number of work items completed within a specific timeframe.","date":"2024-11-10","categories":["kanban","metric","delivery","agile"],"published":true,"slug":"throughput","content":"

🔄 Definition

In the Kanban method, 'throughput' is used to describe the total number of tasks or work items that a team manages to complete during a specified period. This indicator is a measure of the team's productivity and efficiency and is used to assess and improve performance over time.

📊 Metric

Throughput is a key performance indicator that helps teams understand their delivery capacity and efficiency.

🔍 Measurement

Throughput is measured by counting the number of tasks or user stories that have been completed and delivered over a period, often per iteration or per week.

📈 Tracking

Teams can use throughput data to better track improvements in their delivery process and identify potential bottlenecks.

🔢 Type

Throughput is a quantitative measure of how much work is being completed over time within a Kanban system.

🏭 Analogy

It can be compared to the output of a factory, indicating the rate at which work is being processed and delivered.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Timeboxing","question":"What is timeboxing?","description":"It is a technique used to limit the time spent on a meeting or task.","date":"2024-11-10","categories":["time","agile","meeting"],"published":true,"slug":"timebox","content":"

⏳ Definition

A timebox is a time management concept that assigns a specific and predefined period of time to an activity, meeting, or task.

🎯 Purpose

The goal is to enhance efficiency and productivity by preventing excessive time spent on a single task and encouraging concentration and focus.

🏉 Scrum

In Scrum, all events have a recommended fixed timebox.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Top-Down","question":"What does Top-Down mean in transformation?","description":"It's an approach where senior management leads the transformation initiative.","date":"2024-11-10","categories":["transformation","leadership","agile"],"published":true,"slug":"top-down","content":"

🔝 Definition

In the context of agile transformation, the 'top-down' approach refers to a process in which the change initiative is led by the upper levels of the organization. In this method, leaders or senior management make strategic decisions, establish the vision and direction for the transformation, and then these decisions are implemented throughout the organization.

📈 Advantages and Needs

This approach can ensure a coherent vision and direction, providing a good threshold of empowerment and adoption speed in the organization's transformation, but it also requires leaders to understand and practice agile principles and practices to effectively guide the transformation.

🎯 Vision

The top-down approach involves communicating a clear vision and aligning it with organizational goals, which can lead to quick decision-making and clear directions.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"Trello","question":"What is Trello?","description":"It's a visual tool that facilitates the organization of tasks.","date":"2024-11-10","categories":["tool","kanban","productivity","board"],"published":true,"slug":"trello","content":"

🔍 Definition

Trello is a visual project management tool that allows teams to organize tasks and projects using boards, lists, and cards.

🛠️ Features

It offers features such as task assignment, due dates, attaching files, checklists, and integrations with other tools.

🆓 Interface

The Trello interface is based on boards, which represent projects, and within them, lists and cards are used to organize tasks and information.

🔄 Kanban

Trello's design is influenced by the Kanban method, emphasizing the visual management of tasks and workflows.

👁️ Visibility

Trello provides clear visibility on who is working on what and what tasks are pending, aiding in team coordination and project tracking.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"UAT","question":"What does UAT stand for?","description":"It stands for User Acceptance Testing.","date":"2024-11-10","categories":["testing","test","qa","ux"],"published":true,"slug":"uat","content":"

🎯 Acceptance Testing

Acceptance testing is a quality assurance process that evaluates whether a software application meets end-user approval and business requirements.

🔍 Meaning

It is the final phase of the software testing process, conducted to ensure that the system is ready for real-world use.

📈 Focus

Acceptance testing focuses on business objectives and user needs, determining if the software meets the acceptance criteria.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"UI","question":"What does UI stand for?","description":"It stands for User Interface.","date":"2024-11-10","categories":["UI","UX","Design"],"published":true,"slug":"ui---user-interface","content":"

🖥️ Definition

UI (User Interface) refers to the visual design of an application or website that users directly interact with.

🎨 Design

It includes design elements such as colors, typography, icons, forms, animations, buttons, and other interactive components.

👩‍💻 Role

A UI Designer is responsible for creating the visual part of a digital product's interface, focusing on both aesthetics and usability.

🔍 UI vs. UX

UI is often contrasted with UX (User Experience), with UI being the visible part and UX being the overall user experience, including the UI.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","th","tr","zh"]},{"title":"User Story Map","question":"What is a User Story Map?","description":"It's a technique that organizes the Product Backlog into two dimensions to visualize product functionalities and plan releases.","date":"2024-11-10","categories":["agile","user story","jeff patton","development","products","prioritization"],"published":true,"slug":"user-story-map","content":"

📜 Definition

User Story Map (USM), or User Story Mapping, is a technique that organizes the Product Backlog into two dimensions to comprehensively visualize product functionalities and plan their releases.

👤 Creator

Jeff Patton is credited with introducing the User Story Map technique in 2005, through the publication of his book bearing the same name.

🎯 Purpose

Its goal is to provide a common understanding of the product to the development team and stakeholders, facilitating product discovery and the prioritization of construction.

🏗️ Structure

The technique generally starts with identifying the product's backbone, followed by the development of the narrative flow detailing how different parts of the product connect and contribute to the final user experience. After establishing these elements, user stories are grouped under the activities or tasks identified in the backbone, and prioritized according to their importance and the value they deliver to the user to decide potential releases or the MVP.

🦴 Backbone

The backbone, or the spine of the User Story Map, refers to the main structure that organizes and categorizes user stories in a logical and hierarchical sequence that describes the user flow or the product's key activities. This structure acts as a guide to understanding how different parts of the product work together to provide value to the end-user.

📚 Narrative Flow

The narrative flow, within the context of User Story Mapping, describes the progression and relationship between user stories along the backbone. It focuses on how individual stories connect to form a cohesive and complete narrative about the user's experience with the product.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"UX","question":"What does UX stand for?","description":"It stands for User Experience.","date":"2024-11-10","categories":["UX","design"],"published":true,"slug":"ux---user-experience","content":"

📜 Definition

UX, or User Experience, is a strategy focused on providing the best possible experience to users of both digital and physical products and services.

🖥️ Digital Focus

In digital environments, team members specialized in UX ensure that interactions are smooth and obstacle-free with websites, mobile apps, software, and other digital solutions.

🏢 Physical Application

The discipline of UX is also relevant to physical products, aiming to improve the overall experience of users.

🎯 Importance

UX is crucial for customer satisfaction and retention and can significantly impact a company's success.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Value Stream Map","question":"What is a Value Stream Map (VSM)?","description":"It is a visual tool used to depict and analyze the flow of a process.","date":"2024-11-10","categories":["Lean","processes","waste"],"published":true,"slug":"value-stream-map","content":"

📜 Definition

The Value Stream Map, or VSM, is a visual tool used in Lean to depict and analyze the flow of materials and information through a production process.

🎯 Purpose

The main purpose of VSM is to identify areas for improvement and to visualize the entire production process for strategic review and optimization.

🔄 Steps

VSM involves creating a map of the current state, identifying and eliminating waste, creating a map of the future state, and implementing the improved process.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Waste","question":"What does waste mean?","description":"It refers to any activity that consumes resources but does not add value to the customer.","date":"2024-11-10","categories":["lean","kanban","waste","muda","kaizen"],"published":true,"slug":"waste","content":"

📜 Definition

In Lean management, waste refers to any activity that consumes resources but does not add value to the customer. Identifying and eliminating waste is crucial for improving the efficiency and effectiveness of processes.

🔄 Kanban

Kanban is a method within Lean management aimed at minimizing waste by visualizing work, limiting work in progress, and optimizing the workflow.

🏭 Origin

Lean management, including the concept of waste reduction, originated from the Toyota Production System (TPS), which identifies waste as muda, mura, and muri and actively seeks continuous improvement (kaizen) levers for its elimination.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Waterfall","question":"What is the Waterfall methodology?","description":"It's a linear and sequential approach to project management.","date":"2024-11-10","categories":["methodology","pmp","pmi","pmbok"],"published":true,"slug":"waterfall","content":"

🔄 Definition

The Waterfall methodology is a linear and sequential approach to project management, characterized by its phase-by-phase structure, where each phase must be completed before moving on to the next.

🏗️ Structure

Projects are divided into distinct phases, with no overlap between them, resembling the flow of a waterfall.

📊 Gantt Charts

Often visualized using Gantt charts, the Waterfall methodology is commonly used in industries like construction.

🚫 Limited Flexibility

Unlike agile frameworks, the Waterfall approach does not easily accommodate changes once a phase is completed, treating any change as a potential risk against the defined plan.

🌊 Phases

Waterfall typically has the following phases: requirement gathering, design, development, testing, deployment, and maintenance.

📑 Requirement Gathering

The initial phase involves the detailed collection and documentation of all project requirements.

🖥️ Design

This phase includes both high-level and detailed design work, specifying the system architecture and interfaces.

🛠️ Implementation

The actual development work begins, based on the design specifications from the previous phase.

✔️ Testing

Each component is tested to ensure it meets the specified requirements and functions as intended.

🚀 Deployment

The completed project is deployed or released to end-users or customers.

🔧 Maintenance

Maintenance and ongoing support activities are carried out to ensure the project continues to function correctly.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"WET","question":"What does WET mean?","description":"It stands for 'Write Everything Twice' or 'We Enjoy Typing'.","date":"2024-11-10","categories":["antipattern","development","software"],"published":true,"slug":"wet","content":"

💧 WET Principle

The WET principle, translating to 'Write Everything Twice' or 'We Enjoy Typing', represents an approach opposite to the DRY (Don't Repeat Yourself) principle by sarcastically allowing or even encouraging code repetition.

✏️ Write Everything Twice

WET is a humorous acronym suggesting writing or repeating code more than necessary, often seen as a way to emphasize simplicity or avoid the complexity of abstraction.

🧩 Lack of Abstraction

WET code may lack proper abstraction, leading to redundant and harder to maintain code due to excessive repetition of similar structures or logic.

🔀 Unpredictable Changes

Changes in WET code can be less predictable and uniform, as related elements may not change in a uniform manner, increasing the risk of errors and inconsistencies.

🔍 Testing Challenges

WET code can present challenges for testing, as there may be more code paths to cover due to duplication, increasing the effort and complexity to ensure software quality.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"WIP","question":"What does WIP mean?","description":"It stands for Work In Progress.","date":"2024-11-10","categories":["WIP Limit","Kanban"],"published":true,"slug":"wip---work-in-progress","content":"

🔨 Definition

Work In Progress (WIP) refers to tasks or products that are in the process of being completed but are not yet finished.

📊 Relevance

WIP is a crucial metric in production and software development, indicating the amount of work that is actively being done at any given moment.

🏭 Manufacturing

In manufacturing, WIP represents the inventory of partially completed products that are still in the production process.

📈 Development

In software development, WIP limits are used to optimize workflow and ensure that teams do not take on more work than they can effectively manage.

🔄 Kanban

WIP is a key concept in the Kanban method, where it is used to visualize and limit the amount of work in progress to improve efficiency and identify bottlenecks.

⏳ Production Efficiency

Monitoring WIP is essential for assessing the efficiency of the production process and identifying areas for improvement.

🔍 Lean Manufacturing

WIP is an area of focus in lean manufacturing, where balancing WIP levels is a key goal to streamline operations and reduce waste.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fi","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"WIP Limits","question":"What are WIP Limits?","description":"It's the maximum amount of work that can exist at each stage of a workflow.","date":"2024-11-10","categories":["WIP","Kanban"],"published":true,"slug":"wip-limit---work-in-progress-limit","content":"

🔒 Definition

WIP stands for \"Work In Progress,\" and a WIP Limit, or limit of WIP, is the maximum amount of work that can exist at each stage of a workflow in methods like Kanban.

🔎 Clarification

Limiting work in progress isn't about reducing the total amount of work to be done but limiting the number of tasks being handled simultaneously (multitasking). Its purpose is to improve focus and promote the philosophy of \"Stop starting and start finishing.\"

🔄 Importance

WIP limits help teams identify inefficiencies, expose bottlenecks, and focus on completing tasks, ultimately improving workflow performance.

📈 Application

Teams set WIP limits for each stage of the workflow, typically based on historical data, and adjust them over time to optimize performance.

🎯 Performance Improvement

WIP limits focus teams on completing tasks, which can lead to performance improvement, increased throughput, and reduced delivery times.

🔍 Bottlenecks

WIP limits expose bottlenecks and inefficiencies in the workflow, allowing teams to address them more effectively.

🔄 Continuous Evaluation

Teams regularly assess and adjust WIP limits to reflect changes in workflow performance.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]},{"title":"Wireframes","question":"What is a wireframe?","description":"It's a basic visual representation of an interface.","date":"2024-11-10","categories":["wireframe","UX","UI","Mockup","Figma"],"published":true,"slug":"wireframe","content":"

🖼️ Definition

A wireframe is a visual representation, usually in grayscale, that outlines the structure and functionality of a webpage or mobile application before the visual design and content are added.

🎯 Purpose

Wireframes serve to establish the basic layout and user experience, focusing on usability and navigation.

🔍 Use in Design

They are used in the early stages of design to ensure that the project develops according to the agreed objectives and to facilitate ease of use and future content growth.

🧰 Tools

One of the most commonly used tools for creating wireframes is Figma.

\n","language":"en","alternativeLangs":["ar","cs","da","de","el","es","fr","he","hi","hu","it","ja","ko","nl","no","pl","pt","ru","sv","th","tr","zh"]}]

Alcibíades Cabral Díaz

Definition

Purpose