RESEARCH ASSIGNMENT

IT Process Management

Group Members:
Ramon Mercader

Professor: Nihad Al-Juboori

December 13, 2018
 1

Table of Contents

INTRO .......................................................................................................................................................... 2
AGILE OVERVIEW/CONTEXT OF PROPOSAL ..................................................................................... 2
PROCESSES................................................................................................................................................. 2
Design Coordination ............................................................................................................................. 2
Change Management ............................................................................................................................ 3
RATIONALE ................................................................................................................................................ 3
Design Coordination ............................................................................................................................. 3
Change Management ............................................................................................................................ 3
RESOUCRES/ORG STRUCTURE.............................................................................................................. 4
MEASURES ................................................................................................................................................. 5
CONCLUSION ............................................................................................................................................. 6
BIBLIOGRAPHY ......................................................................................................................................... 7
 2

INTRO

As agile methodology rapidly increasing in today’s organization and the combination of ITIL v.3.

The system would greatly improve its performance and keep the stakeholder needs met. Although, not all

ITIL processes will be compatible, following agile methodology as a base, since ITIL leans toward

waterfall model while agile is more on loosely side meaning it has a lot of changes/iteration during its

development. Here, I will show two ITIL v.3 processes that I think would be the best practice.

AGILE OVERVIEW/CONTEXT OF PROPOSAL

Agile is a set of values and principles. Based on your teams beliefs, decision, and to choose which

methods works best for developing software. Making sure it can deliver its objective and purpose. And be

able to self-organize in a fast paced environment and get ready to multiple iterations, while maintaining

good coordination with your teams. Therefore allowing for high value and quality made project.

PROCESSES

Design Coordination

Design Coordination is one of the best practice to improve one’s organization agile development.

It is responsible to coordinate and control the activities and its processes within its scope. It also needs to

balance comprehensive design and prioritization. To ensure all system design runs consistently and

smoothly throughout the process, and meeting business requirements.

 3

Change Management

Another processes that I would like to recommend is Change Management. Change Management,

surely work effectively with agile. As agile has a lot of changes/iteration, this is the perfect combination

which allow change management to log and monitor the activity and prevent incidents, disruption, and re-

work. It also, respond to stakeholder requirement changes. This will accelerate implementation time.

RATIONALE

Design Coordination

Design coordination is a must have, when receiving service charter. It keeps the processes group

together closely to create a single, holistic solution. Making sure each process is aligned to the services,

resources, and customer expectations. This prevents miss communication throughout the processes and

thus reducing the amount of troubles. Less troubles means, increase in productivity project/software

development and reduce cost. Furthermore, design coordination duty is to ensure designers knows their

role or responsibility. It also have access to see business requirements collection, analysis, documentation

and use these information to coordinate the processes. In general, it simply organize the processes

together and make it run efficiently.

Change Management

Change management main role is to prioritize changes that would cause the most benefit.

Stakeholder requirements and developers work items estimation needs to be weighted examined by

change management and prioritize it. Ensuring the workload is balanced through each iteration. Making

the work flow more optimize and better efficiency. Doing so, enables for stakeholder to receive better
 4

ROI. Secondly, change management has the ability to freeze requirements during an iteration. To manage

the stability of the developers during that iteration and introduce it to another iteration. And this not an

easy decision and need to be chosen wisely. Since change management documents all the changes, it can

use its past documentation on which steps should be tackled best. Lastly, it also coordinate all changes

into one process, and to prevent conflicting changes. Change management implementation is a must for

the stability of the project.

RESOUCRES/ORG STRUCTURE

Figure 1: MegaCorp
 5

MEASURES

There are many types of measures, such as customer surveys, management reports and face-to-

face interviews. And this is soft metrics. This is usually handled by HR. For now I will be focusing on

soft metrics, management report. Management report is a good tool to collect business data and convert it

to a meaningful information, so business can make more accurate, data driven decision. It collects data in

each department. In those departments, they track key performance indicators. When collected it should

answer some of CEO questions, such as: “Should I hire more employees?”, “Do I have enough cash to

make payroll for my employees?”, “Where should I spend my marketing dollars?”. This measure should

give you an idea by just looking at the trends provided by management reports and make a good decision

out of it. Here a sample of Management Report shown down below (Figure 2).

Figure2: Management Report

 6

CONCLUSION

In conclusion, having an agile methodology and with a correctly selected ITIL v.3 processes to

integrate to the system. It can significantly increase so called agile and gives you an edge to modern

technology. Having a more agile system provides better responsiveness and dynamic to stakeholders.

Increase efficiency in developing software due to less troubles. And lastly, increases the value of an

organization. So having the best practices in ITIL v.3 plus agile methodology creates an ultimate

advantage.
 7

BIBLIOGRAPHY

Manifesto for Agile Software Development. (n.d.). Retrieved December 13, 2018, from

https://agilemanifesto.org/

Designing Buildings Wiki Share your construction industry knowledge www.designingbuildings.co.uk.

(n.d.). Retrieved December 13, 2018, from

https://www.designingbuildings.co.uk/wiki/Design_coordination

Agile Requirements Change Management. (n.d.). Retrieved December 13, 2018, from

http://agilemodeling.com/essays/changeManagement.htm

Hanks, G. (2017, November 21). The Difference Between Hard and Soft Human Resource Metrics.

Retrieved December 14, 2018, from https://smallbusiness.chron.com/difference-between-hard-soft-

human-resource-metrics-73984.html

CS Status Reporting. (n.d.). Retrieved December 13, 2018, from https://www.campana-

schott.com/de/en/expertise/technologie/cs-produkte-apps/cs-status-reporting/