Environment(s)
The process of identifying and documenting every technical environment needed to build and test the project's deliverables.
Key Points
- Includes all non-production spaces such as development, integration, QA/test, staging, and performance test.
- Documentation covers configurations, versions, data needs, access rights, and setup procedures.
- Captures dependencies on tools, platforms, cloud resources, networks, and licenses.
- Early planning prevents delays, environment conflicts, and quality issues during iterations.
Example
A scrum team plans a mobile app project and lists the environments required: developer workstations, a shared integration server, an automated CI/CD pipeline, a QA test environment with emulators and real devices, and a staging environment for UAT. They document OS versions, SDKs, test data, user access, and provisioning steps, and secure cloud subscriptions before Sprint 1 starts.
PMP Example Question
During Sprint 0, the team wants to avoid delays caused by missing test platforms. What should the project team do?
- Create and maintain a documented list of all development and test environments required, including setup details.
- Expand the WBS to include more testing activities.
- Assign additional testers to increase throughput.
- Delay testing until after the first release to production.
Correct Answer: A — Document required development and test environments
Explanation: Identifying and documenting all needed environments early ensures the team can build and test deliverables without delay.
