Business and System Analysis using UML Notation - Practical Workshop for PO in the Scrum Methodology

• An understanding of software development life cycle and agile principles
• Experience with working in a Scrum team as a product owner or a business analyst

Audience

• Product owners
• Business analysts
• Anyone seeking to understand the role and responsibilities of a product owner in the Scrum methodology

• UML (Unified Modeling Language) is a standard graphical language used to model and document software systems, representing various aspects such as structure, behavior, interaction, and requirements. It helps product owners and business analysts communicate clearly and consistently with developers, testers, and stakeholders.
• This instructor-led, live training is designed for beginner to intermediate-level product owners and business analysts who want to use UML notation for business and system analysis within the Scrum methodology.
• By the end of the course, participants will be able to use UML notation to model and document business processes, use cases, user stories, acceptance criteria, system architecture, components, classes, objects, interactions, behavior, state, activity, and system requirements, constraints, and assumptions.
• They will also learn to use UML tools and diagrams to facilitate and support the Scrum process and artifacts.
• The course format includes interactive lectures, discussions, plenty of exercises, and hands-on practice in a live-lab environment.
• Customized training options are available upon request.

Business Process

• Business process concept
• Business process modeling
• Business and analytical models - connections and elements

Business Process Modeling

• Diagrams related to business processes
• Mapping and documenting business processes

Requirements Analysis

• Requirements concept
• Collecting and documenting requirements
• Relationships between requirements
• Linking requirements with the analytical layer

Modeling the Solution

• Types of domain modeling approaches
• Rationalizing the depth of analysis
• Analysis and project risks

Solution Model and Agile Methodologies

• Agile methodologies - opportunities and threats
• Correlation between documentation and elements of agile methodologies

Techniques for Verifying Model Correctness

• Informal validation techniques
• Review of formal correctness verification techniques
• Correctness verification procedures during the project

Organizing Project Documentation

• Good practices
• Ensuring tracking of changes
• Security and versioning aspects

Embedding Analytical Work within Management Methodologies

• Management methodologies and analytical work
• Aspects of influence
• Project progress control and analytical work