Only $2.99/month

Foundations of Project Managment Ch. 1-2

Terms in this set (52)

▪Project integration management—Integration focuses on coordinating the project plan's development, execution, and control of changes.
▪Project scope management—A project's scope is the work to be completed by the project team. This may include specific requirements, features, functionality, or standards for the product or system to be delivered, or it could include project-related deliverables like the project's schedule and budget.
▪Project time management—Time management is important for developing, monitoring, and managing the project's schedule. It includes identifying the project's phases and activities and then estimating, sequencing, and assigning resources for each activity to ensure that the project's scope and objectives are met.
▪Project cost management—Cost management assures that the project's budget is developed and completed as approved.
▪Project quality management—Quality management focuses on planning, developing, and managing a quality environment that allows the project to meet stakeholder needs or expectations.
▪Project human resource management—People are the most important resource on a project. Human resource management focuses on creating and developing the project team as well as understanding and responding appropriately to the behavioral side of project management.
▪Project communications management—Communication management entails communicating timely and accurate information about the project to the project's stakeholders. ▪Project risk management—All projects face a certain amount of risk. Project risk management is concerned with identifying and responding appropriately to risks that can impact the project.
▪Project procurement management—Projects often require resources (people, hardware, software, etc.) that are outside the organization. Procurement management makes certain that these resources are acquired properly.
▪Project stakeholder management—Stakeholders are people and include individuals, organizations, or business units that have a vested interest in the success (or failure) of a project.
▪Business Case Driven—The business case is a key document that is developed at the beginning of the project and must be continually justified throughout(funding) ▪Product Focus—Projects are undertaken to produce a product. PRINCE2 ® projects emphasize the design and delivery of a quality product.
▪Lessons Learned—PRINCE2 ® is based on proven best practices. Documented lessons learned are an important component for the PRINCE2 ® methodology
▪Manage the Stage—At each stage of the project, the Project Board reviews the project's progress in comparison to the business case. Each stage is planned, monitored, and controlled.
▪Adapt to the Project—. The methodology can be scaled to the size of the project and should be flexible in terms of the risks and environment unique to the project.
▪Manage by Exception—Tolerances are defined and used to empower project stakeholders by allowing them to make decisions without having to ask for approval from the next higher level of authority.
▪Accountability—PRINCE2 ® projects should have clear roles and responsibilities. Stakeholders need to know their role as well as everyone else's. The Project Board includes executive sponsorship that defines the project's objectives and ensures that the project remains viable. Internal or external suppliers provide resources, skills, or the knowledge to deliver the project's products, while users represent those stakeholders who will benefit from the delivery of the final product.
▪Planning: Identifying and responding to a problem or opportunity and incorporates the project management and system development processes and activities. Ensures that the goal, scope, budget, schedule, technology, and system development processes, methods, and tools are in place.
▪Analysis: The analysis phase attempts to delve into the problem or opportunity more fully. I identify and document any problems or bottlenecks associated with the current system. Here the specific needs and requirements for the new system are identified and documented.
▪Design: During the design phase, the project team uses the requirements and "to be" logical models as input for designing the architecture to support the new information system.
This architecture includes designing the network, hardware configuration, databases, user interface, and application programs.
▪Implementation: Implementation includes the development or construction of the system, testing, and installation. In addition, training, support, and documentation must be in place.
▪Maintenance and Support: Once the system has been implemented, it is said to be in production. Changes to the system, in the form of maintenance and enhancements, are often requested to fix any discovered errors (i.e., bugs) within the system, to add any features that were not incorporated into the original design, or to adjust to a changing business environment. Support, in terms of a call center or help desk, may also be in place to help users on an as-needed basis.