Review — Agile Software Development

A comprehensive review of the agile software development, covering all fundamental knowledge areas: the Agile Manifesto and principles, agile method problems and limitations, plan-driven vs agile development, XP practices and release cycle, testing in XP and test-first development, pair programming, Scrum and agile project management, and scaling agile methods

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

QUESTION OF

Views #: 24

Questions #: 20

Time: 20 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Agile Manifesto — Four Values

1 pts

volume_mute

The diagram below shows the four core values of the Agile Manifesto.

Which of the following is the fourth value of the Agile Manifesto (not shown in the diagram above)?

Comprehensive documentation over working software

Responding to change over following a plan

Contract negotiation over customer collaboration

Processes and tools over individuals and interactions

note_alt Add notes

flag Flag

Correct Answer

Explanation

Five Principles of Agile Methods

1 pts

The five principles of agile methods are: Customer involvement, Incremental delivery, People not process, Embrace change, and Maintain simplicity. Match each principle 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

Principle

Customer involvement

People not process

Embrace change

Maintain simplicity

Description

Customers should be closely involved throughout the development process to provide and prioritise new requirements and to evaluate iterations

The skills of the development team should be recognised and exploited — team members should be left to develop their own ways of working without prescriptive processes

Expect the system requirements to change and design the system so that it can accommodate these changes

Focus on simplicity in both the software being developed and the development process — actively work to eliminate complexity from the system

note_alt Add notes

flag Flag

Correct Answer

Explanation

Agile Methods — Practical Difficulties

1 pts

volume_mute

Which of the following are identified as practical difficulties in applying agile principles? Select all that apply.

Agile methods always produce lower quality software than plan-driven approaches

Individual team members may not have suitable personalities for the intense involvement typical of agile methods

Customer involvement depends on a customer who is willing and able to spend time with the development team and can represent all stakeholders — this is often not possible

Prioritising changes is extremely difficult when there are many stakeholders who give different priorities to different changes

Maintaining simplicity requires extra work and delivery pressure may mean there is no time to carry out desirable simplifications

note_alt Add notes

flag Flag

Correct Answer

Explanation

Agile and Maintenance — Key Problem

1 pts

Complete the sentence about the key maintenance problem with agile-developed systems.

Agile methods rely on team members understanding aspects of the system without having to consult (1). If an agile development team is broken up, this implicit knowledge is lost and it is difficult for new team members to build up the same (2) of the system and its components.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Plan-driven vs Agile — Iteration Location

1 pts

volume_mute

How does the location of iteration differ between plan-driven and agile approaches?

In both approaches, iteration occurs within activities only

Neither approach uses iteration — both follow a linear sequence of stages

In plan-driven approaches, iteration occurs within activities with formal documents used to communicate between stages; in agile approaches, iteration occurs across activities so requirements and design are developed together

In agile approaches, iteration occurs within activities; in plan-driven approaches, iteration occurs across activities

note_alt Add notes

flag Flag

Correct Answer

Explanation

Choosing Plan-driven vs Agile

1 pts

Classify each factor as favouring a plan-driven or agile approach.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP Release Cycle

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

XP Practices — Match

1 pts

Match each XP 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

Test-first development

Collective ownership

Continuous integration

Refactoring

Description

An automated unit test framework is used to write tests for new functionality before that functionality is implemented

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

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

All developers are expected to look for possible improvements to the software and implement them immediately to keep code simple and maintainable

note_alt Add notes

flag Flag

Correct Answer

Explanation

Test-First Development — Core Benefit

1 pts

volume_mute

What is the key benefit of writing tests before writing code in test-first development?

It automatically generates production code from the test specifications

Writing the test first implicitly defines both an interface and a specification of behaviour for the functionality being developed — problems of requirements and interface misunderstandings are reduced, and test-lag is avoided

It means programmers can skip code reviews entirely as tests serve as reviews

It eliminates the need for acceptance testing by the customer

note_alt Add notes

flag Flag

Correct Answer

Explanation

Pair Programming — Three Advantages

1 pts

volume_mute

Which of the following are the three stated advantages of pair programming? Select all that apply.

Eliminates all software defects before code is committed

Helps support refactoring — where collective ownership is used, others benefit immediately from improvements and are likely to support the process

Supports collective ownership and responsibility — software owned by the team as a whole, reflecting egoless programming

Acts as an informal code review — each line of code looked at by at least two people

Always produces twice as much code as two individual programmers in the same time

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scrum — Sprint and Scrum Master

1 pts

The diagram below shows the Scrum process.

Complete the sentences.

A Scrum sprint is a fixed-length planning unit, normally (1) weeks, in which features are selected and software is developed. All communications during the sprint are channelled through the (2), whose role is to protect the development team from external distractions.

Please drag and drop the selected option in the right place or type it instead

2–4

Scrum master

3-4

Project Manager

note_alt Add notes

flag Flag

Correct Answer

Explanation

Product Backlog and Daily Stand-ups

1 pts

In Scrum, two mechanisms help keep the team aligned and work prioritised. Match each mechanism 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

Mechanism

Product backlog

Daily stand-up meeting

Description

The list of work to be done on the project — reviewed each sprint, with priorities and risks assigned; customers can introduce new requirements at the beginning of each sprint

A short, focused meeting where all team members share their progress since the last meeting, problems that have arisen, and what is planned for the following day — enabling short-term replanning

note_alt Add notes

flag Flag

Correct Answer

Explanation

Six Ways Large Systems Differ

1 pts

volume_mute

Large software system development differs from small system development in several ways. Which of the following are identified differences? Select all that apply.

Large systems have a long procurement and development time making it difficult to maintain coherent teams

Large systems are usually collections of separate communicating systems where separate teams develop each — it is practically impossible for each team to see the whole system

Large systems always have fewer stakeholders making requirements simpler to manage

Large systems are 'brownfield systems' that include and interact with existing systems — requirements concern this interaction and don't lend themselves to incremental development

A significant fraction of large system development concerns system configuration rather than original code development

Large systems usually have a diverse set of stakeholders making full involvement practically impossible

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scaling Up vs Scaling Out

1 pts

There are two perspectives on scaling agile methods. Classify each statement under the correct perspective.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Classify Techniques by Agile Principle Supported

1 pts

Classify each XP practice under the agile principle it primarily supports.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Why Agile Is Difficult for Large Companies

1 pts

volume_mute

Which of the following are identified reasons why it is difficult to introduce agile methods in large companies? Select all that apply.

There may be cultural resistance in organisations with a long history of conventional systems engineering processes

Agile methods work best with relatively high skill levels but large organisations have a wide range of skills

Project managers may be reluctant to accept the risk of a new approach they are unfamiliar with

Agile tools are always too expensive for large organisations to afford

Large organisations often have quality procedures and standards incompatible with agile methods

note_alt Add notes

flag Flag

Correct Answer

Explanation

Agile Contract Problem

1 pts

Complete the sentence about the agile contract problem.

Because incremental specification is inherent in agile methods, agile methods must rely on contracts where the customer pays for the (1) required for system development rather than the development of a specific (2) of requirements.

note_alt Add notes

flag Flag

Correct Answer

Explanation

XP's Rejection of Designing for Change

1 pts

volume_mute

True or False: XP advocates designing the system in advance for anticipated future changes, to make those changes easier to implement when they arrive.

True

False

note_alt Add notes

flag Flag

Correct Answer

Explanation

Most Important Agile Methods Covered

1 pts

There are two of the most widely used agile methods. Complete the sentence.

(1) as the best-known example of an agile method that integrates programming practices, and (2) as a general agile method focused on managing iterative development rather than specific technical approaches.

Please drag and drop the selected option in the right place or type it instead

extreme programming (XP)

Scrum

Waterfall

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three XP Practices Most Widely Retained

1 pts

volume_mute

In practice, many companies who adopt an XP variant do not use all ten practices. Select the three most widely retained practices.

Continuous integration

Test-first development

Small releases

Pair programming

Refactoring

Collective ownership

note_alt Add notes

flag Flag

Correct Answer

Explanation

Undergraduate Professional

Agile Manifesto — Four Values

Correct Answer

Explanation

Five Principles of Agile Methods

Principle

Description

Correct Answer

Explanation

Agile Methods — Practical Difficulties

Correct Answer

Explanation

Agile and Maintenance — Key Problem

Correct Answer

Explanation

Plan-driven vs Agile — Iteration Location

Correct Answer

Explanation

Choosing Plan-driven vs Agile

drag and drop the selected option to the right place

Correct Answer

Explanation

XP Release Cycle

Correct Answer

Explanation

XP Practices — Match

Practice

Description

Correct Answer

Explanation

Test-First Development — Core Benefit

Correct Answer

Explanation

Pair Programming — Three Advantages

Correct Answer

Explanation

Scrum — Sprint and Scrum Master

Correct Answer

Explanation

Product Backlog and Daily Stand-ups

Mechanism

Description

Correct Answer

Explanation

Six Ways Large Systems Differ

Correct Answer

Explanation

Scaling Up vs Scaling Out

drag and drop the selected option to the right place

Correct Answer

Explanation

Classify Techniques by Agile Principle Supported

drag and drop the selected option to the right place

Correct Answer

Explanation

Why Agile Is Difficult for Large Companies

Correct Answer

Explanation

Agile Contract Problem

Correct Answer

Explanation

XP's Rejection of Designing for Change

Correct Answer

Explanation

Most Important Agile Methods Covered

Correct Answer

Explanation

Three XP Practices Most Widely Retained

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: