OpenText and Six Sigma

2282 Words5 Pages

Introduction

OpenText is a software product company that specialise in enterprise content management solutions. The company is involved in several implementation and consultancy projects across the globe to provide business specific solutions and technology to manage and utilise content.

Over the past 4 years, there has been an exponential growth within OpenText as an organisation through acquisitions. OpenText has been acquiring at a rate of 3 companies every year and this has resulted in several unique challenges within the organisation in the form of different cultures, products, processes and resources. Such diversities bring in ineluctable requirements to consolidate and integrated such differences as a single working unit to make sure corporate strategies are accomplished. This unique challenge has resulted in several internal projects within the core departments, like Research & Development, Human Resources, Operations Management and Customer Support, to come up with business processes that will allow identifying and accessing existing processes and validate any changes and improvements needed to facilitate easy integration with current and future acquisitions. This was vital for the business considering the stake involved for every business unit to have uniformity within the organisation so as to reflect a commonality and company direction for the stake holders and end-users.

I am currently involved in a project to carry out process improvements within Customer Support organisation. Customer support is a high visible business unit for customers and is usually the first point of contact. So the project involves implementing business management strategy like Six Sigma to find and improve areas in customer request, escalat...

... middle of paper ...

...MAIC project methodology.

Since the teams involved in this project works very closely, a strict after-the-fact integration step will not be required. If we can make sure the teams communicate effectively then the integration needs can be reduced when producing project integration plans. I will suggest trying “Mock Objects” as a hybrid to existing Gantt charts, since there are several intangible and can change behaviour as project progresses. Mock Objects will reduce the heavy handed dependencies of Gantt-charts for every object to be4 completed. Introducing these steps will risk increasing the amount of work involved and also run the risk of parallel tasks being performed at the same time, but this will help in reducing the overall cost and time.

The project is currently under planning phase and is scheduled to kick off in the 3rd quarter of this financial year.

Open Document