- Which role does Product Management work with to prioritize Enablers?
a. Solution Management
b. Development Manager
c. Product Owner
d. System Architect
- What is a pattern for splitting Features into Stories?
a. Layers of the technology stack
b. Variations in data
c. Team Skills
d. Task to complete
The correct answer and explanation is:
Question 1: Which role does Product Management work with to prioritize Enablers?
Correct Answer:
d. System Architect
Explanation:
Enablers are technical initiatives that support the architecture and enable future business functionality. They are critical in ensuring that the system remains scalable, maintainable, and technically sound while supporting new features.
Product Management collaborates with System Architects to prioritize enablers because:
- Expertise in System Design: System Architects understand the technical requirements and system design implications. They identify enablers required to address technical debt, improve infrastructure, or adopt new technologies.
- Alignment with Business Goals: Product Management ensures alignment between technical enablers and business priorities. They work with System Architects to evaluate enablers based on their impact on delivering customer value.
- Balancing Innovation and Maintenance: While Product Management focuses on delivering customer-centric features, the System Architect ensures that the system’s foundation is robust enough to support future growth.
- Strategic Planning: Both roles collaborate during Program Increment (PI) planning to prioritize enablers within the backlog, ensuring they fit into the larger strategic goals.
This collaboration ensures the balance between feature development and technical health, enabling sustainable delivery of value to customers.
Question 2: What is a pattern for splitting Features into Stories?
Correct Answer:
a. Layers of the technology stack
Explanation:
When splitting features into smaller stories, layers of the technology stack provide a structured approach. Features often span multiple layers (e.g., database, backend logic, and frontend interface). Splitting by layers ensures manageable and testable increments of work.
- Backend vs. Frontend: For example, one story might involve implementing backend APIs, while another focuses on the frontend UI.
- Database Operations: A separate story can focus on database schema design or modifications.
- Testable Units: Each layer provides a logical boundary, making it easier to test and validate work incrementally.
While other options may sometimes apply, splitting by the technology stack is particularly effective in ensuring clear separation of concerns and efficient delivery in Agile environments.