Norming stage

The Norming stage is the third phase of team development. During this time, the team grows more mature, settles internal disagreements, sets shared ways of working, and figures out how to collaborate effectively. It is a settling-in and adjustment period.

Key Points

  • Third stage after Forming and Storming, before Performing.
  • Roles, norms, and working agreements become clear; communication improves.
  • Conflict decreases while trust, cohesion, and psychological safety increase.
  • The project manager or Scrum Master facilitates lightly as the team self-organizes.

Example

After early friction over coding standards and estimation, an agile team agrees on a Definition of Done, establishes stand-up etiquette, and sets a code review rotation. Disputes are handled constructively, and the team delivers a stable sprint increment together.

PMP Example Question

Which situation best indicates a team is in the Norming stage?

  1. Team members avoid disagreement and depend on the manager for direction.
  2. Frequent personal conflicts and competition dominate team interactions.
  3. The team agrees on working agreements and resolves disagreements constructively.
  4. The team consistently delivers high performance with minimal oversight.

Correct Answer: C — The team aligns on norms and handles conflict productively.

Explanation: In Norming, teams establish shared processes and collaborate smoothly, unlike Forming (A), Storming (B), or Performing (D).

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