Provide a table with the efforts, durations, reliability estimates, maximum errors, and resource intensities required at the activity level within the lowest-level DWBS elements (the work packages) please see the attached image.

Use of a project planning software is mandatory for this part of the assignment. While the choice of the software is open, most students tend to use Microsoft Project 201X or Primavera P6. Please set the start date of the project to Monday, Jan. 4, 2021, with a 5-day work week calendar. If your project requires a specific start date/ end date or an alternate work calendar, please use them as needed and provide reasons to do so.

Break the DWBS's work packages down to two to three activities each with total number of activities across the project in the 60-80 range. The tasks together for each work package should Page 2 of 6 use a minimum of three different resources categories. (If you cannot meet these criteria initially, you may need to increase the scope of the selected project. If you revise the project scope, please update the project objectives and DWBS accordingly. For recurring activities, only the parent recurring activities will be counted and not their individual instances.)

Estimate the volume of the work, identify the resources required and corresponding durations for each of the activities. Next estimate the magnitude and probability of the possible maximum error (= 1- reliability of the estimated duration). What do we mean by reliability? Reliability means the confidence you put on the number that you have given, e.g., "I am 93 percent sure that this task will be completed in 9 days." Thus, seven percent of the time, the task will require more than nine days. Suppose the maximum possible duration is 14 days. Then the maximum error is five days.

Note that the duration estimate assumes a resource intensity, which you must also state. This initial duration should be the optimum duration, i.e., the duration that minimizes the effort, which is the product of the intensity and the duration. For example, if you use 3 brick layers for 4 days to build a wall, then the resource is brick layer, the intensity is 3, the duration is 4 days, and the total effort is 12 worker-days.

Please include a comment on your general approach for estimating durations. For example, explain why you used 3 workers for 4 days instead of 2 workers for 6 days. This explanation is not required for each activity if the activities are similar; the general approach with at least two examples would suffice. Any unique cases should be identified and explained. If you find that for most elements you are using durations in fractions of a time unit, adjust the unit of measure to a smaller unit so that the assigned values in the estimate will be integers or half integers and not other fractions. Please do not use any resource constraints in the project scheduling software; they will be imposed in a later assignment.

If some of the resources for an activity need to be applied serially, divide this activity into several activities, each of which uses its resources in parallel to the others for now since the precedences are not defined.

Please note that while it is okay to have some of the deliverables outsourced, such outsourcing should not reduce the number of deliverables that are developed to the activity level below 20

Work Breakdown Structure (WBS) Real Estate Management System 1.0 Plan 2.0 Design 3.0 Implementation 4.0 Testing 5.0 6.0 Project Close-out 1.1 Project Scope 2.1 Technology Stack 3.1 Public portal 4.1 System Training 5.1 Deployment 6.1 Release Notes 1.2 Project Objectives 2.2 Development Tools 3.2 Internal portal 4.2 Unit Testing 5.2 Installation Testing 6.2 User Guide 1.3 Requirements 2.3 Design System 3.3 Middle-layer 4.3 User Testing 5.3 User 6.3 Admin Guide 1.4 Budget Estimation 2.4 User-story 3.4 Mobile Application 4.4 System Integration 5.4 Contingency 6.4 Contingency 1.5 Scheduling 2.5 Database mapping 3.5 Kiosk portal 4.5 System Rework 5.5 Dry-Run Testing 6.5 Post-launch 1.6 Risk Analysis 2.6 Interface Design 3.6 Onbase Document 4.6 Regression Testing 5.6 Schedule Support 6.6 Project Acceptance 1.7 Initial Project Plan 2.7 Project Plan 3.7 Data Migration 1.8 Project Approval 3.8 Reporting Function 3.9 Cloud hosting 3.10 User Licensing 3.11 Code Figure 1: Tree Structure View