need help project plan week 1
Running head: SIMPLIFIED PROJECT PLAN 1
SIMPLIFIED PROJECT PLAN 2
Simplified Project Plan
Name
Institution
The project to be implemented involves the development of Bank Management Software and entails the use of the waterfall model. Selecting a methodology is essential since it gives a framework of the overall process and associated project documents as well as the deliverables that will control the project development cycle from start to close. The waterfall model ensures that the development phases flow seamlessly and is subdivided into separate sequential stages where the result of the preceding phase becomes the input of the succeeding phase.
In the waterfall model, the development team moves through the stages of development. The phases include; Analysis, Requirements Specification, Design, Coding, and Implementation, Testing and integration. The sequence flow from one phase to another in a top to bottom fashion. Theoretically, all the requirements are initially specified as well as the scope of the project. The app is designed according to the requirements where it is implemented and tested devoid of any modifications. The final product is then delivered to the customer.
Development phases for the project include:
· Requirements gathering and elicitation where the system requirement objectives are met. The user requirements for the system will entail Financial / Management Accounting, Treasury and Risk Management as well as Bank Communication Management.
· The system design phase will enable proper determination of the hardware and software requirements that describes the entire system architecture.
· The Implementation phase involves the development of application modules which are tested separately to establish their functionality.
· The Integration and Testing phase will entail the integration of the individual modules into a single system which is then tested as a single system. Also, user acceptance testing is done at this phase
· System implementation phase. This phase follows the successful integration and testing phase where it is deployed.
· The maintenance phase occurs after the system is implemented to correct or add new modules to meet customer’s changing needs or scope creep.
Simplified project plan for a Bank Management Software
|
Task Mode |
Task Name |
Duration |
Start |
Finish |
Predecessors |
|
Auto Scheduled |
Bank Management Software Development |
23 days |
Wed 5/2/18 |
Fri 6/1/18 |
|
|
Auto Scheduled |
Application conception and initiation |
2 days |
Wed 5/2/18 |
Thu 5/3/18 |
|
|
Auto Scheduled |
Project plan |
2 days |
Wed 5/2/18 |
Thu 5/3/18 |
|
|
Auto Scheduled |
Requirement analysis and specification |
3 days |
Fri 5/4/18 |
Tue 5/8/18 |
|
|
Auto Scheduled |
Develop Financial / Management Accounting requirements |
1 day |
Fri 5/4/18 |
Fri 5/4/18 |
3 |
|
Auto Scheduled |
Supply Chain Management |
1 day |
Mon 5/7/18 |
Mon 5/7/18 |
5 |
|
Auto Scheduled |
Treasury Applications |
1 day |
Mon 5/7/18 |
Mon 5/7/18 |
5 |
|
Auto Scheduled |
Treasury and Risk Management |
1 day |
Mon 5/7/18 |
Mon 5/7/18 |
5 |
|
Auto Scheduled |
Bank Communication Management |
1 day |
Mon 5/7/18 |
Mon 5/7/18 |
5 |
|
Auto Scheduled |
Finalize Requirement specification draft |
2 days |
Mon 5/7/18 |
Tue 5/8/18 |
5 |
|
Auto Scheduled |
Design |
7 days |
Wed 5/9/18 |
Thu 5/17/18 |
|
|
Auto Scheduled |
Design specification |
4 days |
Wed 5/9/18 |
Mon 5/14/18 |
10 |
|
Auto Scheduled |
Configuration management |
3 days |
Tue 5/15/18 |
Thu 5/17/18 |
12 |
|
Auto Scheduled |
Coding and implementation |
7 days |
Tue 5/15/18 |
Wed 5/23/18 |
|
|
Auto Scheduled |
operational source code and unit test |
7 days |
Tue 5/15/18 |
Wed 5/23/18 |
12 |
|
Auto Scheduled |
Integration and testing |
4 days |
Thu 5/24/18 |
Tue 5/29/18 |
|
|
Auto Scheduled |
Validate startup on deployed hardware |
2 days |
Thu 5/24/18 |
Fri 5/25/18 |
15 |
|
Auto Scheduled |
Perform OS, and application testing |
2 days |
Mon 5/28/18 |
Tue 5/29/18 |
17 |
|
Auto Scheduled |
Deployment of System |
3 days |
Mon 5/28/18 |
Wed 5/30/18 |
|
|
Auto Scheduled |
Configure and deploy production hardware |
2 days |
Mon 5/28/18 |
Tue 5/29/18 |
13,17 |
|
Auto Scheduled |
Load software to deployed hardware |
1 day |
Wed 5/30/18 |
Wed 5/30/18 |
20,18 |
|
Auto Scheduled |
Maintenance |
3 days |
Wed 5/30/18 |
Fri 6/1/18 |
|
|
Auto Scheduled |
Obtain updates regarding key deliverables from the project team |
2 days |
Wed 5/30/18 |
Thu 5/31/18 |
18 |
|
Auto Scheduled |
Hold formal customer review after, project plan approval and pilot testing |
1 day |
Fri 6/1/18 |
Fri 6/1/18 |
18,23 |
References
Ashmore, S., & Runyan, K. (2015). Introduction to agile methods. Upper Saddle River, NJ: Addison-Wesley