Disciplined Agile
A process decision toolkit that allows organizations to tailor their agile practices to their specific needs, promoting agility and continuous improvement. Crucial for optimizing agile practices to fit organizational contexts.
86 topics found for:
“agile meeting”
Standup
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.
Agile Manifesto
A declaration of the values and principles essential for agile software development. Foundational for understanding the ethos of agile methodologies.
Scrum Meeting
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.
Agile Transformation
The process of transitioning an organization to agile methodologies, including changes in culture, processes, and practices. Essential for organizations seeking to adopt agile practices for improved efficiency and responsiveness.
Daily Scrum
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.
Sprint Demo
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.
Sprint Planning
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.
T-Shirt Sizing
A relative estimation technique used in Agile project management to quickly assess the size and complexity of tasks by assigning them T-shirt sizes (e.g., small, medium, large). Crucial for efficient project planning and workload management.
ASD
Adaptive Software Development (ASD) is a software development methodology that focuses on continuous adaptation to changing requirements and environments. Essential for managing changing requirements and ensuring agile project delivery.
Agile Values
The core values outlined in the Agile Manifesto, including individuals and interactions, working software, customer collaboration, and responding to change. Fundamental for guiding agile practices and fostering an agile mindset.
Agile Framework
A set of practices and principles that guide agile methodologies, such as Scrum and Kanban, to improve project management and product development. Important for structuring agile practices and ensuring effective project delivery.
Dual-Track Agile
An agile methodology that separates product discovery and product delivery into parallel tracks to ensure continuous learning and delivery. Essential for balancing innovation and execution in agile product development.
Business Agility
The ability of an organization to adapt quickly to market changes and external forces while maintaining a focus on delivering value. Essential for fostering an adaptable and resilient design and development process.
Scrum Master
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.
Definition of Done
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.
Sprint Backlog
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.
Retrospective
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.
Program Increment
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.
Definition of Ready
A set of criteria that a user story or task must meet before being accepted into the development cycle, ensuring it is actionable and clear. Essential for ensuring that tasks are well-defined and ready for development.
Lean Software Development
An agile methodology focused on delivering value to the customer through principles such as eliminating waste, amplifying learning, and delivering as fast as possible. Crucial for improving efficiency and effectiveness in software development processes.
User Story
A simple description of a feature from the perspective of the user, typically used in Agile development to capture requirements and guide development. Crucial for ensuring that development efforts are aligned with user needs and priorities.
Product Owner
A role in Agile development responsible for defining the product vision, prioritizing the product backlog, and ensuring the development team delivers value to users. Essential for guiding product development and ensuring alignment with user needs and business goals.
DSDM
Dynamic Systems Development Method (DSDM) is an agile project delivery framework focused on delivering business value early and continuously. Essential for ensuring that projects align with business goals and user needs through iterative processes.
Feature Team
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.
Engineering Backlog
A prioritized list of tasks, features, and technical debt items that need to be addressed by the engineering team. Essential for managing and organizing work in software development projects.
Stream-Aligned Team
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.
Rapid Experimentation
The practice of quickly testing and iterating on ideas to validate assumptions and learn from user feedback in a short time frame. Essential for agile development and making data-driven decisions efficiently.
MoSCoW Prioritization
Must have, Should have, Could have, and Won't have (MoSCoW) is a method used to prioritize features or tasks. Crucial for effective project management and ensuring focus on essential features.
RAD
Rapid Application Development (RAD) is a software development methodology that emphasizes quick prototyping and iterative delivery. Essential for reducing development time and adapting to changing requirements.
MVP
Minimum Viable Product (MVP) is a version of a product with just enough features to be usable by early customers who can then provide feedback for future product development. Essential for validating product ideas quickly and cost-effectively, allowing teams to learn about customer needs without fully developing the product.
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.
BDD
Behavior-Driven Development (BDD) is a software development approach where applications are specified and designed by describing their behavior. Important for ensuring clear communication and shared understanding between developers and stakeholders.
TDD
Test-Driven Development (TDD) is a software development methodology where tests are written before the code that needs to pass them. Essential for ensuring high code quality and reducing bugs.
Kickoff
The initial meeting or phase where a new feature or initiative is introduced, discussed, and planned, involving all relevant stakeholders. Important for ensuring clear communication and alignment on new feature development.
Acceptance Testing
A type of testing conducted to determine if the requirements of a specification are met, often the final step before delivery to the customer. Important for ensuring that a product meets the defined criteria and is ready for release.
Product Delivery
The process of bringing a product from development to market, ensuring it meets quality standards and customer needs. Crucial for the successful launch and adoption of a product.
UAT
User Acceptance Testing (UAT) is the final phase of the software testing process where actual users test the software to ensure it meets their requirements. Crucial for validating that the software functions correctly in real-world scenarios before its release.
Customer Development
A framework for discovering and validating the right market for a product, building the right product features, and validating the business model. Important for ensuring that products meet market needs and customer expectations.
Beta Testing
A testing phase where a product is released to a limited audience outside the development team to identify issues and gather feedback before the final release. Essential for refining a product based on real user feedback and ensuring it meets user needs.
Acceptance Criteria
Specific conditions that must be met for a product or feature to be considered complete and satisfactory. Essential for product managers and developers to ensure clarity and alignment on what constitutes "done".
Fist To Five
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.
Product Development
Product Development is the process of bringing a new product to market or improving an existing one. Crucial for innovation, meeting customer needs, and maintaining a competitive edge.
Feedback Loop
A system where outputs are fed back into the process as inputs, allowing for continuous improvement based on user responses. Crucial for iterative development and continuous improvement in design and product management.
NPD
New Product Development (NPD) is the complete process of bringing a new product to market, from idea generation to commercialization. Essential for companies to innovate, stay competitive, and meet evolving customer needs through a structured approach to creating and launching new offerings.
MVF
Minimum Viable Feature (MVF) is the smallest possible version of a feature that delivers value to users and allows for meaningful feedback collection. Crucial for rapid iteration in product development, enabling teams to validate ideas quickly and efficiently while minimizing resource investment.
Digital Product Manager
A role focused on overseeing the development, launch, and lifecycle of digital products, ensuring they meet market needs and business goals. Essential for integrating digital product strategy and development.
MRD
Market Requirements Document (MRD) is a comprehensive document that outlines the market's needs, target audience, and business objectives for a product. It serves as a crucial tool for aligning product development efforts with market demands and business goals, ensuring that the final product meets customer needs and achieves market success.
SDLC
Software Development Life Cycle (SDLC) is a process for planning, creating, testing, and deploying an information system. Essential for managing the complexities of software development and ensuring project success.
Implicit Requirements
Needs and expectations that are not explicitly stated by users but are inferred from their behavior and context. Crucial for identifying and addressing unarticulated user needs.
Go-to-Market (GTM)
A strategy or plan that outlines how a company will launch a product to market, including target audience, marketing tactics, and sales strategy. Essential for successfully launching products and capturing market share.
Release
The distribution of a new or updated software product to users. Important for delivering new features, improvements, and fixes to users, ensuring continuous enhancement of the product.
Automated Testing
The use of software tools to run tests on code automatically, ensuring functionality and identifying defects without manual intervention. Crucial for maintaining high code quality and efficiency in the development process.
Alpha Test
A preliminary testing phase conducted by internal staff to identify bugs before releasing the product to external testers or customers. Crucial for ensuring product quality and functionality before broader release.
Product Team
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.
Product Strategy
Product Strategy is a framework that outlines how a product will achieve its business goals and satisfy customer needs. Crucial for guiding product development, prioritizing features, and aligning the team around a clear vision.
Formative Testing
A type of usability testing conducted during the design process to identify issues and improve the design iteratively. Crucial for refining designs and ensuring usability before final release.
Product Development Cycle
The series of stages a product goes through from initial concept to market release, including planning, design, development, testing, and launch. Essential for understanding the full lifecycle of product creation and bringing products to market efficiently.
Evaluative Research
Research conducted to assess the effectiveness, usability, and impact of a design or product. Essential for validating design decisions and improving user experiences.
Placing Bets
A strategic approach where multiple potential solutions are tested to identify the most promising one. Crucial for innovation and reducing risk in decision-making.