serena mainframe virtual user group jan 2014

Mainframe Virtual Users Group – January 2014

SERENA SOFTWARE INC.

News and Announcements

SERENA SOFTWARE INC. 2

GET READY: We’ll be CELEBRATING 50 Years of Mainframe Innovation!

Come visit us at booth #518

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

SERENA SOFTWARE INC. 3

How ERO saves you resources and money!

Benny Westaedt

»  

»  

•  No idea what ERO is? •  CEO or CFO? •  Budget Crunch? •  More requests than you have resources to give? •  Streamlining development operations? •  Higher quality requirements?

Why are you here?

1/23/14   5  

»  Agenda

•  Why are you here? •  ERO? •  The Business Case •  Strategy, People & Instruments •  How does it work? •  Business Value! •  Why Westaedt?

1/23/14   6  

»  ERO?

1/23/14   7  

Enterprise Release Option

Size  ma0ers  (Enterprise)     Not  for  everyone  (Op?on)    

You  want  to  work  in  a  structured  way  (Release)  

»  What happens without ERO?

1/23/14   8  

Project Death Star

Where did it go wrong?

»  First Release = Success

•  Flagship of the Galactic Empire •  Moon-Sized imperial military battlestation •  Planet-destroying superlaser •  Thousands of stationed troops

1/23/14   9  

»  

Those involved in “Project Death-Star” thought going to production with: •  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. . . . .

However …

1/23/14   10  

»  … They were wrong!

1/23/14   11  

»  

Not only was there a total loss of Hardware, Software and Resources. . . .

The Result?

1/23/14   12  

»  

. . . . There was also some staff reduction.

1/23/14   13  

»  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  

»  Project DS 2.0 Release Review These rebels are mad! They don’t have a chance of winning this time..

Yes sir.

Wait!. . .The issues with the central reactor core were resolved, right?

. . . . . Erm

It is too late to correct it now, Captain. . . I mean what are the odds it could happen again?

1/23/14   15  

»  Oops !!!

1/23/14   16  

»  Did you ever had to:

•  Fix a release bug •  Remove a package from a release •  Removing components from a

release

1/23/14   17  

Risk Management

•  Testing •  Dependency mngt

–  Copybooks –  Load relationships –  Overlays

•  Parallel development

•  Audit – out of sync recompile

•  Check points •  Build process automation

(concatenation) •  Development path

1/23/14   18  

»   We should have practiced ERO! . . . . .

•  Release mngt •  Change mngt •  Incident mngt •  Problem mngt •  Impact analysis •  Risk analysis •  Test mngt •  Dependency mngt

Where did the Empire go wrong? . . . . . . . TWICE!

1/23/14   19  

»  Respecting Human (& Alien) Resources

•  Customers •  End Users •  Testers •  Developers •  Release Manager

1/23/14   20  

»  Use the right Instruments & Equipment

•  Applications •  Databases •  Test Environments •  Network •  Disk Space •  CPU Power 1/23/14   21  

»  The Reward

•  Time •  Money •  Quality

The right balance and harmony between:

1/23/14   22  

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?

–  Our setup and the resources

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!

1/23/14   23  

»  

»  ERO Tuning Tools

•  Release Management •  Change Management •  Coding checks •  Compilers •  Linkers •  DB checks •  Automated testing •  Impact analysis

1/23/14   24  

»  Changeman ZMF

•  Packages •  Super packages •  Promotion levels •  Application releases •  Company releases •  Environment management •  Development and Production

management

1/23/14   25  

»  

»  ERO Terminology

•  Release (1 point in time) •  Release dependencies •  Release areas

– Start – Subsystem – Final

•  Release application •  Release package

1/23/14   26  

»  Area Management

1/23/14   27  

»  Package & Application

1/23/14   28  

»  ERO & Enterprise Architecture

•  Target: Business – IT alignment

•  Knowing the impact upfront

•  Managing Release platforms

1/23/14   29  

»  The ERO business value

•  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

1/23/14   30  

»  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  

»  Are you prepared for a stellar performance?

1/23/14   32  

»  

                                             Creative Commons is a non-profit that offers an alternative to full copyright. creativecommons.org  

PHOTO CREDITS

xblackrockx.com

Benny Westaedt CEO & Enterprise Architect e-mail benny.westaedt@westaedt.be Website www.westaedt.be

1/23/14   33  

»  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  

SERENA SOFTWARE INC. 35

Conclusion

Must ask

about …

Kevin Parker Vice President and Product Officer

kparker@serena.com Serena Software Inc. 1850 Gateway Drive, 4th Floor

San Mateo CA 94404 650.224.1691 M

serena.com

Next VUG April 16th 2014

Get milk

Attend VUG

Get newsletter

Get brochure