Most people think "project management" means making a to-do list with due dates. PM1000 exists to correct that. A project is a temporary endeavor with a defined start and end, undertaken to create a unique product, service, or result — and managing one well means deliberately balancing scope, time, and cost while a dozen stakeholders pull in different directions. This course is the foundation every later PM course builds on.
The project life cycle
PM1000 organizes everything around the five process groups defined by the Project Management Institute (PMI): Initiating (defining the project and securing authorization via a project charter), Planning (developing the scope, schedule, budget, and management plans), Executing (doing the work and coordinating people and resources), Monitoring and Controlling (tracking performance against the plan and managing change), and Closing (finalizing all activities, obtaining formal acceptance, and capturing lessons learned). Students learn that these groups overlap in practice — a project is rarely a clean waterfall — and that skipping Initiating or Closing is one of the most common causes of project failure.
The triple constraint and the PMBOK knowledge areas
The triple constraint (sometimes drawn as the "iron triangle") holds that scope, time, and cost are interdependent: change one and at least one other must move, or quality suffers. PM1000 introduces this alongside the ten PMBOK knowledge areas — integration, scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder management — as the map for everything a project manager is responsible for. Students are not expected to master each area yet, but to recognize which knowledge area a given problem belongs to.
Key topics in PM1000
- Project vs. operations: what makes work "temporary and unique" rather than ongoing business-as-usual
- The project charter: purpose, sponsor authority, high-level scope, and why a project without a charter has no formal authorization to consume resources
- Stakeholder identification and the power/interest grid — sponsors, project managers, team members, customers, and influencers who are never in the room but can still kill a project
- Work breakdown structure (WBS) basics: decomposing scope into manageable, assignable work packages
- Organizational structures: functional, matrix (weak/balanced/strong), and projectized — and how each changes a PM's authority over the team
- Project selection methods: payback period, NPV, and strategic alignment as ways organizations choose which projects to fund
- Introduction to Agile vs. Waterfall as two different philosophies of managing the same triple constraint
Working on a project charter, stakeholder analysis, or WBS assignment?
Our project management experts build PM1000-level coursework with the PMBOK grounding this course requires.
Worked example: scoping a small project charter
- Project: A university department wants to launch a peer-tutoring program by the start of next semester
- Purpose & justification: Improve retention in gateway courses; aligns with the department's strategic plan
- High-level scope: Recruit and train 15 tutors, build a scheduling system, launch in two pilot courses
- Constraints: Must launch within 10 weeks; budget capped at $8,000; no dedicated staff — faculty volunteer time only
- Sponsor authority: Department chair signs the charter, authorizing the PM to recruit tutors and reserve room space
Get Help With PM1000
Project charters, stakeholder analyses, WBS assignments. Foundational project management coursework done right.
Place Your OrderView All ServicesRelated courses
Frequently asked questions
The triple constraint (also called the "iron triangle") describes the interdependence of scope, time, and cost in any project. If a stakeholder adds scope, either the timeline must extend, the budget must increase, or quality will suffer to compensate — you cannot change one leg of the triangle without affecting at least one other. Modern frameworks often add a fourth dimension, quality, at the center of the triangle, reflecting that quality is the result of how well scope, time, and cost are balanced rather than a fourth independent variable to trade off. PM1000 uses this model to teach students that "just add more scope, no problem" is never actually free — it is important to make the tradeoff explicit and get sponsor sign-off before executing.
A project charter is the document that formally authorizes a project to exist and names the project manager with the authority to apply organizational resources to it. Without a charter, a project manager has no formal standing — they cannot compel functional managers to release staff time, they have no documented scope to point to when someone tries to add requirements mid-project, and there is no sponsor of record to escalate to when a decision is needed. PM1000 teaches that the charter is the single most important early-stage artifact precisely because so many "informal projects" fail from lack of authority and scope discipline, not from bad execution.