Start Stop Continue Retrospective

The Start, Stop, Continue Retrospective is a popular agile retrospective format that provides a structured way for teams to reflect on their current practices and determine clear action items for improvement. It encourages direct feedback and promotes constructive discussions on team dynamics, processes, and behaviors.

  • Purpose and Scope: The aim is to foster a proactive approach to team development, where team members collaboratively identify adjustments needed for better performance. It’s especially useful for maintaining momentum in continuous improvement and ensuring actionable outcomes from retrospectives.
  • Principal Concepts: The framework is based on three simple prompts: identifying new practices to start, unproductive activities to stop, and successful actions to continue.

Theoretical Foundations of Start, Stop, Continue Retrospective

This retrospective technique is rooted in behavior analysis and change management principles, focusing on:

  • Behavioral Feedback: Providing specific feedback on team behaviors that should be initiated, altered, or maintained.
  • Kaizen (Continuous Improvement): Emphasizes incremental changes for ongoing process improvement, a core principle in Agile methodologies.

Methods and Techniques in Start, Stop, Continue Retrospective

Implementing this retrospective involves a few practical steps:

  • Preparation: Set up a meeting with all relevant team members, ensuring a whiteboard or digital board is divided into three sections labeled “Start,” “Stop,” and “Continue.”
  • Brainstorming: Team members independently jot down their thoughts on sticky notes or digital cards under each category based on their recent experiences in the project cycle.
  • Sharing and Discussion: Each participant presents their notes, explaining why they believe certain actions should start, stop, or continue. The team discusses each suggestion to reach a consensus or understanding.
  • Action Planning: The team agrees on concrete actions for the suggestions under “Start” and “Stop,” and acknowledges the behaviors to “Continue.” These actions are noted for implementation in the next cycle.

Applications of Start, Stop, Continue Retrospective

This retrospective format can be applied in various settings beyond software development:

  • Business Teams: To refine business processes or improve team collaboration.
  • Educational Groups: For teachers and administrators looking to adjust classroom practices or administrative tasks.
  • Healthcare Teams: To enhance patient care or streamline medical procedures.

Industries Influenced by Start, Stop, Continue Retrospective

  • Software Development: Agile teams use it to adjust their workflows or enhance team collaboration.
  • Manufacturing: Teams reflect on production processes to increase efficiency.
  • Service Industries: Used to refine customer service practices and internal operations.

Advantages of Using Start, Stop, Continue Retrospective

This retrospective format offers several benefits:

  • Simplicity and Clarity: The straightforward nature allows for easy understanding and participation from all team members.
  • Action-Oriented Outcomes: Focuses on actionable insights, which can directly influence team performance and project outcomes.
  • Enhanced Team Communication: Facilitates open dialogue, enhancing team cohesion and mutual understanding.

Challenges and Considerations in Start, Stop, Continue Retrospective

While effective, the retrospective has its challenges:

  • Surface-Level Analysis: Without careful facilitation, discussions may remain superficial and not address deeper issues.
  • Resistance to Change: Team members may be resistant to suggest or accept changes, especially in the “Stop” category.
  • Follow-Through: Ensuring that agreed-upon actions are implemented can be challenging without proper tracking and accountability.

Integration with Broader Agile Practices

To maximize effectiveness, integrate this retrospective into broader Agile practices by:

  • Regular Implementation: Conduct these retrospectives at the end of each sprint or project phase to maintain a rhythm of improvement.
  • Documentation and Review: Keep records of retrospective outcomes and review them in future sessions to track progress and accountability.

Future Directions in Start, Stop, Continue Retrospective

As teams continue to evolve, so might the applications of this retrospective format:

  • Digital Facilitation Tools: Leveraging new tools that facilitate remote or hybrid retrospectives efficiently.
  • Integration with Employee Performance Management: Using insights from these retrospectives for personal development plans and performance reviews.

Conclusion and Strategic Recommendations

The Start, Stop, Continue Retrospective is an invaluable tool for any team committed to iterative improvement:

  • Encourage Full Participation: Ensure that all team members feel comfortable contributing to each section of the retrospective.
  • Act on Feedback: Develop a clear plan for implementing changes and monitor their impact, reinforcing the value of each retrospective session.
Related FrameworksDescriptionWhen to Apply
Scrum of Scrums– Scrum of Scrums is a scaled Agile technique used to coordinate work and facilitate communication between multiple Scrum teams working on the same product or project. It involves representatives from each team participating in regular meetings to discuss progress, dependencies, and impediments, and to synchronize efforts. Scrum of Scrums helps ensure alignment, transparency, and collaboration among teams, enabling them to deliver integrated increments of value and address cross-team dependencies effectively.– When organizations adopt the Scrum framework for large-scale projects or products involving multiple teams that need to collaborate and coordinate their efforts effectively. – In environments where ensuring alignment, transparency, and collaboration among distributed or cross-functional teams is essential for delivering integrated increments of value and achieving project or product objectives efficiently and effectively.
Lean Coffee– Lean Coffee is a structured and agenda-less meeting format used for facilitating discussions and generating insights collaboratively. Participants propose topics for discussion, vote on the most relevant ones, and engage in time-boxed conversations focused on those topics. Lean Coffee encourages open dialogue, idea sharing, and collective problem-solving, enabling teams to address issues, share knowledge, and make decisions in a democratic and efficient manner.– When organizations want to foster a culture of continuous improvement, knowledge sharing, and collaboration within Agile teams or communities of practice. – In environments where facilitating engaging and productive discussions, addressing team concerns, and making collective decisions efficiently are essential for driving learning, innovation, and improvement at the team or organizational level.
Agile Health Check– Agile Health Check is a retrospective technique used to assess the health and performance of Agile teams or projects based on a set of predefined criteria or dimensions. It involves conducting regular assessments or surveys to gather feedback from team members on various aspects of Agile practices, team dynamics, and project outcomes. Agile Health Checks help identify strengths, weaknesses, and improvement opportunities, enabling teams to reflect on their performance and implement changes to enhance their effectiveness and productivity.– When organizations seek to evaluate the maturity, effectiveness, and health of Agile practices within teams or projects and identify areas for improvement. – In environments where fostering continuous learning, adaptation, and improvement is essential for optimizing Agile performance, increasing team collaboration, and delivering value predictably and sustainably in dynamic and complex business environments.
Retrospective Starfish– Retrospective Starfish is a retrospective technique used to explore the impact of actions or events on team performance and identify opportunities for improvement. It involves drawing a starfish diagram with five sections representing different levels of impact: Start, Stop, Continue, More, and Less. Team members reflect on recent activities or behaviors and categorize them into these sections based on their perceived impact on team effectiveness. Retrospective Starfish encourages teams to celebrate successes, eliminate inefficiencies, and experiment with new approaches to enhance their performance and collaboration.– When teams want to reflect on their recent experiences, successes, and challenges and identify actionable improvements for enhancing their performance and collaboration. – In environments where fostering a culture of continuous learning, adaptation, and experimentation is essential for driving team effectiveness, innovation, and resilience in response to changing dynamics and challenges.
Retrospective 4Ls– Retrospective 4Ls is a retrospective technique used to explore team experiences, successes, and areas for improvement based on four categories: Liked, Learned, Lacked, and Longed For. It involves team members reflecting on recent activities or events and sharing their perspectives on what they liked, what they learned, what was lacking, and what they longed for in terms of support or resources. Retrospective 4Ls encourages open communication, empathy, and accountability, enabling teams to celebrate achievements, address gaps, and align on future priorities effectively.– When teams want to reflect on their recent experiences, celebrate achievements, and identify opportunities for improvement collaboratively. – In environments where promoting open communication, empathy, and accountability among team members is essential for fostering a positive team culture, driving continuous improvement, and achieving shared goals and objectives effectively.
Retrospective Sailboat– Retrospective Sailboat, also known as Sailboat Retrospective, is a retrospective technique used to identify factors that propel a team forward (winds) and factors that hinder its progress (anchors) toward its goals. It involves drawing a sailboat diagram with the team’s goal represented as an island and labeling winds (positive influences) and anchors (negative influences) around the boat. Team members discuss and prioritize these factors, brainstorming actions to leverage winds and remove anchors to accelerate progress. Retrospective Sailboat encourages teams to reflect on external factors and internal dynamics affecting their performance and resilience, enabling them to navigate challenges effectively and achieve their objectives.– When teams want to reflect on their progress, identify factors influencing their performance, and brainstorm actionable strategies for improvement. – In environments where promoting resilience, agility, and adaptability in response to changing conditions or challenges is essential for achieving desired outcomes and sustaining high performance over time.
Retrospective Start, Stop, Continue– Retrospective Start, Stop, Continue is a simple and effective retrospective technique used to identify actions or behaviors that teams should start, stop, or continue doing based on their perceived impact on team effectiveness and collaboration. It involves team members reflecting on recent activities or practices and categorizing them into three groups: Start (new practices to adopt), Stop (existing practices to discontinue), and Continue (existing practices to maintain or reinforce). Retrospective Start, Stop, Continue enables teams to reflect on their behaviors and make incremental improvements to enhance their performance and productivity.– When teams want to reflect on their recent practices, behaviors, and outcomes and make actionable decisions for improvement. – In environments where fostering continuous learning, adaptation, and improvement is essential for optimizing team performance, enhancing collaboration, and achieving shared goals and objectives effectively and efficiently.
Speed Boat Retrospective– Speed Boat Retrospective, also known as Speed Boat or Speed Car, is a retrospective technique used to identify factors that enable or hinder team progress toward its goals. It involves drawing a boat or car diagram with the team’s goal represented as an island or destination and labeling anchors (hindering factors) and accelerators (enabling factors) along the path. Team members discuss and prioritize these factors, brainstorming actions to remove anchors and leverage accelerators to expedite progress. Speed Boat Retrospective encourages teams to reflect on external and internal factors influencing their performance and resilience, enabling them to navigate challenges effectively and reach their destination efficiently.– When teams want to reflect on their progress, identify factors influencing their performance, and brainstorm actionable strategies for improvement collaboratively. – In environments where promoting resilience, agility, and adaptability in response to changing conditions or challenges is essential for achieving desired outcomes and sustaining high performance over time.
360-Degree Feedback– 360-Degree Feedback is a feedback mechanism used to gather insights from multiple perspectives on an individual’s performance, behaviors, and competencies. It involves soliciting feedback from peers, managers, subordinates, and other stakeholders who interact with the individual regularly, providing a comprehensive view of their strengths, development areas, and areas for improvement. 360-Degree Feedback fosters self-awareness, personal growth, and continuous development, enabling individuals to identify opportunities for skill enhancement, behavior modification, and career advancement effectively.– When organizations aim to provide individuals with holistic feedback on their performance, behaviors, and competencies to support their professional development and growth. – In environments where fostering a culture of continuous feedback, learning, and improvement is essential for enhancing individual and organizational performance, cultivating leadership capabilities, and driving employee engagement and satisfaction effectively.
Retrospective DAKI– Retrospective DAKI is a retrospective technique used to facilitate structured discussions on team dynamics, performance, and improvement opportunities. It involves team members reflecting on four key aspects: Data (observable facts or metrics), Ask (questions or concerns), Keep (things that are working well), and Improve (areas for enhancement). Retrospective DAKI encourages data-driven conversations, open dialogue, and collaborative problem-solving, enabling teams to address issues, capitalize on strengths, and implement actionable improvements effectively.– When teams want to reflect on their performance, discuss concerns, and identify opportunities for improvement collaboratively. – In environments where fostering open communication, transparency, and accountability among team members is essential for driving continuous improvement, innovation, and high-performance outcomes effectively and sustainably.

Connected Agile & Lean Frameworks

AIOps

aiops
AIOps is the application of artificial intelligence to IT operations. It has become particularly useful for modern IT management in hybridized, distributed, and dynamic environments. AIOps has become a key operational component of modern digital-based organizations, built around software and algorithms.

AgileSHIFT

AgileSHIFT
AgileSHIFT is a framework that prepares individuals for transformational change by creating a culture of agility.

Agile Methodology

agile-methodology
Agile started as a lightweight development method compared to heavyweight software development, which is the core paradigm of the previous decades of software development. By 2001 the Manifesto for Agile Software Development was born as a set of principles that defined the new paradigm for software development as a continuous iteration. This would also influence the way of doing business.

Agile Program Management

agile-program-management
Agile Program Management is a means of managing, planning, and coordinating interrelated work in such a way that value delivery is emphasized for all key stakeholders. Agile Program Management (AgilePgM) is a disciplined yet flexible agile approach to managing transformational change within an organization.

Agile Project Management

agile-project-management
Agile project management (APM) is a strategy that breaks large projects into smaller, more manageable tasks. In the APM methodology, each project is completed in small sections – often referred to as iterations. Each iteration is completed according to its project life cycle, beginning with the initial design and progressing to testing and then quality assurance.

Agile Modeling

agile-modeling
Agile Modeling (AM) is a methodology for modeling and documenting software-based systems. Agile Modeling is critical to the rapid and continuous delivery of software. It is a collection of values, principles, and practices that guide effective, lightweight software modeling.

Agile Business Analysis

agile-business-analysis
Agile Business Analysis (AgileBA) is certification in the form of guidance and training for business analysts seeking to work in agile environments. To support this shift, AgileBA also helps the business analyst relate Agile projects to a wider organizational mission or strategy. To ensure that analysts have the necessary skills and expertise, AgileBA certification was developed.

Agile Leadership

agile-leadership
Agile leadership is the embodiment of agile manifesto principles by a manager or management team. Agile leadership impacts two important levels of a business. The structural level defines the roles, responsibilities, and key performance indicators. The behavioral level describes the actions leaders exhibit to others based on agile principles. 

Andon System

andon-system
The andon system alerts managerial, maintenance, or other staff of a production process problem. The alert itself can be activated manually with a button or pull cord, but it can also be activated automatically by production equipment. Most Andon boards utilize three colored lights similar to a traffic signal: green (no errors), yellow or amber (problem identified, or quality check needed), and red (production stopped due to unidentified issue).

Bimodal Portfolio Management

bimodal-portfolio-management
Bimodal Portfolio Management (BimodalPfM) helps an organization manage both agile and traditional portfolios concurrently. Bimodal Portfolio Management – sometimes referred to as bimodal development – was coined by research and advisory company Gartner. The firm argued that many agile organizations still needed to run some aspects of their operations using traditional delivery models.

Business Innovation Matrix

business-innovation
Business innovation is about creating new opportunities for an organization to reinvent its core offerings, revenue streams, and enhance the value proposition for existing or new customers, thus renewing its whole business model. Business innovation springs by understanding the structure of the market, thus adapting or anticipating those changes.

Business Model Innovation

business-model-innovation
Business model innovation is about increasing the success of an organization with existing products and technologies by crafting a compelling value proposition able to propel a new business model to scale up customers and create a lasting competitive advantage. And it all starts by mastering the key customers.

Constructive Disruption

constructive-disruption
A consumer brand company like Procter & Gamble (P&G) defines “Constructive Disruption” as: a willingness to change, adapt, and create new trends and technologies that will shape our industry for the future. According to P&G, it moves around four pillars: lean innovation, brand building, supply chain, and digitalization & data analytics.

Continuous Innovation

continuous-innovation
That is a process that requires a continuous feedback loop to develop a valuable product and build a viable business model. Continuous innovation is a mindset where products and services are designed and delivered to tune them around the customers’ problem and not the technical solution of its founders.

Design Sprint

design-sprint
A design sprint is a proven five-day process where critical business questions are answered through speedy design and prototyping, focusing on the end-user. A design sprint starts with a weekly challenge that should finish with a prototype, test at the end, and therefore a lesson learned to be iterated.

Design Thinking

design-thinking
Tim Brown, Executive Chair of IDEO, defined design thinking as “a human-centered approach to innovation that draws from the designer’s toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success.” Therefore, desirability, feasibility, and viability are balanced to solve critical problems.

DevOps

devops-engineering
DevOps refers to a series of practices performed to perform automated software development processes. It is a conjugation of the term “development” and “operations” to emphasize how functions integrate across IT teams. DevOps strategies promote seamless building, testing, and deployment of products. It aims to bridge a gap between development and operations teams to streamline the development altogether.

Dual Track Agile

dual-track-agile
Product discovery is a critical part of agile methodologies, as its aim is to ensure that products customers love are built. Product discovery involves learning through a raft of methods, including design thinking, lean start-up, and A/B testing to name a few. Dual Track Agile is an agile methodology containing two separate tracks: the “discovery” track and the “delivery” track.

eXtreme Programming

extreme-programming
eXtreme Programming was developed in the late 1990s by Ken Beck, Ron Jeffries, and Ward Cunningham. During this time, the trio was working on the Chrysler Comprehensive Compensation System (C3) to help manage the company payroll system. eXtreme Programming (XP) is a software development methodology. It is designed to improve software quality and the ability of software to adapt to changing customer needs.

Feature-Driven Development

feature-driven-development
Feature-Driven Development is a pragmatic software process that is client and architecture-centric. Feature-Driven Development (FDD) is an agile software development model that organizes workflow according to which features need to be developed next.

Gemba Walk

gemba-walk
A Gemba Walk is a fundamental component of lean management. It describes the personal observation of work to learn more about it. Gemba is a Japanese word that loosely translates as “the real place”, or in business, “the place where value is created”. The Gemba Walk as a concept was created by Taiichi Ohno, the father of the Toyota Production System of lean manufacturing. Ohno wanted to encourage management executives to leave their offices and see where the real work happened. This, he hoped, would build relationships between employees with vastly different skillsets and build trust.

GIST Planning

gist-planning
GIST Planning is a relatively easy and lightweight agile approach to product planning that favors autonomous working. GIST Planning is a lean and agile methodology that was created by former Google product manager Itamar Gilad. GIST Planning seeks to address this situation by creating lightweight plans that are responsive and adaptable to change. GIST Planning also improves team velocity, autonomy, and alignment by reducing the pervasive influence of management. It consists of four blocks: goals, ideas, step-projects, and tasks.

ICE Scoring

ice-scoring-model
The ICE Scoring Model is an agile methodology that prioritizes features using data according to three components: impact, confidence, and ease of implementation. The ICE Scoring Model was initially created by author and growth expert Sean Ellis to help companies expand. Today, the model is broadly used to prioritize projects, features, initiatives, and rollouts. It is ideally suited for early-stage product development where there is a continuous flow of ideas and momentum must be maintained.

Innovation Funnel

innovation-funnel
An innovation funnel is a tool or process ensuring only the best ideas are executed. In a metaphorical sense, the funnel screens innovative ideas for viability so that only the best products, processes, or business models are launched to the market. An innovation funnel provides a framework for the screening and testing of innovative ideas for viability.

Innovation Matrix

types-of-innovation
According to how well defined is the problem and how well defined the domain, we have four main types of innovations: basic research (problem and domain or not well defined); breakthrough innovation (domain is not well defined, the problem is well defined); sustaining innovation (both problem and domain are well defined); and disruptive innovation (domain is well defined, the problem is not well defined).

Innovation Theory

innovation-theory
The innovation loop is a methodology/framework derived from the Bell Labs, which produced innovation at scale throughout the 20th century. They learned how to leverage a hybrid innovation management model based on science, invention, engineering, and manufacturing at scale. By leveraging individual genius, creativity, and small/large groups.

Lean vs. Agile

lean-methodology-vs-agile
The Agile methodology has been primarily thought of for software development (and other business disciplines have also adopted it). Lean thinking is a process improvement technique where teams prioritize the value streams to improve it continuously. Both methodologies look at the customer as the key driver to improvement and waste reduction. Both methodologies look at improvement as something continuous.

Lean Startup

startup-company
A startup company is a high-tech business that tries to build a scalable business model in tech-driven industries. A startup company usually follows a lean methodology, where continuous innovation, driven by built-in viral loops is the rule. Thus, driving growth and building network effects as a consequence of this strategy.

Minimum Viable Product

minimum-viable-product
As pointed out by Eric Ries, a minimum viable product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort through a cycle of build, measure, learn; that is the foundation of the lean startup methodology.

Leaner MVP

leaner-mvp
A leaner MVP is the evolution of the MPV approach. Where the market risk is validated before anything else

Kanban

kanban
Kanban is a lean manufacturing framework first developed by Toyota in the late 1940s. The Kanban framework is a means of visualizing work as it moves through identifying potential bottlenecks. It does that through a process called just-in-time (JIT) manufacturing to optimize engineering processes, speed up manufacturing products, and improve the go-to-market strategy.

Jidoka

jidoka
Jidoka was first used in 1896 by Sakichi Toyoda, who invented a textile loom that would stop automatically when it encountered a defective thread. Jidoka is a Japanese term used in lean manufacturing. The term describes a scenario where machines cease operating without human intervention when a problem or defect is discovered.

PDCA Cycle

pdca-cycle
The PDCA (Plan-Do-Check-Act) cycle was first proposed by American physicist and engineer Walter A. Shewhart in the 1920s. The PDCA cycle is a continuous process and product improvement method and an essential component of the lean manufacturing philosophy.

Rational Unified Process

rational-unified-process
Rational unified process (RUP) is an agile software development methodology that breaks the project life cycle down into four distinct phases.

Rapid Application Development

rapid-application-development
RAD was first introduced by author and consultant James Martin in 1991. Martin recognized and then took advantage of the endless malleability of software in designing development models. Rapid Application Development (RAD) is a methodology focusing on delivering rapidly through continuous feedback and frequent iterations.

Retrospective Analysis

retrospective-analysis
Retrospective analyses are held after a project to determine what worked well and what did not. They are also conducted at the end of an iteration in Agile project management. Agile practitioners call these meetings retrospectives or retros. They are an effective way to check the pulse of a project team, reflect on the work performed to date, and reach a consensus on how to tackle the next sprint cycle. These are the five stages of a retrospective analysis for effective Agile project management: set the stage, gather the data, generate insights, decide on the next steps, and close the retrospective.

Scaled Agile

scaled-agile-lean-development
Scaled Agile Lean Development (ScALeD) helps businesses discover a balanced approach to agile transition and scaling questions. The ScALed approach helps businesses successfully respond to change. Inspired by a combination of lean and agile values, ScALed is practitioner-based and can be completed through various agile frameworks and practices.

SMED

smed
The SMED (single minute exchange of die) method is a lean production framework to reduce waste and increase production efficiency. The SMED method is a framework for reducing the time associated with completing an equipment changeover.

Spotify Model

spotify-model
The Spotify Model is an autonomous approach to scaling agile, focusing on culture communication, accountability, and quality. The Spotify model was first recognized in 2012 after Henrik Kniberg, and Anders Ivarsson released a white paper detailing how streaming company Spotify approached agility. Therefore, the Spotify model represents an evolution of agile.

Test-Driven Development

test-driven-development
As the name suggests, TDD is a test-driven technique for delivering high-quality software rapidly and sustainably. It is an iterative approach based on the idea that a failing test should be written before any code for a feature or function is written. Test-Driven Development (TDD) is an approach to software development that relies on very short development cycles.

Timeboxing

timeboxing
Timeboxing is a simple yet powerful time-management technique for improving productivity. Timeboxing describes the process of proactively scheduling a block of time to spend on a task in the future. It was first described by author James Martin in a book about agile software development.

Scrum

what-is-scrum
Scrum is a methodology co-created by Ken Schwaber and Jeff Sutherland for effective team collaboration on complex products. Scrum was primarily thought for software development projects to deliver new software capability every 2-4 weeks. It is a sub-group of agile also used in project management to improve startups’ productivity.

Scrumban

scrumban
Scrumban is a project management framework that is a hybrid of two popular agile methodologies: Scrum and Kanban. Scrumban is a popular approach to helping businesses focus on the right strategic tasks while simultaneously strengthening their processes.

Scrum Anti-Patterns

scrum-anti-patterns
Scrum anti-patterns describe any attractive, easy-to-implement solution that ultimately makes a problem worse. Therefore, these are the practice not to follow to prevent issues from emerging. Some classic examples of scrum anti-patterns comprise absent product owners, pre-assigned tickets (making individuals work in isolation), and discounting retrospectives (where review meetings are not useful to really make improvements).

Scrum At Scale

scrum-at-scale
Scrum at Scale (Scrum@Scale) is a framework that Scrum teams use to address complex problems and deliver high-value products. Scrum at Scale was created through a joint venture between the Scrum Alliance and Scrum Inc. The joint venture was overseen by Jeff Sutherland, a co-creator of Scrum and one of the principal authors of the Agile Manifesto.

Six Sigma

six-sigma
Six Sigma is a data-driven approach and methodology for eliminating errors or defects in a product, service, or process. Six Sigma was developed by Motorola as a management approach based on quality fundamentals in the early 1980s. A decade later, it was popularized by General Electric who estimated that the methodology saved them $12 billion in the first five years of operation.

Stretch Objectives

stretch-objectives
Stretch objectives describe any task an agile team plans to complete without expressly committing to do so. Teams incorporate stretch objectives during a Sprint or Program Increment (PI) as part of Scaled Agile. They are used when the agile team is unsure of its capacity to attain an objective. Therefore, stretch objectives are instead outcomes that, while extremely desirable, are not the difference between the success or failure of each sprint.

Toyota Production System

toyota-production-system
The Toyota Production System (TPS) is an early form of lean manufacturing created by auto-manufacturer Toyota. Created by the Toyota Motor Corporation in the 1940s and 50s, the Toyota Production System seeks to manufacture vehicles ordered by customers most quickly and efficiently possible.

Total Quality Management

total-quality-management
The Total Quality Management (TQM) framework is a technique based on the premise that employees continuously work on their ability to provide value to customers. Importantly, the word “total” means that all employees are involved in the process – regardless of whether they work in development, production, or fulfillment.

Waterfall

waterfall-model
The waterfall model was first described by Herbert D. Benington in 1956 during a presentation about the software used in radar imaging during the Cold War. Since there were no knowledge-based, creative software development strategies at the time, the waterfall method became standard practice. The waterfall model is a linear and sequential project management framework. 

Read Also: Continuous InnovationAgile MethodologyLean StartupBusiness Model InnovationProject Management.

Read Next: Agile Methodology, Lean Methodology, Agile Project Management, Scrum, Kanban, Six Sigma.

Main Guides:

Main Case Studies:

Discover more from FourWeekMBA

Subscribe now to keep reading and get access to the full archive.

Continue reading

Scroll to Top
FourWeekMBA