Scaling Agile Methods

Covering why scaling agile is important, the two scaling perspectives (scaling up vs scaling out), six ways large systems differ from small, three critical adaptations for large systems, brownfield systems, four reasons agile is difficult to introduce in large companies, conflicts with change management and testing standards, the most enthusiastic agile adopters, and agile introduction as cultural change

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

QUESTION OF

Views #: 17

Questions #: 10

Time: 10 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Why Scaling Agile Is Important

1 pts

volume_mute

The diagram below shows the two perspectives on scaling agile methods.

Why has there been great interest in scaling agile methods to cope with larger systems?

Because agile methods were originally developed for small co-located teams, but the need for faster delivery of software also applies to larger systems developed by large organisations

Because large systems are simpler than small ones and therefore easier to develop with agile methods

Because agile tools only work well at scale and are too complex for small teams

Because regulatory bodies require all large systems to use agile methods

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scaling Up vs Scaling Out

1 pts

There are two perspectives on scaling agile methods. Match each perspective to its correct definition.

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

Perspective

Scaling up

Scaling out

Definition

Concerned with using agile methods for developing large software systems that cannot be developed by a small team

Concerned with how agile methods can be introduced across a large organisation with many years of software development experience

note_alt Add notes

flag Flag

Correct Answer

Explanation

Six Ways Large Systems Differ from Small Systems

1 pts

volume_mute

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

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

Large systems are 'brownfield systems' that include and interact with a number of existing systems — many requirements are concerned with this interaction

Large systems always have fewer stakeholders than small systems, making requirements easier to manage

Where several systems are integrated, a significant fraction of development is concerned with system configuration rather than original code development

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

Large systems usually have a diverse set of stakeholders, making it practically impossible to involve all of them in the development process

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three Critical Adaptations for Large Systems

1 pts

Agile methods must be adapted to cope with large systems engineering. Complete the sentence about the three critical adaptations.

For large systems development, you need more up-front (1) and system documentation. Cross-team (2) mechanisms must be designed and used. And while strict continuous integration is practically impossible at scale, frequent system builds and regular (3) are essential.

note_alt Add notes

flag Flag

Correct Answer

Explanation

Brownfield Systems

1 pts

volume_mute

What is meant by large systems being described as 'brownfield systems', and why does this make agile approaches more difficult?

Brownfield systems are systems that have already failed and are being rebuilt from scratch

Brownfield systems are legacy systems that use outdated programming languages incompatible with agile tools

Brownfield systems are systems developed in industrial areas with environmental constraints

Brownfield systems include and interact with a number of existing systems — many requirements concern this interaction and don't really lend themselves to flexibility and incremental development; changes to existing systems often require negotiation with their managers

note_alt Add notes

flag Flag

Correct Answer

Explanation

Four Reasons Agile Is Difficult to Introduce in Large Companies

1 pts

Introducing agile methods into large companies is difficult for a number of reasons. Classify each reason under the correct category.

drag and drop the selected option to the right place

note_alt Add notes

flag Flag

Correct Answer

Explanation

Change Management and XP's Refactoring Conflict

1 pts

volume_mute

Change management is described as conflicting with XP's refactoring practice. Why?

Change management controls changes so their impact is predictable and costs controlled — all changes must be approved in advance before being made; this conflicts with XP where any developer can improve any code without getting external approval

Change management prevents any refactoring from occurring, making XP's continuous improvement impossible

Change management requires all code to be written in pairs, conflicting with XP's individual coding sessions

Change management requires waterfall planning which is incompatible with XP's incremental approach

note_alt Add notes

flag Flag

Correct Answer

Explanation

Most Enthusiastic Agile Adopters

1 pts

volume_mute

Which type of organisation is identified as among the most enthusiastic adopters of agile methods, and why?

Government agencies, because they have the most to gain from faster delivery

Large multinational corporations, because they have the resources to implement agile at scale

Small software companies that develop software products — they are not constrained by organisational bureaucracies or process standards and can change quickly to adopt new ideas

Academic institutions, because they have freedom to experiment with new methods

note_alt Add notes

flag Flag

Correct Answer

Explanation

Agile Introduction as Cultural Change

1 pts

volume_mute

True or False: Introducing and sustaining agile methods across a large organisation is primarily a technical challenge rather than a cultural challenge.

False

True

note_alt Add notes

flag Flag

Correct Answer

Explanation

External Regulation and Agile Testing Conflicts

1 pts

volume_mute

For large systems, there are testing standards that conflict with agile approaches. What is the specific conflict described?

Testing standards require test-first development which conflicts with agile's code-first approach

For large systems there are testing standards where a system build is handed over to an external testing team — this conflicts with the test-first and test-often approaches used in XP

Testing standards require all tests to be written in a specific formal language incompatible with agile tools

External testing teams must use waterfall processes which prevent integration with agile sprints

note_alt Add notes

flag Flag

Correct Answer

Explanation

Undergraduate Professional

Why Scaling Agile Is Important

Correct Answer

Explanation

Scaling Up vs Scaling Out

Perspective

Definition

Correct Answer

Explanation

Six Ways Large Systems Differ from Small Systems

Correct Answer

Explanation

Three Critical Adaptations for Large Systems

Correct Answer

Explanation

Brownfield Systems

Correct Answer

Explanation

Four Reasons Agile Is Difficult to Introduce in Large Companies

drag and drop the selected option to the right place

Correct Answer

Explanation

Change Management and XP's Refactoring Conflict

Correct Answer

Explanation

Most Enthusiastic Agile Adopters

Correct Answer

Explanation

Agile Introduction as Cultural Change

Correct Answer

Explanation

External Regulation and Agile Testing Conflicts

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: