generated from openmainframeproject/wg-template
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update modernization-definition.md #11
Open
b-around
wants to merge
3
commits into
openmainframeproject:add-definition-proposal
Choose a base branch
from
b-around:patch-1
base: add-definition-proposal
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,21 +1,12 @@ | ||
# Defining Mainframe Modernization | ||
# Defining Modernization | ||
• Modernization is about achieving continuous evolution of the business (products, services, process) in line with the company mission and customer needs | ||
• Modernization is enabled by technology changes (apps, data, platforms, infrastructure, Dev & Ops tooling) and organizational changes (structure, culture, ways of working, alignment of priorities) | ||
• Because of the way business, technology and organization are interconnected, modernization does need to holistically look at these all perspectives to truly achieve its goals and deliver business value | ||
|
||
Businesses are digitally transforming to better serve their customers, | ||
reduce time to market, and increase their ability to respond quickly to | ||
market changes, consumer behavior, and new regulations. As businesses | ||
transform, they are imposing significant demands on existing mainframe | ||
applications and data, driving the need for modernization to better | ||
achieve business outcomes. | ||
|
||
It's often not a question of if you need to modernize mainframe | ||
applications, only a question of how. The OMP Working Group embraces a | ||
hybrid cloud approach to mainframe modernization with the goal of | ||
helping business improve business agility, optimize costs, achieve | ||
non-functional requirements, while leveraging existing investments. We | ||
will provide a framework for modernization that spans applications, | ||
data, operations, interoperability, and security. We encourage looking | ||
at the business needs first, then take an ROI driven approach to help | ||
assess costs, business risks, and tradeoffs. There is rarely a "one-size | ||
fits all" approach to anything in the IT industry. By providing a | ||
framework we intend to feature the range of options available to help | ||
you to achieve your mainframe modernization objectives. | ||
• Mainframes typically support business critical operations and due to its historical criticality and longevity, not always have been through holistic or consistent approaches to modernization | ||
• The above sometimes leads to an incorrect view that the only option for modernizing areas that depend on mainframe is the replacement of the platform | ||
• The OMP Working Group aims to provide a clear articulation of options, principles and patterns for modernization in the mainframe context, delivering a framework that guides the modernization of technology components and organizational practices | ||
• The framework considers business needs, business value & ROI, execution risks & trade-offs, technology options & organizational impact | ||
• The framework is not tied to specific mainframe technologies, vendors, tools, or target states and rather focus on the approach, execution process and required capabilities | ||
• Because organizational context matters and "one-size fits all" approaches don’t exist, thus the framework, parameters and considerations should always be adjusted to a company reality |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"organizational BEST practices"