[Solved] BMw7inAsg

Assignment Prompt & Instructions

– ## ProjectCommunicationsManagementMatrix-Template.xls – ## questionWeek7IndividualAssignmentinstruction.docx – ## completedwk2GroupCharterforGroup6WK2.docx **## ProjectCommunicationsManagementMatrix-Template.xls** [removed] **## questionWeek7IndividualAssignmentinstruction.docx** Week 7 Individual Assignment: Project Communications Management Matrix Hide Assignment Information Turnitin™ Turnitin™ enabledThis assignment will be submitted to Turnitin™. Instructions Purpose The purpose of this individual assignment is to develop a project communications management matrix to use in communicating with the project stakeholders identified in Week 2. Background Your team has selected a project, identified project stakeholders, and created a project charter to officially begin the project planning process. You now want to establish a plan for communicating with your stakeholders. The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, and carried out—and then monitored for effectiveness. The result of the plan communications management process is the project communications management plan. Many project teams summarize the content of the communications management plan in a project communications management matrix. Assignment Prompt Once you have read this week's assigned reading, reviewed the project documentation created for your group's project in earlier sessions, and have a good understanding of the processes used in developing the project communications management plan, you should develop a communications management matrix using this project communications management template. This template is in MS Excel and has notes in each cell to help you determine what information to include under each column heading—just hover over the red triangle of each heading. Complete this matrix for at least five key stakeholders or stakeholder groups (if you have multiple stakeholders with identical communications/information requirements). Assignment Instructions Follow these instructions to complete and submit your assignment. Review the grading rubric attached to this assignment to understand how you will be graded. Using the project communications management matrix template provided, enter communications management information for at least five stakeholders or stakeholder groups. Save the template as Week7IA_yourlastname and submit as an MS Excel file Have one member of your group upload the completed assignment in MS Word to the assignment folder. **## completedwk2GroupCharterforGroup6WK2.docx** | | | | | — | — | — | | | | | **Team Charter: Collaborative Project for BMGT 487** **_Purpose of the Team Charter:_** Our goal is to institute a precise, straightforward, and unified communication structure, concurrently delineating roles and responsibilities grounded in individual strengths and weaknesses. **_Roles and Responsibilities:_** · **Team Lead:** Gabrielle Sims · Responsible for overall project coordination and communication. · Ensures adherence to timelines and quality standards. · **Planner/Scheduler and Communication:** Brittainy Kenner · Responsible for defining project task and leads the maintenance of the schedule · Assists in overall communication with the team · **Business analyst:** Prosper Moses · Assists in analysis of expectations and interests · Provides input on project goals and scope · **Resource Manager:** Danielle Tubbs · Responsible for insight into available resources and usage · Provides input on project goals and scope **_Communications Preferences:_** 1) Preferred communication tools: Email, Teams Messenger, Zoom, 2) Response time expectations: 24 hours **_Contact Information:_** 1. **Planner/scheduler and Communication Manager:** brittainy27@gmail.com 2. **Team Lead:** gabwsims@gmail.com 3. **Business analyst:** prosperpm55@yahoo.com 4. **Resource Manager:** dle8919@yahoo.com **_Individual Strengths and Weaknesses/Opportunities for Individual Development:_** | | | | | — | — | — | | **Team Member** | **Strengths** | **Weaknesses** | | Brittainy Kenner | Proficient in project scheduling and planning<br>Effective communication abilities<br>Organizational skills | Conflict resolution<br>Tendency to micromanage tasks | | Prosper Moses | Writing, PowerPoint presentation, conflict resolution, team player | Multitasking | | Gabrielle Sims | Organization, writing skills, coordination | Public speaking, self-critical, perfectionism | | Danielle Tubbs | TBD | TBD | **_Management of Group Project Work:_** 5. **Virtual Meetings:** · Frequency: Every Wednesday at 7pm EST · Platforms: Teams, Zoom · Agendas: Agendas will be prepared and distributed before each meeting. 6. **Documentation Management:**(UMGC Microsoft Office 365; Final submissions in Doc Locker) · Word · Excel · PowerPoint **_Project Deliverables and Milestones:_** 3) **Project Description (Week 3):** a) Deliverable: Complete an approved project description document. b) Milestone: i) Begin drafting the Project description by Friday of week 2. ii) Conduct a team review and incorporate feedback by 8 pm (Est) on Tuesday 4) **Stakeholder Analysis (Week 4):** a) Deliverable: Stakeholder analysis report identifying key stakeholders and their interests. b) Milestone: i) Begin stakeholder identification by Friday of week 3. ii) Present Stakeholder analysis to the team by the end of Week 4 by 8 pm 5) **Project Charter (Week 4):** a) Deliverable: Formalized project charter document outlining project goals, scope, and key stakeholders. b) Milestone: i) Develop the initial draft of the Project Charter by Friday of Week 3. ii) Approval and project charter sign-off by the end of Week 4 by 8 pm. 6) **Project Scope Statement/WBS (Week 5):** a) Deliverable: Project scope statement and Work Breakdown Structure (WBS) detailing project tasks. b) Milestone: i) Initiate the development of the Project Scope Statement and WBS by Friday of Week 4. ii) Review and finalize the Scope Statement and WBS by the end of Week 5 by 8 pm. 7) **Schedule Model (Week 7):** a) Deliverable: Detailed project schedule model outlining task dependencies and timelines. b) Milestone: i) Begin creating the schedule by Friday of Week 6. ii) Conduct a team review and make necessary adjustments by the end of Week 7 by 8 pm. 8) **Project Activity Costs and Resources (Week 7):** a) Deliverable: Document specifying project activity costs and required resources. b) Milestone: i) Initiate cost and resource estimation by Friday of Week 6. ii) Present the Activity Cost and Resource Plan to the team for validation and adjustments by the end of Week 7 by 8 pm. 9) **Communications Management Matrix (Week 7):** a) Deliverable: Communications management matrix detailing communication plans and channels. b) Milestone: i) Develop the Communications Management Matrix by Friday of Week 6. ii) Conduct a team review, incorporate feedback, and finalize the matrix by the end of Week 7 by 8 pm. **_Review and Approval Process:_** 1) **Initiation:** · The project lead promptly initiates the review process by 11:59 pm on Monday. 2) **Roles Assignment:** · Roles for document approval are assigned, leveraging team members' expertise. 3) **Comprehensive Criteria:** · Reviewers rigorously evaluate deliverables against course rubric. 4) **Individual Assessments:** · Each reviewer conducts individual assessments by 6:00 pm on Wednesday, followed by a collaborative team meeting at 7:00 pm on Wednesday. 5) **Iterative Revisions:** · Document undergoes meticulous revisions based on team feedback. 6) **Final Approval:** · The project lead or manager conducts a final review for approval. 7) **Decision-Making:** · Approval or additional revisions are decided upon professor feedback. 8) **Documented Record:** · Approved documents are documented and securely stored for a comprehensive record. **_Code of Conduct:_** 9) Define acceptable behavior and communication. · All team members are expected to maintain high professionalism and courtesy in all their interactions. It is crucial to maintain a positive tone and refrain from using offensive language or making discriminatory remarks. Communication should help move the project forward in a positive way. · All team members are expected to contribute equally unless previously agreed upon through communication with the team notwithstanding emergencies. In such an instance, it is understood that others will have an increased workload. 10) Encourage open communication and mutual respect. · Embrace open communication by actively engaging in team discussions and contributing ideas. Recognize and value different viewpoints, creating an inclusive atmosphere that values everyone's input. It is important to listen respectfully and acknowledge different opinions. · If circumstances occur that will impede a team member’s contribution, communication with the rest of the team or the professor will occur promptly. 11) Address conflicts promptly and constructively. · Team members are encouraged to address any concerns when conflicts arise promptly and constructively. Use specific channels like team meetings or designated mediators to resolve conflicts. We aim to discover practical solutions that enhance the team's overall success through collaboration. · If team members are not responsive in the timeframe, the professor will be notified and asked to assist as soon as it becomes apparent. | | | | | — | — | — | | | | | **## completedwk2GroupCharterforGroup6WK2.docx** | | | | | — | — | — | | | | | **Team Charter: Collaborative Project for BMGT 487** **_Purpose of the Team Charter:_** Our goal is to institute a precise, straightforward, and unified communication structure, concurrently delineating roles and responsibilities grounded in individual strengths and weaknesses. **_Roles and Responsibilities:_** · **Team Lead:** Gabrielle Sims · Responsible for overall project coordination and communication. · Ensures adherence to timelines and quality standards. · **Planner/Scheduler and Communication:** Brittainy Kenner · Responsible for defining project task and leads the maintenance of the schedule · Assists in overall communication with the team · **Business analyst:** Prosper Moses · Assists in analysis of expectations and interests · Provides input on project goals and scope · **Resource Manager:** Danielle Tubbs · Responsible for insight into available resources and usage · Provides input on project goals and scope **_Communications Preferences:_** 1) Preferred communication tools: Email, Teams Messenger, Zoom, 2) Response time expectations: 24 hours **_Contact Information:_** 1. **Planner/scheduler and Communication Manager:** brittainy27@gmail.com 2. **Team Lead:** gabwsims@gmail.com 3. **Business analyst:** prosperpm55@yahoo.com 4. **Resource Manager:** dle8919@yahoo.com **_Individual Strengths and Weaknesses/Opportunities for Individual Development:_** | | | | | — | — | — | | **Team Member** | **Strengths** | **Weaknesses** | | Brittainy Kenner | Proficient in project scheduling and planning<br>Effective communication abilities<br>Organizational skills | Conflict resolution<br>Tendency to micromanage tasks | | Prosper Moses | Writing, PowerPoint presentation, conflict resolution, team player | Multitasking | | Gabrielle Sims | Organization, writing skills, coordination | Public speaking, self-critical, perfectionism | | Danielle Tubbs | TBD | TBD | **_Management of Group Project Work:_** 5. **Virtual Meetings:** · Frequency: Every Wednesday at 7pm EST · Platforms: Teams, Zoom · Agendas: Agendas will be prepared and distributed before each meeting. 6. **Documentation Management:**(UMGC Microsoft Office 365; Final submissions in Doc Locker) · Word · Excel · PowerPoint **_Project Deliverables and Milestones:_** 3) **Project Description (Week 3):** a) Deliverable: Complete an approved project description document. b) Milestone: i) Begin drafting the Project description by Friday of week 2. ii) Conduct a team review and incorporate feedback by 8 pm (Est) on Tuesday 4) **Stakeholder Analysis (Week 4):** a) Deliverable: Stakeholder analysis report identifying key stakeholders and their interests. b) Milestone: i) Begin stakeholder identification by Friday of week 3. ii) Present Stakeholder analysis to the team by the end of Week 4 by 8 pm 5) **Project Charter (Week 4):** a) Deliverable: Formalized project charter document outlining project goals, scope, and key stakeholders. b) Milestone: i) Develop the initial draft of the Project Charter by Friday of Week 3. ii) Approval and project charter sign-off by the end of Week 4 by 8 pm. 6) **Project Scope Statement/WBS (Week 5):** a) Deliverable: Project scope statement and Work Breakdown Structure (WBS) detailing project tasks. b) Milestone: i) Initiate the development of the Project Scope Statement and WBS by Friday of Week 4. ii) Review and finalize the Scope Statement and WBS by the end of Week 5 by 8 pm. 7) **Schedule Model (Week 7):** a) Deliverable: Detailed project schedule model outlining task dependencies and timelines. b) Milestone: i) Begin creating the schedule by Friday of Week 6. ii) Conduct a team review and make necessary adjustments by the end of Week 7 by 8 pm. 8) **Project Activity Costs and Resources (Week 7):** a) Deliverable: Document specifying project activity costs and required resources. b) Milestone: i) Initiate cost and resource estimation by Friday of Week 6. ii) Present the Activity Cost and Resource Plan to the team for validation and adjustments by the end of Week 7 by 8 pm. 9) **Communications Management Matrix (Week 7):** a) Deliverable: Communications management matrix detailing communication plans and channels. b) Milestone: i) Develop the Communications Management Matrix by Friday of Week 6. ii) Conduct a team review, incorporate feedback, and finalize the matrix by the end of Week 7 by 8 pm. **_Review and Approval Process:_** 1) **Initiation:** · The project lead promptly initiates the review process by 11:59 pm on Monday. 2) **Roles Assignment:** · Roles for document approval are assigned, leveraging team members' expertise. 3) **Comprehensive Criteria:** · Reviewers rigorously evaluate deliverables against course rubric. 4) **Individual Assessments:** · Each reviewer conducts individual assessments by 6:00 pm on Wednesday, followed by a collaborative team meeting at 7:00 pm on Wednesday. 5) **Iterative Revisions:** · Document undergoes meticulous revisions based on team feedback. 6) **Final Approval:** · The project lead or manager conducts a final review for approval. 7) **Decision-Making:** · Approval or additional revisions are decided upon professor feedback. 8) **Documented Record:** · Approved documents are documented and securely stored for a comprehensive record. **_Code of Conduct:_** 9) Define acceptable behavior and communication. · All team members are expected to maintain high professionalism and courtesy in all their interactions. It is crucial to maintain a positive tone and refrain from using offensive language or making discriminatory remarks. Communication should help move the project forward in a positive way. · All team members are expected to contribute equally unless previously agreed upon through communication with the team notwithstanding emergencies. In such an instance, it is understood that others will have an increased workload. 10) Encourage open communication and mutual respect. · Embrace open communication by actively engaging in team discussions and contributing ideas. Recognize and value different viewpoints, creating an inclusive atmosphere that values everyone's input. It is important to listen respectfully and acknowledge different opinions. · If circumstances occur that will impede a team member’s contribution, communication with the rest of the team or the professor will occur promptly. 11) Address conflicts promptly and constructively. · Team members are encouraged to address any concerns when conflicts arise promptly and constructively. Use specific channels like team meetings or designated mediators to resolve conflicts. We aim to discover practical solutions that enhance the team's overall success through collaboration. · If team members are not responsive in the timeframe, the professor will be notified and asked to assist as soon as it becomes apparent. | | | | | — | — | — | | | | | **## ProjectCommunicationsManagementMatrix-Template.xls** [removed] **## questionWeek7IndividualAssignmentinstruction.docx** Week 7 Individual Assignment: Project Communications Management Matrix Hide Assignment Information Turnitin™ Turnitin™ enabledThis assignment will be submitted to Turnitin™. Instructions Purpose The purpose of this individual assignment is to develop a project communications management matrix to use in communicating with the project stakeholders identified in Week 2. Background Your team has selected a project, identified project stakeholders, and created a project charter to officially begin the project planning process. You now want to establish a plan for communicating with your stakeholders. The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, and carried out—and then monitored for effectiveness. The result of the plan communications management process is the project communications management plan. Many project teams summarize the content of the communications management plan in a project communications management matrix. Assignment Prompt Once you have read this week's assigned reading, reviewed the project documentation created for your group's project in earlier sessions, and have a good understanding of the processes used in developing the project communications management plan, you should develop a communications management matrix using this project communications management template. This template is in MS Excel and has notes in each cell to help you determine what information to include under each column heading—just hover over the red triangle of each heading. Complete this matrix for at least five key stakeholders or stakeholder groups (if you have multiple stakeholders with identical communications/information requirements). Assignment Instructions Follow these instructions to complete and submit your assignment. Review the grading rubric attached to this assignment to understand how you will be graded. Using the project communications management matrix template provided, enter communications management information for at least five stakeholders or stakeholder groups. Save the template as Week7IA_yourlastname and submit as an MS Excel file Have one member of your group upload the completed assignment in MS Word to the assignment folder. **## completedwk2GroupCharterforGroup6WK2.docx** | | | | | — | — | — | | | | | **Team Charter: Collaborative Project for BMGT 487** **_Purpose of the Team Charter:_** Our goal is to institute a precise, straightforward, and unified communication structure, concurrently delineating roles and responsibilities grounded in individual strengths and weaknesses. **_Roles and Responsibilities:_** · **Team Lead:** Gabrielle Sims · Responsible for overall project coordination and communication. · Ensures adherence to timelines and quality standards. · **Planner/Scheduler and Communication:** Brittainy Kenner · Responsible for defining project task and leads the maintenance of the schedule · Assists in overall communication with the team · **Business analyst:** Prosper Moses · Assists in analysis of expectations and interests · Provides input on project goals and scope · **Resource Manager:** Danielle Tubbs · Responsible for insight into available resources and usage · Provides input on project goals and scope **_Communications Preferences:_** 1) Preferred communication tools: Email, Teams Messenger, Zoom, 2) Response time expectations: 24 hours **_Contact Information:_** 1. **Planner/scheduler and Communication Manager:** brittainy27@gmail.com 2. **Team Lead:** gabwsims@gmail.com 3. **Business analyst:** prosperpm55@yahoo.com 4. **Resource Manager:** dle8919@yahoo.com **_Individual Strengths and Weaknesses/Opportunities for Individual Development:_** | | | | | — | — | — | | **Team Member** | **Strengths** | **Weaknesses** | | Brittainy Kenner | Proficient in project scheduling and planning<br>Effective communication abilities<br>Organizational skills | Conflict resolution<br>Tendency to micromanage tasks | | Prosper Moses | Writing, PowerPoint presentation, conflict resolution, team player | Multitasking | | Gabrielle Sims | Organization, writing skills, coordination | Public speaking, self-critical, perfectionism | | Danielle Tubbs | TBD | TBD | **_Management of Group Project Work:_** 5. **Virtual Meetings:** · Frequency: Every Wednesday at 7pm EST · Platforms: Teams, Zoom · Agendas: Agendas will be prepared and distributed before each meeting. 6. **Documentation Management:**(UMGC Microsoft Office 365; Final submissions in Doc Locker) · Word · Excel · PowerPoint **_Project Deliverables and Milestones:_** 3) **Project Description (Week 3):** a) Deliverable: Complete an approved project description document. b) Milestone: i) Begin drafting the Project description by Friday of week 2. ii) Conduct a team review and incorporate feedback by 8 pm (Est) on Tuesday 4) **Stakeholder Analysis (Week 4):** a) Deliverable: Stakeholder analysis report identifying key stakeholders and their interests. b) Milestone: i) Begin stakeholder identification by Friday of week 3. ii) Present Stakeholder analysis to the team by the end of Week 4 by 8 pm 5) **Project Charter (Week 4):** a) Deliverable: Formalized project charter document outlining project goals, scope, and key stakeholders. b) Milestone: i) Develop the initial draft of the Project Charter by Friday of Week 3. ii) Approval and project charter sign-off by the end of Week 4 by 8 pm. 6) **Project Scope Statement/WBS (Week 5):** a) Deliverable: Project scope statement and Work Breakdown Structure (WBS) detailing project tasks. b) Milestone: i) Initiate the development of the Project Scope Statement and WBS by Friday of Week 4. ii) Review and finalize the Scope Statement and WBS by the end of Week 5 by 8 pm. 7) **Schedule Model (Week 7):** a) Deliverable: Detailed project schedule model outlining task dependencies and timelines. b) Milestone: i) Begin creating the schedule by Friday of Week 6. ii) Conduct a team review and make necessary adjustments by the end of Week 7 by 8 pm. 8) **Project Activity Costs and Resources (Week 7):** a) Deliverable: Document specifying project activity costs and required resources. b) Milestone: i) Initiate cost and resource estimation by Friday of Week 6. ii) Present the Activity Cost and Resource Plan to the team for validation and adjustments by the end of Week 7 by 8 pm. 9) **Communications Management Matrix (Week 7):** a) Deliverable: Communications management matrix detailing communication plans and channels. b) Milestone: i) Develop the Communications Management Matrix by Friday of Week 6. ii) Conduct a team review, incorporate feedback, and finalize the matrix by the end of Week 7 by 8 pm. **_Review and Approval Process:_** 1) **Initiation:** · The project lead promptly initiates the review process by 11:59 pm on Monday. 2) **Roles Assignment:** · Roles for document approval are assigned, leveraging team members' expertise. 3) **Comprehensive Criteria:** · Reviewers rigorously evaluate deliverables against course rubric. 4) **Individual Assessments:** · Each reviewer conducts individual assessments by 6:00 pm on Wednesday, followed by a collaborative team meeting at 7:00 pm on Wednesday. 5) **Iterative Revisions:** · Document undergoes meticulous revisions based on team feedback. 6) **Final Approval:** · The project lead or manager conducts a final review for approval. 7) **Decision-Making:** · Approval or additional revisions are decided upon professor feedback. 8) **Documented Record:** · Approved documents are documented and securely stored for a comprehensive record. **_Code of Conduct:_** 9) Define acceptable behavior and communication. · All team members are expected to maintain high professionalism and courtesy in all their interactions. It is crucial to maintain a positive tone and refrain from using offensive language or making discriminatory remarks. Communication should help move the project forward in a positive way. · All team members are expected to contribute equally unless previously agreed upon through communication with the team notwithstanding emergencies. In such an instance, it is understood that others will have an increased workload. 10) Encourage open communication and mutual respect. · Embrace open communication by actively engaging in team discussions and contributing ideas. Recognize and value different viewpoints, creating an inclusive atmosphere that values everyone's input. It is important to listen respectfully and acknowledge different opinions. · If circumstances occur that will impede a team member’s contribution, communication with the rest of the team or the professor will occur promptly. 11) Address conflicts promptly and constructively. · Team members are encouraged to address any concerns when conflicts arise promptly and constructively. Use specific channels like team meetings or designated mediators to resolve conflicts. We aim to discover practical solutions that enhance the team's overall success through collaboration. · If team members are not responsive in the timeframe, the professor will be notified and asked to assist as soon as it becomes apparent. | | | | | — | — | — | | | | | **## ProjectCommunicationsManagementMatrix-Template.xls** [removed] **## questionWeek7IndividualAssignmentinstruction.docx** Week 7 Individual Assignment: Project Communications Management Matrix Hide Assignment Information Turnitin™ Turnitin™ enabledThis assignment will be submitted to Turnitin™. Instructions Purpose The purpose of this individual assignment is to develop a project communications management matrix to use in communicating with the project stakeholders identified in Week 2. Background Your team has selected a project, identified project stakeholders, and created a project charter to officially begin the project planning process. You now want to establish a plan for communicating with your stakeholders. The communications management plan is a component of the project management plan that describes how project communications will be planned, structured, and carried out—and then monitored for effectiveness. The result of the plan communications management process is the project communications management plan. Many project teams summarize the content of the communications management plan in a project communications management matrix. Assignment Prompt Once you have read this week's assigned reading, reviewed the project documentation created for your group's project in earlier sessions, and have a good understanding of the processes used in developing the project communications management plan, you should develop a communications management matrix using this project communications management template. This template is in MS Excel and has notes in each cell to help you determine what information to include under each column heading—just hover over the red triangle of each heading. Complete this matrix for at least five key stakeholders or stakeholder groups (if you have multiple stakeholders with identical communications/information requirements). Assignment Instructions Follow these instructions to complete and submit your assignment. Review the grading rubric attached to this assignment to understand how you will be graded. Using the project communications management matrix template provided, enter communications management information for at least five stakeholders or stakeholder groups. Save the template as Week7IA_yourlastname and submit as an MS Excel file Have one member of your group upload the completed assignment in MS Word to the assignment folder. **## completedwk2GroupCharterforGroup6WK2.docx** | | | | | — | — | — | | | | | **Team Charter: Collaborative Project for BMGT 487** **_Purpose of the Team Charter:_** Our goal is to institute a precise, straightforward, and unified communication structure, concurrently delineating roles and responsibilities grounded in individual strengths and weaknesses. **_Roles and Responsibilities:_** · **Team Lead:** Gabrielle Sims · Responsible for overall project coordination and communication. · Ensures adherence to timelines and quality standards. · **Planner/Scheduler and Communication:** Brittainy Kenner · Responsible for defining project task and leads the maintenance of the schedule · Assists in overall communication with the team · **Business analyst:** Prosper Moses · Assists in analysis of expectations and interests · Provides input on project goals and scope · **Resource Manager:** Danielle Tubbs · Responsible for insight into available resources and usage · Provides input on project goals and scope **_Communications Preferences:_** 1) Preferred communication tools: Email, Teams Messenger, Zoom, 2) Response time expectations: 24 hours **_Contact Information:_** 1. **Planner/scheduler and Communication Manager:** brittainy27@gmail.com 2. **Team Lead:** gabwsims@gmail.com 3. **Business analyst:** prosperpm55@yahoo.com 4. **Resource Manager:** dle8919@yahoo.com **_Individual Strengths and Weaknesses/Opportunities for Individual Development:_** | | | | | — | — | — | | **Team Member** | **Strengths** | **Weaknesses** | | Brittainy Kenner | Proficient in project scheduling and planning<br>Effective communication abilities<br>Organizational skills | Conflict resolution<br>Tendency to micromanage tasks | | Prosper Moses | Writing, PowerPoint presentation, conflict resolution, team player | Multitasking | | Gabrielle Sims | Organization, writing skills, coordination | Public speaking, self-critical, perfectionism | | Danielle Tubbs | TBD | TBD | **_Management of Group Project Work:_** 5. **Virtual Meetings:** · Frequency: Every Wednesday at 7pm EST · Platforms: Teams, Zoom · Agendas: Agendas will be prepared and distributed before each meeting. 6. **Documentation Management:**(UMGC Microsoft Office 365; Final submissions in Doc Locker) · Word · Excel · PowerPoint **_Project Deliverables and Milestones:_** 3) **Project Description (Week 3):** a) Deliverable: Complete an approved project description document. b) Milestone: i) Begin drafting the Project description by Friday of week 2. ii) Conduct a team review and incorporate feedback by 8 pm (Est) on Tuesday 4) **Stakeholder Analysis (Week 4):** a) Deliverable: Stakeholder analysis report identifying key stakeholders and their interests. b) Milestone: i) Begin stakeholder identification by Friday of week 3. ii) Present Stakeholder analysis to the team by the end of Week 4 by 8 pm 5) **Project Charter (Week 4):** a) Deliverable: Formalized project charter document outlining project goals, scope, and key stakeholders. b) Milestone: i) Develop the initial draft of the Project Charter by Friday of Week 3. ii) Approval and project charter sign-off by the end of Week 4 by 8 pm. 6) **Project Scope Statement/WBS (Week 5):** a) Deliverable: Project scope statement and Work Breakdown Structure (WBS) detailing project tasks. b) Milestone: i) Initiate the development of the Project Scope Statement and WBS by Friday of Week 4. ii) Review and finalize the Scope Statement and WBS by the end of Week 5 by 8 pm. 7) **Schedule Model (Week 7):** a) Deliverable: Detailed project schedule model outlining task dependencies and timelines. b) Milestone: i) Begin creating the schedule by Friday of Week 6. ii) Conduct a team review and make necessary adjustments by the end of Week 7 by 8 pm. 8) **Project Activity Costs and Resources (Week 7):** a) Deliverable: Document specifying project activity costs and required resources. b) Milestone: i) Initiate cost and resource estimation by Friday of Week 6. ii) Present the Activity Cost and Resource Plan to the team for validation and adjustments by the end of Week 7 by 8 pm. 9) **Communications Management Matrix (Week 7):** a) Deliverable: Communications management matrix detailing communication plans and channels. b) Milestone: i) Develop the Communications Management Matrix by Friday of Week 6. ii) Conduct a team review, incorporate feedback, and finalize the matrix by the end of Week 7 by 8 pm. **_Review and Approval Process:_** 1) **Initiation:** · The project lead promptly initiates the review process by 11:59 pm on Monday. 2) **Roles Assignment:** · Roles for document approval are assigned, leveraging team members' expertise. 3) **Comprehensive Criteria:** · Reviewers rigorously evaluate deliverables against course rubric. 4) **Individual Assessments:** · Each reviewer conducts individual assessments by 6:00 pm on Wednesday, followed by a collaborative team meeting at 7:00 pm on Wednesday. 5) **Iterative Revisions:** · Document undergoes meticulous revisions based on team feedback. 6) **Final Approval:** · The project lead or manager conducts a final review for approval. 7) **Decision-Making:** · Approval or additional revisions are decided upon professor feedback. 8) **Documented Record:** · Approved documents are documented and securely stored for a comprehensive record. **_Code of Conduct:_** 9) Define acceptable behavior and communication. · All team members are expected to maintain high professionalism and courtesy in all their interactions. It is crucial to maintain a positive tone and refrain from using offensive language or making discriminatory remarks. Communication should help move the project forward in a positive way. · All team members are expected to contribute equally unless previously agreed upon through communication with the team notwithstanding emergencies. In such an instance, it is understood that others will have an increased workload. 10) Encourage open communication and mutual respect. · Embrace open communication by actively engaging in team discussions and contributing ideas. Recognize and value different viewpoints, creating an inclusive atmosphere that values everyone's input. It is important to listen respectfully and acknowledge different opinions. · If circumstances occur that will impede a team member’s contribution, communication with the rest of the team or the professor will occur promptly. 11) Address conflicts promptly and constructively. · Team members are encouraged to address any concerns when conflicts arise promptly and constructively. Use specific channels like team meetings or designated mediators to resolve conflicts. We aim to discover practical solutions that enhance the team's overall success through collaboration. · If team members are not responsive in the timeframe, the professor will be notified and asked to assist as soon as it becomes apparent. | | | | | — | — | — | | | | | – 1 – 2 – 3