UPI Study › Courses › System Analysis and Design › Free lessons › Lesson 9.2 Free with a free account
Defining the Project Management System: Examples and Applications
System Analysis and Design · Chapter 9: Project Management, Scheduling, and QualitySection 9.2 · lesson 61 of 697 min · free with a free account
Free preview
Create a free account to keep watching
It takes a minute and costs nothing. Your free account unlocks all of Chapter 1 and 3 more lessons of System Analysis and Design.
Lesson complete
Earn the 3 college credits for System Analysis and Design
Enrolling adds a quiz after each lesson, the graded work and the official transcript. Recommended for credit by NCCRS.
Next lesson: Project Planning: Procedures, Processes, and Toolkits →← What Makes Up Project Management? Components and CharacteristicsNext lesson: Project Planning: Procedures, Processes, and Toolkits →
In this lesson
The PMIS, PMBOK and PRINCE2, organizational structures, and the PMO.
- Define a project management information system, and what it supports
- Compare PMBOK and PRINCE2
- Distinguish functional, matrix, and projectized structures
- Explain the role of a project management office
Transcript
Everything said in the video, section by section (939 words). Read along, or search it.
Project Management, Scheduling, and Quality
The Project Management System
A project does not run on a plan alone. It runs inside a larger project management system. This section looks at the four parts of that system. The information system that tracks a project, the methodology that shapes it, the structure that decides who has authority, and the office that keeps practices consistent.
More Than a Plan
4 Parts of the System Around a Project
Here are the four parts at a glance. A project management information system decides how the project is tracked. A methodology decides how the project is run. The organizational structure decides who has authority over it. And, often, a project management office keeps practices consistent across many projects at once.
The PMIS
One Shared, Up-to-Date Picture
A project management information system, or P M I S, is the combination of processes, data, and tools a team uses to plan, execute, monitor, and report on a project. It gives everyone on the project a shared, up-to-date picture of where things stand. Scheduling tracks tasks, dependencies, and deadlines across the timeline. Budgeting tracks planned versus actual costs, against the approved budget. Resource management tracks who is assigned to what, and how much of their time it takes. The risk log tracks identified risks, their likelihood and impact, and the planned responses. And status reporting summarizes progress for stakeholders who are not in the day-to-day work. Specific software products come later in the chapter. Here, the P M I S is a concept, independent of any one product.
2 Methodologies
PMBOK vs. PRINCE2
A methodology gives a team a shared set of processes and terminology. Two of the most widely used are P M BOK and PRINCE two. P M BOK is a knowledge-area framework, organized around process groups. Initiating, planning, executing, monitoring, and closing. It comes from the Project Management Institute, and is widely used in North America. It is flexible. A team adapts its practices to the project at hand. PRINCE two is a process-based methodology, developed by the U K government, and widely used in the U K and Europe. It defines seven processes, and manages the work in stages, each with strict entry and exit criteria. It is more prescriptive, with defined roles, stages, and documents. So a company that wants every project run through the same tightly controlled, stage-gated process is a natural fit for PRINCE two.
Figure 2
Where Project Authority Sits
How much authority a project manager really has, often depends less on their title, than on the organization's structure. The common structures sit along a spectrum. At one end is a functional structure, where departments and their managers keep control. In the middle are matrix structures, described as weak, balanced, or strong, depending on which way authority leans. At the other end is a projectized structure, where the project manager has full authority over a dedicated team. Moving left to right, the project manager's authority increases.
3 Structures
Functional, Matrix, and Projectized
In a functional structure, authority sits with departments and their managers. The project manager has little to no formal authority, and often coordinates rather than directs. A project manager who has to ask each department head for permission, before assigning anyone's time, is working in a functional structure. In a matrix structure, authority is shared between functional managers and the project manager. How much the project manager gets depends on the matrix design. In a projectized structure, the project manager holds the authority, over a team dedicated to the project. A dedicated team that reports only to the project manager, for the whole project, is projectized.
The PMO
Standardizing How Projects Run
A project management office, or P M O, is a group that standardizes how projects are run, regardless of which department they belong to. Its level of control varies by type. A supportive P M O provides templates, best practices, and training, but does not control individual projects. A controlling P M O requires projects to follow specific frameworks or methodologies, and checks compliance. And a directive P M O manages projects directly, by supplying the project managers who run them. That is the key difference from a supportive P M O. It runs the projects, rather than simply offering help.
Putting It Together
One Company, Every Piece
Here is how the pieces fit together in one company. A mid-sized company uses a matrix structure day to day. But for a major system replacement, it gives the project manager full authority over a dedicated team, for the length of the project. That is a projectized arrangement, inside an otherwise matrix organization. A controlling P M O requires the project to follow the company's P M BOK-based process. And the project reports its status every week through the shared P M I S. That gives leadership a consistent view of this project, alongside every other project in the portfolio.
Key Terms
The Vocabulary of This Section
Let's lock in the key terms. A P M I S is the combination of processes, data, and tools used to plan, execute, monitor, and report on a project. P M BOK is a flexible, knowledge-area framework. PRINCE two is a more prescriptive, process-based methodology. In a functional structure, authority sits with departments. In a projectized structure, it sits with the project manager. In a matrix structure, authority is shared, and the matrix can be weak, balanced, or strong. And a P M O is a group that standardizes how projects are run across departments.
Key Takeaways
What to Carry Forward
To pull this together. A P M I S gives a project team a shared, up-to-date picture of the project. P M BOK is a flexible, adaptable framework. PRINCE two is more prescriptive, and stage-controlled. Functional, matrix, and projectized structures sit along a spectrum of how much authority a project manager holds. A matrix can be weak, balanced, or strong, depending on which side authority leans toward. And a P M O's control ranges from supportive, through controlling, to directive.
About System Analysis and Design at UPI Study
System Analysis and Design (Computer Science 390) is a self-paced online course of 69 video lessons in 9 chapters, from the analyst's role and requirements to UML modeling, interface and database design, testing, maintenance and project management. It carries a NCCRS credit recommendation for 3 semester credits.
Every lesson transcript is free on pages like this one, and the videos are free with a free UPI Study account. Enrolling adds a practice quiz after each lesson, the graded work and final exam that earn the credit, lifetime access, and an official transcript on completion. UPI Study has helped over 130,000 students with college credits. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Enroll now → Course details Download the syllabus All Computer Science courses Every course with PRO →
Why take it here
Why students take System Analysis and Design with UPI Study
Where the credit goes
Universities that work with NCCRS
System Analysis and Design carries a NCCRS credit recommendation. These universities work with NCCRS; some are UPI Study's signed partners. ACE and NCCRS have over 2,100 cooperating colleges that will consider accepting credits; the final decision is with the universities.
Thomas Edison State UniversitySigned partner
University of the PeopleSigned partner
Charter Oak State CollegeSigned partner
Strayer UniversitySigned partner
Columbia Southern UniversitySigned partner
Indiana TechSigned partner
Penn StateWorks with NCCRS
Southern New Hampshire UniversityWorks with NCCRS
SUNYWorks with NCCRS
+many more cooperating universitiesFind my college →Find my college → Not listed? Ask Athena in the corner of this page, or book a 15-minute call.
FAQ
Questions students ask us
About Defining the Project Management System: Examples and Applications
What is a project management information system?
What is the difference between PMBOK and PRINCE2?
What is the difference between functional, matrix, and projectized organizations?
What are the types of project management office?
About the System Analysis and Design course
How many college credits is System Analysis and Design?
How much does System Analysis and Design cost and what is included?
Which universities accept UPI Study credits?
How long does System Analysis and Design take?
How are the exams done?
How do my credits reach my college?
Ready for the full course? Earn 3 credits in System Analysis and Design.
69 video lessons, a quiz after each one, and the graded work that earns the credit. Recommended for credit by NCCRS.
3 credits · NCCRSEnroll →