20-mile-march

20 Mile March

The 20 Mile March strategy focuses on consistent progress by setting achievable performance targets, ensuring disciplined effort in good and bad times. Characterized by performance bands and rigorous metrics, it yields benefits like steady growth and resilience. Challenges include external disruptions, and its application spans business growth and personal development.

Understanding the 20-Mile March

The term “20-Mile March” is derived from the idea of an explorer or traveler who commits to covering a fixed distance each day, rain or shine, to reach their destination. In the context of goal achievement and performance, the 20-Mile March represents a consistent and disciplined approach to progress. It involves setting achievable performance targets and then diligently working to meet or exceed them, day after day, regardless of external conditions.

Key Principles of the 20-Mile March

To grasp the essence of the 20-Mile March concept, it’s essential to understand its key principles:

  1. Discipline: Consistency is at the core of the 20-Mile March. It requires the discipline to stick to predetermined benchmarks and not deviate from them based on external pressures or distractions.
  2. Sustainable Pace: The 20-Mile March is not about sprinting or overexerting oneself in the short term. Instead, it encourages a sustainable pace that can be maintained over the long term.
  3. Self-Imposed Constraints: It involves setting self-imposed constraints or limits on performance to ensure that goals are realistic and achievable.
  4. Resilience: Adhering to the 20-Mile March requires resilience in the face of adversity. It’s about weathering challenges and maintaining steady progress.

Implementing the 20-Mile March

Setting Clear Goals

The first step in implementing the 20-Mile March is to set clear, specific, and achievable goals. These goals should be quantifiable, time-bound, and aligned with the overarching objectives you want to achieve.

Establishing Performance Benchmarks

Once goals are defined, establish performance benchmarks that you commit to hitting consistently. These benchmarks should reflect the level of progress necessary to achieve your goals.

Consistent Execution

The heart of the 20-Mile March is consistent execution. Regardless of external factors, commit to hitting your performance benchmarks every day, week, or month, depending on your goals.

Monitoring Progress

Regularly monitor your progress against the established benchmarks. This tracking provides insights into your performance and helps you make necessary adjustments.

Adaptation and Adjustment

While the 20-Mile March emphasizes consistency, it does not promote blind adherence to a predefined path. It encourages adaptation and adjustment based on changing circumstances or new information. If you consistently fall short of your benchmarks, it may be necessary to reassess and revise your goals and approach.

Benefits of the 20-Mile March

The 20-Mile March approach offers several notable benefits for individuals and organizations:

  1. Consistent Progress: By setting and adhering to performance benchmarks, you ensure consistent progress toward your goals.
  2. Enhanced Discipline: Practicing the 20-Mile March cultivates discipline, helping you resist distractions and stay focused on what matters most.
  3. Reduced Burnout: Unlike erratic, high-intensity efforts that can lead to burnout, the 20-Mile March promotes sustainable, long-term performance.
  4. Improved Resilience: The discipline and consistency of the 20-Mile March build resilience, enabling you to persevere through challenges and setbacks.
  5. Goal Achievement: Ultimately, the 20-Mile March increases the likelihood of achieving your goals, as it provides a structured and effective approach to progress.

Challenges and Considerations

While the 20-Mile March offers numerous advantages, it is not without its challenges and considerations:

  1. Patience: The 20-Mile March requires patience, as it may take time to see significant results. Some individuals may prefer quicker, high-risk approaches.
  2. Flexibility: Balancing consistency with adaptability can be challenging. There may be situations where adjustments are necessary, and finding the right balance is key.
  3. Motivation: Staying motivated to consistently hit performance benchmarks can be demanding, especially during periods of slow progress.
  4. Risk Aversion: The approach’s emphasis on self-imposed constraints may lead to risk aversion, as individuals or organizations may be hesitant to push boundaries.

Real-World Applications

The 20-Mile March concept has been applied in various real-world scenarios:

  1. Business Growth: Organizations often use the 20-Mile March to manage and sustain growth. By setting consistent revenue or customer acquisition targets, they avoid the pitfalls of rapid expansion.
  2. Financial Planning: Individuals may employ the 20-Mile March to achieve financial goals, such as saving for retirement or paying off debt. Consistent contributions and disciplined spending are key components.
  3. Personal Development: The concept is also relevant in personal development. People may set daily or weekly benchmarks for habits like exercise, reading, or skill development.
  4. Project Management: Project managers use the 20-Mile March to ensure steady progress in complex projects. It helps prevent delays and last-minute rushes.
  5. Health and Fitness: Achieving and maintaining physical fitness often involves the 20-Mile March approach. Regular workouts and balanced nutrition are examples of consistent efforts.

Case Study: Amundsen vs. Scott

One of the most famous illustrations of the 20-Mile March principle is the race to the South Pole between explorers Roald Amundsen and Robert Falcon Scott. Amundsen adhered to a disciplined, consistent pace, covering roughly 20 miles per day. In contrast, Scott’s team took a more erratic approach, sometimes pushing hard and then resting for extended periods.

The result was telling: Amundsen’s team reached the South Pole first, and all members returned safely. Tragically, Scott’s team perished on the return journey.

This historical example underscores the power of consistent progress over erratic bursts of effort, even in extreme conditions.

Conclusion

The 20-Mile March is a potent concept that underscores the importance of consistency, discipline, and self-imposed constraints in achieving success. Whether applied to business growth, personal development, or project management, this approach offers a structured and sustainable way to make progress toward your goals.

By setting clear benchmarks, consistently executing your plans, and monitoring your progress, you can navigate challenges, build resilience, and increase your chances of achieving both short-term and long-term success. Remember that the journey to success often requires steady and deliberate steps, much like covering 20 miles each day, rain or shine.

Use Cases:

  • Business growth strategies.
  • Personal development plans.

Key Highlights:

  • Consistent Progress: Emphasizes steady and reliable progress regardless of external factors.
  • Performance Bands: Sets specific performance ranges for acceptable outcomes.
  • Discipline and Adherence: Requires disciplined effort to achieve predetermined targets.
  • Balanced Risk Management: Maintains a balance between risk-taking and consistency.
  • Long-Term Focus: Aims for sustainable growth over the long term.
  • Resilience: Builds resilience against unexpected challenges and disruptions.
  • Adaptability: Allows adjustment within the performance bands while maintaining consistency.
  • Avoids Extremes: Guards against overexertion and complacency.
  • Business and Personal Application: Applicable to both business growth strategies and personal development plans.

Related FrameworksDescriptionWhen to Apply
SMART Goals– SMART Goals are specific, measurable, achievable, relevant, and time-bound objectives that guide goal-setting and performance management. They provide a framework for setting clear and actionable goals that align with organizational priorities and individual capabilities. By defining SMART goals, individuals and teams can establish clear expectations, track progress, and maintain focus on achieving desired outcomes consistently.– When setting goals or objectives to ensure they are specific, measurable, achievable, relevant, and time-bound, facilitating clarity, accountability, and progress tracking. – In situations where leaders need to align individual or team goals with organizational objectives and strategies to drive performance and accountability effectively.
Kaizen (Continuous Improvement)– Kaizen, originating from Japanese business philosophy, refers to the practice of continuous improvement in processes, products, and systems. It emphasizes making small, incremental changes over time to drive efficiency, quality, and innovation. By fostering a culture of continuous improvement, organizations can empower employees to identify and address opportunities for enhancement systematically, leading to incremental gains in productivity, quality, and customer satisfaction. Kaizen complements the 20 Mile March concept by promoting consistent progress and refinement toward long-term goals.– When seeking to improve processes, products, or services iteratively to drive efficiency, quality, and innovation systematically. – In environments where fostering a culture of continuous improvement is essential to sustain long-term growth, adaptability, and competitiveness.
Agile Methodology– Agile Methodology is an iterative approach to software development and project management that emphasizes flexibility, collaboration, and customer feedback. It involves breaking down work into small, manageable tasks or iterations, known as sprints, and delivering value incrementally. Agile teams adapt to changing requirements and priorities, focusing on delivering the highest priority items efficiently. By embracing Agile principles and practices, organizations can enhance responsiveness, reduce risk, and accelerate time-to-market while maintaining quality and customer satisfaction.– When managing projects or initiatives that require flexibility, adaptability, and responsiveness to changing requirements or priorities. – In environments where delivering value incrementally and iteratively is crucial to meet evolving customer needs and market dynamics effectively.
OKRs (Objectives and Key Results)– OKRs (Objectives and Key Results) is a goal-setting framework that aligns individual, team, and organizational goals with measurable outcomes. It involves setting ambitious objectives and defining specific, measurable key results to track progress and success. OKRs encourage stretch goals and accountability, fostering focus, alignment, and transparency across the organization. By implementing OKRs, organizations can clarify priorities, drive performance, and achieve ambitious outcomes effectively.– When setting goals or objectives at different levels of the organization to align efforts, track progress, and drive accountability systematically. – In environments where fostering alignment, focus, and transparency across teams and departments is essential to drive organizational performance and success.
Continuous Delivery– Continuous Delivery is a software engineering approach that enables organizations to release software updates frequently and reliably. It involves automating the build, test, and deployment processes to deliver changes to production quickly and safely. Continuous Delivery emphasizes reducing lead time, minimizing risk, and enhancing feedback loops, allowing organizations to respond rapidly to market demands and customer feedback. By adopting Continuous Delivery practices, organizations can accelerate innovation, improve product quality, and increase customer satisfaction.– When developing software products or applications to enable frequent, reliable, and efficient delivery of updates to production environments. – In environments where reducing time-to-market, enhancing product quality, and responding rapidly to customer feedback are critical to maintaining competitiveness and meeting evolving market demands.
Lean Startup– The Lean Startup methodology, popularized by Eric Ries, advocates for rapid experimentation, validated learning, and iterative product development. It encourages entrepreneurs and organizations to build minimum viable products (MVPs), test assumptions, and gather feedback from customers early and often. By applying Lean Startup principles, organizations can reduce the risk of failure, iterate on ideas quickly, and pivot based on validated learning, leading to more successful and sustainable ventures. The Lean Startup approach complements the 20 Mile March concept by promoting disciplined experimentation and adaptive learning to achieve long-term success.– When launching new products, services, or ventures to validate assumptions, test market demand, and gather feedback from early adopters. – In environments where fostering innovation, agility, and resilience is essential to navigate uncertainty, mitigate risks, and capitalize on emerging opportunities effectively.
Scrum Framework– The Scrum Framework is an Agile project management framework that facilitates collaboration, transparency, and iterative development. It involves organizing work into fixed-length iterations, known as sprints, and holding regular ceremonies, such as daily stand-ups and sprint reviews, to track progress and adapt plans. Scrum empowers cross-functional teams to self-organize, prioritize tasks, and deliver incremental value consistently. By embracing Scrum principles and practices, organizations can enhance teamwork, visibility, and productivity, enabling them to achieve their objectives efficiently.– When managing projects or initiatives that require iterative, collaborative, and adaptive approaches to deliver value incrementally. – In environments where empowering teams, fostering transparency, and embracing change are essential to drive project success and stakeholder satisfaction.
Pomodoro Technique– The Pomodoro Technique is a time management method that involves breaking work into intervals, typically 25 minutes each, separated by short breaks. It aims to enhance focus, productivity, and mental agility by leveraging the natural rhythm of attention and rest. By working in focused bursts and taking regular breaks, individuals can maintain energy levels, reduce procrastination, and sustain motivation throughout the day. The Pomodoro Technique complements the 20 Mile March concept by providing a structured approach to managing time and maintaining momentum toward long-term goals.– When managing time effectively and maintaining focus and productivity during work sessions or tasks. – In situations where individuals need to sustain motivation, combat procrastination, and manage energy levels to achieve consistent progress toward their objectives.
LEAN Thinking– LEAN Thinking is a management philosophy inspired by the Toyota Production System (TPS) that emphasizes continuous improvement, waste reduction, and value creation. It involves identifying and eliminating non-value-added activities, optimizing processes, and empowering employees to contribute to organizational success. LEAN Thinking fosters a culture of efficiency, quality, and customer focus, enabling organizations to deliver greater value with fewer resources. By embracing LEAN principles, organizations can streamline operations, enhance customer satisfaction, and drive sustainable growth.– When optimizing business processes, workflows, or operations to eliminate waste, improve efficiency, and enhance value creation systematically. – In environments where fostering a culture of continuous improvement and customer-centricity is essential to drive organizational excellence and competitive advantage.
Batch Processing vs. Real-time Processing– Batch Processing and Real-time Processing are two approaches to handling data and performing computations in information systems. Batch Processing involves collecting and processing data in large batches or groups, typically at scheduled intervals, while Real-time Processing processes data immediately as it becomes available, enabling instant responses to events or transactions. Each approach has its advantages and use cases, depending on factors such as data volume, latency requirements, and processing complexity. Understanding the differences between batch and real-time processing is essential for designing efficient and responsive information systems.– When designing or optimizing data processing systems, applications, or workflows to meet specific requirements for data volume, latency, and responsiveness. – In situations where organizations need to choose between batch processing and real-time processing approaches based on their data processing needs, resource constraints, and performance objectives.
Decision Tree Analysis– Decision Tree Analysis is a decision-making tool that visualizes complex decisions and their potential outcomes in a tree-like structure. It involves identifying decision points, possible alternatives, and their associated consequences or probabilities. Decision Tree Analysis helps individuals and organizations evaluate different courses of action, assess risks, and make informed decisions based on available information. By mapping out decision scenarios and their potential outcomes, Decision Tree Analysis facilitates clarity, analysis, and risk mitigation in decision-making processes.– When evaluating complex decisions, alternatives, or strategies to assess potential outcomes, risks, and trade-offs systematically. – In environments where visualizing decision scenarios and analyzing their implications is essential to make informed and effective decisions under uncertainty or ambiguity.

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:

Scroll to Top

Discover more from FourWeekMBA

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

Continue reading

FourWeekMBA