Please be sure to read the Team Contribution Assessment and Grading of Team Assignments and the Project Documentation Requirements sections of this ITP Master Document.

Review your previous assignment deliverables before proceeding with this assignment. This assignment has two parts – an MS Project file (.mpp) and an MS Word file.

• The team will determine the appropriate method for consolidating the individual WBSes into a single WBS.  For instance, after review of all team members' WBSs, the best WBS could be adopted, portions of different team members' WBSs could be used, the best features of different team members' WBSs could be used, it could all be scrapped and collaboratively re-built from scratch, or any number of other methods could be used. 
• The team’s WBS should be fleshed out (meaning enough decomposition to be able to see a major task and all the work associated with it).  As a team, make any corrections and updates necessary to the consolidated/integrated team WBS before adding the dependency links.  The schedule should include time/duration for all lowest level leaf-node tasks (sub-sub tasks or work packages).  MS Project will roll-up the durations and calculate them automatically for summary and major task roll-up groups.  Durations should include hours, days, and weeks of time posted in the Gantt view. 

• Then, the team members will add predecessor-successor linkages for all tasks within the consolidated team WBS.  This is the ORDER in which tasks must be performed. Every task except the FIRST task should have a dependency “relationship” (either a predecessor or a successor) to another task. 
• The default in Microsoft Project is a “finish-to-start” relationship (task A must be completed before task B can start)
• Not all tasks have to be 100% completed before another task can start (task A only needs to be 25% completed when task B could start; or task A and task B could start at the same time).
• For example, to use our previous example, we could be selecting paint colors at the same time we are preparing the bathroom.  We could be taping the edges and then filling holes at the same time we are buying paint. But we CAN’T paint the walls without purchasing the paint – so purchasing the paint is a predecessor to painting the walls.
• Again, each member of the team should go through the WBS as a whole to flesh out areas that may not be addressed with tasks.  For example, if one member is assigned the major task of purchasing paint and supplies, but another member notices that tarps and furniture covers are not included, that member would work with the team to add the associated tasks, durations and predecessors.
• As a team, look at the NETWORK View in Microsoft Project.  All tasks should have some linkage to other tasks.  There should be no tasks “standing alone.”  There should be no tasks without predecessors or successors except for the project start task and the project end task, respectively.  There should be multiple paths and the paths should flow generally from left to right toward the final task, which should be the last task to the right with no subsequent tasks.  The final task should be the defined end of the project.

·         As with previous ITP deliverables, DONOT enter hard-coded dates.  Just enter durations at the lowest level tasks and let MS Project calculate the dates. If your "I" column has a little calendar - you have not done this correctly.

• Do not use "manually scheduled" tasks.  Rather, use "automatically scheduled" tasks.  When manually scheduled, the dates are essentially hard-coded and not allowed to automatically adjust when the task durations and critical paths change.
• The higher level tasks are group summary and major task "roll up" tasks and should have no work themselves.  Don't enter a duration for these tasks.  Their timespan will be automatically calculated by MS Project as the sum of the timespans of their component sub-tasks based on the algorithm.

• When done, save a baselined project schedule as described in the textbook, or the various MSP tutorials, or

·         The Gantt Chart View and the Network View should not look like waterfalls, wherein each task has only one predecessor and only one successor.  That is not only unrealistic, but is problematic for most projects.  There should be parallelism.  This means that typical tasks should have multiple successors and/or predecessors.

·         Please ensure that your MS Project (.mpp) file includes at least the following fields (columns) visible in the left-hand table portion of the Gantt chart view or the Tracking Gantt view:

o    All fields from ITP-2i

o    Start date  [a default field]

o    Finish date  [a default field]

o    Predecessors [a default field]

o    Successors

o    Additionally, please ensure that the Critical Tasks box in the Format tab is checked.

When done, save a baselined project schedule as described in the various MSP tutorials. Submit the MS Project (.mpp) file with your name in the file name.

 http://polaris.umuc.edu/~kschank/MS-Project-Skills-Baselining.htm. 

In a Word document, include a cover sheet that includes contributors, the executive summary, and text that describes your team efforts and decisions made.  Answer the following questions in a text document.  As a 400-level class, writing should be of a style appropriate for a senior level college class.  “Yes” or “No” answers with no explanations or discussions are not appropriate answers.

1.    Did your team discuss and/or divide up the major tasks before completing the INDIVIDUAL WBSes?

2.    How did your team “merge” the WBSes of individual teammates?

3.    Were some teammates’ WBSes more thorough or complete than others?

4.    What was the most difficult part of this assignment?

5.    Did every teammate contribute to this WBS effort?

6.    Is your team still following the day-to-day schedule provided in the TPP-1?

Approximate breakdown by areas include:

o    General: Structure, Format, Mechanics, Style (~4%)

o    Schedule WBS (~10%)

o    Schedule linkages (~60%)

o    Network view (~26%)

Your team has been asked to prepare a project plan to install an IT system in a local bakery.   Mamma Mia has been the primary baker and bakery owner since its opening 15 years ago.  The bakery is one of a dozen shops in a strip mall in an up-and-coming part of town. The bakery is a walk-up-and-order configuration with no seating space. Because the bakery has become more successful over the years, Mamma Mia has decided that the time is right to expand the bakery into the next store, which is now vacant, and she has signed a contract for the two stores to be connected and remodeled.  This space will more than double the size of the current bakery. With this added-on/extra space, Mamma Mia would like to offer her customers sandwiches and bakery items, as well as café-type seating.  At the moment, the bakery employs 1 other baker and 2 persons who wait on the customers at the counter. All paperwork, bookkeeping, ordering supplies, hiring and firing, and keeping track of inventory is done by Mamma.   When the expansion construction is complete, Mamma Mia anticipates hiring 4 additional people full time – 2 food-service certified sandwich makers, 1 more baker, and 1 more counter server.  She also intends to hire 1 person to track inventory and order supplies, and 1 person to manage the bookkeeping, bill paying, and finance parts of the business.   

Because the bakery is now a small operation, all business is done by telephone and with paper documents.  There is one cash register and all bakery goods are purchased with cash or check. To coincide with the construction/expansion effort, Mamma would like to have an IT system installed for point-of-sale, inventory, bookkeeping, purposes.  Mamma would like the system to “connect” to her suppliers, the health department for food services, and other business relationships.  She would also like a website so that she has an Internet presence and so her customers can make advance orders for pick-up.  Related to that, she would like the system to be able to process debit and credit cards. 

Mamma Mia has identified $100,000 to provide an IT system that will be modern, easy to use/employee and customer friendly, and will make her bakery and sandwich shop more efficient. The cost estimate is just that – an estimate. 

Mamma has very little experience working with computers and IT systems.  She feels a bit “old fashioned” but she is willing to learn and wants to be sure that her employees learn, too, how to work with the IT system.  Mamma is your point of contact and the person yu will be working with as you “fill-in” and finalize the requirements for the IT system, and then move to the design and implementation of the IT system.  This means you will have a need to define and explain terms as you work with her.  

As you begin to plan the ITP project, keep in mind that until now the client has had little or no IT system and has had no IT staff.  In addition, there is no networking, LAN, or Internet installed, and no productivity software or other applications.  You may assume that Internet connectivity is available in the area, however (whether via ISP or satellite or whatever).  Mamma Mia is the major stakeholder and your point of contact for this proposal.  Your instructor will fill the role of Mamma and the major stakeholder.  So all questions for the client should be directed to your class instructor.  Your team may consider clarifying the requirements, including the available funding, through Private Message email interviews with Mamma Mia.