A component team is an Agile Team whose primary area of concern is focused on a specific component, or set of components, of the system. They leverage their technical skills and interest and focus on building robust components that provide for reliability, separation of concerns, foster re-use, and improve testability. Component teams are typically used when the system has complex, nonfunctional requirements that require deep technical expertise and specialization, such as performance, security, scalability, etc. Component teams can also enable high reuse of components across multiple solutions, reducing duplication and waste. However, component teams also introduce challenges, such as increased dependencies, coordination, and integration efforts with other teams, as well as reduced end-to-end value delivery and customer feedback. Therefore, component teams should be used sparingly and only when the benefits outweigh the costs. References: Organizing Agile Teams and ARTs: Team Topologies at Scale, Agile Teams, Feature Teams vs Component Teams, System Team, Feature Team vs Component Team in Agile
Question 2
Which statement is true about Features and Stories?
Correct Answer: B
In SAFe, a clear distinction is made between the purpose, structure and content of features, and that of stories (including enablers). Features are visible units of business intent that the customer recognizes, and it's at this level of detail that the customer is able to prioritize their needs1. Features are maintained in the ART Backlog and sized to fit in a PI so that each delivers new value2. Stories are short descriptions of a small piece of desired functionality written from the user's perspective. Stories are the primary artifact used to define system behavior in Agile3. Stories are small and must be completed in a single iteration3. Therefore, features can be larger than an iteration but stories should be small enough to fit into an iteration. References: Story - Scaled Agile Framework, Features and Capabilities - Scaled Agile Framework, Right-Sizing Features for SAFe Program Increments - Scaled Agile Framework
Question 3
Apart from the Iteration Planning, when can the team improve stories, add acceptance criteria, and point out missing information to the Product Owner?
Correct Answer: D
Question 4
Kanban teams establish and publish Iteration goals, which consist of the known parts of their work
Correct Answer: B
Question 5
Why is it important to spend time "in the zone"?
Correct Answer: B
Spending time "in the zone" means being fully immersed in a task that is challenging, engaging, and enjoyable. This state of flow is associated with higher levels of creativity, innovation, and performance1. According to SAFe, optimizing the time spent in the zone for individuals and teams makes a substantial difference in ART productivity2. The other options are not directly related to the concept of flow, although they may be influenced by it. Reducing queue lengths, refining productive collaboration, and making work in process visible are all aspects of visualizing and limiting WIP, which is another flow accelerator3.
