Learning Resources

Welcome to the Learning Resources Hub

Your ultimate destination for mastering Agile and Scrum. Whether you're an aspiring Agile coach, a Product Owner, or a team member looking to enhance your skills, our resources are tailored to meet your learning needs. Dive into our extensive collection of articles, guides, and tools, all expertly crafted to enrich your understanding of Agile methodologies and Scrum practices. Start exploring now and take a significant step in advancing your Agile knowledge and skills.

Free Downloads

Self-Paced E-Learning

Videos

Articles, Web Content & Whitepapers

Frequently Asked Questions

Glossary of Terms

Agile: A project management approach that emphasizes flexibility, collaboration, and customer satisfaction. It allows for continual revision of a project throughout its lifecycle.
Scrum: An Agile framework for managing complex projects. Scrum emphasizes an iterative process, collaboration, and the ability to adapt to change.
Iteration: In the context of Agile and Scrum, an iteration is a single development cycle in a project. Typically, an iteration lasts one to four weeks.
Lean: A systematic method for waste minimization and efficiency within a manufacturing system without sacrificing productivity.
Backlog: In Scrum, a backlog is a list of tasks or goals that a team needs to achieve. The tasks are prioritized based on their importance or relevance to the project.
Sprint: A set time period in which specific work has to be completed and made ready for review (commonly 2-4 weeks).
Product Owner: In Scrum, the Product Owner is the person responsible for maximizing the value of the product resulting from the work of the Development Team.
Scrum Master: A facilitator for the Agile development team. The Scrum Master ensures the team adheres to Scrum theory, practices, and rules.
User Story: In Agile development, a user story is a simplified description of a software feature from an end user's perspective.
Epic: A large user story that is broken down into smaller stories. It often requires more than one iteration to complete.
Burndown Chart: A visual representation of work left to do versus time. It helps track progress and manage work throughout the duration of a Sprint.
Standup: Also known as a daily Scrum meeting, a short meeting where the team coordinates activities for the day.
Velocity: A measure of the amount of work a team can tackle during a single Sprint, calculated by the total number of points (estimated size) of user stories completed in the Sprint.
Retrospective: A meeting held at the end of each Sprint where the team discusses what went well, what can be improved, and how they can implement the improvements in the next Sprint.
Kanban: A visual workflow management method derived from Agile methodologies. It uses a board and cards to represent work items and their flow through the process.
Continuous Integration (CI): A development practice where developers integrate code into a shared repository frequently, usually multiple times per day.
Continuous Deployment (CD): A software development practice where code changes are automatically tested and deployed to a production environment.
DevOps: A set of practices that combines software development and IT operations. It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.
Timeboxing: Allocating a fixed time period, called a timebox, to each planned activity. Sprints are an example of timeboxing.
Increment: The sum of all the product backlog items completed during a Sprint combined with the value of the increments of all previous Sprints.
Story Points: A measure of effort required to implement a story. They allow teams to express the difficulty of a story in an abstract way.
Acceptance Criteria: The conditions that a software product must satisfy to be accepted by a user, customer, or in the case of system level functionality, the consuming system.
Test-Driven Development (TDD): A software development practice where test cases are developed before the functional code. It encourages simple designs and inspires confidence.
Pair Programming: An Agile software development technique in which two programmers work together at one workstation, sharing the same screen, keyboard and mouse.
Refactoring: The process of restructuring existing computer code without changing its external behavior for the sake of improving the nonfunctional attributes of the software.
Spike: A user story that cannot be estimated until a development team runs a time-boxed investigation. It's taken on when there is a need to answer questions or reduce uncertainty in a story or epic.
Product Backlog Refinement (PBR): The process through which product backlog items are reviewed by the team and revised. The goal is to keep the backlog up-to-date and ensure that backlog items are prepared for upcoming sprints.
Definition of Done (DoD): A shared understanding within the Scrum Team on what it takes to make a Product Backlog Item (PBI) or an Increment "Done."
Sprint Review: A meeting at the end of each sprint where the team and stakeholders inspect what was done during the sprint and adapt the backlog if needed.
Scrum of Scrums: A technique to scale Scrum up to large groups, where several Scrum teams work together. The Scrum of Scrums meeting helps coordinate their work.