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.

Length of Sprint

The fixed timebox for each Sprint, chosen jointly by the Product Owner and the Scrum Team using inputs such as business requirements and the release plan. After it is set, that duration is typically kept the same for all Sprints in the project.

Key Points

  • Agreed by the Product Owner and Scrum Team, typically during or before release planning.
  • Selected using inputs like business priorities, release planning schedule, risk, and desired feedback frequency.
  • Once chosen, the Sprint duration remains stable; do not extend a Sprint to fit more scope.
  • Common durations are 1–4 weeks; shorter Sprints increase feedback and control, longer Sprints reduce overhead.

Example

During release planning, the Product Owner and Scrum Team pick a 2-week Sprint to align with business needs and the release plan. Throughout the project they keep every Sprint at 2 weeks. When a stakeholder later asks to extend Sprint 5 to 3 weeks to include more features, the team keeps the 2-week timebox and reprioritizes the backlog instead.

PMP Example Question

In a new Scrum project, how is the Sprint length established and maintained?

  1. The Scrum Master sets it and changes it each Sprint to optimize throughput.
  2. The Product Owner sets it alone during release planning and may extend Sprints when scope grows.
  3. The Product Owner and Scrum Team agree on the duration using inputs like business needs and the release plan; once chosen, it remains consistent across Sprints.
  4. The project sponsor mandates it, and the team varies it to match stakeholder availability.

Correct Answer: C — Product Owner and Scrum Team agree on a fixed Sprint duration

Explanation: Sprint length is a collaborative decision informed by business and release planning inputs, and it should stay constant to preserve cadence and predictability.

ICS/OT Incident Response Drills and Exercises

An incident response plan is only a theory until the people who must use it have run it under pressure. This course helps OT engineers, operations leaders, IT responders, and security teams turn a plan on paper into a tested capability.

Define safe states and manual fallback before an incident forces the decision. Build escalation paths, tabletop exercises, and scenarios that expose the gaps a document review cannot find.

Then turn the results into evidence: an after-action report, owned improvements, recovery checks, and a drill cadence that keeps the program alive after the exercise ends.

24 lessons, 2.4 hours. US$47 one-time through HKSM Courses. 30-day money-back guarantee when 50% or less consumed.

Explore the Course


ICS/OT Incident Response Drills and Exercises 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