Project Manager
Course Overview
A Project Manager (PM) is responsible for planning, executing, and closing projects while ensuring that they meet the desired goals, timelines, and budgets. A Project Manager plays a vital role in ensuring projects are completed successfully, on time, and within budget, making them integral to any organization’s success.
Prerequisites: Students are required to have at least an associate’s degree or equivalent with a good knowledge of any object-oriented programming (OOP), or a high school diploma or GED with two years of related work experience and a good knowledge of any object-oriented programming (OOP).
4 Months (224 Hours) of Long Professional Course.
Course Curriculum
- Intro: Introduction to the course or program, setting the stage for what participants can expect.
- Code of Honor: Establishing ethical guidelines and professional conduct standards for the learning or working environment.
- Getting Ahead with PPBS: An Introduction and Overview of the PPBS (Planning, Programming, and Budgeting System) for Effective Project Planning and Resource Allocation.
- The Method: An explanation of the methodology or approach being used for learning or conducting business analysis.
- Getting Started with Business Analysis: Initial Steps and Considerations for Starting a Career or Project in Business Analysis.
- Business Analysis Process: Overview of the systematic approach to analyzing and documenting business requirements and processes.
- Requirement Lifecycle: Understanding the stages and evolution of requirements from inception to implementation and maintenance.
- BABOK: Introduction to the BABOK (Business Analysis Body of Knowledge) as a comprehensive guide for business analysts.
PROJECT MANAGEMENT: Introduction to principles and practices of managing projects efficiently to achieve goals within constraints.
SDLC (Software Development Life Cycle): Overview of the phases and activities involved in the development of software products.
WATERFALL / AGILE: Comparison between traditional waterfall methodology and agile approaches to project management.
SCRUM / KANBAN / XP / PP: Introduction to various agile methodologies including Scrum, Kanban, Extreme Programming (XP), and Lean Product Development.
PM TOOLS (Project Management Tools): Exploration of software tools used for project planning, scheduling, and tracking.
MS PROJECT: Training on Microsoft Project software for project planning, resource allocation, and progress tracking.
JIRA: Overview and usage of JIRA software for agile project management, issue tracking, and team collaboration.
TRELLO: Introduction to Trello as a visual collaboration tool for organizing tasks and projects using boards and cards.
- Rational Unified Process (RUP): A software development process framework emphasizing iterative development and use case-driven approach.
- DevOps: the integration of development and operations teams, practices, and tools to improve collaboration and delivery speed.
- Estimation Klog: Methods and techniques for estimating project effort, duration, and resources needed for successful completion.
- FP (Function Point Analysis): A method for measuring the size and complexity of software by quantifying its functionality.
- COCOMO (Constructive Cost Model): A model used for estimating the cost and effort required for software development based on project characteristics.
- PMI 10 KNOWLEDGE AREA: The ten knowledge areas defined by the Project Management Institute (PMI) in the Project Management Body of Knowledge (PMBOK), covering various aspects of project management.
- SCRUM FRAMEWORK: An agile framework for managing software development projects, emphasizing iterative development, collaboration, and flexibility.
- Kanban Board: A visual management tool used to represent work items and their status in a workflow, facilitating task prioritization and workflow optimization
Gantt Chart: A visual representation of project tasks and their scheduled durations, used for project planning and tracking progress.
Cost management is the process of planning, estimating, budgeting, and controlling costs throughout the project lifecycle.
Change Management: Procedures and processes for identifying, evaluating, and implementing changes to project scope, schedule, or resources.
Project Scheduling: Creating a timeline of project activities and tasks, including their start and end dates, to ensure timely completion.
Project Forecasting: Predicting future project outcomes, resource requirements, and potential risks based on current project data and trends.
Project Kickoff: Initiating the first project with a formal kickoff meeting to outline objectives, expectations, and team roles.
Project Tracking: Monitoring and measuring project progress against the project plan, identifying deviations, and taking corrective actions as needed to ensure project success.
Project Tracking: monitoring and recording the progress of tasks and milestones throughout the project lifecycle to ensure adherence to the schedule and budget.
Risk Management: Identifying, assessing, and mitigating potential risks that could impact the success of the project.
Task Management: organizing, assigning, and tracking individual tasks within a project to ensure they are completed efficiently and on time.
Product Owner vs. Project Manager: Clarifying the roles and responsibilities of product requirements, and the Project Manager, who oversees the project’s execution, resources, and stakeholders. Of the product owner, who represents the customer and defines product requirements, and the project Manager, who oversees the project’s execution, resources, and stakeholders.
Product Road mapping: Creating a strategic plan that outlines the vision, goals, and timeline for product development and evolution over time.
Backlog Management: Prioritizing, refining, and managing the product backlog, which contains a prioritized list of features, enhancements, and fixes for the product.
Release Planning: planning and coordinating the delivery of product increments or releases, considering factors such as scope, resources, and stakeholder priorities.
Product Progress Assessment: Evaluating the progress of the product development effort against predefined criteria, such as quality, functionality, and customer satisfaction, to ensure alignment with project goals and objectives.
SCRUM METRICS: Key performance indicators (KPIs) and measurements used to evaluate the performance and effectiveness of Scrum teams and processes.
SCRUM ENVIRONMENT: The cultural, organizational, and physical setting in which Scrum teams operate, emphasizing collaboration, transparency, and adaptability.
Test phases: stages in the software development lifecycle (SDLC) dedicated to testing activities, including unit testing, integration testing, system testing, and user acceptance testing (UAT).
Vision Management: Defining and communicating the vision, goals, and strategic direction of the project to align stakeholders and team members.
Product Owner Artefacts: Documents, artifacts, and deliverables managed by the product owner, including the product backlog, user stories, acceptance criteria, and release plans.
Project Management Artefacts: Documents, artifacts, and deliverables managed by the Project Manager, including the Project Charter, Project Plan, Work Breakdown Structure (WBS), and Risk Register.
Collaboration: Fostering teamwork, communication, and cooperation among project stakeholders, team members, and other relevant parties to achieve project goals and objectives.
Project Kickoff: Initiating the first project with a formal kickoff meeting to outline objectives, expectations, and team roles.
Team Distribution: allocating team members to specific roles and responsibilities for the project, ensuring a balanced distribution of skills and expertise.
Project planning is the process of defining project objectives, scope, timelines, resources, and deliverables to ensure successful project execution.
Project Scoping: Defining the boundaries and objectives of a project, including identifying what is included and excluded from the project scope.
Scope creeping: the gradual expansion of project scope beyond its original boundaries, often leading to increased costs, delays, and risks.
Assignment 1: Trello Workshop: Training session focusing on using Trello, a project management tool, for organizing tasks and enhancing collaboration within the team.
Assignment 2: GMLN Workshop: Workshop dedicated to mastering GMLN (Generic Modeling Language Notation) for effectively modeling and documenting project requirements.
- Assignment 4 (Optional): An optional project assignment offering additional opportunities for skill development or exploration.
Mock Interview Preparation: Practice sessions to prepare participants for job interviews, focusing on communication, problem-solving, and interview etiquette.
Interview Support for GlobeTechUsa Projects: Assistance and coaching provided to participants involved in GlobeTechUsa projects during job interviews.
Job Support Post-Placement: Ongoing support and guidance are offered to participants after securing job placements to ensure successful transitions into their roles.
About This Course:
- Instructor Lead Online Training
- Certificate of Completion
- Resume Preparation
- Interview Preparation
- Mock Interview
- Client Interview
- Project Support
