5938329_Baillie_IS55_1A_May2[1]

5938329_Baillie_IS55_1A_May2[1] - Running head: DEFINING...

Info iconThis preview shows pages 1–4. Sign up to view the full content.

View Full Document Right Arrow Icon
Running head: DEFINING THE PROJECT 1 Project Management: Components of a Work Package Judith Baillie American Sentinel University
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
DEFINING THE PROJECT 2 Project Management: Components of a Work Package The PMBOK (2004) cite multiple types of project limits: Firstly, control limits – disagreement amongst team members can affect a project’s control as well as past project failures. Good project managers (PM) will develop control limit paths and set standards when issues such as these arise. These project management limitations occur through variations in collected data. Secondly, specification limits unlike control limits, are harder to handle. They are almost always stakeholder related. Even when quality management is utilized , a stakeholder may show some dissatisfaction and sway the project. Effective PMs should set specification limits with the stakeholder in advance allowing them to understand what the project will entail versus a change of heart or mindset. Thirdly, human element limitations – resource management may be at top levels but the human element in any project can harm a project. While change is inevitable, humans are not robots or computers and areas of denial, disagreement, and stubbornness does happen. PM should address this limitation and maintain open communication and develop good listening skills. Both team and individual feedback is necessary to halt this type of limitation before it spreads. It may only take one person to crossover to the path of harm that is easily spread. Be aware of your human element by knowing your team well and spot- checking the areas that you know may cause conflict. Fourth, software limitations – project management software designers may believe if they build it, it will be utilized but that’s not always the case. Not all software will work for every project nor can all software be adapted immediately to meet project needs – no matter what project management methodology you are using. Work with designers and offer realistic guides on desired needs. Meet often during the design process to see, feel, and work with the design. While the ability to rid software of all limitations to make the process flow, smoother communicate throughout the process rather than
Background image of page 2
DEFINING THE PROJECT 3 waiting for the final product. Fifth, information technology (IT) limitations –how many times do IT personnel blame the software designer and vice versa? If the software conflicts with the network and it crashes, the IT department does not communicat e effectively. Some managers may be guilty of not including IT personnel in stages of software design , wants, and needs. Correct this project management limitation by understanding why software and IT must be interconnected at all times. Sixth, vendor and supplier limitations –the suppliers can also put limits on project timelines. If they have backlog or not getting what is requested, your project is at their mercy. Utilize a good vendor selection process in advance of projects
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 4
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 9

5938329_Baillie_IS55_1A_May2[1] - Running head: DEFINING...

This preview shows document pages 1 - 4. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online