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...

Scrum Team

The scrum team is a cross-functional group that is responsible for delivering the software or product. In Agile development, the team usually includes people skilled to understand customer requirements and conduct software design, coding and testing. Additional skills...

Self-Organization

Self-organization is a property of complex adaptive systems, whereby the organization of the system emerges over time as a response to its environment. In Agile development, particularly in Scrum, self-organization is a property of the agile development team, which...

ScrumMaster

The ScrumMaster is responsible for maintaining the Scrum process and the overall health of the team. The ScrumMaster assures that the team is fully functional and productive. The ScrumMaster performs this role by administering the Scrum ceremonies, facilitating the...

Sprint

The Scrum term for an iteration.  It is a time-boxed event of 30 days, or less, that serves as a container for the other Scrum events and activities. Sprints are done consecutively, without intermediate gaps. The sprint starts with a sprint planning meeting. At the...

Sprint Backlog

An overview of the development work to realize a Sprint’s goal, typically a forecast of functionality and the work needed to deliver that functionality. Managed by the Development Team, it is a list of features, user stories or tasks that are pulled from the product...

Sprint Planning Meeting

Each sprint begins with a two-part sprint planning meeting, the activity that prioritizes and identifies stories and concrete tasks for the next sprint. For a one-month or four-week sprint, this two-part meeting should last eight hours; for a two-week sprint, it lasts...

Stakeholder

A person external to the Scrum Team with a specific interest in and knowledge of a product that is required for incremental discovery. Represented by the Product Owner and actively engaged with the Scrum Team at Sprint Review. See also: Chicken  ...

Task

Tasks are descriptions of the actual work that an individual or pair does in order to complete a story. They are manageable, doable, and trackable units of work. Typically, there are several tasks per story. Tasks have the following attributes, and all tasks must be...

Task Board

A chart that presents, at minimum, “to do”, “in progress”, and “done” columns for organizing a team’s work. Some teams include their backlog as a column on the task board, while others limit it to work to be performed during the current iteration. Ideally, the task...

Team

In agile software development, the team refers to the cross-functional group of people that have made a collective commitment to work together to produce the work product and improve their performance over time. In addition to software development and test roles, the...

Test Automation

“The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting function.” (Wikipedia) In agile development, test automation is frequently...

Test-Driven Development (TDD)

Test-first software development practice in which test cases are defined and created first, and subsequently executable code is created to make the test pass. The failing tests are constructed to pass as development proceeds and tests succeed. Ken Beck is credited for...
error: Content is protected !!