Discover published sets by community

A linear sequential flow where progress is seen as flowing steadily downwards like a waterfall through phases such as conception, initiation, analysis, design, construction, testing, and maintenance.

An iterative approach to software delivery that builds software incrementally from the start of the project, instead of trying to deliver it all at once near the end. It advocates adaptive planning, evolutionary development, early delivery, and continual improvement.

A subset of Agile, it is a framework that uses fixed-length iterations called sprints, usually 2-4 weeks long. It includes roles such as Product Owner, Scrum Master, and Development Team. Artifacts include product backlog and sprint backlog.

An Agile framework that aims to produce higher quality software, and higher quality of life for the development team. XP is notable for its emphasis on technical practices like test-driven development, continuous integration, and pair programming.

A visual method for managing the creation of products with an emphasis on continuous delivery while not overburdening the development team. It uses a Kanban board with cards to represent work items and columns to represent each stage of the process.

Translated from lean manufacturing to the software development domain. It is based on principles such as eliminating waste, amplifying learning, deferring commitment, delivering fast, respecting people, and building integrity in.

A set of practices that combines software development (Dev) and information technology operations (Ops) to shorten the systems development life cycle and provide continuous delivery with high software quality.

A family of human-powered, adaptive, ultra-light, ‘stretch-to-fit’ software development methodologies. It focuses on people, interaction, community, skills, talents, and communications.

A model-driven, short-iteration process that consists of five basic activities: developing an overall model, building a feature list, planning by feature, designing by feature, and building by feature.

An Agile framework that embodies the principles of Agile project delivery. It is based on eight principles that focus on business needs/value, active user involvement, empowered teams, frequent delivery, and more.

An adaptive software development approach that prioritizes rapid prototyping over costly planning. The key components include iterative development and the construction of prototypes.

A methodology that involves the client or end user in the design and development of an application, through a series of collaborative workshops called JAD sessions.

Combines elements of both design and prototyping in stages, in an effort to combine advantages of top-down and bottom-up concepts. It allows for incremental releases of the product, or incremental refinement through each iteration around the spiral.

A process for planning, creating, testing, and deploying an information system, which includes phases such as system analysis and design, implementation, testing and integration, and maintenance.

An extension of the waterfall model, where each level of the development life-cycle corresponds to a related testing phase. It is a highly disciplined model and the next phase starts only after the previous phase is complete.

A software development model that focuses on writing code and implementing the features as they are needed without much of a structured plan. It allows for a lot of freedom and creativity, but can be risky due to the lack of planning.

Development begins by specifying and implementing just part of the software, which is then reviewed in order to identify further requirements. This process is repeated, producing a new version of the software at the end of each iteration of the model.

Instead of freezing the requirements before a design or coding can proceed, a throwaway prototype is built to understand the requirements. This prototype is developed based on the currently known requirements.

A process for developing software with a high level of reliability. The Cleanroom process is characterized by incremental development, and a certification process, which involves correctness verification of each increment by the team.