Agile Project Management Agile Release Planning and Roadmaps

Question 1

What is the primary purpose of a product roadmap in Agile?

Accepted Answer

To communicate the strategic direction and planned evolution of a product

Answer

To assign tasks to individual developers

Answer

To document every sprint's completed work

Answer

To replace the product backlog

Question 2

In Agile release planning, what is a 'release' typically defined as?

Accepted Answer

A deployable increment of working software that delivers value to stakeholders

Answer

A single sprint deliverable

Answer

A document listing all completed features

Answer

A milestone in the project charter

Question 3

Which technique is commonly used in Agile to forecast when features will be completed?

Accepted Answer

Velocity-based forecasting

Answer

Gantt chart tracking

Answer

Critical path method

Answer

Earned value management

Question 4

What is a 'rolling wave' release plan?

Accepted Answer

A plan where near-term releases are detailed and future releases are high-level

Answer

A plan that covers all sprints in equal detail

Answer

A plan updated only at the end of each release

Answer

A waterfall plan adapted for Agile teams

Question 5

How does Agile differ from waterfall in release planning?

Accepted Answer

Agile supports frequent, incremental releases rather than one big release at the end

Answer

Agile releases are always annual

Answer

Agile does not plan releases at all

Answer

Agile requires sign-off from all stakeholders before any release

Question 6

What is a 'minimum viable product' (MVP) in the context of Agile release planning?

Accepted Answer

The smallest set of features that delivers value and enables validated learning

Answer

The smallest product that can be sold at any price

Answer

The version with the minimum number of bugs

Answer

A prototype used only for internal testing