Being a Project Manager
A detailed Summary of Being a Project Manager
I am a software project manager at a booming Fortune 500 company having
just been promoted from a position as a software engineer. I have been assigned to an on-going software development project because the previous manager left the company to take a job with one of our competitors. After meeting with my new team and reading the project documentation, I have an overall picture of the problem that my boss wants me to solve: we are four months behind schedule and our customer is furious. Our company is in danger of permanently losing this corporate customer. Many team members are already staying late and coming in on Saturdays. Stress levels are skyrocketing. The project is largely finished, but testing is taking forever. The team keeps finding more defects in the software, and when they fix the problems that they know about, they unwittingly create new problems. The software needs to be cleaned up and shipped as soon as possible. In order to expedite the conclusion of this project, I will start out by holding a meeting to plan the rest of the project by addressing the following: the morale of the engineers and relations with the customer, the testing process, and the conclusion.
The first thing I will deal with is t

he stress among the software engineers. By creating a working atmosphere with less stress and frustration, the team members will be able to think clearer, be more motivated, and work cooperatively. I will reaffirm our vision of completing the software and the impact it will have for our customer and our company. By reminding everyone of our goal, the team will be able to maintain focus
When the project is finished and ready to be shipped, we will contact the customer and complete the transaction. In the meantime, we will work on our analysis of the project: the post mortem phase. Using data collected during the ordeal, we will complete a Project and Process Data and a Summary Report. This is our opportunity to reflect on the experience of the group project. We will explain what we have achieved, how we achieved it, and what lessons we have learned on the way. We will explain about the problems we encountered and also explain how we surmounted or evaded them. Altogether, my first assignment as a project manager will allow me to learn a great deal about software engineering and prepare me for future software developments.
in order to finish the project smoothly and within a reasonable time frame. To further reduce the frenzy, I will not require anyone
Some common words found in the essay are:
Saturdays Stress, , Recording Log, Summary Report, mortem phase, software project, post mortem phase, team able, recording log, code review, project finished, post mortem, project manager,
Approximate Word count = 859
Approximate Pages = 3 (250 words per page double spaced)
Category: Technology
Saved Paper
Newest Essays
- My Personal Value System
- Iraq and High Energy...
- The Development of English...
- Critique of a Research...
- Visiting the Elderly in...
- Ad Critique: Peters, Jeremy...
- Catell's Structure-Based...
- Current Diabetes Epidemic:...
- Job Search: Push Pull...
- Proposal: Social...
Testimonials
-
"Thank You So Much!!! You have saved me once again!!!"
Jack M. -
"With so many papers to chose from, I was able to get ideas to help me with all of my classes. Thank You!"
Brian P. -
"I've used this site for the last 3 years to help me come up with ideas for my papers."
Sara J. -
"I use this site every week to help me write my own papers!"
Rachel W. -
"I love this site!!!"
Marie N.
