AGILE / SCRUM

Course Overview

Course Curriculum

Week 1: Introduction to Business Analysis & AGILE/SCRUM:

CODE OF HONOR: Upholding ethical standards in business analysis and AGILE practices.
Coach / Candidate & Course Intro: Introducing the instructor, participants, and overview of the course.
Three Secrets of AGILE: Efficiency, adaptability, and customer collaboration as core tenets of AGILE.
AGILE & Business Analysis: Integration of AGILE principles into the business analysis process for enhanced outcomes.
Methodologies: Various approaches to implementing AGILE practices in business analysis.
Frameworks: Structured models for applying AGILE methodologies within business analysis contexts.
History / Evolution & Need: Understanding the development and necessity of AGILE methodologies in response to changing business environments.
AGILITY Vs Flexibility: Distinguishing between the agility inherent in AGILE and traditional notions of flexibility.
Manifesto / Principle: The foundational values and guiding principles of the AGILE Manifesto for effective business analysis.

Week 2: AGILITY & Scaling:

Best Practices: Implementing proven strategies for scaling agility effectively.
Tools & Agility in Projects: Leveraging tools to enhance agility and project management efficiency.
AGILE & SCRUM: Understanding the relationship between AGILE principles and the SCRUM framework.
AGILE Values: Embracing collaboration, adaptability, and customer-centricity in AGILE practices.
AGILE Principles: Guiding principles emphasizing customer satisfaction, flexibility, and continuous improvement in AGILE.
SCRUM VALUES: Commitment, courage, focus, openness, and respect as foundational values in SCRUM.
Principles: Core beliefs guiding the implementation of SCRUM methodology.
ROLES: Defining the responsibilities and interactions of key roles within the SCRUM framework.
EVENTS: Essential meetings and ceremonies in SCRUM methodology ensuring progress and alignment.
Planning: Iterative planning processes to adapt and respond to changing project requirements in AGILE environments.

Week 3: AGILE CEREMONIES & PLANNING:

Meeting / Ceremonies: Regular gatherings fostering collaboration and alignment within AGILE teams.
Sprint Planning: Detailed session outlining goals and tasks for the upcoming sprint cycle.
FRAMEWORK: Structured approach providing guidelines for AGILE project management.
KANBAN: Visual management tool for tracking work progress and flow within AGILE teams.
JIRA Review: Utilization of JIRA software for project tracking, task management, and review in AGILE workflows.
Different Tools: Various software and platforms facilitating AGILE project management and communication.
Product Backlogs: Prioritized list of features and tasks representing requirements for product development.
Review Ceremonies: Regular meetings to evaluate completed work and gather feedback from stakeholders.
Backlog Grooming: Ongoing process of refining and prioritizing items in the product backlog.
PBI / PBM: Product Backlog Item / Product Backlog Management: essential elements in AGILE product development.
Cross-Functional & Self-Organizing Team: Team structure promoting diverse skill sets and autonomy in decision-making within AGILE projects.

Week 4: Review with Highest Quality:

DOD (Definition of Done): Clear and agreed-upon criteria ensuring completed work meets quality standards.
Retrospection: Reflective analysis of past iterations to identify areas for improvement in future cycles.
Stringent DOD: Rigorous standards for meeting acceptance criteria and quality benchmarks.
Acceptance Criteria & User Stories: Detailed requirements and narratives defining the scope and functionality of features.
AGILE PLANNING: Dynamic process of organizing tasks and allocating resources to achieve project goals efficiently.
ESTIMATION: Predictive assessment of time and resources needed for completing tasks and deliverables.
Domain Learnings in Details: In-depth understanding of specific industries such as banking, healthcare, and insurance to inform project decisions.
Banking: Insights into the unique challenges and requirements of financial institutions.
Healthcare: Understanding the complexities and regulations governing healthcare systems and processes.
Insurance: Familiarity with the intricacies of insurance products, regulations, and customer needs.
Business Analysis Kickstart Transition: Seamless transition and initiation of business analysis activities for improved project outcomes and stakeholder alignment.

Week 5: BUSINESS ANALYSIS

Introduction: Overview of the role and significance of business analysis in projects and organizations.
BABOK (Business Analysis Body of Knowledge): Comprehensive guide detailing best practices and standards in the field of business analysis.
Evolution: Historical development and progression of business analysis methodologies and practices.
Need: Identifying the necessity of business analysis for effective decision-making and project success.
Prerequisites: Essential skills, knowledge, and qualifications required to excel in business analysis roles.
Responsibilities: Key tasks and duties of business analysts in analyzing, documenting, and communicating requirements.
Requirements: Understanding and documenting the needs and objectives of stakeholders for project success.
Dos & Don’ts: Best practices and common pitfalls to be aware of in the practice of business analysis.
Elicitation: Techniques and methods for gathering requirements from stakeholders effectively.
Business Analysis with Excel: Utilizing Microsoft Excel as a tool for organizing, analyzing, and presenting business data and requirements.

Week 6: BUSINESS ANALYTICS

Analysis vs Analytics: Distinguishing between the processes of analysis (interpreting data) and analytics (using data for predictive insights).
DDDM (Data-Driven Decision Making): Approach to decision-making that relies on data analysis and insights to guide strategic choices.
RG Process (Requirement Gathering Process): Systematic approach to collecting and documenting stakeholder needs and expectations.
Steps for Requirement Gathering: Sequential actions involved in gathering and documenting project requirements from stakeholders.
Artifacts: Tangible outputs such as documents, diagrams, and models used to represent and communicate requirements.
Information Management: Strategies and tools for organizing, storing, and retrieving business-related data and knowledge.
Stakeholders Management: Techniques for identifying, engaging, and satisfying the needs of project stakeholders.
Information Management: Methods and systems for effectively handling and utilizing business information resources.
Document Management: Practices and technologies for organizing, storing, and accessing project documentation.
Wireframing: Creating visual representations (wireframes) of software interfaces to illustrate layout and functionality.

Week 7: MODELLING

BA Models: Various representations used to describe and analyze business processes and requirements.
Advanced BA Models: Sophisticated techniques and frameworks for modeling complex business scenarios and systems.
Docs (Documents): Written records and specifications capturing business requirements, processes, and decisions.
Templates: Standardized formats for documenting and communicating business analysis artifacts.
Understandings: Insights gained through modeling and analysis to inform decision-making and solution development.
WBS Charts (Work Breakdown Structure): Hierarchical diagrams depicting project tasks and deliverables breakdown.
Visual Models: Graphical representations illustrating relationships, processes, and concepts in business analysis.
ERD (Entity-Relationship Diagram): Diagrammatic depiction of the entities and relationships within a database system.
WFD (Workflow Diagram): Graphic representation showing the sequence of steps in a process or workflow.
Process Creation: Designing and documenting procedures and workflows to achieve business objectives.
CTD (Context Diagram): Diagram illustrating the interactions between a system and its external entities.
PFD (Process Flow Diagram): Visual representation of the flow of processes and activities within a system.
AD (Activity Diagram): Diagram illustrating the flow of activities and actions within a process.
FBD (Functional Block Diagram): Diagram representing the functions and their interrelationships within a system.
MMD (Mind Map Diagram): Visual representation of ideas, concepts, and relationships organized around a central theme.
PRD (Product Requirements Document): Document outlining the features, functionalities, and specifications of a product or system.

Week 8: Workshops & Projects

Assignment 1 Project Kickoff: Initiating the first project with a formal kickoff meeting to outline objectives and expectations.
Team Distribution: Allocating team members to specific roles and responsibilities for project execution.
Assignment 2 Trello Workshop: Training session on using Trello, a project management tool, for effective task organization and collaboration.
Assignment 3 – GMLN Workshop: Workshop focusing on mastering GMLN (Generic Modeling Language Notation) for project modeling and documentation.
Assignment 4 – (Optional): Optional project assignment for further skill development or exploration.
Guide To RRRP (Risk, Resource, and Release Planning): Providing guidance on planning for risks, managing resources, and coordinating releases in projects.
Mock Interview Preparation: Practice sessions to prepare participants for job interviews, focusing on communication and problem-solving skills.
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.

AGILE / SCRUM

Course Overview

Course Curriculum

Week 1: Introduction to Business Analysis & AGILE/SCRUM:

CODE OF HONOR: Upholding ethical standards in business analysis and AGILE practices.

Coach / Candidate & Course Intro: Introducing the instructor, participants, and overview of the course.

Three Secrets of AGILE: Efficiency, adaptability, and customer collaboration as core tenets of AGILE.

AGILE & Business Analysis: Integration of AGILE principles into the business analysis process for enhanced outcomes.

Methodologies: Various approaches to implementing AGILE practices in business analysis.

Frameworks: Structured models for applying AGILE methodologies within business analysis contexts.

History / Evolution & Need: Understanding the development and necessity of AGILE methodologies in response to changing business environments.

AGILITY Vs Flexibility: Distinguishing between the agility inherent in AGILE and traditional notions of flexibility.

Manifesto / Principle: The foundational values and guiding principles of the AGILE Manifesto for effective business analysis.

Week 2: AGILITY & Scaling:

Best Practices: Implementing proven strategies for scaling agility effectively.

Tools & Agility in Projects: Leveraging tools to enhance agility and project management efficiency.

AGILE & SCRUM: Understanding the relationship between AGILE principles and the SCRUM framework.

AGILE Values: Embracing collaboration, adaptability, and customer-centricity in AGILE practices.

AGILE Principles: Guiding principles emphasizing customer satisfaction, flexibility, and continuous improvement in AGILE.

SCRUM VALUES: Commitment, courage, focus, openness, and respect as foundational values in SCRUM.

Principles: Core beliefs guiding the implementation of SCRUM methodology.

ROLES: Defining the responsibilities and interactions of key roles within the SCRUM framework.

EVENTS: Essential meetings and ceremonies in SCRUM methodology ensuring progress and alignment.

Planning: Iterative planning processes to adapt and respond to changing project requirements in AGILE environments.

Week 3: AGILE CEREMONIES & PLANNING:

Meeting / Ceremonies: Regular gatherings fostering collaboration and alignment within AGILE teams.

Sprint Planning: Detailed session outlining goals and tasks for the upcoming sprint cycle.

FRAMEWORK: Structured approach providing guidelines for AGILE project management.

KANBAN: Visual management tool for tracking work progress and flow within AGILE teams.

JIRA Review: Utilization of JIRA software for project tracking, task management, and review in AGILE workflows.

Different Tools: Various software and platforms facilitating AGILE project management and communication.

Product Backlogs: Prioritized list of features and tasks representing requirements for product development.

Review Ceremonies: Regular meetings to evaluate completed work and gather feedback from stakeholders.

Backlog Grooming: Ongoing process of refining and prioritizing items in the product backlog.

PBI / PBM: Product Backlog Item / Product Backlog Management: essential elements in AGILE product development.

Cross-Functional & Self-Organizing Team: Team structure promoting diverse skill sets and autonomy in decision-making within AGILE projects.

Week 4: Review with Highest Quality:

DOD (Definition of Done): Clear and agreed-upon criteria ensuring completed work meets quality standards.

Retrospection: Reflective analysis of past iterations to identify areas for improvement in future cycles.

Stringent DOD: Rigorous standards for meeting acceptance criteria and quality benchmarks.

Acceptance Criteria & User Stories: Detailed requirements and narratives defining the scope and functionality of features.

AGILE PLANNING: Dynamic process of organizing tasks and allocating resources to achieve project goals efficiently.

ESTIMATION: Predictive assessment of time and resources needed for completing tasks and deliverables.

Domain Learnings in Details: In-depth understanding of specific industries such as banking, healthcare, and insurance to inform project decisions.

Banking: Insights into the unique challenges and requirements of financial institutions.

Healthcare: Understanding the complexities and regulations governing healthcare systems and processes.

Insurance: Familiarity with the intricacies of insurance products, regulations, and customer needs.

Business Analysis Kickstart Transition: Seamless transition and initiation of business analysis activities for improved project outcomes and stakeholder alignment.

Week 5: BUSINESS ANALYSIS

Introduction: Overview of the role and significance of business analysis in projects and organizations.

BABOK (Business Analysis Body of Knowledge): Comprehensive guide detailing best practices and standards in the field of business analysis.

Evolution: Historical development and progression of business analysis methodologies and practices.

Need: Identifying the necessity of business analysis for effective decision-making and project success.

Prerequisites: Essential skills, knowledge, and qualifications required to excel in business analysis roles.

Responsibilities: Key tasks and duties of business analysts in analyzing, documenting, and communicating requirements.

Requirements: Understanding and documenting the needs and objectives of stakeholders for project success.

Dos & Don’ts: Best practices and common pitfalls to be aware of in the practice of business analysis.

Elicitation: Techniques and methods for gathering requirements from stakeholders effectively.

Business Analysis with Excel: Utilizing Microsoft Excel as a tool for organizing, analyzing, and presenting business data and requirements.

Week 6: BUSINESS ANALYTICS

Analysis vs Analytics: Distinguishing between the processes of analysis (interpreting data) and analytics (using data for predictive insights).

DDDM (Data-Driven Decision Making): Approach to decision-making that relies on data analysis and insights to guide strategic choices.

RG Process (Requirement Gathering Process): Systematic approach to collecting and documenting stakeholder needs and expectations.

Steps for Requirement Gathering: Sequential actions involved in gathering and documenting project requirements from stakeholders.

Artifacts: Tangible outputs such as documents, diagrams, and models used to represent and communicate requirements.

Information Management: Strategies and tools for organizing, storing, and retrieving business-related data and knowledge.

Stakeholders Management: Techniques for identifying, engaging, and satisfying the needs of project stakeholders.

Information Management: Methods and systems for effectively handling and utilizing business information resources.

Document Management: Practices and technologies for organizing, storing, and accessing project documentation.

Wireframing: Creating visual representations (wireframes) of software interfaces to illustrate layout and functionality.

Week 7: MODELLING

BA Models: Various representations used to describe and analyze business processes and requirements.

Advanced BA Models: Sophisticated techniques and frameworks for modeling complex business scenarios and systems.

Docs (Documents): Written records and specifications capturing business requirements, processes, and decisions.

Templates: Standardized formats for documenting and communicating business analysis artifacts.

Understandings: Insights gained through modeling and analysis to inform decision-making and solution development.

WBS Charts (Work Breakdown Structure): Hierarchical diagrams depicting project tasks and deliverables breakdown.

Visual Models: Graphical representations illustrating relationships, processes, and concepts in business analysis.

ERD (Entity-Relationship Diagram): Diagrammatic depiction of the entities and relationships within a database system.

WFD (Workflow Diagram): Graphic representation showing the sequence of steps in a process or workflow.