3 - Planning the Iteration

What is PI Planning?

• PI Planning is a cadence-based event that serves as the heartbeat of the ART, aligning all teams on the ART to a shared mission and Vision.

• PI Planning is a planning event that serves as the heartbeat of the ART, aligning all teams on the ART's deliveries.

• PI Planning is a cadence-based event that serves as the largest of the ART, managing all teams on the ART to a have the same objectives.

• PI Planning is a planning event that serves as the heartbeat of the ART, aligning all teams on the ART to a shared mission and Vision.

Answer explanation

PI Planning is a cadence-based event that serves as the heartbeat of the ART, aligning all teams on the ART to a shared mission and Vision.

What are PI Planning inputs?

• Mission and top 10 objectives

• Vision and Mision

• Vision and top 10 features

• Mission and top 10 features

What are PI Planning outputs?

• Team and ART PI Objectives and ART Planning Board

• Team and ART PI Objectives and ART Program Board

• ART PI Objectives and ART Planning Board

• Team and Objectives and ART Program Board

What are uncommitted objectives used for?

• Uncommitted objectives don't count when calculating load

• They are not included in the commitment, thereby making the commitment more reliable

• They are planned, extra things teams do "just in case you have time"

• Uncommitted objectives help improve the predictability of delivering business value.

Answer explanation

What does 'INVEST' in good stories stand for?

• independent

  negotiable

  valuable

  estimable

  small

  testable

• independent

  non-functional

  valuable

  estimable

  small

  testable

• independent

  non-functional

  valuable

  estimable

  smart

  testable

• independent

  negotiable

  valuable

  estimable

  smart

  testable

Do Enabler Stories build the groundwork for future User Stories?

• True

• False

Are Refactors a systematic approach to improving the system without changing observable system behavior?

• True

• False

What are 'technical spikes' and 'functional spikes'?

• –Technical spikes - Researching a technical approach
  –Functional spikes - Researching how a user might use or interact with the system

• –Technical spikes - Studying different technological solution

  –Functional spikes - Researching how a user might not use or interact with the system

• –Technical spikes - Studying different technological solution

  –Functional spikes - Researching how a user might use other competitive systems

Select which is TRUE about 'story-point':

• A Story point is a singular number that represents volume, complexity, knowledge, uncertainty

• Story points are relative. They are not connected to any specific unit of measure.

• Story points should reflect the number of hours it takes to complete a task

• Story Points are required in Scrum

Answer explanation

Story Points = a technique used to estimate effort with relative estimates instead of time-based estimates

The numbers have no meaning in themselves, but only in relation to other items.

Although the use of Story Points is the most widely spread technique, we could easily generalize to include estimates in hours, ideal days or t-shirt sizes.

Team breakout common anti-patterns are:

• Too much time is spent analyzing each Story

• Shared Scrum Masters and Product Owners are not available enough

• No plan or partial plan at the end of the timebox

• Part-time Scrum Masters don’t have time to plan as part of the team