About the PMO
The Project Management Office (PMO) is part of the University of Florida’s Information Technology organization. Our primary goals are to standardize project-related governance processes and facilitate the sharing of resources, methodologies, tools, and techniques. Through project management and software procedures, the University can document, execute, monitor, control, and fully implement changes regarding unique products, services, or even standard business processes.
Contact us at email@example.com for more information.
As the project lead, Project Managers (PMs) are responsible for the successful planning, design, oversight, and execution of a project. Regardless of size or complexity, the PMO expects the following to be provided throughout the project lifecycle by the Project Manager:
- Clearly define the scope and deliverables.
- Identify the work, and resources, required to achieve project deliverables.
- A work plan, from inception to close, identifying the milestones and deliverables.
- Planning and management of project resources.
- Planning and management of stakeholder communications.
- Planning and management of project risks and issues, including mitigation planning and escalation where appropriate.
- Planning and management of changes to project scope, timeline, and resources.
- Transition planning and management of project deliverables.
- Project closure, with documentation and contributions to the knowledge base.
Although Project Managers regularly take meeting minutes and schedule project sessions, they should not be mistaken for administrative support. A Project Manager is expected to push project members to complete their tasks in a timely manner and strive for success as a team.
Project Managers and Business Analysts commonly have overlap between their roles, yet there is a clear delineation between the two. While the Project Manager is responsible for the project, the Business Analyst (BA) is responsible for the business needs. The PMO expects the following to be provided throughout the project lifecycle by the analyst:
- Responsible for working with stakeholders to define an organization’s business requirements.
- Shape the output of projects and ensure they deliver the expected business benefit.
- Define all functional, non-functional, and transitional requirements.
- Note, there is a difference between business and functional requirements. Business requirements are the higher-level needs of the organization as a whole, such as the business issues or opportunities, and reasons why a project has been undertaken. Functional requirements describe features, functions, and characteristics of the product, service, or result that will meet the business requirements.
- Spearhead the discovery, analysis and overall management of the requirements for a project.
- Demonstrate sufficient knowledge and experience to appropriately apply business analysis tools and techniques to enable project success.