Please help with the following: Use MS Project or ProjectLibre

Create an MS Project (or other project planning software) project as follows:

1. Enter the tasks listed in the work breakdown structure. (Picture)

2. Assign tasks to the available resources so that they can work in parallel as much as possible, and that they can complete the project in as few weeks as possible. Make sure that you assign people only to tasks for which they are qualified. You can assign only one person to a given task.

3. Start date is February 7th, 2022.

4. Create a project Gantt chart, showing the WBS. Remember that the Gantt chart and WBS must be side-by-side to be understandable. Make the chart easy to read and understand.

5. List the tasks on the critical path.

6. Format this Gantt and WBS chart to fit on one page. Include a PDF of the chart as part of your assignment submission.

7. Save your project.

8. Now, using the same project, but saving to a different file:

9. Reassign resources to the various tasks, as follows:

   a. Make sure that task durations change appropriately whenever the number of resources change.

   b. There are now 4 more people working on the project: Angela, who has the same qualifications as Sergei, Howard, who has the same qualifications as Annie, Julie who has the same qualifications as Dimitri, and Fiacre who has the same qualifications as Gerard.

   c.Re-assign the tasks. You can now assign more than one person to a task. Change the duration of the tasks accordingly.

10. Level the resources, without splitting or adjusting individual assignments.

11. Include a PDF of the chart

12. List the tasks on the critical path.

13. Save your project.

14. In a few paragraphs (more than one), describe in detail how the addition of Angela, Howard, Julie and Fiacre has changed the project.

15. What are the end dates for the two projects? What is the duration of the two projects?

16. In a few paragraphs (more than one), describe in detail, how the critical path has changed. Explain why it has changed or why it has not changed.

1 3 4 4 JAWN Below is a work breakdown structure for a simple software development project. Work Breakdown Structure for Software Development Project Task No. Task Name Duration (wks) Predecessors Collect requirements 2 2 Analyze business processes 1 Analyze data 1 Design system processes 1, 2 5 Design classes and database 2 1,3 6 Design screens 3 4,5 7 Design reports 4 4,5,6 8 Design tests 3 7 9 Present prototype 1 6,7 10 Re-evaluate requirements 2 9 11 Program all features 5 10 12 Test 11 13 Analyze and design documentation 3 9,10 14 Write documentation 3 13 15 Debug and refactor 2 11, 12 16 Test 2 15 17 Deploy 1 14,16 For this project, you have four human resources: Dimitri: an analyst, programmer and designer, who can also test and write documentation. Sergei: a programmer, who can also collect and evaluate requirements, design classes, databases, screens and reports. Annie: a programmer/analyst, who can also deploy software at the customer's site. Grard: a programmer and tester 6 1 3 4 4 JAWN Below is a work breakdown structure for a simple software development project. Work Breakdown Structure for Software Development Project Task No. Task Name Duration (wks) Predecessors Collect requirements 2 2 Analyze business processes 1 Analyze data 1 Design system processes 1, 2 5 Design classes and database 2 1,3 6 Design screens 3 4,5 7 Design reports 4 4,5,6 8 Design tests 3 7 9 Present prototype 1 6,7 10 Re-evaluate requirements 2 9 11 Program all features 5 10 12 Test 11 13 Analyze and design documentation 3 9,10 14 Write documentation 3 13 15 Debug and refactor 2 11, 12 16 Test 2 15 17 Deploy 1 14,16 For this project, you have four human resources: Dimitri: an analyst, programmer and designer, who can also test and write documentation. Sergei: a programmer, who can also collect and evaluate requirements, design classes, databases, screens and reports. Annie: a programmer/analyst, who can also deploy software at the customer's site. Grard: a programmer and tester 6