4.4 + 4.5

Question 1

portfolio management

Answer 1

about which initiatives to pursue and how to connect these to strategic goals

Question 2

Epics (in Agile Portfolio Management practices and their rationale according to SAFe)

Answer 2

• epic = large and complex body of work

Avoid a long queue of development items that will get outdated.
- specify new epics when needed
- focus on value derived from epic

Question 3

portfolio backlog (in Agile Portfolio Management practices and their rationale according to SAFe)

Answer 3

• consists of epics
• clear visibility and communication of implementation methods

Question 4

epic owner (in Agile Portfolio Management practices and their rationale according to SAFe)

Answer 4

responsible for al decisions regarding its contents

Question 5

EA (in Agile Portfolio Management practices and their rationale according to SAFe)

Answer 5

Architecture solutions impact ROI

Question 6

What is the problem with Scaled Agile Framework (SAFe)

Answer 6

There exists little practice or research on this subject

Question 7

What are goals in large-scale agile SW development? Name three characteristics of goals.

Answer 7

• goals are high-level objects of the business
• express the rationale for proposed systems
• aligned with strategic themes & broken down along the hierarchy

Question 8

Goal-setting challenge in LSAD

Answer 8

• prioritization conflicts between goals
• management control limits team authority
• missing attachment of teams to goals

–> involve ATs in definition, prioritization, and communication of middle to lower-level goals. This ensures consideration technical aspects and acceptance of goals by the team

• unclear goals from higher levels
  –> All goals should be maintained in backlogs to facilitate clear understanding and transparency

Question 9

SW metric categories

Answer 9

• processes: SW related activities (design or testing)
• products: documents resulting from the process (code)
• resources: entities required by a process (personnel, teams)

Question 10

Metrics in SW development (characteristics suggested by practitioners=

Answer 10

• Affirmation and enforcement of agile principles
• Focus on trends and not numbers
• simple data collection
• input for meaningful conversation
• feedback on a frequent and regular basis

Question 11

OKRs

Answer 11

Objectives and Key Results
- OKRs are goal-setting framework to define a set of objectives and measure progress towards them.

Question 12

objectives

Answer 12

what you want to accomplish (annually)

Question 13

key results

Answer 13

how you will accomplish the objetives (quarterly)

Question 14

Goal-Question-Metric (GQM) Approach

Answer 14

• the goal is refined into numerous questions before creating metrics for each question.

Question 15

Most used metrics in large-scale agile development

Answer 15

• story point estimation = sum of story points estimated for a user story
• velocity = sum of story points of all user stories completed by a team in a sprint
• defects in production

Question 16

Reasons for metric deviation

Answer 16

• undesirable internal competition -> decreasing collaboration
• metrics only serve as input for initial discussion –> further qualitative information is required to understand the metric
• comparing teams based on a burndown chart is difficult because they estimate differently and are subjective to external and internal factors.

Question 17

Cumulative Flow Diagram in Jira

Answer 17

• automated data collection for metrics
• visualizes done, in-progress, and to-do
• potential points of failure: scrum team does not follow the predefined workflow