How to Get a Job For Project Managers

Learn how to write resume and interview

Leadership for Project Managers

Learn how to lead and drive project success.

Project Management with AI

From a beginner to project management professional.

Agile Project Management and SCRUM with AI

Learn to run Scrum and Agile with AI.

Potentially Shippable Deliverables from Projects

Project teams produce increments that could be released, and these artifacts are used to align work at the program and portfolio levels. Each Sprint ends with a finished product increment or deliverable. The user stories in that increment meet the team's Definition of Done as well as their specific acceptance criteria.

Key Points

  • Serve as inputs for coordination and decision making across programs and portfolios.
  • Completed at the end of each Sprint as a usable product increment or deliverable.
  • Considered potentially releasable only when both the Definition of Done and acceptance criteria are satisfied.
  • Enable integration, demos, feedback, and release planning across multiple projects.

Example

A program manages three agile teams building a healthcare portal. After a Sprint, Team A delivers a secure login feature that passes all tests, meets the Definition of Done, and satisfies its acceptance criteria. The program manager uses this increment to plan the next integration, coordinate dependencies with Teams B and C, and update portfolio release timelines.

PMP Example Question

Which statement best describes potentially shippable deliverables from projects in an agile environment?

  1. Draft features used only for internal testing between Sprints.
  2. Completed increments at the end of a Sprint that meet the Definition of Done and acceptance criteria and support program/portfolio coordination.
  3. Any backlog items committed during Sprint Planning, regardless of completion status.
  4. Only items that have been released to end users during a production deployment.

Correct Answer: B — Completed increments meeting DoD and acceptance criteria used for higher-level coordination

Explanation: Potentially shippable deliverables are finished, test-passed increments produced at Sprint end that satisfy the Definition of Done and acceptance criteria and are used to align work at program and portfolio levels.

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

Build an ICS/OT cybersecurity foundation that fits the real environment

Standard IT controls can disrupt the industrial systems they are meant to protect. Learn how to assess OT risk, design zones and conduits, apply IEC 62443 security levels, use MITRE ATT&CK for ICS, and establish passive asset visibility without risking production. Eight reconstructed incidents connect attacker techniques to the controls that failed, giving you the vocabulary and judgment to make credible security decisions from day one.

Explore the Course