1. What is the primary purpose of the Funnel state in the Portfolio Kanban?

A) To implement high-priority epics
B) To visualize WIP across ARTs
C) To capture all new epic ideas
D) To write PI Objectives

Answer: ✅ C) To capture all new epic ideas
Explanation: The Funnel is where all new ideas (business or enabler epics) are collected before they are reviewed or analyzed.

2. What artifact is developed during the Analyzing state of the Portfolio Kanban?

A) PI Objectives
B) Epic Hypothesis Statement
C) Lean Business Case
D) Solution Intent

Answer: ✅ C) Lean Business Case
Explanation: In the Analyzing state, a Lean Business Case is developed to evaluate feasibility, cost, and benefit.

3. Who is primarily responsible for shepherding an epic through the Portfolio Kanban?

A) Product Owner
B) Scrum Master
C) Epic Owner
D) Release Train Engineer (RTE)

Answer: ✅ C) Epic Owner
Explanation: The Epic Owner is accountable for guiding the epic through its lifecycle in the Portfolio Kanban.

4. What prioritization method is commonly used in the Portfolio Kanban to rank epics?

A) MoSCoW
B) RICE
C) WSJF
D) FIFO

Answer: ✅ C) WSJF
Explanation: WSJF (Weighted Shortest Job First) is used to prioritize epics based on economics.

5. When is an epic considered "done" in the Portfolio Kanban?

A) When it is split into features
B) When MVP is implemented and evaluated
C) When PI Planning is complete
D) When it enters the Implementing stage

Answer: ✅ B) When MVP is implemented and evaluated
Explanation: The "Done" state is reached after MVP delivery and a decision to persevere, pivot, or stop.

6. Which Portfolio Kanban state involves determining whether the epic should be implemented based on deeper analysis?

A) Reviewing
B) Analyzing
C) Funnel
D) Portfolio Backlog

Answer: ✅ B) Analyzing
Explanation: In the Analyzing stage, the Lean Business Case is developed and a go/no-go decision is made.

7. What does the Portfolio Backlog contain?

A) Daily team tasks
B) Unprioritized ideas
C) Prioritized epics ready for implementation
D) Completed program increments

Answer: ✅ C) Prioritized epics ready for implementation
Explanation: The Portfolio Backlog holds epics that are approved and prioritized for execution.

8. A company has submitted several new epic ideas from various departments. These ideas are in early conceptual stages and have not yet been evaluated for feasibility. Which Portfolio Kanban state should they be placed in?

A) Reviewing
B) Analyzing
C) Funnel
D) Portfolio Backlog

Answer: ✅ C) Funnel
Explanation: The Funnel is the entry point where raw, unvetted ideas are collected.

9. During a Portfolio Sync, the LPM team is reviewing an epic that has a completed Lean Business Case and initial WSJF calculation. They are discussing whether to approve it for implementation. Which Kanban state is this epic likely in?

A) Funnel
B) Reviewing
C) Analyzing
D) Implementing

Answer: ✅ C) Analyzing
Explanation: The Analyzing stage includes the creation of a Lean Business Case and ends with a go/no-go decision.

10. An epic has been approved, prioritized, and added to the Portfolio Backlog. ARTs are now working on delivering its MVP. What is the current state of this epic in the Portfolio Kanban?

A) Analyzing
B) Implementing
C) Reviewing
D) Done

Answer: ✅ B) Implementing
Explanation: Once ARTs start building and delivering, the epic moves into the Implementing state.

11. An epic's MVP has been implemented, and the team has conducted an evaluation showing it delivered the expected business outcome. What is the next appropriate step in the Portfolio Kanban?

A) Return to Analyzing
B) Move it back to the Backlog
C) Mark it as Done
D) Break it into Capabilities

Answer: ✅ C) Mark it as Done
Explanation: Epics are moved to Done once MVP evaluation is complete and objectives are achieved (or a decision to pivot/stop is made).

12. A Portfolio Epic is taking longer than expected in the Analyzing state. Upon review, the Epic Owner discovers that teams are waiting on strategic alignment and business value clarification. What would be the best next step?

A) Move it to Implementing anyway
B) Return it to the Funnel
C) Escalate it to LPM for prioritization clarification
D) Add it directly to the Program Backlog

Answer: ✅ C) Escalate it to LPM for prioritization clarification
Explanation: If an epic stalls in analysis due to alignment issues, LPM should help resolve strategic ambiguity.

13. A stakeholder asks how a particular epic is progressing and wants to know what value has been delivered so far. The MVP is still being validated. What is the best way to provide visibility?

A) Show the Portfolio Backlog
B) Use the Portfolio Kanban board and relevant PI metrics
C) Present the Capability Breakdown
D) Refer to the Product Owner

Answer: ✅ B) Use the Portfolio Kanban board and relevant PI metrics
Explanation: The Kanban board shows epic progress; PI Objectives and MVP metrics provide value tracking.

14. An epic has been implemented, but during MVP validation, the results do not meet expected outcomes. After a retrospective, the team decides not to proceed. What should happen in the Portfolio Kanban?

A) Move to Reviewing
B) Re-prioritize it in the Backlog
C) Mark it as Done with a note to Pivot
D) Return to Analyzing

Answer: ✅ C) Mark it as Done with a note to Pivot
Explanation: Epics that do not meet MVP goals are still considered complete but should be labeled accordingly (e.g., Pivot, Stop).

15. What is the primary purpose of the Lean Business Case in SAFe?
A) To plan all detailed technical solutions
B) To define Agile Release Train features
C) To provide just enough information for economic decision-making
D) To document complete project requirements

✅ Answer: C) To provide just enough information for economic decision-making
Explanation: The Lean Business Case is a lightweight document focused on enabling rapid and lean decisions—not heavy planning.

16. Which of the following is a key component of a Lean Business Case?
A) Gantt chart
B) Epic Hypothesis Statement
C) Sprint backlog
D) SAFe PI Roadmap

✅ Answer: B) Epic Hypothesis Statement
Explanation: The hypothesis defines the business need and expected outcome of the epic.

17. In which state of the Portfolio Kanban is the Lean Business Case created?
A) Funnel
B) Implementing
C) Analyzing
D) Done

✅ Answer: C) Analyzing
Explanation: During the Analyzing state, the Epic Owner creates the Lean Business Case to evaluate the initiative.

18. What does the MVP section of the Lean Business Case define?
A) A fully-featured final product
B) A roadmap of all PI objectives
C) The minimum functionality needed to validate the epic
D) The velocity of all teams

✅ Answer: C) The minimum functionality needed to validate the epic
Explanation: MVP allows fast testing of the hypothesis with the least effort and cost.

19. What type of metrics are included in the Lean Business Case to track early progress?
A) Lagging indicators
B) Leading indicators
C) OKRs
D) SAFe Maturity Metrics

✅ Answer: B) Leading indicators
Explanation: These provide early signals of whether the epic is on track to deliver its intended outcomes.

20. Who is responsible for developing the Lean Business Case in SAFe?
A) Scrum Master
B) Release Train Engineer
C) Epic Owner
D) System Architect

✅ Answer: C) Epic Owner
Explanation: The Epic Owner leads the analysis and creation of the Lean Business Case.

21. What happens after the Lean Business Case is approved in the Portfolio Kanban?
A) It's archived for documentation
B) The MVP is built and validated
C) Teams estimate story points
D) A PI Planning event is triggered

✅ Answer: B) The MVP is built and validated
Explanation: Approval moves the epic to Implementing, where MVP development begins.

22. Why does SAFe emphasize a "lean" business case instead of a traditional business case?
A) To meet ISO documentation standards
B) To allow more financial control by PMOs
C) To support fast, decentralized decision-making with minimal overhead
D) To enable detailed technical planning upfront

✅ Answer: C) To support fast, decentralized decision-making with minimal overhead
Explanation: Lean Business Cases help avoid analysis paralysis and support agility at the portfolio level.

23. What is the core cycle used in the Lean Startup approach in SAFe?
A) Define-Design-Deliver
B) Build-Measure-Learn
C) Plan-Do-Check-Act
D) Analyze-Develop-Test

✅ Answer: B) Build-Measure-Learn
Explanation: This cycle is used to validate hypotheses quickly and make data-informed decisions.

24. What is the main purpose of developing an MVP in SAFe's Lean Startup approach?
A) To release a market-ready product
B) To comply with architecture governance
C) To validate the epic hypothesis with minimum effort
D) To gather feature requests from stakeholders

✅ Answer: C) To validate the epic hypothesis with minimum effort
Explanation: MVPs test assumptions before full-scale investment.

25. In SAFe, which phase of the Portfolio Kanban is the Lean Startup approach primarily applied?
A) Funnel
B) Reviewing
C) Implementing
D) Done

✅ Answer: C) Implementing
Explanation: MVPs are developed and validated during the Implementing phase.

26. What does a "pivot" decision mean in SAFe's Lean Startup cycle?
A) Deliver more features in the next PI
B) Stop the epic and release the team
C) Change direction based on MVP feedback
D) Increase WSJF score

✅ Answer: C) Change direction based on MVP feedback
Explanation: A pivot involves adapting based on what has been learned.

27. Which of the following best describes "validated learning" in SAFe's Lean Startup model?
A) Gathering anecdotal feedback
B) Documenting lessons learned post-implementation
C) Using real data from MVPs to confirm or refute hypotheses
D) Conducting classroom training for agile teams

✅ Answer: C) Using real data from MVPs to confirm or refute hypotheses
Explanation: It's about learning through data-driven experimentation.

28. What triggers a pivot, persevere, or stop decision in SAFe's Lean Startup loop?
A) Completion of two PIs
B) MVP performance based on leading indicators
C) Feedback from the System Architect
D) Approval from Release Train Engineer

✅ Answer: B) MVP performance based on leading indicators
Explanation: These early signals help determine next steps for the epic.

29. What is the result if the MVP confirms the hypothesis and business outcomes are promising?
A) The epic is stopped
B) The MVP is discarded
C) The epic is fully implemented
D) The Portfolio Kanban resets

✅ Answer: C) The epic is fully implemented
Explanation: A validated MVP can justify further investment and scaling.

30. What role typically leads the implementation of MVPs in SAFe?
A) Scrum Master
B) Release Train Engineer
C) Epic Owner
D) Product Manager

✅ Answer: C) Epic Owner
Explanation: Epic Owners guide the epic through the Portfolio Kanban, including MVP validation.

🎯 What is ART Kanban?

The ART Kanban is a visual system used by the Agile Release Train (ART) in SAFe to manage the flow of Features from idea to delivery. It helps the ART see what's coming, what's in progress, and what's done—making work visible and improving flow.

🔁 How ART Kanban Works

The Kanban board is divided into several states that represent the journey of a feature:

1. Funnel – This is where all new feature ideas land first. It's the initial intake area, where anything worth considering gets captured.

2. Analyzing – Once a feature enters this state, the Product Management team and architects start exploring it further. They look at feasibility, dependencies, and business value.

3. Ready – After a feature is analyzed and meets the "Definition of Ready," it's placed here. This means it's ready to be pulled into an upcoming PI and can be planned and implemented by the teams.

4. Implementing – In this phase, teams are actively working on the feature during a Program Increment (PI). They develop, test, and integrate it into the system.

5. Validating – Once built, the feature goes through validation. This includes testing, customer feedback, and system demos to ensure it meets expectations.

6. Deploying – Here, the feature is being rolled out into production. It may involve release coordination and deployment readiness checks.

7. Done – Finally, once the feature is in production and meets the "Definition of Done," it's marked as complete.

🚦 WIP Limits and Flow

To avoid overloading the system, teams apply Work-In-Progress (WIP) limits to each stage. This ensures the ART doesn't take on too much at once and can maintain a steady flow of value delivery.

🔧 Who Uses It?

• Product Managers use the Kanban to prioritize and track progress.

• System Architects use it to ensure technical enablers are aligned.

• Agile Teams use it to know what's ready for implementation.

• The Release Train Engineer (RTE) helps facilitate the flow of features across the board and remove bottlenecks.

🌟 Why It Matters

ART Kanban supports transparency, alignment, and predictability across multiple teams. It helps everyone on the train understand priorities, progress, and where support is needed—all in one visual place.

1. What does the ART Kanban primarily help visualize?
A) User Stories
B) PI Objectives
C) Features flowing through the Agile Release Train
D) Daily stand-up activities
✅ Answer: C) Features flowing through the Agile Release Train

2. Which of the following is the first state in the ART Kanban?
A) Ready
B) Funnel
C) Implementing
D) Validating
✅ Answer: B) Funnel

3. What is the goal of the 'Analyzing' state in ART Kanban?
A) To approve funding
B) To prioritize Features based on WSJF
C) To break Features into User Stories
D) To explore value, feasibility, and alignment
✅ Answer: D) To explore value, feasibility, and alignment

4. What must be satisfied before a Feature can move to the 'Ready' state?
A) Business Case approval
B) Architecture sign-off
C) Definition of Ready (DoR)
D) Team capacity validation
✅ Answer: C) Definition of Ready (DoR)

5. What typically happens during the 'Implementing' state of ART Kanban?
A) Features are removed
B) Teams work on Features in the current PI
C) Features are handed off to stakeholders
D) Features are written into the portfolio backlog
✅ Answer: B) Teams work on Features in the current PI

6. In the 'Validating' state, what is the key activity?
A) Continuous integration
B) Final acceptance testing
C) Gathering feedback and confirming business value
D) Documentation and compliance
✅ Answer: C) Gathering feedback and confirming business value

7. What does the 'Deploying' state in ART Kanban represent?
A) Teams are beginning to analyze the Feature
B) The Feature is added to the product roadmap
C) The Feature is being released to production
D) The MVP is being created
✅ Answer: C) The Feature is being released to production

8. When is a Feature considered 'Done' in the ART Kanban?
A) When all stories are complete
B) When MVP is validated
C) When it meets Definition of Done (DoD) and is released
D) When Product Management accepts it
✅ Answer: C) When it meets Definition of Done (DoD) and is released

9. What is a key benefit of using WIP limits on ART Kanban?
A) Maximizing the number of Features worked on
B) Encouraging multitasking
C) Reducing context switching and improving flow
D) Tracking individual team performance
✅ Answer: C) Reducing context switching and improving flow

10. Which role is most responsible for facilitating the flow on the ART Kanban?
A) Scrum Master
B) Release Train Engineer (RTE)
C) Product Owner
D) Business Owner
✅ Answer: B) Release Train Engineer (RTE)

🧠 What is Team Kanban in SAFe?

Team Kanban is a visual system that helps Agile teams manage the flow of work items (like stories, tasks, or defects) through a series of states. It's particularly useful for Kanban teams but also supports Scrum teams during execution.

It aligns with SAFe's principle of flow—helping teams visualize work, limit WIP, and optimize delivery speed and predictability.

🚦 Key Elements of Team Kanban

1. Visualize the Workflow

The team defines its own Kanban board with states that reflect how their work flows. These could include:

• To Do

• In Progress

• In Review

• Testing

• Done

Each state helps track where each work item is and who is working on what.

2. Limit Work in Progress (WIP)

WIP limits reduce multitasking and context switching. If a state is full (e.g., only 3 tasks allowed "In Progress"), no new work can enter until something moves forward. This boosts focus and flow efficiency.

3. Manage Flow

Teams monitor how quickly items move across the board (flow time, cycle time) to identify and remove bottlenecks. This encourages smoother, faster delivery of value.

4. Make Process Policies Explicit

Each team clearly defines and agrees on what it means for work to enter or exit a column (e.g., "Definition of Done" or "Ready for Review"). This improves clarity and accountability.

5. Improve Collaboratively

Using metrics and team retrospectives, teams reflect and continuously optimize their flow—adjusting WIP limits, redefining workflow stages, or removing blockers.

🧰 When to Use Team Kanban

• When the team works on a continuous flow of work (e.g., support, operations, DevOps).

• When they want more flexibility than timeboxed Sprints.

• When managing service-oriented or non-functional work.

• Even Scrum teams can use Kanban during a sprint to visualize work items.

🎯 Benefits of Team Kanban in SAFe

• Greater visibility and transparency

• Improved focus and team flow

• Faster issue identification and resolution

• Better work predictability and throughput

• Complements other SAFe practices (e.g., ScrumXP, DevOps)

1. What is the primary purpose of Team Kanban in SAFe?
A) To define PI Objectives
B) To manage and visualize the flow of stories and tasks
C) To manage the portfolio backlog
D) To replace Scrum completely

✅ Answer: B) To manage and visualize the flow of stories and tasks

2. Which of the following is a key practice in Team Kanban?
A) Epic approval
B) WIP Limits
C) Sprint Goals
D) PI Planning

✅ Answer: B) WIP Limits

3. What does WIP stand for in the context of Kanban?
A) Work in Phases
B) Work in Planning
C) Work in Progress
D) Work in Portfolio

✅ Answer: C) Work in Progress

4. Why are WIP limits important in a Team Kanban system?
A) They allow teams to deliver more features
B) They help avoid planning issues during PI
C) They encourage teams to multitask
D) They prevent overloading and encourage smooth flow

✅ Answer: D) They prevent overloading and encourage smooth flow

5. What type of teams benefit most from using Team Kanban?
A) Portfolio-level management teams
B) Teams working on continuous flow or service work
C) Marketing strategy teams
D) Teams that do not work on Agile

✅ Answer: B) Teams working on continuous flow or service work

6. What is one of the key metrics used in Team Kanban to measure performance?
A) Velocity
B) Sprint Burndown
C) Flow Time (Cycle Time)
D) Epic Completion Ratio

✅ Answer: C) Flow Time (Cycle Time)

7. Which of the following is NOT typically a Kanban board column?
A) To Do
B) In Progress
C) Sprint Planning
D) Done

✅ Answer: C) Sprint Planning

8. What is one reason a Scrum team might also use Kanban?
A) To eliminate the need for Sprint Reviews
B) To visualize and optimize flow within a Sprint
C) To remove the role of the Product Owner
D) To replace their backlog refinement process

✅ Answer: B) To visualize and optimize flow within a Sprint

9. What are "explicit policies" in Team Kanban used for?
A) Setting business priorities
B) Documenting PI objectives
C) Defining clear entry and exit criteria for workflow stages
D) Controlling access to the team board

✅ Answer: C) Defining clear entry and exit criteria for workflow stages

10. What continuous improvement practice is often paired with Team Kanban?
A) Annual planning
B) System demos
C) Retrospectives
D) Portfolio sync

✅ Answer: C) Retrospectives