Development Methodologies

There are a variety of development methodologies covering more traditional waterfall approaches to agile techniques. There are several variants of agile frameworks and also several combination ones. The methodology for the project is likely to depend on the type of project – proof of concept, medical product, aerospace, high reliability and the level of documented and stable requirements at the start of the project.

Waterfall

A sequential flow through stages of development that are executed once. Requires a clear definition and design at the start of the project. Has the advantage of being able to estimate the effort and predict a date but is not flexible to changes once the project has started. A common framework is PRINCE2 in the UK.

Agile

An approach of rapid iteration where the emphasis is on working software at all stages, and delivering the minimum amount of engineering to achieve the requirements. There are a variety of agile frameworks that give more detail and structure, and the depth of definition and prescription varies by famework.

Agile Frameworks

scrum

A framework that defines a team with a set of roles (product owner, scrum master, development team, product owner) , a development phase (called a sprint that is typically 1 to 4 weeks in duration) that is repeated, and backlog that defines the product (as a set of user stories). During the

less

Large scale scrum, which has two variations one for upto 8 teams and another for even larger numbers in a scaled organisation.

kanban

kanban is a way of delivering work which has several key principles including visualising the work (ready to do, in progress, done) and limiting the work in progressthe amoun.