4.5.12 Glossary (Product Owner - Requirements Management Plan)

Covering key agile roles, project initiation documents, team environment, and planning artifacts.

• Product Owner (PO): Agile role managing product backlog for value. Practical Context: Represents the business/customer to the development team, prioritizes work.
• Project Charter: Document formally authorizing the project and outlining high-level objectives. Practical Context: Formally initiates the project.
• Project Management Plan (PMP): Comprehensive document integrating subsidiary plans (common in predictive/hybrid). Practical Context: The master plan detailing how the project will be executed, monitored, and controlled.
• Psychological Safety: Environment where team feels safe to speak up/take risks. Practical Context: Foundational element for high-performing, collaborative teams.
• Pull System: Work is pulled into next stage only when capacity exists (Kanban). Practical Context: Prevents overburdening and improves flow.
• Relative Sizing: Estimating size based on comparison to other items. Practical Context: Faster and often more reliable than absolute estimation for agile teams.
• Release Plan: Plan outlining the work and goals for a specific release. Practical Context: High-level plan for delivering a set of features.
• Requirements Management Plan: Defines how requirements will be managed. Practical Context: Outlines processes for elicitation, analysis, documentation, validation.