Home > Free Essays > Business > Case Study > Microsoft’s Challenges in Office Product Development
Cite this

Microsoft’s Challenges in Office Product Development Report


Introduction

Microsoft is one of the most successful companies in the world today. It is among the few companies that have reported profits year after year since their foundation [1]. However, the company faced many challenges in designing and developing its flagship products Office 4.0, Office 95, Office 97, and Office 2000 [1]. Microsoft had to address these challenges to guarantee better products according to the customers’ tastes and preferences. The subsequent products had to be on schedule unlike the first products [1].

Analysis

The major challenge Microsoft faced when working on office 4.0 was the failure to keep schedules. The developers worked to attain certain features and functions of the software without considering the time factor and schedule [1]. In addition, the different teams had various goals. This complicated the entire company vision. It is theoretically and practically impossible for a company with diverging visions within to achieve its corporate vision [1].

In the case of office 95, the teams working on the application disagreed frequently slowing the development process [1]. Microsoft came head-on with a potential competitor as well. In 1992, Lotus Corporation introduced the Smart Suite that was a plausible threat to Microsoft office applications [1]. In addition, windows shifted its bit architecture to 32-bit from 16-bit bringing up a possible compatibility challenge to development teams. Microsoft office 97 faced the same predicament in addition to the relatively larger size [1]. The office 97 application was 30 megabytes larger than its predecessor, office 95 was [1]. The application took a lot of hard drive space. For Office 2000, the major challenge Microsoft had to bypass was the internet [1]. Microsoft felt that the internet was a threat to its products.

Customers Satisfaction

Microsoft had to address the above challenges to keep the customers satisfied [1]. The company worked on several strategies. For office 4.0, Microsoft upgraded customers’ old application versions free of charge when new versions were launched [1]. Microsoft emphasized keeping the set schedules for application development and launch [1]. To achieve this, Microsoft developers decided to re-architecture previous versions of the applications. In this case, the developers just added new features and functions to the previous programs [1].

In addition, Microsoft did surveys to understand the customers’ tastes and preferences. This assisted the company to make drastic changes during office 97 development [1]. The design and development of all applications were done in one place. In addition, Microsoft introduced well-defined common goals, applicable to all design and development teams [1]. Microsoft also changed the design and development process to meet specific schedules for the design, development, and launch of the applications.

Quality Development

Microsoft introduced the milestone concept to develop quality applications on schedule [1]. Developers were to write codes and compare them with the master code every day. The developers did simple tests on the codes to confirm each part was okay [1]. It was now possible for the developers to work within the stipulated deadline [1]. The disadvantage of the milestone concept is that it was possible to waste because of the many checks.

Office 2000

The milestone concept was a good idea for Microsoft to manage the design and development of office 2000 [1]. This guaranteed better design and development of the application. However, it seems that all the preparation in design and development was faulty. The office 2000 failed to meet the client expectations and the set schedule [1]. It is therefore certain office 2000 failed. If the milestone strategy was well planned and rolled out, office 2000 would be more successful.

References

[1] Harvard Business School, Microsoft Office 2000, Harvard University, Cambridge, Massachusetts, June 20, 2000.

This report on Microsoft’s Challenges in Office Product Development was written and submitted by your fellow student. You are free to use it for research and reference purposes in order to write your own paper; however, you must cite it accordingly.

Need a custom Report sample written from scratch by
professional specifically for you?

Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar
Writer online avatar

301 certified writers online

GET WRITING HELP
Cite This paper

Select a referencing style:

Reference

IvyPanda. (2020, October 10). Microsoft's Challenges in Office Product Development. Retrieved from https://ivypanda.com/essays/microsofts-challenges-in-office-product-development/

Work Cited

"Microsoft's Challenges in Office Product Development." IvyPanda, 10 Oct. 2020, ivypanda.com/essays/microsofts-challenges-in-office-product-development/.

1. IvyPanda. "Microsoft's Challenges in Office Product Development." October 10, 2020. https://ivypanda.com/essays/microsofts-challenges-in-office-product-development/.


Bibliography


IvyPanda. "Microsoft's Challenges in Office Product Development." October 10, 2020. https://ivypanda.com/essays/microsofts-challenges-in-office-product-development/.

References

IvyPanda. 2020. "Microsoft's Challenges in Office Product Development." October 10, 2020. https://ivypanda.com/essays/microsofts-challenges-in-office-product-development/.

References

IvyPanda. (2020) 'Microsoft's Challenges in Office Product Development'. 10 October.

More related papers