HKSM

A session held to create a shared calendar that coordinates how Scrum Teams will access and share environments (such as development, test, and staging) to prevent conflicts and downtime.

Key Points

• Sets a time-based plan for environment usage across multiple Scrum Teams.
• Typical attendees include Scrum Masters, Product Owners, DevOps/Environment managers, and affected team reps.
• Outputs include a published environment calendar, booking rules, priorities, and maintenance windows.
• Used before busy periods or releases to resolve conflicts, capacity limits, and data refresh needs.

Example

Three Scrum Teams all need the QA environment next week. In the Environment Planning Meeting they map a calendar: Team A books Monday-Tuesday, Team B Wednesday with a data refresh that night, and Team C Thursday-Friday after a planned patch window. The agreed schedule avoids overlap and clarifies ownership and support contacts.

PMP Example Question

Several Scrum Teams anticipate contention for a shared test environment next Sprint. Which meeting is designed to produce a coordinated usage calendar and rules for access?

1. Sprint Planning
2. Daily Scrum
3. Environment Planning Meeting
4. Sprint Review

Correct Answer: C — Environment Planning Meeting

Explanation: The Environment Planning Meeting creates the shared schedule and guidelines for how teams will use common environments, preventing conflicts and downtime.