Scrum Course Outlines

This course has been created for test managers, quality assurance staff, testers, software developers, project managers and management in order to explain how the Agile project management frameworks (notably SCRUM) deal with testing.
At the end of the course, each of the delegates will design and execute a test plan for a sample application (it can be an actual client application if available)
Where the requirements come from?
Traditional Business Analysis
Use Cases, Scenarios and Tests
Non functional requirements
Performance
Conformance
UML in Business Analysis
Introduction to testing
Functional Tests
Regression Test
UAT Tests
Unit Tests
Usability Tests
Non Functional Tests
Performance test
Load test
Stress test
Soak test
Test or not to test
Who is making decisions about what to test?
The cost of testing irrelevant things
Calculating ROI (what if something fails analysis)
The role of Test Manager
The process of Testing
Testing is a process and a strategy
Identifying testing needs
Gathering requirements (use cases, user stories)
Scoping (choosing and prioritize scenarios)
Designing tests
Preparing data
Preparing environment
Creating or Recording tests
Perform the test
Analysis and reports
Conclusions and improvement
When to say "stop"
Product owner and Tests
The customer representative and test priority
Prioritizing tests
Writing effective stories for UAT
Acceptance criteria
Group exercise to produce customer requirements and write stories based on the requirements and create tests
The sprint
Sprint backlog and tests user stories
Group exercise to plan a sprint
Finishing a sprint
Scrum review meeting is a test
Is Agile and Scrum for you?
Review of the Scrum process
Comparison with other methodologies
Benefits of pair programming
Question and Answers Session

This course is also know as SCRUM awareness training.
Who should attend?
This course has been created for managers, executives and other decision makers who want to know how to calculate the benefits of implementing the methodology or want to understand what their team is doing.
It is also suitable for customers of software development wishing to have a stake holding in the development process.
Short Overview of Project Management Methodologies and Frameworks
Chaos
Waterfall
Prince2
Agile
Why Agile?
Comparison of iterative methodologies
Why things go wrong
The Agile approach
What is Scrum?
Pigs and chickens
Product owner
The customer representative
Prioritizing product requirements
Writing effective stories
Acceptance criteria
Negotiating sprint contents
Group exercise to produce customer requirements and write stories based on the requirements
The sprint
Sprint backlog
Sprint planning: what to do
Sprint planning how to do it
What happens during a sprint
Burn down charts
Group exercise to plan a sprint
Scrum Master
Implementing Scrum
Ensuring proper practices
Maintaining documentation
Standup meetings
When to pair program
Group exercise to implement Scrum
Finishing a sprint
Scrum review meeting
Scrum retrospective meeting
Releasing an iteration
Group exercise the review a sprint
Is Agile and Scrum for you?
Review of the Scrum process
Comparison with other methodologies
Benefits of pair programming
Question and Answers Session

This course is for: Product owners, managers, or anyone interested in Agile planning and estimating techniques.
The course, Scrum Product Owner (SPO), utilizes a combination of presentations, discussions, and hands-on exercises explaining and demonstrating through practice. It illustrates what it is like to take on the role of an Agile team. The course covers all aspects of a product owner's involvement in an Agile product's life-cycle, such as gathering requirements rapidly, writing user stories, estimating story points, tracking, release planning, reporting, forecasting, scaling, and so on.
How to be an effective Product Owner
The Duties, Rights, Privileges
The Promoting self-organizing teams
How to Write User-Stories (Agile requirements)
Establishing and Knowing your stakeholders
Looking at Planning for quality
Addressing Story points
Discovering the Business value
How to manage an Agile product throughout the Software Development Life Cycle
The Creation and prioritizing of the Product Backlog
Sizing and Estimation
Looking at Effective team communication
How to Monitor, progress and look at forecasting
Reporting
Scaling
Agile Release Planning and Tracking

Who should attend?
This 2 day course is suitable for any IT professionals who are interested in implementing Iterative Agile and Scrum methodologies to manage software development. This course is particularly suited to project managers, team leaders, developers and customers of software development wishing to have a stake holding in the development process.
Why Agile?
Comparison of iterative methodologies
Why things go wrong
The Agile approach
What is Scrum?
Pigs and chickens
Product owner
The customer representative
Prioritizing product requirements
Writing effective stories
Acceptance criteria
Negotiating sprint contents
Group exercise to produce customer requirements and write stories based on the requirements
The sprint
Sprint backlog
Sprint planning: what to do
Sprint planning how to do it
What happens during a sprint
Burn down charts
Group exercise to plan a sprint
Scrum Master
Implementing Scrum
Ensuring proper practices
Maintaining documentation
Standup meetings
When to pair program
Group exercise to implement Scrum
Finishing a sprint
Scrum review meeting
Scrum retrospective meeting
Releasing an iteration
Group exercise the review a sprint
Is Agile and Scrum for you?
Review of the Scrum process
Comparison with other methodologies
Benefits of pair programming
Group exercise to discuss which aspects of Agile and Scrum can be applied to attendees organisations

This two-day course prepares current Scrum Masters for their leadership role in facilitating Agile team, program, and enterprise success in a SAFe® implementation. The course covers facilitation of cross-team interactions in support of the program execution and relentless improvement. It enhances the Scrum paradigm with an introduction to scalable engineering and DevOps practices; the application of Kanban to facilitate the flow of value; and supporting interactions with architects, product management, and other critical stakeholders in the larger program and enterprise contexts. The course offers actionable tools for building high-performing teams and explores practical ways of addressing Agile and Scrum anti-patterns in the enterprise.
Attending the class prepares you to take the exam and become a certified SAFe® Advanced Scrum Master (ASM).Audience
The following individuals will benefit from this course:
Existing Scrum Masters
Team leaders, project managers, and others who have assumed the role of an Agile team facilitator in a SAFe® or enterprise Agile context
Engineering and development managers who will be responsible for Agile execution and for coaching teams and teams of teams
Agile coaches
Agile program managers and prospective Release Train Engineers
Learning Goals
After this course, you should be able to:
Apply SAFe® principles to facilitation, enablement, and coaching in the multi-team environment
Build a high-performing team and foster relentless improvement at the team and program levels
Address Agile and Scrum anti-patterns
Support the adoption of engineering practices, DevOps, and Agile architecture
Apply Kanban and flow to optimize the team’s work
Facilitate program planning, execution, and delivery of end-to-end systems value
Support learning through participation in Communities of Practice and innovation cycles
Learning Objectives
Topics Covered
SAFe® framework, values, and Lean-Agile principles
Agile and Scrum anti-patterns
Program increment planning, execution, and Inspect and Adapt workshops
Quality engineering, Agile architecture, and DevOps practices
Kanban for facilitating team and program flow of work
Building high-performing teams
Interaction with the system team, deployment, UX, architects, product owners, product management, and business owners
Learning and Communities of Practice

This two-day course teaches teams who are part of an Agile Release Train (ART) how to work in an Agile environment using Scrum, Kanban, and XP. The teams will learn how to become Agile Teams, build their backlog, and plan and execute iterations. Agile teams learn about their ART and their role in it, planning, executing, and improving with other teams. This class prepares teams to run a Program Increment (PI), including all meetings at the Team and Program level with a specific focus on the upcoming PI planning.
Attending the class prepares participants to take the exam and become a certified SAFe® Practitioner (SP).Learning Goals
After this course, you should be able to:
Apply SAFe to scale Lean and Agile development in your enterprise
Know your team and its role on the Agile Release Train
Know all other teams on the train, their roles and the dependencies between the teams
Plan iterations
Execute iterations, demo value, and improve your process
Plan Program Increments
Integrate and work with other teams on the train
Topics Covered
Introducing the Scaled Agile Framework® (SAFe®)
Building an Agile Team
Planning the Iteration
Executing the Iteration
Executing the Program Increment

Objective:
This training course aims at helping product managers, products owners, business analysts, system architects and developers understand how to efficiently Manage Requirements on the basis of the product vision till guiding developers accurately in implementing them.
More in detail, this course aims at assisting product managers in better defining the value propositions of their products on the basis of strategies and stakeholder needs. Business Analysts and product owners understand how to describe requirements of the product backlog then discover appropriate epics and user stories of the system while contributing to the required value creation. Along interactive case study exercises, participants learn how to describe in detail such requirements in order to validate correct understanding of needs and prepare system acceptance tests. Thus, only using a very common and productive UML profile, they learn to structure requirements in order to communicate efficiently with architects and developers through an iterative requirement gathering process.
Audience:
Product Managers
Product Owners
Business Analysts
Anyone interetsted in the Requirements Management Process
Introduction
What is the Requirement Management Process ? Why Agile ?
Business agility and agile software delivery : Definitions
Linking Agile to Business : Business Motivation Model vs. Business Model Canvas,
How to effciently use the Value Proposition Canvas for defining the Product Vision ?
Business agility vs. agile software delivery principles
What is Agile Not ? Impacts of alignment with strategies and capabilities
Requirement Management in an Agile Context
Scrum Life Cycle : Issues about completeness of requirements and traceability
How productive models enhance communication in 'Agile' ?
Business Extensions of Agile : Structuring Business Value Contribution of a User Story
A Panorama of UML diagrams for modeling requirements
Frameworks for tracing requirements toward software implementation and tests
The 5 levels planning of an agile project (from Clarifying the Vision and Product Backlog to Tasks… and the Architecture Walking Skeleton)
Managing Requirements within Agile Methods (Scrum, DAD) vs. the Unified Process (RUP)
Roles, teams, environments
Presentation of the Case Study for Structuring requirements and managing them using an iterative process
How to describe the business vision and needs via traceable models ?
Qualification of the requirements : The Kano model vs. the Value Proposition Canvas
Structuring the Vision of the Product on the basis of strategies, environmental forces and trends
Value proposition, key activities, key resources, revenue streams and cost structures,
Discovering the business scope of the product using the customer needs, gains and pains
Describing business use cases using 'value streams' and 'value stages'
Bridging the business scope of the product with expected 'value contributions'
Case Study : Describing the vision of the product
How to describe user needs via agile use case modeling (epics and user stories) ?
Agile Estimating and Planning
Building and managing the product backlog / granularity of requirements
Ahead of the sprint planning
Creation of the sprint backlog
Agile User Story Pattern : system scope (the subject), actors, use cases, user stories, acceptance criteria, the INVEST model
The Walking Skeleton using Disciplined Agile Delivery : From Processes to Technology
How to find out epics and user stories on the basis of value streams ?
Value contribution of epics and user stories
Writing tasks : granularity and size using the SMART model
Case Study : Discovering epics and user stories on the basis of value streams
Validating and testing correct understanding of detailed specifications
Using an incremental requirement gathering process and the sprint backlog
Rules for efficient epic, user story and architecture descriptions
Diagrams for validating epics and user story descriptions
How to choose the right diagram ?
Refining features using use cases and relationships modeling
Testing correct understanding of requirements using Test-Driven Requirements
Given/When/Then structures and Operation Contracts for guiding developers in implementing requirements
Coverage analysis and change management
Case Study : Validating, testing and communicating detailed requirements to developers
Conclusion
Steps of efficient requirement gathering and system analysis processes
Traceability between requirements and analysis models
Patterns for gathering and testing requirements
Notice: The above training-mentoring sessions are conducted interactively using examples from Requirement Engineering and Modeling tools in order to ensure good level of traceability between requirements and underlying solutions. Concepts are first explained using basic examples and are then followed by solution drafts to your potential case. After this session, we can also accompany you by reviewing and validating your solutions depending on your needs.

This two-day course teaches the Lean-Agile principles and practices of the Scaled Agile Framework® (SAFe®). You’ll learn how to execute and release value through Agile Release Trains, how to build an Agile Portfolio, and how to lead a Lean-Agile transformation at enterprise scale. You will gain an understanding of the Lean-Agile mindset and how to apply the principles and practices of SAFe to support Agile teams, programs, program portfolio management, and to coordinate large Value Streams.
Attending the class prepares you to take the exam and become a certified SAFe® Agilist (SA).
Associated Certification: SAFe Agilist (SA)The following individuals will benefit from this course:
Executives and Leaders, Managers, Directors, CIOs, and VPs
Development, QA and Infrastructure Management
Program and Project Managers
Product and Product Line Management
Portfolio Managers, PMO, and Process Leads
Enterprise, System and Solution Architects
Learning Objectives
After this course, you will understand how to:
Apply SAFe to scale Lean and Agile development in your enterprise
Support the execution of Agile Release Trains
Coordinate large Value Streams
Manage a Lean-Agile Portfolio
Align the organization to a common process model
Configure the Framework for your context
Unlock the intrinsic motivation of knowledge workers
Support a Lean-Agile transformation in your enterprise
Topics Covered
Introducing the Scaled Agile Framework (SAFe)
Embracing a Lean-Agile Mindset
Understanding SAFe Principles
Implementing an Agile Release Train
Experiencing PI Planning
Executing and Releasing Value
Building an Agile Portfolio
Coordinating Large Value Streams
Leading the Lean-Agile Enterprise

This course is a comprehensive introduction to the world of Scrum for all those prospective members of the Scrum team (analysts, developers, testers et al) who want to be more effective as a Scrum member, but don’t particularly want to become a ScrumMaster or Product Owner.
For those who do want to become a ScrumMaster, it also provides a good introduction to the Scrum Alliance Certified ScrumMaster syllabus.
Overview of Agile
Comparison of Agile to traditional methodologies
The Agile manifesto and principles
Benefits of Agile
Scrum overview and context
Scrum Development Process
Scrum components – 4 ceremonies, 4 artefacts, 3 roles
The Scrum Process
User Stories
Understanding User Stories
Story grooming
Effective Teamwork
Self-organising team principles
Techniques for developing more effective teamwork
Estimation
Estimating principles
Estimating as a team with Planning Poker

QA/CI
What is QA?
What is CI
The costs of software development, refactoring and fix errors
Identifying and understanding the project
Profit for the organization
DDD
Software development based on business requirements, assumptions DDD
Problems in communication IT-Business
Domain Model
Best Practices
KISS principle and DRY
Coding standards
Creating reusable code through OOP and design patterns
Identifying and reducing cyclomatic complexity
Software Metrics
Weight Method per Class
Response For a Class
Depth of Inheritance Tree
Coupling Between Objects
Lack of Cohesion of Methods
Number of Children
Cyclomatic complexity
Metrics class
Model Metrics
Metrics for use
Software Testing
What, when and how to test?
The method of "white-box" and "black box&quot
The role of testing in agile methodologies
TDD only a potential increase in the cost of the project
Unit testing
Behavioral tests
Functional tests
Refactoring
What is refactoring?
Debt technology
Code smell
Refactoring patterns
Documentation
The role of documentation in agile methodologies
What to document?
Types of documentation
Documentation and agile methodologies, or you can call (Working software over comprehensive documentation)?
Standard XMI
Automatic generation of documentation
Tools and Environment CI
Tools and Environment CI
Agile and CI/QA
Planning and incremental development
Embracing Change
Short stages
Interdisciplinary team
Extreme Programming, Code Review
Individuals and interactions over processes and tools
Summation
Discussion
Questions
How do you begin the process of implementation?
Introduction to testing
Functional Tests
Regression Test
UAT Tests
Unit Tests
Usability Tests
Non Functional Tests
Performance test
Load test
Stress test
Soak test
Test or not to test
Who is making decisions about what to test?
The cost of testing irrelevant things
Calculating ROI (what if something fails analysis)
The role of Test Manager
The process of Testing
Testing is a process and a strategy
Identifying testing needs
Gathering requirements (use cases, user stories)
Scoping (choosing and prioritize scenarios)
Designing tests
Preparing data
Preparing environment
Creating or Recording tests
Perform the test
Analysis and reports
Conclusions and improvement
When to say "stop"
Product owner and Tests
The customer representative and test priority
Prioritizing tests
Writing effective stories for UAT
Acceptance criteria
Group exercise to produce customer requirements and write stories based on the requirements and create tests

The self-organising Scrum Team is the bedrock of the Scrum development process. An effective team is directly related to more effective delivery of products of value. Belbin Team Roles theory is used worldwide to help create more effective teams, in all kinds of environments. This course is led by a Belbin Accredited Trainer and Certified ScrumMaster. It provides a detailed overview of Scrum and examines how understanding Belbin Team Roles can benefit the Scrum Team.
Scrum Overview
The Agile manifesto and principles
Scrum components – 4 ceremonies, 4 artefacts, 3 roles
The Scrum Process
Belbin Team Roles
The 9 Belbin Team Roles
Developing your individual strengths for team success
Understanding allowable weaknesses
Understanding Team Roles in the Scrum Activities
User Story grooming
Backlog estimation
Self-organising task allocation
Review and retrospective meetings
Team Dynamics
Understanding how others affect your behaviour
Handling difficult people
How to deal with missing Team Roles

This course is designed for testers, from a traditional test background, who are seeking to find their place in an Agile development environment. There is no specific Tester role in Scrum - there is just the Team. The Team collectively is responsible for the quality of the delivery, including testing, and so the ‘traditional’ Tester role is redundant. However, this course demonstrates how a Team member specialising in testing can add a great deal of value in the Scrum development process.
Overview of Agile
The Agile manifesto and principles
Benefits of Agile
Scrum overview and context
Scrum Development Process
Scrum components – 4 ceremonies, 4 artefacts, 3 roles
The Scrum Process
Comparison of V-Model to Agile Approach to Software Testing
Traditional requirements v User Stories
Valuing working software over documentation – what test documentation is needed?
Conveyor belt v Collaboration – working in one Team
The Contribution of the ‘Test Perspective’ to:
The Sprint Review
The Sprint Retrospective
Backlog grooming and estimation
The Test Specialist’s Tool Bag
Exploratory testing
Automated testing

Target group:
IT Director, Project Manager, Technical Team Leader, Analyst, Software Developer, Tester
Learning objective:
The purpose of this training is to acquire knowledge and practice of the workshops aspects of Kanban and Agile foundations.
Introduction to Agile
Why Agile?
What are the main objectives of Agile?
How works mechanisms in Agile?
How Agile can help?
Command & Control vs. Agile
Factory model
The functioning of canon
The functioning of missile
Pillars of Kanban
Big Picture
Process
Concepts behind Kanban
Kanban Rules
Metrics
Flow Diagram
+ technical practices
Team work
Shared responsibility
Self-organization
Interdisciplinary
Benefit the "right" team work
Kanban Board
How to visualize process?
How to create Kanban Board?
What are and how to introduce WIP limits?
What are and how to introduce Classes of Service?
Customer Engagement
The most common waste
Value Stream
Waste
Value Stream Mapping
Waste analysis
Main concepts behind Kaizen (MUDA / MURI / MURA)
Bottlenecks analysis
Five Focusing Steps
Simulation
Simulation game
Discussions
Advanced topics

NobleProg® Limited 2004 - 2016 All Rights Reserved
This site is operated by the NobleProg franchisor . If you interested in opening a franchise in your country, please visit http://training-franchise.com for more information.

NobleProg® is a registered trade mark of NobleProg Limited and/or its affiliates.