Agile Architecture

Agile Architecture

Business / By /

Agile Architecture is an extension of Agile software development principles, which prioritize customer collaboration, working software, and responsiveness to change. Traditionally, architecture in software development was seen as a rigid, upfront process, often resulting in extensive documentation and lengthy planning phases. However, Agile Architecture advocates for a more adaptive and evolutionary approach.

Key Principles of Agile Architecture

  1. Customer-Centric Approach: Agile Architecture places the customer at the center of the design process. It prioritizes understanding customer needs and continuously adapting the architecture to meet those needs.
  2. Flexibility and Adaptability: Agile Architecture promotes flexibility by avoiding overly detailed, upfront designs. Instead, it encourages iterative and incremental development, allowing the architecture to evolve as requirements change.
  3. Collaboration: Collaboration is a fundamental aspect of Agile Architecture. It fosters cross-functional teams where architects, developers, and other stakeholders work together throughout the project, sharing their expertise and insights.
  4. Minimalist Documentation: Unlike traditional architecture approaches that produce extensive documentation, Agile Architecture focuses on lightweight documentation that is just sufficient to guide the development process.

Benefits of Agile Architecture

Implementing Agile Architecture can bring several advantages to software development projects:

  1. Improved Responsiveness: Agile Architecture enables teams to respond quickly to changing requirements, market conditions, and customer feedback, ensuring that the software remains aligned with business goals.
  2. Enhanced Collaboration: The emphasis on collaboration fosters a shared understanding of the architecture among team members, reducing the risk of misunderstandings and misalignments.
  3. Reduced Risk: By breaking down architecture tasks into smaller, manageable pieces, Agile Architecture reduces the risk associated with large-scale design decisions made upfront.
  4. Higher Quality Software: Continuous feedback and testing throughout the development process lead to the early detection and resolution of issues, resulting in a higher-quality end product.
  5. Faster Time to Market: Agile Architecture’s iterative approach allows for the delivery of functional software increments more rapidly, helping organizations bring new features to market faster.

Challenges of Agile Architecture

While Agile Architecture offers numerous benefits, it also comes with its set of challenges:

  1. Maintaining Balance: Striking the right balance between enough architecture upfront and being too minimalistic can be challenging. Over-architecting or under-architecting can lead to issues down the road.
  2. Technical Debt: Rapid development cycles may lead to accumulating technical debt if architectural concerns are not adequately addressed during sprints.
  3. Scalability: Agile Architecture may face scalability challenges when applied to large and complex projects, requiring careful planning and coordination.
  4. Resistance to Change: Teams and organizations accustomed to traditional architecture approaches may initially resist the shift towards Agile Architecture, leading to cultural and mindset challenges.

Practical Guidelines for Implementing Agile Architecture

Implementing Agile Architecture effectively involves a combination of mindset, practices, and tools. Here are some practical guidelines to help you get started:

Foster a Collaborative Culture

  • Encourage open communication and collaboration among architects, developers, and other stakeholders.
  • Create cross-functional teams that include architecture expertise to ensure architectural decisions are made collaboratively.

Prioritize Customer Feedback

  • Continuously gather and incorporate customer feedback into the architecture.
  • Use feedback to guide architecture decisions and adapt to changing requirements.

Embrace Lightweight Documentation

  • Focus on documentation that adds value to the project, avoiding excessive documentation that can become outdated quickly.
  • Use visual diagrams, prototypes, and living documentation whenever possible.

Start Small and Iterate

  • Begin with a minimal viable architecture and incrementally build upon it.
  • Use short iterations to gather insights and adjust the architecture accordingly.

Address Technical Debt

  • Regularly assess and address technical debt to prevent it from accumulating.
  • Allocate time in sprints for refactoring and architectural improvements.

Use Agile Architecture Patterns

  • Explore architectural patterns that align with Agile principles, such as microservices, containerization, and serverless computing.

Continuous Integration and Testing

  • Implement continuous integration and automated testing to ensure that architectural changes do not introduce regressions.

Adapt and Learn

  • Be open to adapting your architectural approach based on what you learn during the project.
  • Encourage a culture of continuous improvement.

Conclusion

Agile Architecture represents a shift from rigid, upfront design to a more adaptive and customer-centric approach. While it brings numerous benefits, it also poses challenges that organizations must address. By embracing a collaborative culture, prioritizing customer feedback, and following practical guidelines, teams can successfully implement Agile Architecture and deliver software that is more responsive to customer needs and market demands. In today’s rapidly evolving software landscape, Agile Architecture is a crucial framework for staying competitive and delivering value to customers.

Key Highlights:

  • Traditional vs. Agile Architecture:
    • Traditional architecture in software development was rigid and upfront, while Agile Architecture advocates for adaptability and evolution.
  • Principles of Agile Architecture:
    • Customer-Centric Approach, Flexibility and Adaptability, Collaboration, and Minimalist Documentation are key principles guiding Agile Architecture.
  • Benefits:
    • Improved Responsiveness, Enhanced Collaboration, Reduced Risk, Higher Quality Software, and Faster Time to Market are some of the benefits of implementing Agile Architecture.
  • Challenges:
    • Maintaining Balance, Technical Debt, Scalability, and Resistance to Change are challenges associated with Agile Architecture.
  • Practical Guidelines:
    • Foster a Collaborative Culture, Prioritize Customer Feedback, Embrace Lightweight Documentation, Start Small and Iterate, Address Technical Debt, Use Agile Architecture Patterns, Implement Continuous Integration and Testing, and Adapt and Learn.
  • Conclusion:
    • Agile Architecture represents a shift towards adaptability and customer-centricity. While it brings benefits, organizations must address challenges by fostering collaboration, prioritizing customer feedback, and following practical guidelines to successfully implement Agile Architecture and deliver value to customers.
Related FrameworkDescriptionWhen to Apply
Scalable ArchitectureScalable architecture is designed to accommodate growth and expansion without requiring significant changes to the system’s structure or performance. It involves modular design, loosely coupled components, and horizontal scaling capabilities to handle increased workload or user demand. Scalable architecture enables systems to grow seamlessly while maintaining reliability and performance.When designing systems or applications expected to experience growth or increased demand over time, ensuring flexibility and adaptability to accommodate evolving requirements without sacrificing performance or reliability.
Microservices ArchitectureMicroservices architecture is an approach to software development that structures applications as a collection of small, independently deployable services. Each service focuses on a specific business capability and communicates with other services via APIs. Microservices enable teams to develop, deploy, and scale components independently, fostering agility, scalability, and resilience in complex systems.When building large, complex applications or systems with multiple interdependent components, promoting autonomy and flexibility in development teams, and enabling rapid deployment and scalability of individual services or components.
Domain-Driven Design (DDD)Domain-Driven Design is a design methodology that focuses on modeling software based on the business domain and its concepts, rather than technical implementation details. DDD emphasizes collaboration between domain experts and software developers to develop a shared understanding of the domain and create a flexible, maintainable design. It involves identifying domain entities, defining bounded contexts, and encapsulating business logic within domain objects.When developing software systems that reflect complex business domains, fostering collaboration between domain experts and development teams, and creating a flexible, maintainable design that aligns with business objectives and requirements.
Event-Driven Architecture (EDA)Event-Driven Architecture is an architectural pattern where the flow of information is based on the occurrence of events and their subsequent handling by event consumers. Events represent significant occurrences within the system or the external environment, triggering asynchronous processing and communication between system components. EDA enables systems to react to changes in real-time and decouples components, improving scalability and responsiveness.When designing systems that need to react to real-time events or changes, decoupling system components to improve scalability and flexibility, and enabling asynchronous communication and processing for improved responsiveness and performance.
Service-Oriented Architecture (SOA)Service-Oriented Architecture is an architectural style where software components are organized as services that can be accessed and reused across different applications or systems. Services are self-contained, modular units of functionality that communicate via standardized protocols such as SOAP or REST. SOA promotes interoperability, flexibility, and reusability by encapsulating business logic within services.When building distributed systems with reusable and interoperable components, promoting agility and adaptability in changing business environments, and enabling integration and collaboration across disparate systems and technologies.
DevOps ArchitectureDevOps architecture focuses on aligning development and operations processes to enable continuous integration, delivery, and deployment of software. It involves automating infrastructure provisioning, configuration management, and deployment pipelines to streamline software delivery and improve collaboration between development and operations teams. DevOps architecture aims to accelerate the software development lifecycle and enhance the reliability and scalability of applications.When implementing DevOps practices to streamline software delivery and deployment processes, fostering collaboration between development and operations teams, and automating infrastructure management to improve efficiency and reliability of software deployments.
Cloud-Native ArchitectureCloud-Native Architecture is an approach to designing and deploying applications optimized for cloud environments. It leverages cloud-native technologies such as containers, microservices, and serverless computing to build scalable, resilient, and agile applications. Cloud-native architecture enables organizations to take full advantage of cloud services, improve resource utilization, and accelerate innovation and time-to-market.When developing applications for cloud platforms such as AWS, Azure, or Google Cloud, leveraging cloud-native technologies to optimize scalability, resilience, and agility, and maximizing the benefits of cloud services for improved performance and efficiency.
ContainerizationContainerization is a lightweight virtualization technology that encapsulates applications and their dependencies into isolated containers. Containers provide a consistent runtime environment, enabling applications to run reliably across different infrastructure environments. Containerization simplifies deployment, scaling, and management of applications, making it easier to build and deploy cloud-native architectures.When deploying and managing applications across different environments, ensuring consistency and portability of runtime environments, and improving resource utilization and scalability through container-based deployment strategies.
Immutable InfrastructureImmutable infrastructure is an architectural approach where infrastructure components, such as servers and containers, are replaced rather than modified in place. Infrastructure changes are achieved by deploying new, immutable instances rather than updating existing ones. Immutable infrastructure reduces configuration drift, enhances security, and enables rapid rollback in case of failures, improving system reliability and maintainability.When managing infrastructure at scale, minimizing configuration drift and ensuring consistency across environments, improving security posture by reducing attack surface, and enabling rapid and reliable deployments with easy rollback capabilities.
Serverless ArchitectureServerless architecture is an approach to building and deploying applications without managing underlying infrastructure. In serverless computing, cloud providers dynamically manage the allocation and scaling of resources, allowing developers to focus on writing code and defining event-driven functions. Serverless architectures offer scalability, cost-efficiency, and simplicity by abstracting away infrastructure management tasks.When developing event-driven or microservices-based applications, optimizing resource utilization and reducing operational overhead, and achieving cost efficiency and scalability without managing infrastructure resources directly.

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 Innovation, Agile Methodology, Lean Startup, Business Model Innovation, Project Management.

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

Main Guides:

Main Case Studies:

More Resources

Discover more from FourWeekMBA

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

Continue reading

Scroll to Top
FourWeekMBA