Organizing teams around Features can significantly reduce dependencies between teams. When teams are aligned to deliver specific features, they have more autonomy and can work more independently, without needing to wait for other teams to complete their parts. This alignment minimizes coordination and dependency management overhead, enabling faster and more efficient delivery. It also allows teams to focus on delivering end-to-end functionality, which enhances the quality and coherence of the product.
SAFe Scrum Master References
SAFe 5.0 framework: principles of organizing teams around features to reduce dependencies
SAFe Agile Teams: benefits of feature-based team organization
Question 2
When creating an Improvement Roadmap, what is one source of guidance for improving a team's technical practices?
Options:
A.
The Agile Program Management Office
B.
Communities of Practice
C.
The Lean Agile Center of Excellence
D.
The Solution Architect
Answer:
B
Explanation:
Communities of Practice (CoPs):CoPs are groups of people who share a common interest in a particular domain or practice and come together to share knowledge, solve problems, and improve their skills.
Improvement Roadmap:When creating an Improvement Roadmap, CoPs provide valuable insights and guidance on best practices, emerging trends, and effective techniques for improving technical practices.
SAFe Scrum Master References:
SAFe recognizes CoPs as a vital resource for fostering continuous learning and improvement within organizations. They provide a platform for practitioners to exchange ideas and elevate their practices.
Question 3
What is one problem with phase-gate Milestones?
Options:
A.
They assume a point Solution exists and can be built right the first time
B.
They force design decisions too late in the process
C.
They account for variability inherent in the process
D.
They require the Product Owner to act as gatekeeper or guardian of the process
Answer:
A
Explanation:
Phase-gate milestones are traditional project management mechanisms that mark the end of one phase and the beginning of another. One major problem with phase-gate milestones is that they assume a point solution exists and can be built correctly the first time. This assumption does not account for the iterative nature of Agile methodologies, where solutions are developed incrementally and iteratively, with feedback loops and continuous improvement. Assuming a point solution can be finalized early often leads to rigidity, lack of adaptability, and higher risks of delivering a product that does not meet the actual needs or expectations.