Backlog

A prioritized and continually updated list of product work items (features, fixes, enhancements, research, and technical work) that represents the single source of potential future work. Items at the top are most valuable and better refined, enabling the team to pull them into near-term plans.

Key Points

  • Owned and ordered by the product owner; transparent to the team and stakeholders.
  • Includes functional, nonfunctional, and technical items; each should have clear acceptance criteria when ready.
  • Continuously refined: split large items, clarify details, and adjust priority based on value, risk, and feedback.
  • Guides planning by providing ready, high-priority items, but is not a fixed commitment until work is selected.

Example

A product team building a mobile banking app maintains a backlog with items like "Enable biometric login," "Improve funds transfer speed," and "Address security vulnerability XYZ." The product owner orders these by value and risk. Before the next sprint, the team refines the top items and then pulls the most valuable, ready items into the sprint plan.

PMP Example Question

Which statement best describes the backlog in an agile product development effort?

  1. A fixed list of requirements approved in the project charter.
  2. An ordered, evolving queue of product work items maintained by the product owner.
  3. A daily task list created by the Scrum Master for the team.
  4. The set of tasks each developer plans to complete today.

Correct Answer: B — An ordered, evolving queue of product work items maintained by the product owner

Explanation: The backlog is a dynamic, prioritized list that guides what the team might build next; it is owned and ordered by the product owner, not fixed or managed as daily tasks.

ICS/OT Cybersecurity Fundamentals — Security Built for Industrial Systems

Industrial control systems cannot be secured like ordinary IT. A forced reboot, aggressive scan, or incompatible patch can interrupt production and create real safety consequences. Effective OT security begins with understanding the systems, constraints, and risks unique to industrial environments.

This course gives IT professionals, engineers, operators, and security practitioners a practical foundation in ICS threats, zone and conduit design, risk assessment, passive asset visibility, and vendor evaluation. You will learn how IEC 62443, NIST CSF, and MITRE ATT&CK for ICS apply where availability and safety come first.

Eight reconstructed incidents—including Stuxnet, Triton, Ukraine 2015, Colonial Pipeline, and PIPEDREAM—show how attackers move through OT environments, what they target, and which defenses could have changed the outcome.

Watch the course preview, then build the vocabulary, frameworks, and judgment needed to take credible first steps in ICS/OT cybersecurity.

Explore the Course


ICS/OT Cybersecurity Fundamentals course preview

Run the drill before the incident runs you

Design, run and prove OT drills and tabletop exercises before an incident tests your team. OT Incident Drills and Exercises includes 24 lessons and practical exercise materials, delivered through HKSM Courses for US$47 one-time. 30-day money-back guarantee when 50% or less of the course has been consumed.

Explore the Course