Team Topology
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
The organizational structure and dynamics of teams within a company, designed to enhance collaboration and delivery. Important for optimizing team performance and project outcomes.
A small, cross-functional team of 6-12 people focused on delivering a specific product feature or component. Essential for agile development, allowing for rapid iteration and close collaboration among team members.
A team that supports other teams by providing specialized expertise and tools to improve their performance. Crucial for enhancing overall team effectiveness and efficiency.
A team structure focused on delivering value streams, often organized around a specific business capability or customer need. Crucial for enhancing delivery efficiency and aligning with business goals.
A cross-functional team that is given the autonomy, resources, and authority to make decisions and take ownership of the product's success, focusing on solving user problems and achieving business outcomes. Important for fostering innovation, accountability, and agility, leading to more effective product development and higher user satisfaction.
A team responsible for delivering specific features or enhancements, typically working on predefined requirements and focusing on the implementation of assigned features. Important for executing well-defined tasks and ensuring timely delivery of specific functionalities within a product.
A role in Agile project management responsible for ensuring the team follows Agile practices, facilitating meetings, and removing obstacles to progress. Essential for supporting Agile teams and ensuring successful implementation of Scrum practices.
Large-Scale Scrum (LeSS) is a framework for scaling agile product development to multiple teams working on a single product. It provides a minimalist, large-scale agile approach that maintains the simplicity and effectiveness of Scrum while addressing the challenges of coordination and integration in multi-team environments.
Walk the Wall (WTW) is a practice where team members physically move along a wall displaying their project's progress, discussing and updating tasks. Essential for fostering team collaboration and ensuring transparency in project status.
A lightweight, flexible approach to software development that emphasizes team communication and continuous improvement. Useful for tailoring agile practices to fit the specific needs of the development team.
Work that is not performed in real-time, allowing team members to collaborate without needing to be online simultaneously. Crucial for increasing flexibility and productivity in remote and distributed teams.
A brief daily meeting in Agile project management where team members share updates on their progress, plans for the day, and any obstacles they face. Essential for maintaining communication, transparency, and coordination within Agile teams.
A psychological phenomenon where the desire for harmony and conformity in a group results in irrational or dysfunctional decision-making. Crucial for recognizing and mitigating the risks of poor decision-making in teams.
Product-Oriented Delivery (POD) is a methodology that focuses on organizing teams around products rather than projects. This approach is essential for enhancing product focus, agility, and cross-functional collaboration.
A team responsible for developing and maintaining the foundational systems and services that support other teams and products. Crucial for ensuring scalability and efficiency across the organization.
A cross-functional team focused on solving customer problems and achieving business outcomes, with a strong emphasis on discovery, experimentation, and continuous improvement. Crucial for creating valuable and innovative products that meet user needs and drive business success through iterative development and close collaboration with stakeholders.
A team structure within an organization focused on managing and integrating complex subsystems. Important for ensuring seamless integration and functionality of complex projects.
A team focused on designing and improving the user experience across products and services. Essential for ensuring cohesive and high-quality user experiences.
A short, daily meeting (separate from Standup) for the development team to sync on progress and plan for the day, part of the Scrum agile framework. Crucial for maintaining team alignment and momentum in agile projects.
A measure used in Agile project management to quantify the amount of work a team can complete in a given sprint, typically measured in story points. Crucial for planning and forecasting in Agile projects and understanding team capacity.
A senior technical role responsible for guiding the development team and ensuring the technical quality of projects. Important for maintaining technical standards and mentoring team members.
A regular meeting in Agile project management where team members discuss progress, plan work, and identify any obstacles, typically held daily. Crucial for maintaining communication, transparency, and accountability within Agile teams.
A leadership philosophy where the leader prioritizes the needs of the team, empowering and supporting members to achieve their full potential and fostering a collaborative, inclusive environment. Important for building strong, motivated teams, enhancing collaboration, and promoting a culture of trust and respect within an organization.
Agile Release Train (ART) is a long-lived team of Agile teams that, along with other stakeholders, incrementally develops, delivers, and operates one or more solutions in a value stream. Important for coordinating Agile development and delivery at scale.
A consensus-building technique where participants show their level of agreement or support by raising zero to five fingers. Useful for quickly gauging team agreement and making collaborative decisions in product design and development meetings.
Program Increment (PI) Planning is a cadence-based event that serves as the heartbeat of the Agile Release Train, aligning teams on goals and priorities for the next increment. Crucial for aligning teams, setting goals, and planning work.
The practice of guiding and inspiring teams to develop and deliver successful products, often involving strategic vision, team management, and innovation. Crucial for driving product success and fostering a culture of innovation and excellence.
A concise statement of what the team aims to achieve during a sprint, providing direction and a shared understanding of the sprint's purpose. Crucial for ensuring team alignment and focus on the most important outcomes during a sprint.
A psychological state where individuals feel as though the success and well-being of a project or task is their personal responsibility, akin to having an "owner's mentality.". Essential for fostering accountability, motivation, and proactive engagement within a product design team.
A unit of measure used in Agile project management to estimate the relative effort required to complete a user story or task. Crucial for planning and managing workload within Agile teams.
An estimation technique used in Agile software development where team members assign story points to tasks through consensus-based discussion. Essential for collaborative and accurate project planning and estimation.
A prioritized list of ideas and potential features for future product development, embodying a collective vision for innovation and improvement. Essential for managing creative input and maintaining an innovation pipeline that aligns with the team's entrepreneurial spirit and shared commitment to product excellence.
A meeting where the Agile team discusses and decides what tasks will be completed in the upcoming sprint, establishing a clear plan for the sprint's duration. Crucial for ensuring the team is aligned and has a clear understanding of the work to be done in the sprint.
A clear and concise list of criteria that a product or task must meet to be considered complete, ensuring alignment and understanding within a team. Essential for maintaining quality and consistency in agile project management.
The tendency to favor people who are similar to oneself in terms of background, beliefs, or interests. Important for recognizing and mitigating bias in user research and team dynamics.
Drivers, Approvers, Contributors, and Informed (DACI) is a responsibility assignment framework that clarifies roles and responsibilities. Essential for making clear and effective decisions in collaborative environments.
A skill set that combines deep knowledge in a single area (the vertical stroke) with a broad understanding across multiple disciplines (the horizontal stroke). Valuable for fostering versatility and collaboration within teams, enhancing problem-solving and innovation.
A meeting at the end of a sprint where the development team presents their completed work to stakeholders. Crucial for gathering feedback and demonstrating progress.
A senior role responsible for guiding the product management team and overseeing the development and strategy of products. Crucial for ensuring successful product development and alignment with business goals.
A list of tasks and deliverables that a team commits to completing during a sprint, providing a clear focus and scope for the sprint's duration. Essential for organizing and prioritizing work within an Agile sprint.
A management framework that organizes employees into small, cross-functional teams (tribes) to enhance agility, collaboration, and innovation. Important for fostering a collaborative and agile work environment.
A phenomenon where group members make decisions that are more extreme than the initial inclination of its members due to group discussions and interactions. Crucial for understanding and mitigating the risks of extreme decision-making in group settings.
A time-boxed period in which Agile teams deliver incremental value in the form of working, tested software and systems. Essential for aligning teams, managing dependencies, and ensuring continuous delivery.
A cognitive bias where group members tend to discuss information that everyone already knows rather than sharing unique information, leading to less effective decision-making. Important for understanding group dynamics and improving the quality of collaborative decision-making among designers.
An agile framework for managing work with an emphasis on software development, characterized by sprints and iterative progress. Essential for improving productivity and delivering incremental value in development projects.
The orchestration and optimization of design operations to improve efficiency, quality, and impact of the design function within an organization. Crucial for enhancing the efficiency and effectiveness of design teams.
A strategic planning tool that outlines the future direction of a project or product using Kanban principles, emphasizing continuous delivery and improvement. Important for aligning team efforts and maintaining focus on long-term goals.
A time-constrained, intensive process that helps teams quickly design, prototype, and test ideas. Important for rapidly developing and validating design solutions.
A repository for team members to submit and collect innovative ideas, reflecting a commitment to fostering creativity and shared ownership of product development. Crucial for maintaining an open culture of innovation and capturing diverse perspectives that contribute to the product's evolution and success.
Responsible, Accountable, Consulted, and Informed (RACI) is a responsibility assignment framework that clarifies roles and responsibilities in a projec. Crucial for ensuring clear communication and accountability in project management.
The ability to recognize, understand, and manage one's own emotions and the emotions of others. Essential for designing empathetic user experiences and effective team collaboration.
SAFe is a framework designed to scale agile practices across large organizations by integrating agile and lean principles. It is widely used but criticized for its rigidity, bureaucratic structure, and potential to stifle true agile culture.
Also known as Parkinson's Law of Triviality, is the tendency to spend excessive time on trivial details while neglecting more important issues. Crucial for improving project management and team efficiency.
A meeting held at the end of a project or development cycle, also known as a "post-mortem," to review what went well, what didn't, and how processes can be improved in the future. Crucial for continuous improvement and learning from past experiences to enhance future projects.
A cognitive bias where individuals favor others who are perceived to be similar to themselves, affecting judgments and decision-making. Crucial for understanding biases in team dynamics and decision-making processes among designers.
The set of shared values, practices, and goals that characterize a startup company. Important for fostering innovation, agility, and a collaborative environment within product design teams.
Getting Things Done (GTD) is a productivity methodology that emphasizes capturing tasks, organizing them, and taking action. Essential for improving personal and team productivity and task management.
A collection of multiple squads working in the same domain or on related projects, typically consisting of 40-150 people. Important for ensuring alignment and coordination across related squads, fostering a larger community with shared goals.
The practice of guiding and inspiring teams to create effective, user-centered design solutions that align with business goals. Crucial for fostering a culture of innovation, collaboration, and excellence in design practices within organizations.
A strategy used to determine the proportion of various SMEs needed to support a pipeline of work. Important for optimizing resource allocation, enhancing efficiency, and ensuring teams have the appropriate support based on design demand and complexity.