Final answer:
The Development Team defines the final scope of a committed iteration, self-selecting the tasks from the product backlog they feel confident to complete within the iteration based on their capacity.
Step-by-step explanation:
The final scope of a committed iteration, in the context of Agile frameworks, such as Scrum, is defined by the Development Team. Once the Product Owner has established the priorities in the product backlog, the Development Team selects the tasks to be completed during the upcoming iteration based on their understanding of their capacity. This self-management aspect is crucial as it ensures that the team commits to only what they believe they can accomplish without undue pressure.
The scope is considered committed once the team has planned and agreed upon the work for that iteration. The Scrum Master helps facilitate this process and ensures that the Agile principles are upheld throughout. However, they do not define the iteration's scope. Similarly, the System Architect may influence the technical direction but does not determine the iteration commitment.