Extreme Programming — Practices & Release Cycle

XP — Origin and Naming

1 pts

volume_mute

Extreme programming (XP) takes its name from pushing recognised good practices to 'extreme' levels. Which of the following correctly illustrates this extreme approach?

XP requires all requirements to be fully documented before any code is written

In XP, several new versions of a system may be developed by different programmers, integrated and tested in a single day

XP uses only waterfall-style planning to ensure predictability

XP eliminates all testing to achieve faster delivery

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP Release Cycle — Correct Order

1 pts

Please drag and drop the options to sort them

The diagram below shows the XP release cycle. Sort the six stages into the correct order, from first to last.

Release software

Select user stories for this release

Plan release

Evaluate system

Develop / Integrate / Test software

Break down stories to tasks

note_alt Add notes

flag Flag

Correct Answer

Explanation

Requirements as User Stories

1 pts

Complete the sentence about how requirements are expressed in XP.

In XP, requirements are expressed as (1) (also called user stories), which are implemented directly as a series of tasks. Programmers work in (2) and develop tests for each task before writing the code.

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP Practices — Descriptions

1 pts

The diagram below shows the ten XP practices.

Match each practice to its correct description.

To complete the line match

Click on an item in the first group
Click on the match in the second group

To delete a match, double click on a line

Practice

Simple design

Collective ownership

Continuous integration

Sustainable pace

Description

Enough design is carried out to meet the current requirements and no more

Developer pairs work on all areas of the system so no islands of expertise develop — anyone can change anything

As soon as work on a task is complete it is integrated into the whole system; all unit tests must then pass

Large amounts of overtime are not acceptable as the net effect is often to reduce code quality and medium-term productivity

note_alt Add notes

flag Flag

Correct Answer

Explanation

The On-Site Customer Practice

1 pts

volume_mute

What does the on-site customer practice in XP require, and what is the customer's responsibility?

A customer representative visits the team once a month to review progress

A representative of the end-user should be available full time for the XP team — they are a member of the development team and are responsible for bringing system requirements to the team for implementation

The customer performs all acceptance testing independently from the development team

The customer writes all user stories without involving the development team

note_alt Add notes

flag Flag

Correct Answer

Explanation

Story Cards and the Planning Game

1 pts

Complete the sentence about story cards in XP.

The development team breaks story cards down into (1) and estimates the effort and resources required for implementing each one. The customer then prioritises the stories, choosing those that can deliver useful business support and that can be implemented in about (2) weeks.

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP and Release Deadlines

1 pts

volume_mute

How does XP handle the situation when there are development problems and a release deadline is approaching?

The release is cancelled and restarted from scratch in the next iteration

The development team works overtime to meet the deadline

The release deadline is slipped to allow all planned functionality to be completed

The customer is consulted and functionality is removed from the planned release — release deadlines are never slipped

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP's Approach to Designing for Change

1 pts

volume_mute

Traditional software engineering advocates designing for change — anticipating future changes and designing the system to accommodate them easily. What is XP's position on this?

XP fully agrees with designing for change and requires all teams to produce architectural change plans

XP requires designing for change only in the first release, not subsequent ones

XP has discarded this principle — designing for change is often wasted effort because anticipated changes often never materialise and completely different changes may be requested; XP accepts that changes will happen and reorganises the software when they actually occur

XP advocates designing for change using UML models before any coding begins

note_alt Add notes

flag Flag

Correct Answer

Explanation

Refactoring — Purpose and Practice

1 pts

volume_mute

What is refactoring in XP, and why does incremental development make it necessary?

Refactoring means constantly looking for possible improvements to the software and implementing them immediately — this counters the tendency of incremental development to degrade software structure through code duplication, inappropriate reuse, and structural degeneration

Refactoring means removing test cases that are no longer relevant to the current system version

Refactoring is the process of rewriting the entire system from scratch when it becomes too complex

Refactoring is the process of adding new features to the software without testing them

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP in Practice — Which Practices Are Most Commonly Adopted?

1 pts

volume_mute

In practice, many companies that have adopted XP do not use all ten practices. Which three practices are identified as most commonly retained even in XP variants?

Small releases, test-first development, and continuous integration

Collective ownership, waterfall planning, and simple design

Formal requirements documents, pair programming, and sustainable pace

On-site customer, database design, and formal code inspections

note_alt Add notes

flag Flag

XP — Origin and Naming

Correct Answer

Explanation

XP Release Cycle — Correct Order

Correct Answer

Explanation

Requirements as User Stories

Correct Answer

Explanation

XP Practices — Descriptions

Practice

Description

Correct Answer

Explanation

The On-Site Customer Practice

Correct Answer

Explanation

Story Cards and the Planning Game

Correct Answer

Explanation

XP and Release Deadlines

Correct Answer

Explanation

XP's Approach to Designing for Change

Correct Answer

Explanation

Refactoring — Purpose and Practice

Correct Answer

Explanation

XP in Practice — Which Practices Are Most Commonly Adopted?

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: