Microsoft Office: From Office 4.0 to Office 2000

Major Challenges

The development process of creating different Microsoft Office versions faced varied challenges. The first three versions, including Office 4.0, Office 95, and Office 97 encountered internal challenges while Office 2000 faced external challenges. Office 2000 had an extensive struggle with the emergence of the internet. During the production of Office 4.0, the Microsoft Corporation allowed people to operate freely in an informal capacity for effective results. However, the business approach led to delays and untimely delivery of the necessary materials from different groups. The Excel team and PowerPoint department did not deliver their work on time, forcing the company to release Office 4.0 with old Excel and PowerPoint versions. The creation of office 95 had its share of trouble as well. The word team and the Excel team were in constant conflict with this production. As a result, the company released the Office 95 version comprising two different menu organizations and two different visuals. Customers criticized the production, forcing the company to upgrade the program to office 97. During this period, the company faced significant competition from SmartSuite, but the release of Office 97 neutralized the effects. The main challenge in the production of office 97 was a conflict between the application teams and the office production unit. Lastly, the main challenge in the production of office 2000 was the internet emergence and competition from upcoming companies like SmartSuite.

Strategies to Address the Challenges

After the office 4.0 delays, the company introduced certain protocols that every department within the production team had to follow. The approach was to ensure that every office version was released with the right package to suit consumer needs. The company developed Office product units (OPU), a new unit within the application division to oversee the process of production. The strategy improved coordination between different teams, which in turn enhanced the efficiency of the entire production process. During the production of office 2000, the company introduced a new way of operation where teams worked in bits. The testing team determined if a product was ready to move to the next phase based on the condition of the current phase. The strategy was quite effective in the production of Microsoft Office 2000.

Pros and Cons of Checking Codes with the Main Server

Checking codes to the main server ensures that all units within the production team work towards the same goal. Additionally, the process reduces the chances of delays that affect the production process negatively. On the other hand, checking codes to the main server is a slow process, and it prolongs the production process. In the case of Microsoft Corporation, the strategy of checking codes with the main server contributed to the success of the organization. Most of the challenges facing the company resulted from delays and different opinions among the groups. The idea of checking codes with the main server helped unite the teams, hence the success.

Who Had the Most Power at the Microsoft 2000 Project?

The testers had the most power during the production and the release of Office 2000. The testers had the mandate to determine if a project was ready to release thus giving the team control over the organization’s production.

Differences between Unplanned Iterations and Reworks

Both iteration and rework involve repeating a process, but they use different approaches. In unplanned iterations, only the problematic areas are repeated while, in reworks, the whole program is redone. Additionally, unplanned iterations occur once a loop fails while reworks occur once the result fails. Unplanned iterations aim at achieving the original product while reworks aim at improving the original product.

Find out the price of your paper