| | | | | | RESOURCE REQUIREMENTS DOCUMENT |
| WBS ID | Task Name | Duration | Start | Finish | Resources | QTY | Description |
| 3 | Project Charter Approval | | | | Project Manager | 1 | 1 Project Manager is assigned to complete the project charter approval & 1 Sponsor is need for approval. During this phase the project manger will collect pertinet information from key stakeholders & document results in charter. |
| 4 | Collect Requirements from Stakeholders | | | | Project Manager | 1 |
| 5 | Develop Mission/Purpose | | | | Project Manager | 1 |
| 6 | Define Statement of Work | | | | Project Manager | 1 |
| 7 | Identify Objectives | | | | Project Manager | 1 |
| 8 | Identify Business Needs | | | | Project Manager | 1 |
| 9 | Identify Key Stakeholders | | | | Project Manager | 1 |
| 10 | List Project Milestones | | | | Project Manager | 1 |
| 11 | Determine Budget | | | | Project Manager | 1 |
| 12 | Identify User Acceptance Criteria/Quality | | | | Project Manager | 1 |
| 13 | Identify Major Risk | | | | Project Manager | 1 |
| 14 | Generate Project Timeline | | | | Project Manager | 1 |
| 15 | Gather charter information and insert into charter | | | | Project Manager | 1 |
| 16 | Formalize Project Charter | | | | Project Manager | 1 |
| 17 | Project Manager Approval | | | | Project Manager | 1 |
| 18 | Sponsor Approval | | | | Project Sponsor | 1 |
| 19 | Develop Scope Statement | | | | Project Manager | | 1 Project Manager needed to develop scope statement. The scope statement is more detailed and document confimation of results and what it intends to produce. Contain limitation, exclusions, and provide a solution. Assist with devlopment of breaking down the WBS |
| 20 | Establish Detailed SOW | | | | Project Manager | 1 |
| 21 | Determine Product Solution | | | | Project Manager | 1 |
| 22 | Determine Deliverables | | | | Project Manager | 1 |
| 23 | Identify Objectives | | | | Project Manager | 1 |
| 24 | Identify Project Assumption | | | | Project Manager | 1 |
| 25 | Identify project constraints | | | | Project Manager | 1 |
| 26 | List of Exclusions | | | | Project Manager | 1 |
| 27 | Detailed Acceptance Criteria | | | | Project Manager | 1 |
| 28 | Identify Technical Requirements | | | | Project Manager | 1 |
| 29 | Document information in scope statement document | | | | Project Manager | 1 |
| 30 | Project Manager Approval | | | | Project Manager | 1 |
| 31 | Project Contract Approval | | | | | | 1 Project Manager ,1 Sponsor, 1 Contract Manager is need. This phase intiates the contract approval process between both parties. Deliverables, payment method, terms, agreements, timelines, and etc are completed. Formalization of contract established. |
| 32 | Initiate Contract | | | | Project Manager | 1 |
| 33 | Develop SOW | | | | Project Manager | 1 |
| 34 | Evaluate Criteria (Terms, Agreements) | | | | Project Manager | 1 |
| 35 | Identify Deliverables | | | | Project Manager | 1 |
| 36 | Proposed timelines | | | | Project Manager | 1 |
| 37 | Invoice/Payment | | | | Project Manager | 1 |
| 38 | Draft contract | | | | Contract Manager | 1 |
| 39 | Review Contract | | | | Project Sponsor, Project Manager | 1,1 |
| 40 | Contract Adjustments | | | | Contract Manager | 1 |
| 41 | Finalized contract | | | | Contract Manager | 1 |
| 42 | Project Manager Sign-off | | | | Project Manager | 1 |
| 43 | Project Sponsor Sign-off | | | | Project Sponsor | 1 |
| 44 | Begin of Kickoff Meeting | | | | | | 1 Project Manager is need to begin kickoff meeting. This meeting will introduce the project team to the project while soliciting feedback, documenting results, and discussing work activities. |
| 45 | Identify Project team | | | | Project Manager | 1 |
| 46 | Schedule dates to meet project team | | | | Project Manager | 1 |
| 47 | Get attendance confirmation from team | | | | Project Manager | 1 |
| 48 | Discuss Project with team | | | | Project Manager | 1 |
| 49 | Gather feedback | | | | Project Manager | 1 |
| 50 | Document meeting | | | | Project Manager | 1 |
| 51 | Business Requirements Gathered | | | | | | 4 Business Analyst need to collect business requirements, and 1 Educational Advisor need to help define a business solution. This phase requires the BA to solicite information from stakeholders to determine what they would like the finished project look and how it will function. The ED Advisor will assist with esthetics and functionality. |
| 52 | Evaluate pre-existing processes | | | | Business Analyst1 | 1 |
| 53 | Interview stakeholders | | | | Business Analyst1&2 | 2 |
| 54 | Collect requirements | | | | Business Analyst1&2 | 2 |
| 55 | Define business processes | | | | Business Analyst3 | 1 |
| 56 | Identify business process modifications | | | | Business Analyst1&2 | 2 |
| 57 | Define business solution requirements (behavioral conditions) | | | | Business Analyst1&2, Educational Advisor | 2,1 |
| 58 | Identify affected business areas | | | | Business Analyst4 | 1 |
| 59 | Document requirements/process information | | | | Business Analyst4 | 1 |
| 60 | Analyze requirements | | | | Business Analyst1&2 | 2 |
| 61 | Review requirements | | | | Business Analyst Lead | 1 |
| 62 | Approve requirements | | | | Business Analyst Lead | 1 |
| 63 | Develop Design Concept | | | | | | 2 Software Architects are needed, 2 Graphic Designers, 1 Software Lead is needed for the Design phase of the project. The team will develop a visual representation of what the stakeholders are requesting via storyboards, protoypes and workshops. |
| 64 | Define the problem | | | | Software Architect Lead | 1 |
| 65 | Research indusrty standards | | | | Software Architect Lead | 1 |
| 66 | Setup brainstorming sessions | | | | Software Architect Lead | 1 |
| 67 | Establish detailed design workshops | | | | Software Architect Lead | 1 |
| 68 | Establish Joint application design workshop | | | | Software Architect Lead | 1 |
| 69 | Document brainstorming sessions | | | | Software Architect1&2, Graphic Designer1&2 | 2,2 |
| 70 | Sketch prototype | | | | Software Architect1&2, Graphic Designer1&2 | 2,2 |
| 71 | Create physical model | | | | Software Architect1&2, Graphic Designer1&2 | 2,2 |
| 72 | Establish Storyboard workshops | | | | Software Architect Lead | 1 |
| 73 | Evaluation of software using | | | | Software Architect1&2, Graphic Designer1&2 | 2,2 |
| 74 | Integrate technical standards | | | | Software Architect Lead | 1 |
| 75 | Review design prototype | | | | Software Architect Lead | 1 |
| 76 | Approve design prototype | | | | Software Architect Lead | 1 |
| 77 | Review storyboard | | | | Software Architect Lead | 1 |
| 78 | Approve storyboard | | | | Software Architect Lead | 1 |
| 79 | Develop Detailed Software Design | | | | | | The software design phase will include 4 Software Developers, 2 SubContractors, 2 Database Analyst, 2 Graphic Designer, 1 Software Developer Lead, 1 Database Administrator. The team will design actual prototypes of the user interface, graphics, storyboards, and include how each entity will function and flow. |
| 80 | Design prototypes | | | | Software Developer1&2, SubContractor1 | 2,1 |
| 81 | Design of user interfaces | | | | Software Developer1&2 | 2 |
| 82 | Design storyboard | | | | Software Developer3&4, SubContractor2 | 2,1 |
| 83 | Design graphics | | | | Graphic Designer1&2 | 2 |
| 84 | Design Functionality | | | | Software Developer1&2, SubContractor1 | 2,1 |
| 85 | Design Process flows | | | | Database Analyst1&2, Software Developer1&2 | 2,2 |
| 86 | Design SQL database schemas | | | | Database Analyst3&4 | 2 |
| 87 | Verification of detailed designs | | | | Software Developer Lead, Database Administrator | 1,1 |
| 88 | Document system design specifications | | | | Software Developer | 1 |
| 89 | Review detailed designs | | | | Software Developer Lead | 1 |
| 90 | Approve detailed designs | | | | Software Developer Lead, Database Administrator | 1,1 |
| 91 | Documentation of detailed design | | | | Software Developer | 1 |
| 92 | Software Development | | | | | | The software development phase will include: 5 Software Developers, 4 Database Analyst, 1 Subcontractor,1 Software Developer Lead. The devlopment phase is where the team will start building the phyical software and parallel it against specifications and requirements |
| 93 | Collect business requirements documents | | | | Software Developer4, Database Analyst1 | 1,1 |
| 94 | Collect requirements specification documents | | | | Software Developer4, Database Analyst1 | 1,1 |
| 95 | Collect design documents | | | | Software Developer4, Database Analyst1 | 1,1 |
| 96 | Collect design specifications | | | | Software Developer4 | 1 |
| 97 | Generate code for user interface | | | | Software Developer1,2,3, Subcontractor1 | 3, 1 |
| 98 | Integrate graphics | | | | Software Developer1&2 | 2 |
| 99 | Construct database tables | | | | Database Analyst3&4 | 2 |
| 100 | Establish table relationships | | | | Database Analyst3&4 | 2 |
| 101 | Generate code for reports (SQL) | | | | Software Developer3, Database Analyst2 | 1,1 |
| 102 | Review product | | | | Software Developer Lead | 1 |
| 103 | Approve product | | | | Software Developer Lead | 1 |
| 104 | Develop System Documentation | | | | | | The documentation phase require: 2 Technical Writer, 1 Database Administrator, 1 Network Engineer, 2 Database Analyst, 4 Software Developers, 1 Software Developer Lead. The documentation phase documents the entire flow of the system, functionality, specifications, system help files, configurations, and etc. for troubleshooting and maintenance purposes |
| 105 | Write document overview of system | | | | Technical Writer | 1 |
| 106 | Write document disaster recovery backups | | | | Database Administrator | 1 |
| 107 | Write document troubleshooting material | | | | Database Administrator | 1 |
| 108 | Write document hardware configuration | | | | Network Engineer | 1 |
| 109 | Write document process flows | | | | Database Analyst1&2 | 2 |
| 110 | Write document technical software specification | | | | Technical Writer, Software Developer1&2 | 1,2 |
| 111 | Write Network documentation | | | | Network Administrator | 1 |
| 112 | Write user/system help files | | | | Software Developer1&2 | 2 |
| 113 | Write user techninal training manual | | | | Software Developer3&4 | 2 |
| 114 | Review system documentation | | | | Software Lead | 1 |
| 115 | Approve system documentation | | | | Software Lead | 1 |
| 116 | Design Software Test Plans | | | | | | Design software test plans require: 4 Software Developers, 1 Software Developer Lead. Designing software test plans involves creating action scenarios and testing scripts to ensure software function to its full capacity. |
| 117 | Design test scenarios | | | | Software Developer3&4 | 2 |
| 118 | Design use cases | | | | Software Developer3&4 | 2 |
| 119 | Design test scripts | | | | Software Developer1&2 | 2 |
| 120 | Design results document | | | | Software Developer2 | 1 |
| 121 | Review test plan designs | | | | Software Developer Lead | 1 |
| 122 | Approve test plan designs | | | | Software Developer Lead | 1 |
| 123 | Develop Software Test Plans | | | | | | Developing the software test plans require: 4 Software Developers, and 1 Software Lead. Scenarios and test scripts are developed to start testing functionality and quality. Testing environment is established and user acceptance procedures are also develped. |
| 124 | Create test scenario/cases | | | | Software Developer1&2 | 2 |
| 125 | Create user test scripts | | | | Software Developer1&2 | 2 |
| 126 | Create results document | | | | Software Developer3 | 1 |
| 127 | Write System Test procedures | | | | Software Developer3&4 | 2 |
| 128 | Verify system test procedures | | | | Software Developer Lead | 1 |
| 129 | Establish the System Testing environment | | | | Software Developer Lead | 1 |
| 130 | Write User acceptance test procedures | | | | Software Developer Lead | 1 |
| 131 | Verify user acceptance test procedures | | | | Software Developer Lead | 1 |
| 132 | Approve test plans and procedures | | | | Software Developer Lead | 1 |
| 133 | Q&A Testing | | | | | | Q&A Testing require: 4 Software Developers, 3 Testers, 1 Subcontractor, 1 Quality Assurance Manager. Q&A Testing phase validate and verify data elements are properly conveyed to ensure information displayed back to end user is correctly displayed and table relationships are correctly joined. It also confirms no defects are present in the final delivery. |
| 134 | Conduct system testing | | | | Software Developer3&4 | 2 |
| 135 | Conduct integration testing | | | | Software Developer1&2 | 2 |
| 136 | Generate requirements matrix | | | | Quality Assurance Manager | 1 |
| 137 | Verify/Validate functionality | | | | Software Tester1,2,3 | 3 |
| 138 | Verify/Validate table relationships | | | | Software Tester1,2,3 | 3 |
| 139 | Verify/Validate data elements | | | | Software Tester1,2,3 | 3 |
| 140 | Verify results match results documents | | | | Software Tester1,2,3 | 3 |
| 141 | Document defects reported | | | | Software Developer1 | 1 |
| 142 | Fix defects | | | | Software Developer2&3, Subcontractor | 2,1 |
| 143 | Retest | | | | Software Tester1,2,3 | 3 |
| 144 | Complete software readiness review | | | | Quality Assurance Manager | 1 |
| 145 | Approve software readiness review | | | | Quality Assurance Manager | 1 |
| 146 | User Acceptance Testing | | | | | | User Acceptance Testing require: 1 Software Developer Lead, 1 Software Developer, 1 Sponsor, 1 Project Manger. User acceptance testing is conducted to produce final deliverable to the end user(s) for their own testing to ensures their criteria has been meet. |
| 147 | Produce final deliverable | | | | Software Developer Lead | 1 |
| 148 | Draft user acceptance test document | | | | Software Developer Lead | 1 |
| 149 | Provide user acceptance criteria check off sheet | | | | Software Developer Lead | 1 |
| 150 | Conduct user acceptance testing | | | | Software Developer Lead | 1 |
| 151 | Document findings | | | | Software Developer | 1 |
| 152 | Review modifications | | | | Software Developer Lead | 1 |
| 153 | Make adjustments | | | | Software Developer | 1 |
| 154 | User approval sign-off | | | | Sponsor | 1 |
| 155 | Project Manager approval sign-off | | | | Project Manager | 1 |
| 156 | Environment Readiness | | | | | | Environment Readiness requires: 1 Project Manager, 1 Software Developer. This phase of the project ensures that the environment is ready for installation and meet necessay requirements. |
| 157 | Establish delivery of final product | | | | Project Manager | 1 |
| 158 | Installation of product | | | | Software Developer | 1 |
| 159 | Deploy Software | | | | | | Deploy Software: 3 Software Developer 1 Software Developer Lead. Software is deployed to the Cloud server along with files, data, and documentation. Ready for use |
| 160 | Setup cloud server | | | | Software Developer | 1 |
| 161 | Transfer files to cloud server | | | | Software Developer | 1 |
| 162 | Transfer software to cloud server | | | | Software Developer | 1 |
| 163 | Migrate data | | | | Software Developer1&2 | 2 |
| 164 | Transfer system documentation | | | | Software Developer | 1 |
| 165 | Review migrated data, files, documentation | | | | Software Developer Lead | 1 |
| 166 | Approve everything transferred sucessfully | | | | Software Developer Lead | 1 |
| 167 | Database Security | | | | | | Database Security requires: 1 Database Administrator. Database Adminstrator will secure database to establish layers of security to ensure personal data is not compromised. |
| 168 | Identify sensitive data needing secured | | | | Database Administrator | 1 |
| 169 | Eliminate any vulnerabilites to comprimising data | | | | Database Administrator | 1 |
| 170 | Enforce user access and establish controls | | | | Database Administrator | 1 |
| 171 | Establish limited data accessibility privilages | | | | Database Administrator | 1 |
| 172 | Monitor activity deviations to ensure polices are being monitored and controlled | | | | Database Administrator | 1 |
| 173 | Document suspecious behaviors | | | | Database Administrator | 1 |
| 174 | Respond to suspicious behaviors | | | | Database Administrator | 1 |
| 175 | Alert any suspicious activity, minimizes risk | | | | Database Administrator | 1 |
| 176 | Reviewal of documented security breaches | | | | Database Administrator | 1 |
| 177 | Network Security | | | | | | Network Security requires: 1 Network security Administrator, 1 Network Engineer. Network Security is established to ensure the network is properly secured to block out any threats that may cause harm to hardware/software. Consistently monitored for threats. |
| 178 | Create multiple layers of defense | | | | Network Administrator | 1 |
| 179 | Block resources that are threats to hardware/software | | | | Network Administrator | 1 |
| 180 | Install anitvirus software | | | | Network Engineer | 1 |
| 181 | Generate analytical reports | | | | Network Administrator | 1 |
| 182 | Document findings | | | | Network Engineer | 1 |
| 183 | Provide resolution | | | | Network Engineer | 1 |
| 184 | Review network parameters | | | | Network Administrator | 1 |
| 185 | Approve Network parameters | | | | Network Administrator | 1 |
| 186 | Train End Users | | | | | | Train End Users require: 1 Software Developer. End user training is required to demonstrate how the software can be utilized. Training material is distributed to users to utilize during training sessions. |
| 187 | DevelopTraining materials | | | | Software Developer | 1 |
| 188 | Use case scripts utilized | | | | Software Developer | 1 |
| 189 | End user training Internal | | | | Software Developer | 1 |
| 190 | End user training External | | | | Software Developer | 1 |
| 191 | Technical Support | | | | | | Technical Support requires: 2 Technical Support Technicians, 1 Technical Support Lead. Technical support is provided to end users after software has been deployed to address and concerns. Technical support will review issues and provide a resolution. |
| 192 | Log issues | | | | Technical Support1&2 | 2 |
| 193 | Review technical issues | | | | Technical Support1&2 | 2 |
| 194 | Provide resolution | | | | Technical Support1&2 | 2 |
| 195 | Monitor satisfaction | | | | Technical Spupport Lead | 1 |
| 196 | Online E-Learning Educational Software Closure | | | | | | Online E-Learning Educational Software Closure require: 1 Project Manager. The final deliverables has been distributed to the client and the project has come to an end. Project documents are reviewed for team performance, financial performance, and endusre satisfaction was met. |
| 197 | Asses satisfaction | | | | Project Manager | 1 |
| 198 | Review team performance | | | | Project Manager | 1 |
| 199 | Review financial performance | | | | Project Manager | 1 |
| 200 | Summarize project results | | | | Project Manager | 1 |
| 201 | Close project records | | | | Project Manager | 1 |
| 202 | Contract closure | | | | | | Contract Closure requires 1 Project Manager. All contracts are formalized, project files gathered and filed away for later review, lessons learned is documented. |
| 203 | Close contract with subcontractor | | | | Project Manger | 1 |
| 204 | Close Contract with CPS | | | | Project Manger | 1 |
| 205 | Gather project files and file away | | | | Project Manger | 1 |
| 206 | Document lessons learned | | | | Project Manger | 1 |