Pre-production environments are part of every software application delivery lifecycle and are critical path to your delivery pipeline. As all code must flow through these environments, they can represent a choke path for all application delivery and a breeding ground for issues that waste time, reduce quality, and allow defects to escape into production.

1. James Gregory
Solutions Architect
Plutora
Jeff Keyes
Director of Product
Marketing, Plutora

2. Agenda
• What is Environment Management?
• Doesn’t DevOps Already Handle This?
• Top 5 Pitfalls
• Plutora Spotlight
• Q&A

3. PAGE 3
What is
Environment
Management?
SIT Performance UAT Staging
Manual Request Processes
Test Data / Service Virtualization
Applications & Builds
Configuration & Componentry
Infrastructure / Cloud Instance
Monitoring
On-Premises Cloud

4. PAGE 4
Direct impacts to quality, efficiency,
delivery
None of the time invested in
managing environments is building
or testing the application
Areas of
Concern
Scheduling & Arbitration
Managing environment requests
Handling conflicts and/or project coexistence
Ensuring capacity & availability
Configuration & Provisioning
Incorporate vendor, operations, and Dev/QA teams required for each environment
Making provisioning reliable and reduce time
Keeping track of configurations and applications deployed
Management & Efficiency
Planning for maintenance
Improving utilization and efficiency
Managing chargebacks
Communication & Coordination
Coordinating outages and dependencies
Managing booking, approvals, and notifications workflows
Providing management reporting

5. PAGE 5
Tightly coupled legacy
architectures
Enterprise
Environments
Are Complex

6. PAGE 6
Environment
Management
& DevOps?

7. PAGE 7
What is left to
be solved
Partial Test Automation
Pockets within an organization
Partial Cloud Adoption
Pockets of differing Cloud technologies
Partial Deployment Automation
Differing deployment tools
Dev Tool Sprawl
Organic rather than directed growth of dev tooling
Communication Gaps
DevOps resources are technical, but don’t necessarily
have good stakeholder management skills
Lack of a clear DevOps strategy
1
2
3
4
5
6

8. Pitfalls

9. PAGE 9
I don’t have visibility of
environment bookings
and am unable to
manage my contention.
#1
?
?

10. PAGE 10
I don’t know what non-
Production environments
exist today and what
they contain in terms of
applications and
infrastructure.
#2

11. PAGE 11
My non-Production
environments aren’t in
sync and I’m invalidating
my testing.
#3

12. PAGE 12
I don’t understand how the
applications in my non-
Production environments
hang together, and everyone
is looking to me to come up
with the answers.
#4

13. PAGE 13
I don’t what size team I’ll
need to support the new
environment
management team?
#5

14. PAGE 14
Plutora Test Environment Management

15. Plutora is the TEM Market Leader
Enterprise Management Associates (EMA) asked top North American enterprises what TEM product
they used. Plutora dominated the results.

16. PAGE 16
Outcomes
Plutora Management Creates Efficiency
Environments reliable and
resilient
Environments available
Implicit coordination &
notifications
Increase team efficiency.
1
2
3
Benefits
Complete visibility4
Establish fit for purpose configurations exactly when
needed.
Predict and remediate contentions.
Ensure accurate and comprehensive test coverage.
Create a culture of relentless improvement.
Comprehend dependencies between projects,
systems, schedules and teams.

17. PAGE 17
Visual representation of environment
schedule assignments.
View as
- Release
- Conflicts
- Environment Groups
Environment
Schedules

18. PAGE 18
Maintain configuration details
manually or populated from the
CMDB. Stakeholders define
Responsible, Accountable, Consulted,
and Informed members (RACI).
Environment
Details

19. PAGE 19
Visually identify conflicts and
schedule associations. Color coding
represents approval status.
Impact Matrix

20. PAGE 20
Environment
Group Mapping
Associate environments based upon
type of connections.

21. PAGE 21
• TECR – Change Request
• TEBR – Booking Request
Manage requests in a similar fashion
to managing support tickets.
Request
Management

22. James Gregory
Solutions Architect
Plutora
Jeff Keyes
Director of Product
Marketing, Plutora
Q&A
?