MICROSOFT PROJECT Essay Example

Name

Course

Instructor

Date

Мiсrоsоft Рrоjесt

Problem 1

Activity number

Duration

Predecessors

Resource Names

Entire product

Tue 5/12/15

Tue 6/9/15

Software

Wed 6/10/15

Tue 7/28/15

Hardware

Wed 7/29/15

Fri 9/4/15

Market research

Mon 9/7/15

Tue 9/15/15

Software

Wed 7/29/15

Thu 9/24/15

Hardware

Mon 9/7/15

Fri 10/23/15

Market research

Wed 9/16/15

Mon 10/5/15

User interface

Fri 9/25/15

Wed 12/2/15

Functionality

Mon 2/1/16

Mon 2/29/16

Mon 10/26/15

Thu 11/12/15

Tue 3/1/16

Tue 5/17/16

Mon 10/26/15

Mon 11/23/15

Outer cover

Mon 10/26/15

Tue 12/22/15

Mon 2/1/16

Thu 2/18/16

User interface

Mon 3/21/16

Wed 4/27/16

Functionality

Tue 3/1/16

Thu 4/7/16

Fri 11/13/15

Wed 12/2/15

Wed 5/18/16

Mon 7/25/16

Tue 11/24/15

Mon 1/11/16

Outer cover

Wed 12/23/15

Tue 2/9/16

Software

Mon 6/6/16

Wed 7/13/16

15,16,27

hardware

Tue 7/26/16

Tue 8/23/16

17,18,19,27

Entire product

Wed 8/24/16

Thu 9/1/16

20,21,22

Fri 9/2/16

Thu 10/20/16

Market research (implementation)

Tue 10/6/15

Fri 1/29/16

Games (design and implementation)

Mon 2/1/16

Fri 3/18/16

Camera (implementation)

Fri 2/19/16

Fri 5/6/16

MICROSOFT PROJECT

MICROSOFT PROJECT 1

MICROSOFT PROJECT 2

Activity number

Activity name

Duration (week)

Resources requirement

Float/days

Entire project

Software

hardware

Market research

Software

hardware

Market research

User interface

Functionality

Outer cover

User interface

Functionality

Outer cover

Software

hardware

Entire project

Market research (implementation)

0

Games (design and implementation)

Camera (implementation)

0

Early Start

Early Finish

Late Start

Late Finish

Float/days

Tue 5/12/15

Tue 6/9/15

Tue 5/12/15

Wed 6/10/15

Wed 6/10/15

Tue 7/28/15

Wed 6/10/15

Wed 7/29/15

Wed 7/29/15

Fri 9/4/15

Wed 7/29/15

Mon 9/7/15

Wed 7/29/15

Thu 9/24/15

Thu 12/3/15

Mon 2/1/16

Mon 9/7/15

Tue 9/15/15

Mon 9/7/15

Wed 9/16/15

Mon 9/7/15

Fri 10/23/15

Fri 2/19/16

Fri 4/8/16

Wed 9/16/15

Mon 10/5/15

Wed 9/16/15

Tue 10/6/15

Fri 9/25/15

Wed 12/2/15

Wed 3/30/16

Tue 6/7/16

Tue 10/6/15

Fri 1/29/16

Tue 10/6/15

Mon 2/1/16

Mon 10/26/15

Thu 11/12/15

Thu 7/21/16

Tue 8/9/16

Mon 10/26/15

Mon 11/23/15

Mon 5/9/16

Tue 6/7/16

Mon 10/26/15

Tue 12/22/15

Mon 5/9/16

Wed 7/6/16

Fri 11/13/15

Wed 12/2/15

Wed 7/6/16

Tue 7/26/16

Tue 11/24/15

Mon 1/11/16

Tue 6/7/16

Tue 7/26/16

Wed 12/23/15

Tue 2/9/16

Wed 7/6/16

Wed 8/24/16

Mon 2/1/16

Mon 2/29/16

Tue 1/12/16

Tue 3/9/16

Mon 2/1/16

Thu 2/18/16

Fri 4/8/16

Thu 4/28/16

Mon 2/1/16

Fri 3/18/16

Tue 4/19/16

Tue 6/7/16

Fri 2/19/16

Fri 5/6/16

Thu 4/28/16

Fri 7/15/16

Tue 3/1/16

Tue 5/17/16

Wed 2/10/16

Wed 5/27/16

Tue 3/1/16

Thu 4/7/16

Tue 6/7/16

Fri 7/15/16

Mon 3/21/16

Wed 4/27/16

Tue 6/7/16

Fri 7/15/16

Wed 5/18/16

Mon 7/25/16

Wed 5/18/16

Tue 7/26/16

Mon 6/6/16

Wed 7/13/16

Fri 7/15/16

Wed 8/24/16

Tue 7/26/16

Tue 8/23/16

Tue 7/26/16

Tue 8/23/16

0

Wed 8/24/16

Thu 9/1/16

Wed 8/24/16

Fri 9/2/16

Fri 9/2/16

Thu 10/20/16

Fri 9/2/16

Thu 10/20/16

0

Float = Latest finish – Early finish

Problem 2

Resource diagram (histogram)

MICROSOFT PROJECT 3

Conclusion

In this project management, most of the activities are dependent on the others and before the first one was entirely finished the preceding activity could not start. From the network diagram and the histogram the activities that consumed most of the resources are the entire product and the software. The critical events were those activities with zero float meaning that they could not wait before the start, but when they are delayed the whole project also delays. These critical activities are Market Research (implementation) and Camera (implementation)