Loading content
Agile Ways of Working describes principles, practices and roles that enable teams to deliver value adaptively and incrementally. It includes frameworks such as Scrum and Kanban and emphasizes customer focus, short feedback cycles and continuous improvement across product and delivery processes. Teams use metrics and retrospectives to adapt.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Agile Ways of Working is an umbrella term for ways teams deliver work in short cycles and adapt based on feedback.
The approach gathers practices from agile software development as a response to rigid, heavy, document-driven delivery processes. The 2001 Agile Manifesto set out shared values and principles around collaboration, working results, and responding to change. Scrum later turned part of this thinking into a clearly defined framework; today the idea is also used for product and delivery work beyond software.
Think of agile ways of working as a learn-and-deliver loop: a prioritized goal is broken into small pieces, the team delivers a visible increment, stakeholders inspect the result, and feedback flows back into the next planning step. Roles, artifacts, and fixed touchpoints give the rhythm structure; metrics and retrospectives show whether adaptation is actually improving delivery.
Guiding ideas such as collaboration, transparency, and responsiveness set the direction.
Concrete routines and working forms make day-to-day collaboration manageable.
Clear responsibilities help with prioritization, alignment, and decision-making.
A small, usable result makes progress visible and testable.
Short review-and-learn loops expose assumptions early and support course correction.
Teams regularly reflect on how they work and adjust it deliberately.
The approach helps when requirements change, fast alignment matters, or product work needs tighter connection to customer value. It only works well when responsibilities, decision rights, and priorities are genuinely clear; rituals or slogans do not replace discipline or good governance. Highly regulated or highly coupled environments often need additional guardrails.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.