In the January Mainframe Virtual User Group (VUG) meeting, guest speaker, Benny Westaedt, CEO and Chief Architect of PSW solutions discussed “How ChangeMan ZMF’s ERO option saves you resources and money.” Benny stepped our audience through the Enterprise Release Option (ERO) of ChangeMan ZMF and made a very compelling case for how ERO does save time and resources in a manner that was accessible to all technical levels and easily understood by those with or without actual ERO experience.

1. Mainframe Virtual Users Group –
January 2014
SERENA SOFTWARE INC.

2. News and Announcements
GET READY: We’ll be CELEBRATING 50 Years of Mainframe Innovation!
Come visit us at booth #518
2
SERENA SOFTWARE INC.

3. News and Announcements
• New quarterly mainframe newsletter
• Serenade, Q1 2014
• Serena Release Manager V5
• GA December 2013
• ZMF and zLinux support
• ChangeMan ZMF 7.2 Beta Program
• Beta T1, Feb 1
• Subsequent drop every 2 months
• David Jackson
djackson@serena.com
3
SERENA SOFTWARE INC.

4. »
How ERO saves you resources and
money!
Benny Westaedt

5. »
Why are you here?
•
•
•
•
•
•
1/23/14
No idea what ERO is?
CEO or CFO?
Budget Crunch?
More requests than you have resources to give?
Streamlining development operations?
Higher quality requirements?
5

6. »
Agenda
•
•
•
•
•
•
•
Why are you here?
ERO?
The Business Case
Strategy, People & Instruments
How does it work?
Business Value!
Why Westaedt?
1/23/14
6

7. »
ERO?
Enterprise Release Option
Size
ma0ers
(Enterprise)
Not
for
everyone
(Op?on)
You
want
to
work
in
a
structured
way
(Release)
1/23/14
7

8. »
What happens without ERO?
Project Death Star
Where did it go wrong?
1/23/14
8

9. »
First Release = Success
•
•
•
•
1/23/14
Flagship of the Galactic Empire
Moon-Sized imperial military battlestation
Planet-destroying superlaser
Thousands of stationed troops
9

10. »
However …
Those involved in “Project Death-Star” thought going to production with:
1/23/14
• No Risk or Impact analysis,
• A minimum amount of testing
• And a thermal exhaust port from the central reactor core
Was not going to be an issue. . . . .
10

11. »
… They were wrong!
1/23/14
11

12. »
The Result?
Not only was there a total loss of Hardware, Software and
Resources. . . .
1/23/14
12

13. »
. . . . There was also some staff reduction.
1/23/14
13

14. »
Death Star 2.0 lessons learned
• Load balanced central reactor core
• No direct access to the central reactor core including
exhaust port
• Do NOT underestimate the competition
. . . right?
1/23/14
14

15. »
Project DS 2.0 Release Review
It is too.The issues with now,
These late to correct
Wait!. .rebels are mad! it the
Captain. . . I mean chance the
They don’t have a what are
central reactor core were of
odds it couldtime..
winning this happen again?
resolved, right?
. . . . Yes sir.
. Erm
1/23/14
15

16. »
Oops !!!
1/23/14
16

17. »
Did you ever had to:
• Fix a release bug
• Remove a package from a release
• Removing components from a
release
1/23/14
17

18. Risk Management
• Testing
• Dependency mngt
– Copybooks
– Load relationships
– Overlays
• Parallel development
1/23/14
• Audit – out of sync
recompile
• Check points
• Build process automation
(concatenation)
• Development path
18

19. »
Where did the
Empire go wrong?
. . . . . . . TWICE!
1/23/14
We should have practiced ERO!
.....
•
•
•
•
•
•
•
•
Release mngt
Change mngt
Incident mngt
Problem mngt
Impact analysis
Risk analysis
Test mngt
Dependency mngt
19

20. »
Respecting Human (& Alien) Resources
•
•
•
•
•
1/23/14
Customers
End Users
Testers
Developers
Release Manager
20

21. »
Use the right Instruments & Equipment
1/23/14
•
•
•
•
•
•
Applications
Databases
Test Environments
Network
Disk Space
CPU Power
21

22. »
The Reward
The right balance and harmony between:
• Time
• Money
• Quality
1/23/14
22

23. »
Strategy & Tactics
1. Define objectives/principles and get
commitment
–
–
Business
IT
2. Define Architecture vision
–
–
Scope, expectations
Business context
3. How will business be impacted?
–
Impact on business goals and dependencies
4. Which applications and information are
impacted?
–
1/23/14
5. Which technology do we need for this?
–
Instruments & Equipment
6. Opportunities and solutions
–
Quick Win, Changeman, ERO, SBM, …
7. Migration planning
–
Plan the transformation for the Instruments
and the Resources
8. Implementation
–
Put ERO to work every day
9. Optimize and Learn!
Our setup and the resources
23

24. »
ERO Tuning Tools
•
•
•
•
•
•
•
•
Release Management
Change Management
Coding checks
Compilers
Linkers
DB checks
Automated testing
Impact analysis
1/23/14
24

25. »
Changeman ZMF
•
•
•
•
•
•
•
Packages
Super packages
Promotion levels
Application releases
Company releases
Environment management
Development and Production
management
1/23/14
25

26. »
ERO Terminology
• Release (1 point in time)
• Release dependencies
• Release areas
– Start
– Subsystem
– Final
• Release application
• Release package
1/23/14
26

27. »
Area Management
1/23/14
27

28. »
Package & Application
1/23/14
28

29. »
ERO & Enterprise Architecture
• Target: Business –
IT alignment
• Knowing the impact
upfront
• Managing Release
platforms
1/23/14
29

30. »
The ERO business value
•
•
•
•
•
•
1/23/14
Streamline the development process
Managing complex releases
Quality gateways are in place
Predict the impact
Flexible environments at a minimal cost
A backup plan in case it goes wrong
30

31. »
Westaedt added value:
• Mapping and documenting the operational terrain
• Systematic identification of bottlenecks and weaknesses to
be handled and strengthened
• Identify “Quick Wins” with low risk and big ROI
• Free up time through automation of mundane manual
administration tasks
• Stress free audits
• Quick business pain relief
• Discovery of hidden revenue
• Work method optimization based upon the organizational
best practices
1/23/14
31

32. »
Are you prepared for a stellar performance?
1/23/14
32

33. PHOTO CREDITS
»
xblackrockx.com
Benny Westaedt
CEO & Enterprise Architect
e-mail
Website
benny.westaedt@westaedt.be
www.westaedt.be
Creative Commons is a non-profit that offers an alternative to full copyright.
creativecommons.org
1/23/14
33

34. »
Summary
•
•
•
•
Test and build environments cost precious resources: not planning for them costs even
more.
The right ERO implementation helps you balance your resources and makes sure you use
the right ones at the right time.
Disk space, CPU time, human resources, quality and risk can be managed by ERO.
The build management and impact analysis features, deliver crucial information about the
potential risk and quality impact.
1/23/14
34

35. Conclusion
Kevin
Vice P Parker
re
kpark sident an
d Pro
e r @s
d
erena
.com uct Office
r
Sere
n
1850 a Softwa
G
re
San M ateway Dr Inc.
ive, 4 th
ateo
C
650.2
Floor
24.16 A 94404
91 M
seren
a.com
k
ust as
M
out …
ab
Next VUG
April 16th 2014
Attend VUG
Get mi
lk
35
Get newsletter
Get brochure
SERENA SOFTWARE INC.