The Daily Standup

In the Daily Standup led by the Scrum Master, every team member briefly reports three items: what they completed since the previous meeting, what they intend to do before the next one, and any blockers they face. The event is strictly time-boxed; when work is not finished within a time-box, it is carried forward to a later time-box. Time-boxing adds discipline and predictability to Scrum initiatives that are uncertain and change frequently.

Key Points

  • What have I done since the last meeting?
  • What do I plan to do before the next meeting?
  • What impediments or obstacles (if any) am I currently facing?
  • Events and work are time-boxed; unfinished work at the end of a time-box moves to a subsequent time-box, providing structure for dynamic Scrum projects.

Example

At a 15-minute Daily Standup, a developer says: Since yesterday I completed the API tests; before tomorrow I plan to integrate authentication; I am blocked by missing test data. The Scrum Master notes the impediment and schedules a follow-up after the standup. A task that remains unfinished at the end of the sprint time-box is moved forward and re-planned in the next sprint.

PMP Example Question

What is the primary reason the Daily Standup is time-boxed while each team member answers the three standard questions?

  1. To keep the event short and focused on coordination, pushing detailed problem-solving to follow-ups.
  2. To ensure all tasks are completed within 24 hours of being started.
  3. To give the Product Owner time to reprioritize the entire backlog during the meeting.
  4. To capture detailed technical designs for upcoming work.

Correct Answer: A — Keep the standup brief and focused on coordination

Explanation: Time-boxing enforces a short, predictable meeting focused on sharing progress, plans, and impediments; deeper discussions happen outside the standup.

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