PM/PO/BA/SAFe

Course Overview

Course Curriculum

Week 1:

Intro: Introduction to the course or program, setting the stage for what participants can expect.
Code of Honour: Establishing ethical guidelines and professional conduct standards for the learning or working environment.
Getting Ahead with PPBS: Introduction and overview of the PPBS (Planning, Programming, Budgeting System) for effective project planning and resource allocation.
The Method: 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.

Week 2:

BA TOOLS & TECHNIQUES: Overview of various tools and techniques used in business analysis for gathering, analyzing, and documenting requirements.
REQUIREMENT & SCOPE: Understanding the relationship between project requirements and scope, defining boundaries and deliverables.
DATA DRIVEN DECISION MAKING: Emphasizing the importance of using data analysis to inform decision-making processes in business analysis.
BUSINESS ANALYTICS WITH EXCEL: Exploring the application of Excel for business analytics, including data visualization and analysis techniques.
DDDM (Data-Driven Decision Making): Further exploration of the principles and practices of making decisions based on data insights.
REQUIREMENT MANAGEMENT: Strategies and techniques for effectively managing requirements throughout the project lifecycle, ensuring alignment with stakeholder needs and project goals.

Week 3:

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.
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.

Week 4:

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.

Week 5:

PRODUCT OWNER RESPONSIBILITIES: Duties and roles of the Product Owner in Agile development, including prioritizing features, defining requirements, and representing the customer.
SCRUM TEAM: The cross-functional group responsible for delivering increments of product functionality, including developers, testers, and other necessary roles.
PBI (Product Backlog Item): A single requirement or piece of work listed in the Product Backlog, representing a feature, enhancement, or bug fix.
PBM (Product Backlog Management): Managing the Product Backlog, including prioritizing items, refining requirements, and ensuring alignment with project goals.
GROOMING: Refinement of items in the Product Backlog, including clarifying requirements, estimating effort, and preparing items for selection in upcoming Sprints.
PLANNING: Collaborative sessions for setting goals, defining priorities, and establishing a plan of action for upcoming work.
KICKOFF: Initiating a project or Sprint with a meeting to align the team, set expectations, and establish goals.
SCRUM EVENTS: Regularly occurring meetings and ceremonies in the Scrum framework, including Sprint Planning, Daily Standups, Sprint Review, and Sprint Retrospective.
SCRUM ARTIFACTS: Tangible outputs of the Scrum process, including the Product Backlog, Sprint Backlog, Increment, and various charts and reports.
SPRINT PLANNING: Collaborative session at the beginning of each Sprint to define the Sprint Goal and select items from the Product Backlog for implementation.

Week 6:

Understanding Windows Func (Functions): Exploring functions in the context of windowing operations, such as aggregating data over specific ranges or partitions.
Scaler func (Functions) and Date Functions: Examining scalar functions used for processing individual data values, including those focused on manipulating dates and times.
Data types and function: Exploring different data types and their associated functions for manipulating and processing data effectively.
Understanding Procedures and func (Functions): Delving into stored procedures and functions, which are precompiled sets of SQL statements for specific tasks.
Understanding Triggers: Investigating triggers, which are special types of stored procedures that automatically execute in response to certain events on a table.
Aggregate functions: Examining functions that operate on sets of values and return a single value summarizing the data, such as SUM, AVG, MIN, and MAX.
Group by having a clause: Utilizing the GROUP BY and HAVING clauses to organize data into groups based on specified criteria and filter the results based on aggregate values.

Week 7:

DAILY SPRINT: Daily Scrum meetings where the Scrum team synchronizes activities and plans for the day.
SPRINT REVIEW: A meeting held at the end of each sprint to review the work completed and gather feedback from stakeholders.
DEFINITION OF DONE: Agreed-upon criteria that must be met for a product increment to be considered complete and ready for release.
SAFe (Scaled Agile Framework) – Need & Understanding: Exploration of the reasons for adopting SAFe and understanding its principles and practices for scaling Agile methodologies across large enterprises.
CI/CD (Continuous Integration/Continuous Delivery): Practices of automatically integrating code changes into a shared repository and delivering software in small, frequent increments.
CI/CD TOOLS: Software tools and platforms used to automate the CI/CD process, such as Jenkins, GitLab CI/CD, and Travis CI.
Project Planning: 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.

Week 8:

Gantt Chart: A visual representation of project tasks and their scheduled durations, used for project planning and tracking progress.
Cost Management: 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.
KANBAN Board: A visual management tool used to represent work items and their status in a workflow, facilitating task prioritization and workflow optimization.
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 Tracking: Monitoring and measuring project progress against the project plan, identifying deviations, and taking corrective actions as needed to ensure project success.

Week 9:

Project Tracking: Monitoring and recording the progress of tasks and milestones throughout the project lifecycle to ensure adherence to 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 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 Roadmapping: 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.

Week 10:

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.

Week 11:

Week 12:

Assignment 2 Trello Workshop: Training session focusing on using Trello, a project management tool, for organizing tasks and enhancing collaboration within the team.
Assignment 3 – GMLN Workshop: Workshop dedicated to mastering GMLN (Generic Modeling Language Notation) for effectively modeling and documenting project requirements.
Assignment 4 – (Optional): Optional project assignment offering additional opportunities for skill development or exploration.
Guide To RRRP: Providing guidance on Risk, Resource, and Release Planning strategies to enhance project planning and execution.
Mock Interview Preparation: Practice sessions to prepare participants for job interviews, focusing on communication, problem-solving, and interview etiquette.
Interview Support for Gururschools Projects: Assistance and coaching provided to participants involved in Gururschools projects during job interviews.
Job Support post Placement: Ongoing support and guidance offered to participants after securing job placements to ensure successful transitions into their roles.

PM/PO/BA/SAFe

Course Overview

Course Curriculum

Week 1:

Intro: Introduction to the course or program, setting the stage for what participants can expect.

Code of Honour: Establishing ethical guidelines and professional conduct standards for the learning or working environment.

Getting Ahead with PPBS: Introduction and overview of the PPBS (Planning, Programming, Budgeting System) for effective project planning and resource allocation.

The Method: 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.

Week 2:

BA TOOLS & TECHNIQUES: Overview of various tools and techniques used in business analysis for gathering, analyzing, and documenting requirements.

REQUIREMENT & SCOPE: Understanding the relationship between project requirements and scope, defining boundaries and deliverables.

DATA DRIVEN DECISION MAKING: Emphasizing the importance of using data analysis to inform decision-making processes in business analysis.

BUSINESS ANALYTICS WITH EXCEL: Exploring the application of Excel for business analytics, including data visualization and analysis techniques.

DDDM (Data-Driven Decision Making): Further exploration of the principles and practices of making decisions based on data insights.

REQUIREMENT MANAGEMENT: Strategies and techniques for effectively managing requirements throughout the project lifecycle, ensuring alignment with stakeholder needs and project goals.

Week 3:

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.

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.

Week 4:

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.

Week 5:

PRODUCT OWNER RESPONSIBILITIES: Duties and roles of the Product Owner in Agile development, including prioritizing features, defining requirements, and representing the customer.

SCRUM TEAM: The cross-functional group responsible for delivering increments of product functionality, including developers, testers, and other necessary roles.

PBI (Product Backlog Item): A single requirement or piece of work listed in the Product Backlog, representing a feature, enhancement, or bug fix.

PBM (Product Backlog Management): Managing the Product Backlog, including prioritizing items, refining requirements, and ensuring alignment with project goals.

GROOMING: Refinement of items in the Product Backlog, including clarifying requirements, estimating effort, and preparing items for selection in upcoming Sprints.

PLANNING: Collaborative sessions for setting goals, defining priorities, and establishing a plan of action for upcoming work.

KICKOFF: Initiating a project or Sprint with a meeting to align the team, set expectations, and establish goals.

SCRUM EVENTS: Regularly occurring meetings and ceremonies in the Scrum framework, including Sprint Planning, Daily Standups, Sprint Review, and Sprint Retrospective.

SCRUM ARTIFACTS: Tangible outputs of the Scrum process, including the Product Backlog, Sprint Backlog, Increment, and various charts and reports.

SPRINT PLANNING: Collaborative session at the beginning of each Sprint to define the Sprint Goal and select items from the Product Backlog for implementation.

Week 6:

Understanding Windows Func (Functions): Exploring functions in the context of windowing operations, such as aggregating data over specific ranges or partitions.

Scaler func (Functions) and Date Functions: Examining scalar functions used for processing individual data values, including those focused on manipulating dates and times.

Data types and function: Exploring different data types and their associated functions for manipulating and processing data effectively.

Understanding Procedures and func (Functions): Delving into stored procedures and functions, which are precompiled sets of SQL statements for specific tasks.

Understanding Triggers: Investigating triggers, which are special types of stored procedures that automatically execute in response to certain events on a table.

Aggregate functions: Examining functions that operate on sets of values and return a single value summarizing the data, such as SUM, AVG, MIN, and MAX.

Group by having a clause: Utilizing the GROUP BY and HAVING clauses to organize data into groups based on specified criteria and filter the results based on aggregate values.

Week 7:

DAILY SPRINT: Daily Scrum meetings where the Scrum team synchronizes activities and plans for the day.

SPRINT REVIEW: A meeting held at the end of each sprint to review the work completed and gather feedback from stakeholders.

DEFINITION OF DONE: Agreed-upon criteria that must be met for a product increment to be considered complete and ready for release.

SAFe (Scaled Agile Framework) – Need & Understanding: Exploration of the reasons for adopting SAFe and understanding its principles and practices for scaling Agile methodologies across large enterprises.

CI/CD (Continuous Integration/Continuous Delivery): Practices of automatically integrating code changes into a shared repository and delivering software in small, frequent increments.

CI/CD TOOLS: Software tools and platforms used to automate the CI/CD process, such as Jenkins, GitLab CI/CD, and Travis CI.

Project Planning: 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.

Week 8:

Gantt Chart: A visual representation of project tasks and their scheduled durations, used for project planning and tracking progress.

Cost Management: 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.

KANBAN Board: A visual management tool used to represent work items and their status in a workflow, facilitating task prioritization and workflow optimization.

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 Tracking: Monitoring and measuring project progress against the project plan, identifying deviations, and taking corrective actions as needed to ensure project success.

Week 9:

Project Tracking: Monitoring and recording the progress of tasks and milestones throughout the project lifecycle to ensure adherence to 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 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 Roadmapping: Creating a strategic plan that outlines the vision, goals, and timeline for product development and evolution over time.