Agile Methodologies

Scrum Artifacts

Product increment, product backlog, sprint backlog

MoSCow Rule

80/20 Rule is the key reason why the system of prioritization works. According to this technique, 80% of typical activities contribute something like 20% to the value of our work. It means that 80% of the project's benefits come from 20% of the time spent by its staff. When you do only the most important 20% of your tasks, you get most of the value.

ASD (Adaptive Software Development)

ASD embraces the principle of continuous adaptation of the processes to the project. It consists of repeating series of speculate, collaborate and learn cycles. Characteristics of ASD includes: mission focused, feature based, iterative, timeboxed, risk driven and change tolerant.

DSDM (Dynamic Systems Development Method) Atern

DSDM was first released in 1994 to provide guidance on Rapid Application Development (RAD) and was primarily focused on software development. DSDM has evolved over the years to become a generic approach for Agile project management and solution delivery by providing a comprehensive foundation for planning, managing, executing, and scaling agile and iterative software development projects. By utilizing DSDM, costs, quality and time are fixed. DSDM singles out "fitness for business purpose" as the primary criteria for delivery and acceptance of a product. It makes use of the MoSCoW prioritization principles to deliver values which is based on the principle that "80% of features can be deployed in 20% of the time".

Feature Driven Development

Domain, Design, Design Inspection, Code, Code Inspection, Promote to Build -- [Action], the [Result], by [Object]

Core Lean Principles

Eliminating Waste, Amplifying Learning, Deciding as Late as Possible, Delivering as Fast as Possible, Empowering the Team, Building Integrity In, and Seeing the Whole.

FDD (Feature Driven Development)

FDD is a feature-driven methodologies that consists of short iterations (two weeks). It makes use of a "design by feature, build by feature" approach where features through a client perspective. FDD adapts the project development process around feature delivery by making use of the following 8 practices: Domain Object Modeling, Developing by Feature, Component/Class Ownership, Feature Teams, Inspections, Configuration Management, Regular Builds, Visibility of Progress and Results.

Kanban

Kanban is a scheduling system used in Lean and JIT (Just-in-time) production. When applied to software development, kanban is a "pull-based" planning and execution method. For software development teams, "cards" representing tasks to be done are kept on a Kanban Board which is organized into columns and rows. The columns represent the status, i.e. from initial planning, work-in-process through customer acceptance. The status can be tailored to find the project context. The rows contain the tasks to be performed. Since Kanban focuses on maximizing throughput, a limit would be set on the maximum tasks in the Work-in-Process (WIP) column to avoid bottlenecks. Queues or inventories of work in any state are seen as waste. The WIP limit allows the team to focus on optimizing the flow of work items through the work processes, thereby achieving process optimization at a sustainable pace.

LSD (Lean Software Development)

Lean Software Development is an iterative methodology developed from the processes and practices in Lean Enterprise movement (for the production industry). Lean Software Development focuses the team on delivering value to the customers by focusing on the "Value Stream". The value stream approach emphasizes on the speed and efficiency of development workflow, and relies on rapid and reliable feedback between programmers and customers. Lean methods try to eliminate waste by prioritizing and working on "truly" valuable features of a system and delivering values rapidly in small batches.

Scrum

Scrum is considered a lightweight management framework suitable for managing iterative and incremental projects (including product development projects other than software). Scrum is renowned for its simplicity, proven success, productivity, and its flexibility to be used as a framework for various engineering practices promoted by other Agile methodologies, i.e. Scrum Masters are allowed to select the most suitable Agile practices to be brought under the Scrum framework. Scrum adopts an empirical approach by accepting problems cannot be fully understood at the beginning and must be continuously attended to along the project.

XP 12 Supporting Practices

The 12 supporting practices are: Planning Game, Small Releases, Customer Acceptance Tests, Simple Design, Pair Programming, Test-Driven Development, Refactoring, Continuous Integration, Collective Code Ownership, Coding Standards, Metaphor and Sustainable Pace.

XP 4 Values

The 4 values are: simplicity, communication, feedback, and courage.

DSDM 9 Principles

The 9 key principles that primarily revolve around business needs/value, active user involvement, empowered teams, frequent delivery, integrated testing, and stakeholder collaboration. * Active user involvement is imperative * DSDM teams must be empowered to make decisions * The focus is on frequent delivery of products * Fitness for business purpose is the essential criterion for acceptance of deliverables * Iterative and incremental development is necessary to converge on an accurate business solution * All changes during development are reversible * Requirements are baselined at a high level * Testing is integrated throughout the life cycle * A collaborative and cooperative approach between all stakeholders is essential

Crystal Family

The Crystal methodology is one of the most lightweight, adaptable approaches to software development. Crystal is a family of methodologies including Crystal Clear, Crystal Yellow, Crystal Orange, etc. The different methodologies in the Crystal family are differentiated by factors like team size, system criticality and project priorities. The Crystal family allows a tailored set of policies, practices and processes for individual projects in order to suit the characteristics of the projects. Crystal methodologies emphases on the interaction between people and processes.

Scrum three pillars

Transparency, introspection, adaptation

Agile Methodologies

XP (eXtreme Programming) Scrum LSD (Lean Software Development) Crystal Family ASD (Adaptive Software Development) DSDM (Dynamic Systems Development Method) Atern FDD (Feature Driven Development) Kanban

XP (eXtreme Programming)

XP (eXtreme Programming) is currently one of the most popular Agile methods. XP is a disciplined approach to delivering high-quality software quickly and continuously at very short intervals (typically every 1-3 week). XP promotes responsiveness to changes, higher customer involvement, rapid feedback loops, continuous testing, continuous planning and close teamwork. The name suggests that the beneficial elements of traditional programming practices are taken to the extreme.