This document discusses ISO 16350, which provides guidance for application management throughout the lifecycle. It covers initial development, operation and use, and stages in between. The document outlines several key processes, including tactical/managerial processes that support the organization, application support connecting to ISO 20000, connecting operational run and change processes, and application maintenance and renewal focusing on continuous improvement. It emphasizes managing applications to add value for customers through strategies that anticipate future needs and capabilities.

1. ISO 16350
Application Management throughout the Life Cycle

2. INITIAL DEVELOPMENT AND THEN?
Stage of the lifecycle in scope
Initial
Develop-
ment
Stage of Operation
and Use

3. STAGE OF OPERATION AND USE
Initial
Develop-
ment
Stage of Operation and Use
Business
Information
Management
IT
Infrastructure
Management
Application
Management

4. PROCES OVERVIEW
Strategic level
Looking ahead, be pro-active
Tactical/Managerial level
Controlling en improving
Operational level
Day to day operations

6. TACTICAL/MANAGERIAL
This part is the centre of the model.
It supports the organization by its business.
Here all kind of things come together in a structured
way.
It’s about controlling aspects, improving, standards,
connecting with other organizations.

7. APPLICATION SUPPORT
This part is connecting with ISO 20000-series.
It offers a day to day support of the applications as an
intermediate to servicemanagement.
It’s not for helping with trouble, it’s about preventing
to getting into trouble.
This is about Operational Excellence, doing things
good at a reasonable price).

8. CONNECTING PROCESSES
This is about the interaction between the
operational run and the operational change in
the organisation.
This is about doing releasemanagement and
proper handling the changes, even when there
are several releases (functional and correcting for
instance) performed in parallel.
Here is prevention also a big part of the
processes. It’s about controlling environments
(Development, Test, Acceptance and Operations)
and software.

9. APPLICATION MAINTENANCE AND
RENEWAL
Note this is not ment to be as a waterfall.
These are processes, that can perfectly be used with
Waterfall, but also with Agile, DevOps, Scrum, et
cetera.
It is describing the outcomes, not how people should
do the work. That you can read in the manuals of the
software development standards.
It pays attention to the installed base and is not only
an vehicle to deliver a release.
This is about doing things better (Customer Intimacy,
Productleadership) and enhance value.

10. APPLICATION STRATEGY
This part is helpfull for anticipate the future of
the application(s).
What changes in IT, and can influence the
existing applications.
What about the needs of the clientorgani-zations
and their environment.
What about the functional and technical value of
the applications (preventing risks)
What about the money we can spend, what
brings the most value (adding value).

11. APPLICATION MANAGEMENT
ORGANIZATION STRATEGY
This part anticipates on the future of your
organization.
Which accounts and markets are interesting
(adding value and preventing from risk).
What capabilities and technologies are needed in
future (investing and add value).
On what way does the organization work together
with suppliers (in- and oursourcing).
On what way do we deliver our services (Customer
Intimate (effective), Operational Excellence
(efficiënt), productleadership (innovative)) (about
adding value)

12. APPLICABLE TO MANY SITUATIONS

13. Thanks for asking,
listening & watching