Category: Project Management

Post #1: Parahraph for each
I was fortunate to have the opportunity to be the project manager for Week 9-10 for Team 6. This week was particularly demanding as we had several tasks at hand: finalizing the integrated project plan, refining the project schedule, preparing the sponsor presentation, and completing an individual assignment.
This week marked the culmination of our research work, which we have been diligently pursuing for the past 8-10 weeks. The primary focus was on finalizing the integrated project plan, incorporating the professor’s feedback, and adding any additional research required. As we delved into the finer details, our understanding improved, leading to better outcomes. A key personal takeaway was the importance of perseverance; efforts to resolve issues tend to pay off over time. Initially, I faced some confusion regarding certain aspects of the project, but with the team’s support, my understanding improved significantly.
In terms of the project schedule, we did not have to make major changes, thanks to the team’s consistent efforts. A few refinements were sufficient to keep us on track. The sponsor presentation was a significant milestone this week. Our team worked hard to compile and present our research and recommendations effectively. At this stage, our team was in the performing phase, where everyone was familiar with each other’s working styles, and we functioned cohesively. Completing the sponsor presentation in a timely manner to get the professor’s review was a priority.
What Went Well:
Team Energy and Morale: Despite working on the same topic for several weeks, the team’s energy remained high. We maintained our communication, trust, and respect for each other’s work and timelines, which was crucial in keeping the momentum going.
Task Delegation: I learned the importance of delegating tasks and trusting team members to complete them. Initially, I preferred handling tasks myself, but with the complexity of our project, delegation became key to our success. This also empowered team members and utilized everyone’s strengths.
Adaptability and Support: We were able to handle external crises effectively because team members had each other’s backs and completed tasks when needed. This adaptability and mutual support were vital to our smooth progress.
Communication Tools: Although coordinating meetings was challenging due to different schedules, we effectively used technology like WhatsApp and Teams to provide feedback and updates regularly. This ensured continuous communication and collaboration.
What Could Be Improved:
Team Meetings: While we adhere to our timelines, I wish we could have conducted more team meetings. Scheduling conflicts made it difficult to find a common time, but our reliance on digital communication helped mitigate this issue to some extent.
Additional Lessons Learned:
Leadership Style: I employed a blend of democratic and authoritative leadership styles. This approach allowed for team input and collaboration while ensuring decisive action and clear direction when necessary. This balance helped in making informed decisions while maintaining team cohesion and motivation.
Adaptation to Feedback: We revised the integrated project plan in response to the professor’s comments and our additional research. Additionally, each team member accepted changes suggested by others, highlighting the importance of being open to feedback and continuously improving our work.
Clarity Through Detailing: As we delved into the details of the project, we gained clearer insights, leading to better outcomes. This emphasized the value of thorough analysis and attention to detail.
Timely Execution: We achieved the timeline we set for ourselves, especially with the sponsor presentation. Completing tasks promptly for the professor’s review highlighted our commitment to deadlines and quality work.
Post#2:
I was the Project Manager for Team 4 during Weeks 9-10. This period proved to be particularly demanding, as we had several critical tasks at hand: finalising the integrated project plan, refining the project schedule, preparing the sponsor presentation, and completing an individual assignment.
These weeks marked the culmination of our extensive research efforts, which we have been diligently undertaking for the past 8-10 weeks. Our primary focus was on finalising the integrated project plan, incorporating the professor’s feedback, and supplementing it with any additional research required. As we delved deeper into the finer details, our understanding improved, leading to better outcomes.
While I am still honing my skills in Work Breakdown Structure (WBS) creation, the unwavering support and diverse expertise of our team enabled us to complete it on time and in the required format. As the youngest Project Manager in the group, it was a truly enriching experience to learn from my teammates, each bringing unique perspectives and knowledge, which instilled confidence in me to lead our team effectively and complete all group assignments smoothly.At one point, we inadvertently deleted a file, causing momentary panic. However, our team’s collective determination and collaborative effort enabled us to recover the file successfully, demonstrating our resilience in the face of challenges.
Key Takeaways:
The importance of clear and consistent communication cannot be overstated in ensuring project success and maintaining alignment among team members.
Embracing diverse perspectives and leveraging the unique strengths of each team member foster a collaborative and productive environment.
Perseverance and a solution-oriented mindset are essential when facing challenges, as they enable us to overcome obstacles and deliver high-quality work.
Effective time management and prioritisation skills are crucial for juggling multiple tasks and meeting deadlines in a demanding project environment.
What Went Well:
Effective collaboration and communication among team members fostered a supportive environment, enabling us to leverage our diverse strengths and expertise.
Our perseverance and commitment to resolving issues paid off, as we were able to address challenges and deliver high-quality work within the given timeline.
The feedback and guidance provided by the professor proved invaluable in refining our integrated project plan and ensuring we were on the right track.
Despite facing a setback with the accidental file deletion, our team’s swift and coordinated response allowed us to recover the file promptly, minimising disruption to our workflow.
As the Project Manager, I gained valuable experience in leading a team, managing tasks, and fostering an environment conducive to learning and growth.
It was a privilege to work with such a dedicated and talented team, and I look forward to building upon the lessons learned from this experience in our future endeavours.

(1) For your mock project for this class, first create a WBS using Figure 9.3 in the Verzuh text as an example. 
(2) Second, create a network diagram using Figure 10.1 in the Verzuh text as an example. 
(3) Third and last, create work packages using Tables 10.1 – 10.5 in the Verzuh text as examples.   
Submit 4-5 pages (not counting cover and references), APA format.
NOTES: PLEASE READ CAREFULLY 
(1) Images and Phtos of : 9.3; 10.1; 10.2; 10.3, 10.4; 10.5 are attached
(2) Copy of MOCK Project PROPOSAL are attached. Thiis is the Mock Project proposal that you submitted 
in previous weeks.

The objective of this assignment is to help students understand the concept of critical path and how to determine it using an existing work breakdown structure (WBS). Students will also learn how to create a network diagram and highlight the critical path.
Instructions:
Use the WBS created in Milestone 4. 
Using the WBS, identify all the activities and their durations.
Determine the sequence of activities and create a network diagram using a tool of your choice.
Identify the critical path of the project using the forward and backward pass methods.
Highlight the critical path on the network diagram.
Write an executive summary report discussing the critical path, its importance in project management, and how it can affect project scheduling.
Deliverables:
Executive Summary
A table that lists all WBS Activities and their durations, ES, EF, LS, LF of your project (See the WBS dictionary template in Module 8)
Network Diagram that shows the critical path of your project
Tips:
The activities list in this milestone may be expanded from the WBS created in Milestone 4.
Your paper should be 2 to 3 pages in length and conform to APA 7 guidelines.

What do you hope to accomplish with your e-portfolio? Why and how? Share a brief presentation (PowerPoint, Prezi) of what you have included and intend to include in your e-portfolio. The presentation should include: (1) a personal profile including career theme (project management, human resource management, etc.), (2) career goal(s), and (3) at least three examples of artifacts that will support your e-portfolio (does not need to be an entire document- include snapshot).
** my career theme will be project management

Due to financial pressures that many hospitals face, the Deaconess Clinic in Billings, Montana, decided to outsource several services, although in somewhat different ways.
First, the hospital outsourced its cafeteria food service. Although the food service employees were hired by the outside firm, they still felt a sense of ownership of their jobs and still felt connected to the hospital because of the family atmosphere in the kitchen and the cafeteria.
When the hospital tried the same thing with housekeeping, employee turnover became a problem. An investigation revealed that because the housekeeping employees were more isolated in their work, they lost what little feeling of being connected to the hospital they had. The problem was solved by hiring the employees back but using the outsourcing company to manage housekeeping.
The hospital also decided to outsource its laundry service. This time the hospital approached a rival hospital about joining it in outsourcing laundry service.
Source: Based on Norm Friedman, “Is Outsourcing the Solution?” www.hpnonline.com/inside/June04/outsourcing.htm.
Step 1. use factual, relevant data and examples to address the following questions:
In some instances, the outsourced service occurs in a different location, while in others it takes place inside the organization doing the outsourcing, as the food service did in this case. What advantages were there in having the outsourced work performed within the hospital? Suppose a different hospital outsourced its food service but decided not to have the work performed in-house. What might its rationale be?
In the housekeeping situation, why not just forget about outsourcing, especially since the hospital ended up rehiring its employees anyway?
For laundry service, what might have been the rationale for asking another hospital to join it?

This assignment is based off my order 404733652. Basically repainting my townhouse as the project. Attached is the brief summary and stakeholder analysis that was from my order 404733652. This Project charter builds off of the same project. Here is directions for project charter: As we have learned in this module’s readings and videos, a project charter is the final stage of the initiation phase. Now it is time to develop your own project charter.
Using the project that you chose in module 2, develop a Project Charter for your project. Use the project charter template you found in the discussion in this module, or create your own. Your project charter should include:
• A brief scope of the project
• Initial project risks
• Identification of team members, including their roles, responsibilities and time commitments
• Key milestones of the project
• A high-level budget with categorized expenses
Your Project Charter should be 2-3 pages in length.

Communications Plan
For this milestone, you will be responsible for creating a communications plan for your project using the communications plan template located in the Project Artifact Repository (PAR) in Module 8.  Your communications plan should outline how you will communicate with all stakeholders involved in the project, including team members, clients, vendors, and other interested parties.
Instructions:
Identify the key stakeholders for the project, including internal and external stakeholders.
Develop a communications matrix that outlines the following:
The key messages that need to be communicated to each stakeholder group.
The frequency of communication with each stakeholder group.
The method of communication (e.g., email, phone call, in-person meeting) for each stakeholder group.
The owner of each communication (i.e., who will be responsible for sending the communication).
Develop a project communication plan that includes the following:
An overview of the project and its objectives.
A summary of the key messages that will be communicated to each stakeholder group.
A description of the communication channels that will be used.
A timeline of when each communication will be sent.
A description of how feedback and questions will be managed.
Develop a contingency plan for communication in the event of a delay or change in the project.
Executive Summary
Deliverables:
Communications matrix
Project communication plan
Contingency plan for communication
Executive Summary

Projet Background Info:
CapraTek® a longtime leader in computer server
technology, is developing Alfred!, an integrated wireless smart-home system
that seamlessly connects household electronics, appliances, and devices.
While many of the functions Alfred! will
manage are actually third party devices, one that is being designed and
manufactured by CapraTek® specifically for the Alfred! system is a smart
thermostat for the consumer market. You have been brought in as the project
manager for the IOS software that will interface with Alfred! and the
thermostat. 
The Sprint Assignment:
The Sprint is the essence of the Scrum methodology and is manifest in daily meetings. During each meeting, the team addresses what has been done, what needs to be done, and how to remove existing impediments to progress.
The first Sprint meeting is an opportunity for the project sponsor or project manager to introduce the project or product that the team will be working on, including the project schedule and the product backlog. It is also an opportunity for the team members to become acquainted with one another and discuss ideas, skills, and other factors to enable the project to get off to a good start. As the meeting progresses, the team needs to:
Identify a Sprint goal.
Identify Sprint tasks and times for completion.
Designate team member roles.
Define what it means to be “done,” that is, when the Sprint is considered finished.
Subsequent Sprint meetings occur on a daily basis and focus on what has been done, what needs to be done, and identification of impediments and how to address them.
You have carefully planned your first Sprint meeting. Now it is time to conduct it. Your goal in this first Sprint meeting is to gain enough information to plan a Sprint that fits into the project schedule and is within the abilities of your team to deliver. The meeting should produce a well-informed team that is ready to attack the Sprint backlog efficiently. Please note, this is the backlog for this individual Sprint. Do not confuse it with the product backlog that you created earlier.
View the CapraTek: Sprint Meeting activity.
Complete the following two parts of this assessment.
Part 1: The Sprint Plan
Create a Sprint plan based upon the CapraTek activity that includes:
Sprint goals. This should be a detailed description.
Sprint tasks.
A description of the roles, responsibilities, and authorities of project stakeholders.
A Sprint burndown chart (for the Sprint, not the entire project) that derives its source data from an Excel table. Include both the table and the chart in your submission. Paste the table from Excel into your Word document if possible. The table should include the following items:
Sprint tasks.
Days dedicated to the Sprint.
Start hours.
Total hours.
Estimated remaining hours.
Actual remaining hours. (Because this is the beginning of the first Sprint, actual remaining hours and estimated remaining hours will be the same.)
Note: The graph should depict a straight line representing estimated remaining hours. An example of a burndown chart can be found in Mastering Agile, in this assessment.
A definition for “done.” This should be detailed. For example, if your Sprint goal was to create a button that turns the system on/off, just writing “the button turns the system on and off,” is insufficient. You must describe the functionality, how it appears to the user, how it might affect other systems, et cetera. It should describe “done” in enough detail so that the team is clear about the product’s entire functionality at Sprint completion.
Part 2: Updated Burndown Chart
Imagine on day three one of your team members gets sick and does not come in to work. In addition, another team member is required to spend three hours in an unexpected mandatory training. Update your burndown chart to reflect the new project conditions.
Create a single Word document with both parts of the assessment. Copy your Excel table and graphs into the document if possible. Make sure all headings and graphics are effectively labeled.
I am attaching previous assignments/relevant documents that provide context. please use specifics (names, details,  user story ID#, story info, etc.) from these supporting documents in this assignment. Please create the part 2, the burndown chart, in Excel & then paste into the word document along with part 1 of the assignment. Also, please attach the excel document seperately to the finished assignment.

For this assignment you will focus on identifying and analyzing stakeholders from the DIA Case Study.
Please reference the attached document for specific assignment instructions and the assignment rubric.

Overview and Rationale
In order to demonstrate proficiency with the content in this course we will complete a number of different assignments to validate your learning – and allow you to implement relevant practices a real-world setting. Program Level – Student Learning Outcomes:
Describe the importance of the monitoring and controlling process group through incorporation of key tools, techniques, and processes
Explain the change control process and necessary activities associated with project integration
Summarize the processes to monitor project performance using Earned Value Management and other analytics
Use performance reporting to update project progress
Identify techniques associated with managing changes to the project schedule and cost performance baselines
Module 2 Learning Objectives Establish a process and documentation for integrated change control
Lead the integrated change process
Evaluate and recommend actions to manage project change, using the integrated change control process
Establish a process and documentation for issue management
Refine the project communication plan for Project Monitoring and Controlling
Communicate project issues and changes, their impact, variance, changes, and proposed solutions to stakeholders Essential Components
This assignment provides the opportunity to build the Project Control Plan. For this assignment, use your project from PJM 1400 or a project you are currently leading at work. Be sure to note the project your work is based on – and provide a short paragraph summary of the project, its success criteria and challenges.
Issue Management process:
Create your project’s process for identifying, analyzing, recommending, approving, implementing and communicating issues- What information is necessary and what decision points need to be included in the process? Be sure to consider communication as well. Consider the roles/responsibilities in each step of the process (did you find additional stakeholders?).
A flow chart/swim lane diagram is a good way to lay out this process.
Include the templates for documentation that is completed through the process – if you build from another template, be sure to cite it. Include a brief overview of how the template is completed (for example, where parts are done in the process, who completes each section and what information goes in each section).
Please make sure mention the issue management plan in this project, I get half of the credit because missing the issue management plan!!