HKSM
Company Policies
The organization's adopted rules, standards, and guidance that steer behavior and decisions. Because user stories are written to align with current policies, any policy change can force updates to existing stories, acceptance criteria, and related delivery practices.
Key Points
- Policies are organization-wide rules, principles, and guidelines that teams must follow.
- They directly shape user stories, acceptance criteria, and the Definition of Done/Ready.
- Policy changes require impact analysis, backlog updates, and possible reprioritization.
- Clear communication and traceability to tests help ensure compliance and reduce risk.
Example
A company updates its data retention policy from 90 to 30 days. The team reviews in refinement, adds or updates user stories and acceptance criteria to reflect 30-day retention, adjusts the Definition of Done, and coordinates with the product owner to reprioritize affected items in the backlog.
PMP Example Question
Mid-sprint, corporate updates its privacy policy. What should the agile team do first?
- Assess the policy change, update the backlog and acceptance criteria with the product owner, and adjust plans as needed.
- Add the new policy work to the current sprint immediately without discussion.
- Ignore the change until the next release to avoid disrupting velocity.
- Escalate to the sponsor and wait for formal change control before acting.
Correct Answer: A — Evaluate the policy change and update backlog and criteria
Explanation: Company policy changes are organizational constraints. The team should first perform impact analysis and update user stories and acceptance criteria through backlog refinement with the product owner, then replan as needed.
