HKSM
Environment Meeting
A meeting held to determine the kinds and quantities of environments needed to develop, manage, and test the project's deliverables, and to agree on the people, tools, infrastructure, and other resources required to set them up.
Key Points
- Clarifies which environments are needed (e.g., development, QA/test, UAT, staging, production, training, demo).
- Decides environment counts, sizing, access controls, configurations, and data needs.
- Identifies required resources such as cloud/on-prem capacity, licenses, tooling, staffing, and budget.
- Reduces risks like environment contention, schedule delays, and compliance issues by planning early.
Example
During initiation of a new software product, the project team holds an environment meeting to decide on separate development, QA, UAT, performance test, and staging environments. They document required VM sizes, service accounts, test data, monitoring tools, and estimate costs for cloud instances and licenses. Ownership and setup timelines are assigned to the DevOps and security teams.
PMP Example Question
Which meeting focuses on identifying the types and number of environments needed for development, management, and testing, and on determining the resources to provision them?
- Release planning meeting
- Environment meeting
- Daily standup
- Architecture review
Correct Answer: B — Environment meeting
Explanation: An environment meeting defines which environments are required and what resources are needed to establish them. The other options do not primarily address environment provisioning.
