Demonstration: 4 Hours
Lab: 0 Hours
Total: 4 Hours

The module “Introduction to the Software Industry and Testing Jobs” is an essential component of the course “Scrun Master.” This module serves as a comprehensive introduction to the software industry and provides an overview of testing jobs within this field. Students will gain a solid understanding of the software development life cycle (SDLC) and the role of testing in ensuring the quality and reliability of software applications. They will explore various types of testing, such as functional testing, regression testing, and performance testing. Additionally, the module will highlight the importance of test automation and the benefits it brings to the software testing process. By the end of this module, students will have a clear grasp of the software industry’s landscape and the different QA testing roles available to them.

• 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 are 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 the SCRUM methodology ensure progress and alignment.
• Planning: Iterative planning processes to adapt and respond to changing project requirements in AGILE environments.

• Meetings and Ceremonies: Regular gatherings foster collaboration and alignment within AGILE teams.
• Sprint Planning: A detailed session outlining goals and tasks for the upcoming sprint cycle.
• Framework: a 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 facilitate AGILE project management and communication.
• Product Backlogs: a 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 is the ongoing process of refining and prioritizing items in the product backlog.
• PBI/PPBM: Product Backlog Item/Product Backlog Management: Essential Elements in AGILE Product development.
• Cross-Functional & Self-Organizing Team: Team structure promotes diverse skill sets and autonomy in decision-making within AGILE projects.

• 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 define the scope and functionality of features.

• Agile planning: It is the dynamic process of organizing tasks and allocating resources to achieve project goals efficiently.

• Estimation: a predictive assessment of the time and resources needed to complete 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.

• Introduction: An overview of the role and significance of business analysis in projects and organizations.

• BABOK (Business Analysis Body of Knowledge): A 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.

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

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

• RG Process (Requirement Gathering Process): A 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.

• BA Models: Various representations are 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 deliverable breakdowns.

• 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): a 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): a 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): a 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.

• 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 GlobeTecUsa Projects: Assistance and coaching provided to participants involved in GlobeTecUs 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.