A software development methodology. It focuses on flexibility, collaboration between team members, and delivering consistent value to stakeholders. With each iteration comes new, actionable insights into what’s working, what isn’t, and what needs to change. It’s a multidimensional way of working that removes the bottlenecks inherent in traditional project management.
An agile coach provides professional coaching and know-how by helping organizations understand the agile methodology and its benefits well enough to implement it at scale across cross-functional teams.
A set of values and principles that drive improvement in software development processes. These values are Individuals and interactions over processes and tools, Working software over comprehensive documentation, Customer collaboration over contract negotiation, and Responding to change over following a plan.
Find out what the 12 agile manifesto principles are.
Understanding and living the four core values; respect people, optimize flow, encourage innovation, and relentlessly improve.
In each development cycle — or sprint — of an agile project, each agile team iterates the product according to customer feedback. That increases the speed of product development and the efficiency of that process. And in each iteration, the team releases or launches a new or improved product functionality.
Find out the three key roles of an Agile team.
A meeting with everyone (esp. including distributed team members) to understand how the whole team is going.
Includes keeping the backlog up-to-date and complete, splitting broad user stories such as tasks or bugs, adding detail to them to improve comprehension, adding or reviewing estimates to issues, and ordering backlog issues to deliver high-priority ones.
A visualization of how much work is left to do and how much time there is to complete it. Visible to everyone. This graphical representation predicts how much work the team plans to complete within the allotted time.
The team is made up of people from across the business with different expertise and skill sets. Together the team works toward a common goal.
A short meeting to briefly hear from each person on the team what they've been doing, what they're planning to do, and if anything is blocking their work.
You need to clearly define the sprint's goals and what it means to be done. How will the team know if they achieved the desired outcomes? What does “done” look like? Does everyone agree on this definition for every given task and the overall goals of the sprint?
How does having a definition of done help my sprint?
An epic is a bigger, overarching story or step in the journey that contains user stories.
Having an idea of how much work it will take to finish each user story.
Is an agile approach centered around improving software quality and responsiveness while evolving with customer requirements.
Read more about extreme programming here.
An agile workflow where you visually organize tasks that ensure work items move forward while allowing changes and adjustments to be made along the way.
In its simplest form, a Kanban board has three columns; To-Do, Doing, and Done. Work moves from one section to the next on a physical or digital board, depending on how far along the specific task is.
A person whose job involves handling or using information; typically, someone whose job is to sit in front of a computer.
An agile methodology that, in basic terms, is quite simple: improve efficiency by eliminating waste. Lean agile strives to reduce all tasks and activities that don’t provide real value.
A principle that observes that 80% of outcomes are the result of only 20% of actions. A reason to focus on higher-impact work.
Companies that work with us to sell and implement our solutions for customers. You can find our Easy Agile Partners here.
Fictional generalizations of your most valuable customers. They help teams understand their customers by bringing together demographic information like age, gender, location, and income, alongside psychographic information like interests, frustrations, and personal or professional motivations.
Is an accurate, collaborative, team-building method of estimating the work for each user story.
A product backlog is a prioritized and ordered list that represents the work to be completed by a development team.
Find out the 4 characteristics of a good product backlog.
The agile team member with the deepest knowledge of the product. When something isn't right with the product, they should know that quickly. They deeply understand how the product contributes to the company's vision and goals.
A long-term theme of work for several teams towards a business objective. A part of the SAFe framework.
A visual summary of features or goals, cross-team dependencies, and other factors that impact their delivery.
A meta-work cycle composed of several teams working over several sprints to develop a set of work or features within a program; characterized by a PI planning session at the beginning. A part of the SAFe framework.
They link the scheduled features to broader business objectives. This helps align work that needs to be done with broader business goals. They are then broken down into committed and uncommitted objectives.
A meeting at the end of a work cycle (such as a sprint) to review the work process and consider improvements.
SAFe stands for scaled agile framework enterprise. As agile focuses on small-scale continuous improvement, SAFe uses its philosophy at an enterprise level. SAFe increases business agility, resulting in flexible and responsive teams for larger organizations.
An Agile framework characterized by set-length work cycles (sprints) and meetings at the beginning and end of cycles to plan and review work.
They guide the team through the Scrum process. They facilitate the process, helping the team to master the framework and improve from one sprint to the next.
Find out how to become a successful scrum master.
To spend a fixed period investigating the viability of a task or feature; prevents tasks with a lot of unknowns expanding to take more time than they're worth.
A work cycle in Scrum-style Agile typically one or two weeks of work.
A sprint backlog consists of the items that must be completed to reach the sprint goal.
An agile ceremony designed to align the team around a goal for the next sprint and the specific set of backlog items that will make that sprint goal a reality.
Time to showcase the team’s completed work and gather feedback from stakeholders. A variety of attendees from outside the team offer valuable insights from different viewpoints. This event also helps build trust with both external and internal stakeholders.
A development team's velocity is the amount of work completed in each sprint. It can be used as a measure of how long it will take the team to work through its backlog.
A measure of the estimated difficulty or duration of a task or ticket.
It is an arbitrary scale that a team develops over time as story points aren't directly proportional to time in hours or a 1-10 scale: story points estimate tasks relative to other estimated tasks.
Find out why user story points matter.
To propose the first solution that comes to mind; the immediate or instinctive answer (Daniel Kahneman, Thinking Fast and Slow, 2011).
To consider a problem more deeply/thoroughly (Daniel Kahneman, Thinking Fast and Slow, 2011).
The basic, expected features or requirements of a product. For example, a social networking app where you couldn't directly message other people would be weird.
A user story is a goal or outcome that the user or customer wants to achieve. Usually, you’ll write user stories like this:
“As a [persona type], I want to [action] so that [benefit].”
A user story should be the smallest unit of work that can deliver value back to the customer.
A useful way to organize and prioritize your user stories so that you can schedule your work and design your releases.