20 DevOps Frameworks For Your Digital Business

DevOps Methodology

devops-methodology
A DevOps methodology is a suite of practices, tools, and philosophies that combines software development (Dev) and information technology operations (Ops).

Lean Methodology

lean-methodology
The lean methodology is a continuous process of product development to meet customers’ needs. It was in part borrowed by the auto industry and its roots are found in the Toyota Production System, which was heavily influenced by Henry Ford’s assembly line system. The lean methodology is, therefore, an evolution from lean manufacturing, based on continuous improvement.

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.

Buy-a-feature Prioritization Model

buy-a-feature-prioritization-model
The Buy-a-Feature Prioritization Model is a quantifiable exercise helping product teams to identify features that customers value most. The Buy-a-Feature Prioritization Model endeavors to answer some basic questions around product development – Which product feature will get customers excitedly telling their friends about it? – Which will cause them to rush to upgrade their model? – Which feature(s) will make the customer so happy that they ignore less desirable aspects of the product?

Dynamic Systems Development Method

dynamic-systems-development-method
During the 1990s, rapid application development (RAD) was becoming increasingly popular. The Dynamic Systems Development Method (DSDM) is an agile approach that focuses on the full project lifecycle while adding further discipline and structure. DSDM is founded on eight key principles. Each principle supports the DSDM philosophy that “best business value emerges when projects are aligned to clear business goals, deliver frequently and involve the collaboration of motivated and empowered people”.

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.

ICE Scoring Model

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.

Value vs. Complexity Framework

value-vs-complexity-framework
The Value vs. Complexity framework is a prioritization model. It allows product teams to evaluate ideas based on how much value they add and how difficult they are to implement. The Value vs. Complexity framework helps businesses prioritize product feature lists during development.

Impact Mapping

impact-mapping
Impact mapping is a product development technique based on user design, mind mapping, and outcome-driven planning. Impact mapping is an agile technique intended to help teams connect individual product features that can impact the user behaviors while connecting to the key, guiding metrics for the business.

Behavior-Driven Development

behavior-driven-development
Behavior-Driven Development (BDD) is a process that gives examples of how software should behave in various scenarios. This behavior is written in a format that is easily understood, tested, and integrated.

Acceptance Test-Driven Development

acceptance-test-driven-development
Acceptance Test-Driven Development (ATDD) is a part of the agile methodology where automated tests are written from the user’s perspective. Unlike test-driven development โ€“ where acceptance tests are created from the perspective of the developer – ATDD advocates the automation of tests from the various perspectives of the user.

Experiment-Driven Development

experiment-driven-development
Test-Driven Development (TDD) and Behavior-Driven Development (BDD) are popular agile development techniques. However, they don’t measure application usage or provide guidance on gaining feedback from customers. Experiment-Driven Development (EDD) is a scientific, fact-based approach to software development using agile principles.

Continuous Integration

continuous-integrationcontinuous-deployment
Continuous Integration/Continuous Deployment (CI/CD) introduces automation into the stages of app development to frequently deliver to customers. CI/CD introduces continuous automation and monitoring throughout the app lifecycle, from testing to delivery and then deployment.

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.

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.

DevSecOps

devsecops
DevSecOps is a set of disciplines combining development, security, and operations. It is a philosophy that helps software development businesses deliver innovative products quickly without sacrificing security. This allows potential security issues to be identified during the development process โ€“ and not after the product has been released in line with the emergence of continuous software development practices.

Starbursting

starbursting
Starbursting is a structured brainstorming technique with a focus on question generation. Starbursting is a structured form of brainstorming allowing product teams to cover all bases during the ideation process. It utilizes a series of questions to systematically work through various aspects of product development, forcing teams to evaluate ideas based on viability.

MVP

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

Waterfall Model

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.ย 

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.

Main Free Guides:

About The Author

Scroll to Top
FourWeekMBA