HWE Accessories Website Project
gmhobbs87
HWEAccessoriesWebsiteProjectPlanRiskMatrixandKeyFactors.docxHWE Accessories Website: Project Plan, Risk Matrix, and Key Factors
HWE Accessories Website: Project Plan, Risk Matrix, and Key Factors
Gregory Hobbs
BSA/515
2/5/18
Anthony Seymour
Start Tue 2/6/18
Finish Wed 5/9/18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
outline the technical requirements Wed 2/21/18 - Fri 2/23/18
Gather data Tue 2/6/18 - Wed 2/7/18
Analyze data Thu 2/8/18 - Sat 2/10/18
document data Mon 2/12/18 - Wed 2/14/18
Define and develop the site concept Fri 2/16/18 - Sat 2/17/18
Define the overall budget Mon 2/19/18 - Tue 2/20/18
Complete the sitemap Mon 2/26/18 - Tue 2/27/18
Adress the technical requirements outlined Wed 2/28/18 - Fri 3/2/18
Begin site's content acquisition Mon 3/5/18 - Tue 3/6/18
Present the design Wed 3/7/18 - Thu 3/8/18
Set the website's look and feel Fri 3/9/18 - Tue 3/13/18
content acquisition Wed 3/14/18 - Thu 3/15/18
design the user interface Sat 3/17/18 - Tue 3/20/18
Finalize the website design Wed 3/21/18 - Fri 3/23/18
Programming outline phase Sat 3/24/18 - Wed 3/28/18
finalize prototype Fri 3/30/18 - Mon 4/2/18
submit final design Thu 4/5/18 - Wed 4/11/18
Perform client sign off Thu 4/12/18 - Fri 4/13/18
perform Usability testing Wed 4/18/18 - Thu 4/19/18
Carry out cross platform testing Sat 4/21/18 - Tue 4/24/18
perform browser testing Wed 4/25/18 - Thu 4/26/18
Make neccesary modifications Tue 5/1/18 - Wed 5/2/18
Final approval Thu 5/3/18 - Fri 5/4/18
Launch the website Sat 5/5/18 - Wed 5/9/18
outline the technical requirements Wed 2/21/18 - Fri 2/23/18
Gather data Tue 2/6/18 - Wed 2/7/18
Analyze data Thu 2/8/18 - Sat 2/10/18
document data Mon 2/12/18 - Wed 2/14/18
Define and develop the site concept Fri 2/16/18 - Sat 2/17/18
Define the overall budget Mon 2/19/18 - Tue 2/20/18
Complete the sitemap Mon 2/26/18 - Tue 2/27/18
Adress the technical requirements outlined Wed 2/28/18 - Fri 3/2/18
Begin site's content acquisition Mon 3/5/18 - Tue 3/6/18
Present the design Wed 3/7/18 - Thu 3/8/18
Set the website's look and feel Fri 3/9/18 - Tue 3/13/18
content acquisition Wed 3/14/18 - Thu 3/15/18
design the user interface Sat 3/17/18 - Tue 3/20/18
Finalize the website design Wed 3/21/18 - Fri 3/23/18
Programming outline phase Sat 3/24/18 - Wed 3/28/18
finalize prototype Fri 3/30/18 - Mon 4/2/18
submit final design Thu 4/5/18 - Wed 4/11/18
Perform client sign off Thu 4/12/18 - Fri 4/13/18
perform Usability testing Wed 4/18/18 - Thu 4/19/18
Carry out cross platform testing Sat 4/21/18 - Tue 4/24/18
perform browser testing Wed 4/25/18 - Thu 4/26/18
Make neccesary modifications Tue 5/1/18 - Wed 5/2/18
Final approval Thu 5/3/18 - Fri 5/4/18
Launch the website Sat 5/5/18 - Wed 5/9/18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
Feb 11, '18
Feb 18, '18
Feb 25, '18
Mar 4, '18
Mar 11, '18
Mar 18, '18
Mar 25, '18
Apr 1, '18
Apr 8, '18
Apr 15, '18
Apr 22, '18
Apr 29, '18
May 6, '18
|
Task Mode |
Task Name |
Duration |
Start |
Finish |
Predecessors |
|
Manually Scheduled |
Analysis tasks |
8 days |
Tue 2/6/18 |
Thu 2/15/18 |
|
|
Auto Scheduled |
Gather data |
2 days |
Tue 2/6/18 |
Wed 2/7/18 |
|
|
Auto Scheduled |
Analyze data |
3 days |
Thu 2/8/18 |
Sat 2/10/18 |
2 |
|
Auto Scheduled |
document data |
3 days |
Mon 2/12/18 |
Wed 2/14/18 |
3 |
|
Manually Scheduled |
Outline site design goals |
7 days |
Fri 2/16/18 |
Mon 2/26/18 |
|
|
Auto Scheduled |
Define and develop the site concept |
2 days |
Fri 2/16/18 |
Sat 2/17/18 |
|
|
Auto Scheduled |
Define the overall budget |
2 days |
Mon 2/19/18 |
Tue 2/20/18 |
6 |
|
Auto Scheduled |
outline the technical requirements |
3 days |
Wed 2/21/18 |
Fri 2/23/18 |
7 |
|
Manually Scheduled |
Define site structure |
7 days |
Mon 2/26/18 |
Tue 3/6/18 |
|
|
Auto Scheduled |
Complete the sitemap |
2 days |
Mon 2/26/18 |
Tue 2/27/18 |
|
|
Auto Scheduled |
Adress the technical requirements outlined |
3 days |
Wed 2/28/18 |
Fri 3/2/18 |
10 |
|
Auto Scheduled |
Begin site's content acquisition |
2 days |
Mon 3/5/18 |
Tue 3/6/18 |
11 |
|
Manually Scheduled |
Design user interface |
7 days |
Wed 3/7/18 |
Thu 3/15/18 |
|
|
Auto Scheduled |
Present the design |
2 days |
Wed 3/7/18 |
Thu 3/8/18 |
|
|
Auto Scheduled |
Set the website's look and feel |
3 days |
Fri 3/9/18 |
Tue 3/13/18 |
14 |
|
Auto Scheduled |
content acquisition |
2 days |
Wed 3/14/18 |
Thu 3/15/18 |
15 |
|
Manually Scheduled |
Develop HTML protosite |
7 days |
Fri 3/16/18 |
Fri 3/23/18 |
|
|
Auto Scheduled |
Coding |
1 day |
Fri 3/16/18 |
Fri 3/16/18 |
|
|
Auto Scheduled |
design the user interface |
3 days |
Sat 3/17/18 |
Tue 3/20/18 |
18 |
|
Auto Scheduled |
Finalize the website design |
3 days |
Wed 3/21/18 |
Fri 3/23/18 |
19 |
|
Manually Scheduled |
Begin HTML production |
7 days |
Sat 3/24/18 |
Mon 4/2/18 |
|
|
Auto Scheduled |
Programming outline phase |
4 days |
Sat 3/24/18 |
Wed 3/28/18 |
|
|
Auto Scheduled |
incorporate the content and graphics |
1 day |
Thu 3/29/18 |
Thu 3/29/18 |
22 |
|
Auto Scheduled |
finalize prototype |
2 days |
Fri 3/30/18 |
Mon 4/2/18 |
23 |
|
Manually Scheduled |
Design tasks |
7 days |
Tue 4/3/18 |
Wed 4/11/18 |
|
|
Auto Scheduled |
Develop storyboard |
1 day |
Tue 4/3/18 |
Tue 4/3/18 |
|
|
Auto Scheduled |
Document design |
1 day |
Wed 4/4/18 |
Wed 4/4/18 |
26 |
|
Auto Scheduled |
submit final design |
5 days |
Thu 4/5/18 |
Wed 4/11/18 |
27 |
|
Manually Scheduled |
Make the website live |
7 days |
Thu 4/12/18 |
Thu 4/19/18 |
|
|
Auto Scheduled |
Perform client sign off |
2 days |
Thu 4/12/18 |
Fri 4/13/18 |
|
|
Auto Scheduled |
perform internal unit testing |
3 days |
Sat 4/14/18 |
Tue 4/17/18 |
30 |
|
Auto Scheduled |
perform Usability testing |
2 days |
Wed 4/18/18 |
Thu 4/19/18 |
31 |
|
Manually Scheduled |
Move the site to the end server |
7 days |
Sat 4/21/18 |
Mon 4/30/18 |
|
|
Auto Scheduled |
Carry out cross-platform testing |
3 days |
Sat 4/21/18 |
Tue 4/24/18 |
|
|
Auto Scheduled |
perform browser testing |
2 days |
Wed 4/25/18 |
Thu 4/26/18 |
34 |
|
Auto Scheduled |
question and answers |
2 days |
Fri 4/27/18 |
Mon 4/30/18 |
35 |
|
Manually Scheduled |
Further tests |
8 days |
Tue 5/1/18 |
Wed 5/9/18 |
|
|
Auto Scheduled |
Make necessary modifications |
2 days |
Tue 5/1/18 |
Wed 5/2/18 |
|
|
Auto Scheduled |
Final approval |
2 days |
Thu 5/3/18 |
Fri 5/4/18 |
38 |
|
Auto Scheduled |
Launch the website |
4 days |
Sat 5/5/18 |
Wed 5/9/18 |
39 |
The above project plan for the HWE accessories website was scheduled to run for a period of three months. All the requirements and planning phase was done in the first week and the following tasks were allocated a week each. The website’s main purpose was to revolutionize the company’s transactions into a more modern online environment thus the developers employed the company’s prior information and used it in the project planning. No new information about the functionalities was collected to save time and resources.
|
Risk |
Risk Level/impact |
Probability of occurrence |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Low(L)/Medium(M)/High(H) |
|
|
Project Size |
|
|
|
Person Hours |
H: Over 20,000 |
Certainty |
|
Estimated Schedule |
H: Over 3 months |
Certainty |
|
Team Size |
H: Over 15 members |
Certainty |
|
Number of Interfaces to Existing Systems Affected |
H: Over 3 |
Certainty |
|
Project Definition |
|
|
|
Narrow Knowledge Level of Users |
M: Knowledgeable of user area only |
Likely |
|
Available documentation clouds establishment of baseline |
M: above 75% complete |
Likely |
|
Project Scope Creep |
L: Scope generally defined and subject to revision |
Unlikely |
|
Consultant Project Deliverables unclear |
L: Well defined |
Unlikely |
|
Vendor Project Deliverables |
M: Estimated, not clearly defined |
Somewhat likely |
|
|
|
|
|
Cost Estimates Unrealistic |
L: Thoroughly predicted by industry experts using proven practices to 15% margin of error |
Unlikely |
|
Timeline Estimates Unrealistic |
M: Timeline assumes no derailment |
Somewhat likely |
|
Number of Team Members Unknowledgeable of Business |
L: Team well versed in business operations impacted by technology |
Unlikely |
|
Project Leadership |
|
|
|
Steering Committee existence |
L: Identified and enthusiastic |
Unlikely |
|
Absence of Commitment Level/Attitude of Management |
L: Understands value & supports project |
Unlikely |
|
Absence of Commitment Level/Attitude of Users |
L: Understands value & supports project |
Unlikely |
|
Absence of Mid-Management Commitment |
L: Most understand value & support project |
Unlikely |
|
Project Staffing |
|
|
|
Project Team Availability |
M: Distributed team makes availability questionable |
Somewhat likely |
|
Physical Location of Team prevents effective management |
M: Team is dispersed among several sites |
Likely |
|
Project Team’s Shared Work Experience creates poor working relationship |
M: Some have worked together before |
Somewhat likely |
|
Weak User Participation on Project Team |
L: Users are part-time team members |
Unlikely |
|
Project Management |
|
|
|
Procurement |
L: Procurement Methodology familiar to team |
Unlikely |
|
Methodology Used foreign to team |
|
|
|
Change Management Procedures undefined |
L: Well-defined |
Unlikely |
|
Quality Management Procedures unclear |
L: Well-defined and accepted |
Unlikely |
|
Software Vendor |
|
|
|
Number of Times Team Has Done Prior Work with Vendor Creates Foreign Relationship |
H: Never |
Certainty |
|
Team’s Lack of Knowledge of Package |
M: Conceptual understanding |
Somewhat likely |
|
|
|
|
|
|
|
|
|
Poor Functional Match of website to Initial System Requirements |
L: Minimal customization required |
Unlikely |
The following are the key factors that will help to determine whether the HWE accessories website project is successful.
1) A standing final contract.
The contract should be a written document that includes all the agreed upon items with the software provider. Clearly defined project items goes a long way to assist the project managers since they now have leverage that they can hold the providers accountable if any conditions are not met.
A proper plan of the project should be created to show how various issues will be handled, the communication channels to be used during the project undertaking and a clear statement of the project schedule. The whole team should review this to make sure they understand the agreed upon terms and can be referred to in case of any deviation.
3) Defining the project scope.
This is a document that entails what is and is not in the project. The steering committee should approve this before the execution stage of the project begins.
4) Testing.
This is a crucial phase since it helps all users to understand the application functionality. It helps gauge if the application or website created is performing as expected or whether further modifications need to be made before the actual live launch of the website. Security is also tested thoroughly to ensure people with malicious intent don’t cause harm or losses to the company.
5) Verification.
Everyone who was involved in the development of the website should check and countercheck if everything was completed. All the deliverables and allocated tasks should be complete as a single error could lead to the whole project failure. Staff who have deep knowledge of the website’s business operations should assist users during the first days to ensure they are well acquainted with the site. Help stations or lines should be set up to offer any assistance required.
6) Communication and follow up reports.
Lack of communication is the main problem facing projects that have been noted to be having problems. The committee should be informed, and meetings held from time to time to perform reviews on the website. This also helps to identify the necessary updates required to keep the site running effectively.
References:
CISA Certification Job Practice. (n.d.). Retrieved from ISACA: http://www.isaca.org/Certification/CISA-Certified-Information-Systems-Auditor/Job-Practice-Areas/Pages/CISA-Job-Practice-Areas.aspx
