Incorporate feedback into functional specifications

The provided content is a detailed project plan for the development, testing, and deployment of software. The plan spans over several weeks, with tasks such as creating functional specifications, designing, developing code, testing, documenting, piloting, and deploying the software. The timeline starts on May 5th and ends on July 5th, with various milestones and deadlines throughout.

Project Management: Benefits Administration Software
The method that can be employed to cut cost in the project is by ensuring that the project finishes
as per the requirements. Moreover, the project procurement manager will be procuring materials
through the channel that are comparatively cheaper. Also, the use of bidding can be the most
effective method. The scope changes are mostly impact the budget and time of the whole project.
However, one of the strategies that can be implemented is to eliminate the scope that are less
important and can be coped later. The table below shows the WBS with duration, time period,
and the predecessors:
Task Name Duration Start Finish Predecessors
1. Benefits Administration Software 111
days?
Wed
01-02-
17
Wed 05-
07-17
1.1 Scope 11 days Wed
01-02-
17
Wed 15-
02-17
1.1.1 Determine project scope 2 days Wed 01-
02-17
Thu 02-
02-17
1.1.2 Secure project sponsorship 3 days Fri 03-
02-17
Tue 07-
02-17
3
1.1.3 Define preliminary resources 2 days Wed 08-
02-17
Thu 09-
02-17
4
1.1.4 Secure core resources 4 days Fri 10-
02-17
Wed 15-
02-17
5
1.1.5 Scope complete 0 days Wed 15-
02-17
Wed 15-
02-17
6
1.2 Analysis/Software Requirements 23 days? Thu 16-
02-17
Mon 20-
03-17
1.2.1 Conduct needs analysis 3 days Thu 16-
02-17
Mon 20-
02-17
7
1.2.3 Draft preliminary software
specifications
2 days Tue 21-
02-17
Wed 22-
02-17
9
1.2.4 Review software
specifications/budget with team
4 days Thu 23-
02-17
Tue 28-
02-17
10
1.2.5 Incorporate feedback on software
specifications
5 days Wed 01-
03-17
Tue 07-
03-17
11
1.2.6 Develop delivery timeline 3 days Wed 08-
03-17
Fri 10-
03-17
12
1.2.7 Obtain approvals to proceed
(concept, timeline, budget)
1 day? Mon 13-
03-17
Mon 13-
03-17
13
1.2.8 Secure required resources 5 days Tue 14-
03-17
Mon 20-
03-17
14
1.2.9 Analysis complete 0 days Mon 20-
03-17
Mon 20-
03-17
15

1.3 Design 39 days Tue 21-
03-17
Fri 12-
05-17
1.3.1 Review preliminary software
specifications
3 days Tue 21-
03-17
Thu 23-
03-17
16
1.3.2 Develop functional specifications 10 days Fri 24-
03-17
Thu 06-
04-17
18
1.3.3 Develop prototype based on
functional specifications
15 days Fri 07-
04-17
Thu 27-
04-17
19
1.3.4 Review functional specifications 5 days Fri 28-
04-17
Thu 04-
05-17
20
1.3.5 Incorporate feedback into functional
specifications
5 days Fri 05-
05-17
Thu 11-
05-17
21
1.3.6 Obtain approval to proceed 1 day Fri 12-
05-17
Fri 12-
05-17
22
1.3.7 Design complete 0 days Fri 12-
05-17
Fri 12-
05-17
23
1.4 Development 22 days Fri 05-
05-17
Mon 05-
06-17
1.4.1 Review functional specifications 2 days Fri 05-
05-17
Mon 08-
05-17
21
1.4.2 Identify modular/tiered design
parameters
3 days Tue 09-
05-17
Thu 11-
05-17
26
1.4.3 Assign development staff 2 days Fri 12-
05-17
Mon 15-
05-17
27
1.4.4 Develop code 15 days Tue 16-
05-17
Mon 05-
06-17
28
1.4.5 Development complete 0 days Mon 05-
06-17
Mon 05-
06-17
29
1.5 Testing 22 days Tue 21-
03-17
Wed 19-
04-17
1.5.1 Develop unit test plans using
product specifications
3 days Tue 21-
03-17
Thu 23-
03-17
16
1.5.2 Develop integration test plans using
product specifications
4 days Tue 21-
03-17
Fri 24-
03-17
16
1.5.3 Unit Testing 18 days Mon
27-03-
17
Wed 19-
04-17
1.5.3.1 Review modular code 5 days Mon 27-
03-17
Fri 31-
03-17
33
1.5.3.2 Modify code 10 days Mon 03-
04-17
Fri 14-
04-17
35
1.5.3.3 Re-test modified code 3 days Mon 17-
04-17
Wed 19-
04-17
36
1.5.3.4 Unit testing complete 0 days Wed 19-
04-17
Wed 19-
04-17
37
1.5.4 Integration Testing 10 days Mon Fri 07-

27-03-
17
04-17
1.5.4.1 Test module integration 3 days Mon 27-
03-17
Wed 29-
03-17
33
1.5.4.2 Modify code 5 days Thu 30-
03-17
Wed 05-
04-17
40
1.5.4.3 Re-test modified code 2 days Thu 06-
04-17
Fri 07-
04-17
41
1.5.4.4 Integration testing complete 0 days Fri 07-
04-17
Fri 07-
04-17
42
1.6 Documentation 31 days Mon
10-04-
17
Mon 22-
05-17
1.6.1 Develop Help specification 5 days Mon 10-
04-17
Fri 14-
04-17
43
1.6.2 Develop Help system 5 days Mon 17-
04-17
Fri 21-
04-17
45
1.6.3 Review Help documentation 6 days Mon 24-
04-17
Mon 01-
05-17
46
1.6.4 Incorporate Help documentation
feedback
5 days Tue 02-
05-17
Mon 08-
05-17
47
1.6.5 Develop user manuals 4 days Tue 09-
05-17
Fri 12-
05-17
48
1.6.7 Documentation complete 6 days Mon 15-
05-17
Mon 22-
05-17
49
1.7 Pilot 28 days Mon
10-04-
17
Wed 17-
05-17
1.7.1 Identify test group 6 days Mon 10-
04-17
Mon 17-
04-17
43
1.7.2 Develop software delivery
mechanism
4 days Tue 18-
04-17
Fri 21-
04-17
52
1.7.3 Install/deploy software 10 days Mon 24-
04-17
Fri 05-
05-17
53
1.7.4 Obtain user feedback 5 days Mon 08-
05-17
Fri 12-
05-17
54
1.7.5 Evaluate testing information 3 days Mon 15-
05-17
Wed 17-
05-17
55
1.7.6 Pilot complete 0 days Wed 17-
05-17
Wed 17-
05-17
56
1.8 Deployment 35 days Thu 18-
05-17
Wed 05-
07-17
1.8.1 Determine final deployment strategy 5 days Thu 18-
05-17
Wed 24-
05-17
57
1.8.2 Develop deployment methodology 10 days Thu 25-
05-17
Wed 07-
06-17
59

1.8.3 Secure deployment resources 5 days Thu 08-
06-17
Wed 14-
06-17
60
1.8.4 Deploy software 15 days Thu 15-
06-17
Wed 05-
07-17
61
1.8.5 Deployment complete 0 days Wed 05-
07-17
Wed 05-
07-17
62