Assignment Prompt & Instructions
– ## BIT-415-RS-Global-Treps-Project-Resource-Assignments.pdf
– ## BIT-415-RS-Global-Treps-Project-Risk-Register-Template.xlsx
**## BIT-415-RS-Global-Treps-Project-Resource-Assignments.pdf**
Lowest Level Task Resource Assignments
Finalize project team Project Manager
Develop project charter Project Manager
Develop scope statement Project Manager
Develop and refine other plans Project Manager
Conduct research for income mechanism into Global Treps Support Team Manager
Evaluate current systems Support Team Manager, System Test Engineer
Define requirements Website Developer
Define user requirements Website Developer
Define content requirements Website Developer
Define system requirements Website Developer
Define server owner requirements Website Developer
Define specific functionality Support Team Manager, System Test Engineer
Define risks and risk management approach Project Manager, Website Developer
Develop project plan Project Manager
Brief web development team Project Manager
Create templates and guidelines for running events Support Team Manager, System Test Engineer
Design donation portal for potential investors Website Developer
Design a submission page for new ideas on products/services Website Developer
Design registration for organizations to develop custom websites Website Developer
Design tracking system Website Developer
Design incentive system Website Developer
Develop donation portal for potential investors Website Developer
Develop a submission page for new ideas on products/services Website Developer
Develop a registration page for organizations to develop custom websites Website Developer
Develop tracking system Website Developer
Develop incentive system Website Developer
Upload templates and guidelines Support Team Manager
Conduct Verification Testing System Test Engineer
Conduct Validation Testing System Test Engineer
Conduct Pilot Testing Support Team Manager, System Test Engineer
Hold Four Events (in different countries) to Test Site Functionality Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Obtain Feedback Project Manager
Implement Changes Website Developer
Move site to production server System Test Engineer
Determine roll out schedule Project Manager
Communicate roll out plan to users Project Manager
Conduct user training System Test Engineer
Deploy system System Test Engineer
Determine what support resources are needed Support Team Manager, System Test Engineer
Make appropriate staffing changes Project Manager
Determine method that users will attain support Project Manager, Website Developer, Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Determine support process Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Launch support Website Developer, System Test Engineer, Support Team Manager, Event Runner: Ethiopia
Hold formal customer review Project Manager
Prepare final report and presentation Project Manager
Deliver final report and presentation Project Manager
**## BIT-415-RS-Global-Treps-Project-Risk-Register-Template.xlsx**
## Template
| | | | | | | | | | | | |
| — | — | — | — | — | — | — | — | — | — | — | — |
| | Risk Register |
| No. | Risk | Description | Category | Root Cause | Triggers | Potential Responses | Risk Owner<br>(select from Microsoft Project Resource Sheet) | Probability<br>(High, Med, Low) | Impact Assessment<br>(High, Med, Low) | Reason for Impact Assessment Selection | Status |
| R1 | Project Team Selection | May not get functional management support for project team member assignments to the project | Planning | Not enough coordination with functional management | Poor lateral communication | | | Medium | | | Open |
| R2 | Senior management Approval of Plans | May not get senior management buy-in on other plans | Planning | Not enough coordination with senior management | Poor upward communication | | | Low | | | Open |
| R3 | Server owner requirements definition | May not be able to accurately define server requirements due to implementation of new technologies | Executing-Web Site Concept | Not enough technical documentation available from server hardware suppliers | Inadequate supplier support | | | Medium | | | Open |
| R4 | Registration for classes and programs design undefined | May not be able to accurately design "Registration for classes and programs" modules due to complex algorithm requirements | Executing-Web Site Design | Programmer/ Analyst unfamiliar with algorithm | Increased Programmer/Analyst anxiety | | | Low | | | Open |
| R5 | "Develop registration for classes and programs" code incomplete | "Develop registration for classes and programs" code completion may be delayed | Executing-Web Site Development | Programmer/ Analyst unfamiliar with algorithm | Delay in completing code walkthroughs | | | High | | | Open |
| R6 | Verification Testing delayed | Verification Testing delayed due to errors in code regression testing | Executing-Web Site Development | Code incompatibilities | Test Plans unapproved | | | High | | | Open |
| R7 | Uncooperative Users | Users may not cooperate and be difficult during training | Executing-Roll Out | No plan for conflict management | Poor team dynamics | | | Low | | | Open |
| R8 | Support process definition | May be challenges defining the technical support processes | Executing-Support | Support team unfamiliar with new software product line | New intranet software products causing anxiety with field support personnel | | | Medium | | | Open |
| R9 | Customer not willing to hold formal customer review | Customer may refuse to hold formal customer review due to unavailability or product issues | Controlling | Lack of communication from Customer | Customer not communicating and/or not committing to "formal customer review" date | | | High | | | Open |
| R10 | Customer not willing to hear final presentation | Customer may refuse to hear final presentation due to unavailability or product issues | Closing | Lack of communication from Customer | Customer not communicating and/or not committing to "final presentation" date | | | Low | | | Open |
**## BIT-415-RS-Global-Treps-Project-Risk-Register-Template.xlsx**
## Template
| | | | | | | | | | | | |
| — | — | — | — | — | — | — | — | — | — | — | — |
| | Risk Register |
| No. | Risk | Description | Category | Root Cause | Triggers | Potential Responses | Risk Owner<br>(select from Microsoft Project Resource Sheet) | Probability<br>(High, Med, Low) | Impact Assessment<br>(High, Med, Low) | Reason for Impact Assessment Selection | Status |
| R1 | Project Team Selection | May not get functional management support for project team member assignments to the project | Planning | Not enough coordination with functional management | Poor lateral communication | | | Medium | | | Open |
| R2 | Senior management Approval of Plans | May not get senior management buy-in on other plans | Planning | Not enough coordination with senior management | Poor upward communication | | | Low | | | Open |
| R3 | Server owner requirements definition | May not be able to accurately define server requirements due to implementation of new technologies | Executing-Web Site Concept | Not enough technical documentation available from server hardware suppliers | Inadequate supplier support | | | Medium | | | Open |
| R4 | Registration for classes and programs design undefined | May not be able to accurately design "Registration for classes and programs" modules due to complex algorithm requirements | Executing-Web Site Design | Programmer/ Analyst unfamiliar with algorithm | Increased Programmer/Analyst anxiety | | | Low | | | Open |
| R5 | "Develop registration for classes and programs" code incomplete | "Develop registration for classes and programs" code completion may be delayed | Executing-Web Site Development | Programmer/ Analyst unfamiliar with algorithm | Delay in completing code walkthroughs | | | High | | | Open |
| R6 | Verification Testing delayed | Verification Testing delayed due to errors in code regression testing | Executing-Web Site Development | Code incompatibilities | Test Plans unapproved | | | High | | | Open |
| R7 | Uncooperative Users | Users may not cooperate and be difficult during training | Executing-Roll Out | No plan for conflict management | Poor team dynamics | | | Low | | | Open |
| R8 | Support process definition | May be challenges defining the technical support processes | Executing-Support | Support team unfamiliar with new software product line | New intranet software products causing anxiety with field support personnel | | | Medium | | | Open |
| R9 | Customer not willing to hold formal customer review | Customer may refuse to hold formal customer review due to unavailability or product issues | Controlling | Lack of communication from Customer | Customer not communicating and/or not committing to "formal customer review" date | | | High | | | Open |
| R10 | Customer not willing to hear final presentation | Customer may refuse to hear final presentation due to unavailability or product issues | Closing | Lack of communication from Customer | Customer not communicating and/or not committing to "final presentation" date | | | Low | | | Open |
**## BIT-415-RS-Global-Treps-Project-Resource-Assignments.pdf**
Lowest Level Task Resource Assignments
Finalize project team Project Manager
Develop project charter Project Manager
Develop scope statement Project Manager
Develop and refine other plans Project Manager
Conduct research for income mechanism into Global Treps Support Team Manager
Evaluate current systems Support Team Manager, System Test Engineer
Define requirements Website Developer
Define user requirements Website Developer
Define content requirements Website Developer
Define system requirements Website Developer
Define server owner requirements Website Developer
Define specific functionality Support Team Manager, System Test Engineer
Define risks and risk management approach Project Manager, Website Developer
Develop project plan Project Manager
Brief web development team Project Manager
Create templates and guidelines for running events Support Team Manager, System Test Engineer
Design donation portal for potential investors Website Developer
Design a submission page for new ideas on products/services Website Developer
Design registration for organizations to develop custom websites Website Developer
Design tracking system Website Developer
Design incentive system Website Developer
Develop donation portal for potential investors Website Developer
Develop a submission page for new ideas on products/services Website Developer
Develop a registration page for organizations to develop custom websites Website Developer
Develop tracking system Website Developer
Develop incentive system Website Developer
Upload templates and guidelines Support Team Manager
Conduct Verification Testing System Test Engineer
Conduct Validation Testing System Test Engineer
Conduct Pilot Testing Support Team Manager, System Test Engineer
Hold Four Events (in different countries) to Test Site Functionality Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Obtain Feedback Project Manager
Implement Changes Website Developer
Move site to production server System Test Engineer
Determine roll out schedule Project Manager
Communicate roll out plan to users Project Manager
Conduct user training System Test Engineer
Deploy system System Test Engineer
Determine what support resources are needed Support Team Manager, System Test Engineer
Make appropriate staffing changes Project Manager
Determine method that users will attain support Project Manager, Website Developer, Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Determine support process Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Launch support Website Developer, System Test Engineer, Support Team Manager, Event Runner: Ethiopia
Hold formal customer review Project Manager
Prepare final report and presentation Project Manager
Deliver final report and presentation Project Manager
**## BIT-415-RS-Global-Treps-Project-Risk-Register-Template.xlsx**
## Template
| | | | | | | | | | | | |
| — | — | — | — | — | — | — | — | — | — | — | — |
| | Risk Register |
| No. | Risk | Description | Category | Root Cause | Triggers | Potential Responses | Risk Owner<br>(select from Microsoft Project Resource Sheet) | Probability<br>(High, Med, Low) | Impact Assessment<br>(High, Med, Low) | Reason for Impact Assessment Selection | Status |
| R1 | Project Team Selection | May not get functional management support for project team member assignments to the project | Planning | Not enough coordination with functional management | Poor lateral communication | | | Medium | | | Open |
| R2 | Senior management Approval of Plans | May not get senior management buy-in on other plans | Planning | Not enough coordination with senior management | Poor upward communication | | | Low | | | Open |
| R3 | Server owner requirements definition | May not be able to accurately define server requirements due to implementation of new technologies | Executing-Web Site Concept | Not enough technical documentation available from server hardware suppliers | Inadequate supplier support | | | Medium | | | Open |
| R4 | Registration for classes and programs design undefined | May not be able to accurately design "Registration for classes and programs" modules due to complex algorithm requirements | Executing-Web Site Design | Programmer/ Analyst unfamiliar with algorithm | Increased Programmer/Analyst anxiety | | | Low | | | Open |
| R5 | "Develop registration for classes and programs" code incomplete | "Develop registration for classes and programs" code completion may be delayed | Executing-Web Site Development | Programmer/ Analyst unfamiliar with algorithm | Delay in completing code walkthroughs | | | High | | | Open |
| R6 | Verification Testing delayed | Verification Testing delayed due to errors in code regression testing | Executing-Web Site Development | Code incompatibilities | Test Plans unapproved | | | High | | | Open |
| R7 | Uncooperative Users | Users may not cooperate and be difficult during training | Executing-Roll Out | No plan for conflict management | Poor team dynamics | | | Low | | | Open |
| R8 | Support process definition | May be challenges defining the technical support processes | Executing-Support | Support team unfamiliar with new software product line | New intranet software products causing anxiety with field support personnel | | | Medium | | | Open |
| R9 | Customer not willing to hold formal customer review | Customer may refuse to hold formal customer review due to unavailability or product issues | Controlling | Lack of communication from Customer | Customer not communicating and/or not committing to "formal customer review" date | | | High | | | Open |
| R10 | Customer not willing to hear final presentation | Customer may refuse to hear final presentation due to unavailability or product issues | Closing | Lack of communication from Customer | Customer not communicating and/or not committing to "final presentation" date | | | Low | | | Open |
**## BIT-415-RS-Global-Treps-Project-Resource-Assignments.pdf**
Lowest Level Task Resource Assignments
Finalize project team Project Manager
Develop project charter Project Manager
Develop scope statement Project Manager
Develop and refine other plans Project Manager
Conduct research for income mechanism into Global Treps Support Team Manager
Evaluate current systems Support Team Manager, System Test Engineer
Define requirements Website Developer
Define user requirements Website Developer
Define content requirements Website Developer
Define system requirements Website Developer
Define server owner requirements Website Developer
Define specific functionality Support Team Manager, System Test Engineer
Define risks and risk management approach Project Manager, Website Developer
Develop project plan Project Manager
Brief web development team Project Manager
Create templates and guidelines for running events Support Team Manager, System Test Engineer
Design donation portal for potential investors Website Developer
Design a submission page for new ideas on products/services Website Developer
Design registration for organizations to develop custom websites Website Developer
Design tracking system Website Developer
Design incentive system Website Developer
Develop donation portal for potential investors Website Developer
Develop a submission page for new ideas on products/services Website Developer
Develop a registration page for organizations to develop custom websites Website Developer
Develop tracking system Website Developer
Develop incentive system Website Developer
Upload templates and guidelines Support Team Manager
Conduct Verification Testing System Test Engineer
Conduct Validation Testing System Test Engineer
Conduct Pilot Testing Support Team Manager, System Test Engineer
Hold Four Events (in different countries) to Test Site Functionality Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Obtain Feedback Project Manager
Implement Changes Website Developer
Move site to production server System Test Engineer
Determine roll out schedule Project Manager
Communicate roll out plan to users Project Manager
Conduct user training System Test Engineer
Deploy system System Test Engineer
Determine what support resources are needed Support Team Manager, System Test Engineer
Make appropriate staffing changes Project Manager
Determine method that users will attain support Project Manager, Website Developer, Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Determine support process Support Team Manager, System Test Engineer, Event Runner: Ethiopia
Launch support Website Developer, System Test Engineer, Support Team Manager, Event Runner: Ethiopia
Hold formal customer review Project Manager
Prepare final report and presentation Project Manager
Deliver final report and presentation Project Manager
**## BIT-415-RS-Global-Treps-Project-Risk-Register-Template.xlsx**
## Template
| | | | | | | | | | | | |
| — | — | — | — | — | — | — | — | — | — | — | — |
| | Risk Register |
| No. | Risk | Description | Category | Root Cause | Triggers | Potential Responses | Risk Owner<br>(select from Microsoft Project Resource Sheet) | Probability<br>(High, Med, Low) | Impact Assessment<br>(High, Med, Low) | Reason for Impact Assessment Selection | Status |
| R1 | Project Team Selection | May not get functional management support for project team member assignments to the project | Planning | Not enough coordination with functional management | Poor lateral communication | | | Medium | | | Open |
| R2 | Senior management Approval of Plans | May not get senior management buy-in on other plans | Planning | Not enough coordination with senior management | Poor upward communication | | | Low | | | Open |
| R3 | Server owner requirements definition | May not be able to accurately define server requirements due to implementation of new technologies | Executing-Web Site Concept | Not enough technical documentation available from server hardware suppliers | Inadequate supplier support | | | Medium | | | Open |
| R4 | Registration for classes and programs design undefined | May not be able to accurately design "Registration for classes and programs" modules due to complex algorithm requirements | Executing-Web Site Design | Programmer/ Analyst unfamiliar with algorithm | Increased Programmer/Analyst anxiety | | | Low | | | Open |
| R5 | "Develop registration for classes and programs" code incomplete | "Develop registration for classes and programs" code completion may be delayed | Executing-Web Site Development | Programmer/ Analyst unfamiliar with algorithm | Delay in completing code walkthroughs | | | High | | | Open |
| R6 | Verification Testing delayed | Verification Testing delayed due to errors in code regression testing | Executing-Web Site Development | Code incompatibilities | Test Plans unapproved | | | High | | | Open |
| R7 | Uncooperative Users | Users may not cooperate and be difficult during training | Executing-Roll Out | No plan for conflict management | Poor team dynamics | | | Low | | | Open |
| R8 | Support process definition | May be challenges defining the technical support processes | Executing-Support | Support team unfamiliar with new software product line | New intranet software products causing anxiety with field support personnel | | | Medium | | | Open |
| R9 | Customer not willing to hold formal customer review | Customer may refuse to hold formal customer review due to unavailability or product issues | Controlling | Lack of communication from Customer | Customer not communicating and/or not committing to "formal customer review" date | | | High | | | Open |
| R10 | Customer not willing to hear final presentation | Customer may refuse to hear final presentation due to unavailability or product issues | Closing | Lack of communication from Customer | Customer not communicating and/or not committing to "final presentation" date | | | Low | | | Open |
– 1
– 2