Karteikarten
Project Management (PID)
Karten in diesem Stapel (34)
- 1What are assumptions and list one example?Include a minimum of 4
An assumption is a condition you think to be true, and a constraint is a limitation on your project. Assumptions need to be analysed
One example is "An estimated 2.5TB of data will be generated by the new building project" - 2What are the constraints and list one example?Include a minimum of 3
A constraint is a limitation on your project. Constraints need to be identified.
One example of a constraint is "The project will start on 17th Sept 2019"
Another example is "There is a budget of £25,500 for the project" - 3What are risks and list one example?Include a minimum of 6
An uncertain event or condition that, if it occurs, has a positive or negative effect on a project’s objectives.
An example is "The changeover fails and results in the upgraded system not being ready for handover" - 4What are the key assumption categories?Human Resource Availability, Budget Availability, Scheduling accuracy, Performance of contractors, suppliers and vendors, Achievable success criteria, Upper Management Support
- 5Human Resource AvailabilityAll key project team members are available and have the necessary skills and knowledge to work on the project.
- 6Budget AvailabilityThe determined budget is accurate and covers all project expenses.
- 7Key Risk Categories (Scope Risks)Scope creep
Integration issues
Change in dependencies - 8Key Risk Categories (Scheduling Accuracy)Unexpected delays at an external vendor
Errors in estimation
Delays in acquisition of parts - 9Key Risk Categories (Resource Risk)Project team doesn’t have skills needed
Funding is inadequate
Key members of project team leave or don’t complete work - 10Key Risk Assumptions (Technology Risk)Software & hardware defects
Failure of an underlying service or a platform
Critical tool that no longer supports your fuctions - 11What is a project deliverable?Include a minimum of 4
A deliverable is a tangible or intangible good or service produced as a result of a project that is intended to be delivered to a customer. - 12Examples?A document
Equipment
A product
Software
A result
An approval - 13Detailed example #1 Part 1Category: Documentation
Item: Analysis & design documentation
Components: Interfaces, Processes, Outputs, Storyboards
Description: Analysis of the existing system, identifying customisations, and design of the upgraded system - 14Part 2Item: Development documentation (category)
Components: Data dictionaries, flowcharts, pseudocode
Description: Record of the developed upgrade system to help support and maintain the system going foward - 15Detailed example #22. Software & Hardware (category)
New server and upgraded software
Components: Check task brief for specifics
New system
Components: Check task brief for functions - 16Detailed example #33. A result (category)
Business goals from task brief must be specific!
E.g. “Productivity savings of £2000 per annum”
How will this be measured?
E.g. “User time spent on system figures, Comparison of new and old user time figures” - 17Detailed example #4Item: The company expects a substantial reduction in labour costs
Components: Due to the new system monitoring and controlling the production lines
Description: This will enable the company to be much more competitive, which will lead to an increase in sales - 18Detailed example #5Item: A server for the new system
Components: RDBMS, SQL software, RAID enabled Hard Disk Drive with large capacity
Description: Cost of £940. - 19Detailed example #6Item: Windows-based control system
Components: inputs, processes, scripts and outputs such as reports
Description: The upgrade to the control hardware will be offered at an introductory price of £4,500. The control software will be provided free of charge - 20StakeholdersIndividuals and organizations who are actively involved in the project, or whose interests may be positively or negatively affected as a result of project execution or successful project completion
- 21Project SponsorBudget decisions
Provides business context
Escalation point for decisions and issues above PM - 22ClientAgree project requirements
Answer questions & give feedback
Provide sign-off
Recipient of deliverables at handover - 23Scheduling AccuracyThe set deadlines and milestones are achievable and the project can be finished on time.
- 24Project ManagerPlan & monitor project progress
Maintain scheduling documents
Control time and budget
Manage risks
Provide comms - 25Senior DeveloperLead product development
Manage team of developers
Review and improvise code
Run tests and fix bugs
Update PM with development progress - 26Server ManagerInstall server hardware
Update server software
Provide support during system changeover
Identify need hardware - 27Consultant/ContractorComplete set task or phase of the project
Provide expert advice
Check task brief for specifics. - 28End UsersProvide feedback on design
Conduct end user/black box testing - 29Types of communication with stakeholdersFace to face meetings
Formal documentation
Email
Phone conversation - 30Outcome of the communication with StakeholdersPID, Checkpoint report
- 31Frequency of communicationDaily, twice daily
Bi-weekly
Weekly
At each milestone
Monthly
At start/end of project - 32Performance of contractors, suppliers and vendorsAll necessary equipment and goods are available whenever you need them.
- 33Achievable success criteriaThe success criterias used to measure if the project achieved its objective are reasonable.
- 34Upper management supportYou have the support and buy-in from the client and the project sponsor, who will back you up when issues arise.
Informationen
- Beschreibung
- A level Computing Karteikarten am Project Management (PID), erstellt von Sana Ayub am 02/10/2020.
- Erstellt von
- Sana Ayub
- Aufrufe
- 0
- Bewertung