Iteration

A period (from 1 week to 2 months in duration) during which the Agile development team produces an increment of completed software. All system lifecycle phases (requirements, design, code, and test) must be completed during the iteration and then (empirically)...

Kanban

Kanban is a tool derived from lean manufacturing and is associated with the branch of agile practices loosely referred to as Lean Software Development. Like a task board, Kanban visually represents the state of work in process. Unlike a task board, the Kanban...

Lean Software Development

An adaption of Lean manufacturing principles and practices to the software development domain. Lean software development (also known as Lean-Agile) is focused on reducing (lean) waste and optimizing the software production value stream. In large part, the principles...

Minimum Marketable Features

The smallest set of functionality that must be realized in order for the customer to perceive value. A “MMF” is characterized by the three attributes: minimum, marketable, and feature. A feature is something that is perceived, of itself, as value by the user....

Minimum Viable Product (MVP)

Potentially confusing, the strict Lean Startup definition is the smallest thing we can test to enable one cycle of the build – measure – learn loop. As opposed to Minimum Marketable Feature (MMF) that is the smallest thing that delivers a user value.

Pair Programming

“An Agile software development technique in which two programmers work together at one workstation. One types in code while the other reviews each line of code as it is typed in. The person typing is called the driver. and the person reviewing the code is called the...

Parallel Development

Parallel development occurs whenever a software development project requires separate development efforts on related code bases. For example, when a software product is shipped to customers, a product development team may begin working on a new major feature release...

Pirate Metrics

A set of metrics designed to support LSU analytics and validation. AARRR is short for Acquisition, Activation, Retention, Referral, Revenue.

Planning Game

“The main planning process within extreme programming is called the Planning Game. The game is a meeting that occurs once per iteration, typically once a week. The planning process is divided into two parts.” (Wikipedia) In XP, the planning game includes iteration (or...

Planning Poker

“Planning Poker is a consensus-based technique for estimating, mostly used to estimate effort or relative size of tasks in software development.” (Wikipedia)

Product

Broadly speaking, product refers to a collection of tangible and intangible features that are integrated and packaged into software releases that offer value to a customer or to a market. The term “product” is often used in Agile software development to denote the...

Product Backlog

Equivalent to Backlog. A collection of stories and tasks the Sprint team will work on at some point in the future. Either the Product Owner has not prioritized them or has assigned them lower priority. Teams or organizations may use the term “backlog” in one of the...

Product Owner

Product Owner is one of the key roles in Scrum. The product owner is the primary business representative who represents the business stakeholders’ “voice of the customer” and the “voice of the business” to the sprint team. The responsibilities of the Product Owner...

Product Vision

A product vision is a brief statement of the desired future state that would be achieved through the project initiative. The product vision may be expressed in any number of ways including financial performance, customer satisfaction, market share, functional...

Refactoring

Agile software development practice in which code is adjusted within the code base without impacting the external, functional behavior of that code.it improves its internal structure. For example, if a programmer wants to add new functionality to a program, she may...

Release (Software)

The movement of a software product or system from development into production. One principle of Agile development is to focus on releasing software into productive use as soon as a minimum marketable feature set can be delivered, and then proceeding with frequent...

Release Plan

The release plan is a schedule for releasing software into productive use. Typical release plans include the key features to be delivered, along with corresponding release dates. Release plans may also expose key milestones or dependencies that parallel project...

Release Planning

Release planning refers to planning activities used to estimate when software will be released into product use. Activities include projecting the level of effort in terms of the number of iterations that will be necessary to deliver the desired features. This is...

Retrospective

A timeboxed meeting held at the end of an iteration, or at the end of a release, in which the team examines its processes to determine what succeeded and what could be improved. The retrospective is key to an Agile team’s ability to “inspect and adapt” in the pursuit...

Scrum

A framework to support teams in complex product development. Scrum consists of Scrum Teams and their associated roles, events, artifacts, and rules, as defined in the Scrum GuideTM. Scrum is comprised of a series of short iterations – called sprints – each of...
error: Content is protected !!