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?

  1. Assess the policy change, update the backlog and acceptance criteria with the product owner, and adjust plans as needed.
  2. Add the new policy work to the current sprint immediately without discussion.
  3. Ignore the change until the next release to avoid disrupting velocity.
  4. 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.

AI Systems with Claude, for Scrum Masters and Project Managers

Most AI pilots in project management do not fail on the model. They fail because somebody pointed the thing at a decision instead of at a task. This course is built around that distinction, and around the work that follows once you get it right.

Eight teaching sections, taught against one running project from the first lecture to the last. You watch a system get built, then you build the same one against your own sprint. Nothing here is a demo that works only on the example.

You finish with five working systems and you keep them. The sprint report machine turns your board export and standup notes into the report you currently write by hand. The retro intelligence system tells you what the team keeps saying, not just what it said this time. The stakeholder comms engine drafts the update in the register the audience expects. The backlog health monitor flags the quiet decay nobody has time to check for. The risk and dependency tracker follows the chains that actually bite.

Seventy-six working files ship with it, across four sections, so every system is built against real sprint data rather than material invented for a slide. Four sprints of retrospectives, board exports, standup notes, backlog and risk data.

Explore the Course


Launch your career!

HK School of Management and Technology offers training in project management, job-search strategies, and career growth. Practical skills, tools, and guidance you can apply right away. Covered by Udemy's 30-day refund policy.

Learn More