During a delivery team meeting, some members of the team are confused about the "time" dimension depicted on a story map. After some discussion they conclude it describes:

• A.Time to complete stories
• B.User story implementation order
• C.Sequence of activities a user follows
• D.The project timeline

Comment: *

Name: *

Email: *

Verification: *

The team is very busy working on a top priority initiative. They have delivered many user stories and have many left to complete. However the components they are delivering are not yet delivering end-to-end business value. How can the team maintain understanding of the big picture without getting lost in the details?

• A.Create a gantt chart
• B.Refine their backlog
• C.Create a story map
• D.Fully elaborate user stories

Comment: *

Name: *

Email: *

Verification: *

When decomposing stories, the concept of "breadth before depth" signifies progressively breaking down:

• A.Backlog items to the lowest level of detail upfront
• B.Tests to align with usable functionality delivered through each story
• C.Estimates and resources required to accomplish the story
• D.Business goals into user stories representing smaller increments of value

Comment: *

Name: *

Email: *

Verification: *

While working at the Strategy Horizon, one of the key decisions to make upfront is:

• A.Have we delivered enough value?
• B.Is a need worth satisfying?
• C.What features should we deliver?
• D.Should we cancel the work?

Comment: *

Name: *

Email: *

Verification: *

While reviewing criteria for a well-written story, the team discusses the following criteria:

• A.Achievable unit of development
• B.Cost-benefit valuation
• C.Alignment to the organization's vision statement
• D.Detailed persona characteristics

Comment: *

Name: *

Email: *

Verification: *