Project Manager Definition
The person responsible for the success of the project in conjunction with the project sponsor and team. The project manager must ensure that the processes of project planning, tracking and reporting are undertaken in a rigorous manner. The project manager is also responsible for managing the relationships with other related groups (see Stakeholders) and related projects.
Project Manager Responsibilities
The project manager has specific accountability for achieving all of the defined project objectives within the time and resources allocated.
Project management is not just about deadlines. The Gantt chart is only one component. If you had believed this to be true, go and invest in yourself by learning more.
The Wiki on Project Managemnt is a good place to start. With this being said, don't become a text book PM. You'll only show yourself as being a rookie!!!
- Accountability for project results
- Scoping a Project
- Proactively disseminating project information to all stakeholders
- Identifying, managing and mitigating project risk
- Proactively managing scope to ensure that only what was agreed to is delivered, unless changes are approved through scope management
- Resourcing
- Scheduling - including gather estimates of work
- Resolve Issues or problems
- Removing road blocks
- Mentoring
- etc etc
Are You a Project Manager Or a Project Mangler?
Which one are you? An effective IT project manager, able to deliver software on time, according to specs, and within budget, or someone referred to by your peers as a project mangler? Find out with these Top 10 Signs You're a Project Mangler.
10. Your .mpp attachments are considered to be more harmful than the Netsky virus.
9. You think your job description is limited to running around and asking people "Are you done yet?"
8. Your record for the "longest consecutive number of days without changing your project plan" is 3, which was achieved over a weekend.
7. You don't publish your project plan for fear developers might find out what the REAL dates are.
6. When the first 90% of your project is done, the second 90% begins.
5. You couldn't write a line of code to save your life, yet you tell developers how long it will take them to complete their feature.
4. You only work from 9 to 5 but expect developers to work evenings and weekends to meet your deadlines.
3. Your best motivational skill: telling people you're working from home tomorrow.
2. You DO think that 9 people can have a baby in 1 month.
And the number one sign you're a project mangler...
1. Your name is R. U. Dunyet.
Software Project Bill of Rights
Customers have the right to:
- Set objectives for the project and have them followed.
- Know how long the project will take and how much it will cost.
- Decide which features are in and which are out.
- Make reasonable changes to requirements.
- Know the project's status clearly and confidently.
- Be apprised regularly of risks that could affect cost, schedule or quality.
- Have ready access to project deliverables.
Project teams have the right to:
- Know the project objectives and clarify priorities.
- Know in detail what product they're supposed to build and clarify the product definition.
- Have ready access to the customer, manager or other person responsible for making decisions about software functionality.
- Work each phase of the project in a technically responsible way, and not be forced to start coding too soon.
- Approve labor and schedule estimates for any work they're asked to perform.
- Have the project's status reported accurately to customers and upper management.
- Work in a productive environment free from frequent interruptions and distractions.
|
Previous
