Include Bruno's comments into the definition

[ijmitch]

Taking @b_around's comments...

          Sharing some ideas that I think should be in our definition of modernization which probably should be split into two parts – what we understand as modernization and how we will address modernization

OUR PERCEPTION OF MODERNIZATION CONTEXT
• Modernization is about enabling continuous evolution of business operations (products, services, process) in line with a 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)
• Mainframe platforms 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

OUR WE WILL ADDRESS MODERNIZATION DEFINITION AND OUR BOUNDARIES
• The OMP Working Group aims to provide a clear articulation of options, principles and patterns for mainframe platforms modernization in the form of a framework that guides the modernization of technology components and organizational practices around mainframes
• The framework considers business needs, business value & ROI, execution risks & trade-offs, technology options & organizational impact
• The framework is not tied to specific mainframe platforms, vendor technologies, 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

Originally posted by @b-around in #6 (comment)

[b-around]

Pull request created - think we can close this issue and manage any iterations of the definition directly on pull requests

[Nihit25]

Hello @ijmitch , should I update the modernization-definition.md file with the following content:

Modernization is about achieving continuous evolution of the business (products, services, process) in line with the company mission and customer needs. This journey is enabled by technology changes (apps, data, platforms, infrastructure, Dev & Ops tooling) and people and culture changes (organizational structure changes, culture, ways of working, alignment of priorities).
Because of the way business, technology and people are interconnected, modernization does need to holistically look at these all perspectives to truly achieve its goals and deliver business value.

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. A common pitfall this leads to is a biased view that the only option for modernizing capabilities that depend on mainframes, is the replacement of such platforms.
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.
This 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, the proposed framework, parameters and considerations should always be adjusted to a company reality.