Project Management Methodologies History

  • Kanban

    Kanban
    a scheduling system for lean manufacturing and just-in-time manufacturing (JIT). Taiichi Ohno, an industrial engineer at Toyota, developed Kanban to improve manufacturing efficiency.
  • American Association of Cost Engineers

    American Association of Cost Engineers
    AACE was formed by a collection of project managers and associated specialists of planning, scheduling, cost estimating and other related fields.
  • Six Sigma

    Six Sigma (6σ) is a set of techniques and tools for process improvement. It was introduced by engineer Bill Smith while working at Motorola in 1980. Jack Welch made it central to his business strategy at General Electric in 1995. A six sigma process is one in which 99.99966% of all opportunities to produce some feature of a part are statistically expected to be free of defects.
  • Rapid Application Development

    Rapid application development was a response to plan-driven waterfall processes, developed in the 1970s and 1980s, such as the Structured Systems Analysis and Design Method (SSADM). One of the problems with these methods is that they were based on a traditional engineering model used to design and build things like bridges and buildings. Software is an inherently different kind of artifact. Software can radically change the entire process used to solve a problem.
  • Unified Process

    The Unified Process is not simply a process, but rather an extensible framework which should be customized for specific organizations or projects. The Rational Unified Process is, similarly, a customizable framework. As a result, it is often impossible to say whether a refinement of the process was derived from UP or from RUP, and so the names tend to be used interchangeably.
  • Dynamic systems development method

    Dynamic systems development method
    The DSDM Consortium was founded in 1994 by an association of vendors and experts in the field of software engineering and was created with the objective of "jointly developing and promoting an independent RAD framework" by combining their best practice experiences.
  • Scrum

    Scrum
    The Agile software development model that incorporates multiple small teams working intensely and interdependently is known as Scrum, which was named as a project management style
  • Extreme programming

    Extreme programming
    Extreme programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted
  • Feature-driven development

    Feature-driven development (FDD) is an iterative and incremental software development process. It is a lightweight or Agile method for developing software. FDD blends a number of industry-recognized best practices into a cohesive whole. These practices are driven from a client-valued functionality (feature) perspective. Its main purpose is to deliver tangible, working software repeatedly in a timely manner in accordance with the Principles behind the Agile Manifesto
  • PMBOK is Published

    PMBOK is Published
    The Project Management Body of Knowledge is a set of standard terminology and guidelines for project management. The body of knowledge evolves over time and is presented in A Guide to the Project Management Body of Knowledge, a book whose sixth edition was released in 2017.
  • Manifesto for Agile Software Development

    Manifesto for Agile Software Development
    Based on their combined experience of developing software and helping others do that, the seventeen signatories to the manifesto proclaimed that they value: Individuals and Interactions over processes and tools
    Working Software over comprehensive documentation
    Customer Collaboration over contract negotiation
    Responding to Change over following a plan