Certifications and Workshops

Agile Engineering Practices Workshop – 2 Days Workshop

Program Overview: TWO Days of Training and Coaching Workshop

This 2 days training is to give engineering teams an overview of the most popular engineering practices under the agile umbrella. We can extend this to a 3 day training if specific practices need more focus.

Day 1

Delivery lifecycle in an Agile project

Introducing XP

Fine-scale feedback
- Pair programming
- Planning game
- Test-driven development
- Whole team
Continuous process
- Continuous integration
- Refactoring or design improvement
- Small releases
Shared understanding
- Coding standards
- Collective code ownership
- Simple design
- System metaphor
Programmer welfare
- Sustainable pace

Test Automation

Test pyramid
SOLID principles
Unit testing through Junit
Junit idioms and patterns
What is Agile testing?
Functional test automation through Selenium

Day 2

Test Driven Development

Introduction to TDD
Test First Vs Test Last
TDD Rhythm: Red, Green, Refactor
Crucial Design Principles
TDD and Design
Avatars of TDD

Executable Specification (ATDD/BDD)

Crafting acceptance criteria for user stories
Writing executable examples for each criterion
Demo of BDD frameworks (Cucumber, FitNesse, SpecFlow, Jasmine)

Continuous Integration and Continuous Inspection

Automated static code review with Maven plugins and Jenkins
SonarQube based continuous inspection

Continuous Delivery vs Continuous Deployment

Distributed Version Control Systems (git) and branching

Trunk based development
- Feature toggle
Feature branch based development
Trunk based development vs feature branch

Non functional testing in Agile project

Performance testing
Security testing

Terms and Conditions:

Number of participant/trainees in a batch should not exceed 20 people.

Method of Instruction

Interactive Dialogues, Programming Exercises, Demos, and Instructional Games

Target Audience

Primary: Sr. Object-Oriented Programmers, Architects, and Designers
Secondary: Technical Managers, Testers

Course Level

Intermediate to Advanced

Course Prerequisites

Required: some understanding of OO concepts and an OO language
Highly Recommended: basic understanding of the life-cycle of software projects

General Requirements

To ensure a successful class, we require the following facilities:

VGA projector (1024×768 minimum) & Projector screen
1 White board & Dry erase markers
Cluster seating with 5-6 people on each table
1 Flip chart with the stand and marker pens for each table
Notepad and Pen for each participant
Ample room for students in terms of room size and set up
For Dev trainings: at least one powerful workstation between two programmers

Development Tools

Latest Java JDK
Latest Standard EclipseOR IntelliJ Idea
JUnit, Mockito, JBehave, FitNesseor Cucumber JVM

Behavior Driven Development (BDD) with Behat/Mink – 2 Days Workshop

Program Overview: Two Day Training and Coaching – Hands-on workshop

Acceptance tests prove your solution actually works, and using them to implement executable specifications proves your solution does what it should do. In this course we look at capturing requirements as executable specifications and implementing them as end-to-end tests with Behat.

Format of Workshop:

Participants get to understand behavior driven development in the form of sessions and hands-on exercises and discussions.

Learning Outcomes:

Behat is an absolute favorite library to use. First, it let’s you think about the behavior of the features first, before you start developing. In this tutorial, we’ll do that, and it’ll change the way you develop. Second, Behat turns that written behavior into functional tests against your application. Does your feature behave correctly? Just run the automated robots to find out!

Along the way, we’ll master Mink – the partner library to Behat. Here are the learning outcomes of this workshop:

That BDD is primarily a communication tool, to be used by the whole team
Understand other disciplines, perspectives on communication issues within the team
Understand the importance of developing a ubiquitous language within the team
Experience of the BDD process: breaking down user stories into scenarios
Understand the distinction between features, user stories. acceptance criteria and scenarios, and how those artifacts can be used by each discipline
Understand the difference between unit testing and acceptance testing, and the
importance of each
See what Behat is, and how it can be used to automate BDD scenarios
Learn the syntax of Behat and implement the same for acceptance scenarios

Following topics in detail will be addressed in 2 days:

What is BDD?
Practical exercise: breaking down user stories into scenarios
Writing acceptance criteria for user stories
- Feature acceptance tests
- Technical acceptance tests
- Negative acceptance tests
- Writing BDD scenarios for acceptance criteria
- Splitting user stories that are too big
- Behat demo
- Behat syntax
- Writing readable specifications
- Demo (part 1): Given steps
- Demo (part 2): When steps
- Demo (part 3): Running the test
- Practical exercise: imperative vs declarative style
- Working with Behat and Mink
- Step Definitions
- BEHAT History
- Context Class
- PHP Versions
- Assertions
- Installation
- Command Line
- Quick Usage Reference
- Gherkin Language
- Features
- Mink Web Testing
- What you will learn?
- Behaviour Driven Development
- Context Class and Assertions
- BEHAT Overview and Configuration
- Command Line Usage
- End to End BEHAT Examples
- Syntax – Givens, Whens, Thens, And, But
- Understand Features, Scenarios, Step Definition
- Test Data
- Mink for Web Testing
- Traps, pitfalls, hints and tips
- Facilitating specification workshops
- Choosing what to automate
- How Scrum, Kanban and BDD fit together
- How to track progress and predict velocity with Kanban
- Collecting metrics to measure the success of your BDD adoption

When conducting these workshops, we focus on an organization’s specific needs, challenges and expertise level in Agile as BDD implementation has lot to do with Agile maturity of a team/organization.

Facilitator will address all the questions from participants about applying BDD practices on real life projects.

Prerequisites:

Object oriented PHP knowledge
Drupal 7 experience
Some familiarity with Linux and Command Line tools.
A laptop with VirtualBox, Vagrant, and your favorite IDE or code editor installed.

Infrastructure requirements:

Participants will be divided to pairs. Each pair will be sharing a laptop
1-2 whiteboards at least and markers of different colors
Laptops or desktop for a pair

Behavior Driven Development (BDD) with SpecFlow – 2 Days Workshop

Program Overview: Two Day Training and Coaching – Hands-on workshop

Format of Workshop:

Participants get to understand behavior driven development in the form of sessions and hands-on exercises and discussions.

Learning Outcomes:

That BDD is primarily a communication tool, to be used by the whole team
Understand other disciplines, perspectives on communication issues within the team
Understand the importance of developing a ubiquitous language within the team
Experience of the BDD process: breaking down user stories into scenarios
Understand the distinction between features, user stories. acceptance criteria and scenarios, and how those artifacts can be used by each discipline
Understand the difference between unit testing and acceptance testing, and the
importance of each
See what SpecFlow is, and how it can be used to automate BDD scenarios
Learn the syntax of SpecFlow and implement the same for acceptance scenarios

Following topics in detail will be addressed in 2 days:

What is BDD?
Practical exercise: breaking down user stories into scenarios
Writing acceptance criteria for user stories
- Feature acceptance tests
- Technical acceptance tests
- Negative acceptance tests
- Writing BDD scenarios for acceptance criteria
- Splitting user stories that are too big
- SpecFlow demo
- SpecFlow syntax
- Writing readable specifications
- Demo (part 1): Given steps
- Demo (part 2): When steps
- Demo (part 3): Running the test
- Practical exercise: imperative vs declarative style
- Working with SpecFlow
- Automating WPF
  - Demo (part 1): Then steps
  - Demo (part 2): Finishing the test
- Automating the browser
  - Demo (part 1): Technical steps
  - Demo (part 2): Resetting state
- Checking the database
- The discontinue and reorder features
- Reorder by email
  - Demo (part 1): Papercut
  - Demo (part 2): SMTP stub
  - Demo (part 3): Verifying emails
- Reorder by web service
  - Demo (part 1): WCF stub
  - Demo (part 2): Verifying web service calls
- Reorder by message queue
  - Demo (part 1): message handler stub
  - Demo (part 2): Verifying messages
- Technical acceptance tests
- Get product AIP feature
  - Demo (part 1): The GET feature
  - Demo (part 2): Automating the GET
  - Demo (part 2): Negative testing
- PUT product API feature
  - Demo (part 1): Discontinue with PUT
  - Demo (part 2): Reorder with PUT
- PUT product acceptance tests
- API performance feature
  - Demo (part 1): Load testing with loader.io
  - Demo (part 2): Message handler stub
  - Demo (part 3): Verifying messages
- Performance testing in the cloud
- Traps, pitfalls, hints and tips
- Facilitating specification workshops
- Choosing what to automate
- How Scrum, Kanban and BDD fit together
- How to track progress and predict velocity with Kanban
- Collecting metrics to measure the success of your BDD adoption

Facilitator will address all the questions from participants about applying BDD practices on real life projects.

Prerequisites:

Basic .NET knowledge is recommended so the participants can actively contribute with questions and shared experiences.

Infrastructure requirements:

Participants will be divided to multiple teams of 3-4 people. Each team will be sitting around round table
2-3 whiteboards at least and markers of different colors
Laptops or desktop for each participant

Continuous Delivery for Practitioners – 2 Days Workshop

Program Overview: Two Day Training and Coaching – Hands-on workshop

This 2 day training course is an introduction for practitioners to Continuous Delivery – a delivery method that advocates the creation of an automated Deployment Pipeline to release software rapidly and reliably into production.

Continuous Delivery

The goal of Continuous Delivery is to adopt a holistic end-to-end delivery perspective and optimise cycle time – the average time from code checkin to production release – so that costs are lowered, risks are minimised, and revenues are increased via faster customer feedback. This training course will explain the principles of Continuous Delivery, how to automate a Deployment Pipeline including zero-downtime production releases, and how combining Continuous Delivery with DevOps can deliver success in both startup and enterprise organisations.

Learning Outcomes

In this course, you will learn:

What Continuous Delivery is, and why it has such a compelling business case
How the Deployment Pipeline pattern enables a reliable, repeatable automated release mechanism
How to weave together different technologies to form an automated pipeline
How development practices can enable the evolutionary design of an always releasable codebase
How automated acceptance testing, smoke testing, and operational testing reduce risk and empower testers
How incremental releases and database updates enable zero-downtime production releases
Why Continuous Delivery needs organisational change, and how DevOps can help

You only need a laptop if you wish to take electronic notes – course and exercise materials are supplied.

Agenda

This training course comprises 2 days of in-depth discussions and group exercises aimed at developers, technical leaders, architects, operations engineers, testers, performance engineers, etc.

Day 1:

What is Continuous Delivery

Discussion: Your Release Process
The Last Mile Problem
What Is Continuous Delivery
Continuous Delivery Principles

The Deployment Pipeline

The Deployment Pipeline
Deployment Pipeline Practices
Work In Small Batches
Exercise: Isabel’s Issued Invites [Lean Envelopes]

Building A Pipeline

Deployment Pipeline Toolchain
Automated Configuration
Automated Infrastructure
Deployment Pipeline Patterns

Developing For The Pipeline

Trunk Based Development
Incremental Design Practices
Effective Architecture
Discussion: Your Pipeline

Day 2:

Testing In The Pipeline
- Discussion: Your Testing
- Continuous Testing
- Automated Testing Patterns
- Testing External Systems
Operations In The Pipeline:
- Release And Remediation Plan
- Incremental Release Patterns
- Databases And Data
- Business Monitoring
Organisational Change

Exercise: Percy’s Paper Planes [Lean Aeroplanes]
The Need For Change
How To Drive Change
Discussion: Your Organisation

Adopting Continuous Delivery
- Exercise: Dialogue Sheet
- Discussion: Your Adoption Plan

Audience max 20 practitioners
Duration 2 days
Location On site

Scrum Product Owner – 2 Days Workshop

Program Overview: TWO Days Training and Coaching Workshop

It is designed especially for Business Analysts, Product Managers, and Product Owners and for those who want to grow to Agile Product Owner role or for Senior Management who want to implement Agile Product Ownership in their Organization. Participants can maximize the benefit they receive from their Agile projects by learning how to better prfioritize and interface with Agile teams. The high level learning goals of this Workshop are:

Outcome of this workshop:

How to best fulfill your role as Product Owner(PO) towards a Scrum team
How to effectively create, groom, and prioritize the Product Backlog
How to do Sprint Planing and Release planning using story mapping
How to create a personas, user stories to conceptualize the product
Role of PO in Sprints and sprint meetings
Applying key Agile Management practices to improve effectiveness of business solution and of Agile teams
Using Agile estimation and release planning by pointstechnique to better forecast their work
How to structure your teams to facilitate collaboration, and self-organization to maximize business value to the clients
Using Agile empirical metrics to measure progress and quality
How to be effective PO in distributed agile teams and address communication, trust, and quality issues

Format of Workshop:

Participants get to understand core principles and in-depth Agile/Scrum framework in the form of videos, group discussions, exercises, interactive sessions, innovation games. Facilitator will address all the questions from participants about applying Scrum on real life projects.

Following topics in detail will be addressed in 2 days:

Why and What is Agile
- Industry facts about failures and need for Agile
- Agile Values and Principles
- Agile vs Traditional Approach
- Business outcome and stats of using Agile
- Lean Innovation game – Batch vs Flow

Scrum framework in detail
- Scrum Roles(Product Owner,ScrumMaster and Team)
- Scrum Ceremonies and artifacts
- How to prepare for Sprint planning, pre-planning
- Velocity and Commitment driven planning techniques
- Role of PO in Sprint planning, daily stand-up, demo and retrospectives
- Role of PO in backlog grooming and making it effective

Product Ownership and Personas
- Crafting product vision
- Facets of customer needs
- Identifying and modeling users
- Personifying for a business case with example
- Different PO Success modes
- Overcoming 6 common problems of PO

User Stories
- What Is/Not a User Story and 3C/INVEST model
- Functional and Non-Functional Stories
- How to validate requirements using acceptance criteria
- Writing acceptance criteria with examples
- Who and When to write stories with tips
- Applying story splitting patterns to break stories
- Exercise on Story writing

Agile Estimation and Planning
- Using sizing technique for estimation and planning
- Story Point Estimation and How to do it using planning poker
- How to use sizing/velocity for release planning
- Calculating capacity using focus factor and using it for sprint planning

Progress Tracking using Agile Metrics
- How to create and use Burn-down charts
- Different charts and metrics effectiveness and its different usages
- How to use story wall to find project progress
- Using Release burn-down and story acceptance charts

Backlog Prioritization and Release planning
- How to make your product backlog DEEP
- Prioritization using themes
- Prioritization using desirability
- Converting Flat backlog to hierarchical backlog with sequencing, dependency and with perceived business value prioritization
- Release planning using Story Mapping technique
- Using story thinning parameters
- Exercise: Solving a business case by creating personas, user stories and then using story mapping to create a release roadmap

Scaling Scrum
- Effective scaling strategies for teams/organization
- Different distributed agile models to apply across different geographies and how to make product ownership effective on distributed scrums

Explore the site and our blog http://www.agilebuddha.com, and get to know us. Then, if you think I might be right for your organization, contact us. We would love to help you get started or get better with agile.