Agile Project Management - Scrum

Covering why plan-driven management doesn't suit agile, Scrum's focus and scope, the three Scrum phases, sprints, the product backlog, the Scrum master role, team isolation during sprints, daily stand-up meetings, five advantages of Scrum, and Scrum's original co-located team design versus distributed development

download Export

search_insights Statistics

stylus_note White Board

Quran

calculate Calculator

dictionary Dictionary

fullscreen Full Screen

QUESTION OF

Views #: 5

Questions #: 10

Time: 10 minutes

Pass Score: 80.0%

Style

Step

List

Mode

Exam

Practice

Why Plan-driven Management Doesn't Suit Agile

1 pts

volume_mute

The standard plan-driven approach to project management requires a manager to have a stable view of everything that has to be developed. Why does this not work well with agile methods?

Because agile teams always refuse to report progress to managers

Because agile development has requirements developed incrementally, software delivered in short rapid increments, and changes to requirements and software as the norm — a stable view is impossible

Because plan-driven management tools are incompatible with agile development environments

Because plan-driven management always costs more than agile management

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scrum — Focus and Scope

1 pts

volume_mute

The Scrum approach is a general agile method. What is its primary focus, and what does it deliberately not prescribe?

Scrum focuses on specific programming techniques such as pair programming and test-first development

Scrum focuses on managing the iterative development rather than prescribing specific technical approaches such as pair programming and test-first development — it can therefore be used with more technical agile approaches like XP

Scrum focuses on requirements engineering and producing detailed specifications before development

Scrum prescribes all aspects of agile development including coding standards, testing, and deployment

note_alt Add notes

flag Flag

Correct Answer

Explanation

Three Scrum Phases

1 pts

Please drag and drop the options to sort them

The diagram below shows the Scrum process.

Sort the three Scrum phases into the correct order.

Project closure

Outline planning and architectural design

Sprint cycles

note_alt Add notes

flag Flag

Correct Answer

Explanation

What Is a Sprint?

1 pts

Complete the sentence about Scrum sprints.

A Scrum sprint is a planning unit in which the work to be done is (1), features are selected for development, and the software is implemented. Sprints are fixed length, normally (2) weeks, and at the end of a sprint the completed functionality is delivered to stakeholders.

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

assessed

2–4

ignored

5-6

note_alt Add notes

flag Flag

Correct Answer

Explanation

Product Backlog

1 pts

volume_mute

What is the product backlog in Scrum, and what happens to it during the assessment phase of a sprint?

The product backlog is a log of all bugs found during testing, prioritised for fixing

The product backlog is the list of completed work — it grows as each sprint is finished

The product backlog is a fixed list defined at the start of the project that cannot be changed during development

The product backlog is the list of work to be done on the project; during the assessment phase it is reviewed, priorities and risks are assigned, and the customer can introduce new requirements or tasks at the beginning of each sprint

note_alt Add notes

flag Flag

Correct Answer

Explanation

The Scrum Master Role

1 pts

volume_mute

What is the role of the Scrum master, and how does Scrum's approach differ from traditional project management?

The Scrum master is a facilitator who arranges daily meetings, tracks the backlog, records decisions, measures progress, and communicates with customers and management — the term 'project manager' is deliberately avoided as the whole team should be empowered to make decisions

The Scrum master is responsible for writing all user stories and converting them to tasks before each sprint begins

The Scrum master is the project manager who assigns tasks top-down to team members and monitors individual performance

The Scrum master is a technical architect who designs the system architecture for each sprint

note_alt Add notes

flag Flag

Correct Answer

Explanation

Team Isolation During a Sprint

1 pts

volume_mute

During the development stage of a Scrum sprint, how is the team managed in terms of external contact?

The customer is embedded in the team and communicates directly with all developers throughout the sprint

The team is isolated from the customer and organisation with all communications channelled through the Scrum master — the Scrum master's role is to protect the development team from external distractions

Team members individually decide whether to communicate externally based on their personal preference

The team interacts freely with customers and management at all times to ensure continuous alignment

note_alt Add notes

flag Flag

Correct Answer

Explanation

Daily Stand-up Meetings

1 pts

volume_mute

What happens during Scrum's daily stand-up meetings, and what is their purpose?

The Scrum master assigns new tasks to team members for the day

The customer presents new requirements and the team estimates the effort required

Only senior developers attend to discuss architectural decisions for the current sprint

All team members share information: describe their progress since the last meeting, problems that have arisen, and what is planned for the following day — this means everyone knows what is going on and can replan short-term work to cope with problems

note_alt Add notes

flag Flag

Correct Answer

Explanation

Five Advantages of Scrum

1 pts

volume_mute

Which of the following are stated advantages of Scrum? Select all that apply.

Customers see on-time delivery of increments and gain feedback on how the product works

Unstable requirements do not hold up progress

Trust between customers and developers is established and a positive culture created where everyone expects the project to succeed

The whole team has visibility of everything, improving team communication

Scrum eliminates all software defects before delivery

The product is broken down into a set of manageable and understandable chunks

note_alt Add notes

flag Flag

Correct Answer

Explanation

Scrum Originally for Co-located Teams

1 pts

volume_mute

Scrum, as originally designed, was intended for use with co-located teams where all members could get together every day in stand-up meetings. What challenge has emerged as software development has evolved?

Stand-up meetings have been proven ineffective and are being replaced with written status reports in all Scrum teams

Much software development now involves distributed teams with team members in different places around the world — consequently there are various experiments to develop Scrum for distributed development environments

Co-located teams have become too large for Scrum's original stand-up meeting format

Scrum's original design is now considered legally incompatible with remote work regulations in most countries

note_alt Add notes

flag Flag

Correct Answer

Explanation

Undergraduate Professional

Why Plan-driven Management Doesn't Suit Agile

Correct Answer

Explanation

Scrum — Focus and Scope

Correct Answer

Explanation

Three Scrum Phases

Correct Answer

Explanation

What Is a Sprint?

Correct Answer

Explanation

Product Backlog

Correct Answer

Explanation

The Scrum Master Role

Correct Answer

Explanation

Team Isolation During a Sprint

Correct Answer

Explanation

Daily Stand-up Meetings

Correct Answer

Explanation

Five Advantages of Scrum

Correct Answer

Explanation

Scrum Originally for Co-located Teams

Correct Answer

Explanation

Quran Recitation

Query Dictionary

Select a result: