Course #:TP2818

Introduction to Product Thinking for Agile Teams Training

The advent of agile has helped teams increase delivery speed, increase quality, and increase overall productivity.
When a team transitions from waterfall to agile, it’s very common to still hang on to old ways of thinking.   One of the last hold-outs is typically keeping a “project” mindset, where everything has to be fit into a project structure.  This fits in with the “big planning up front” mentality, which is not agile at all.
While there will always be larger initiatives, it’s important for teams to transition to a “product” mindset, where testing every idea before implementation is part of the culture, and software isn’t just delivered and forgot about.  The value of the software that’s delivered should be measured and customer feedback actively sought, which then becomes feedback for new ideas.

Objectives

In this course we’ll cover how to make the transition from project thinking, to product thinking.  We will also introduce techniques on measuring the customer value of features, along with how the software delivery process can be changed to support this new way of thinking.

Duration

Two days.

Outline of Introduction to Product Thinking for Agile Teams Training

Chapter 1. Agile Overview

  • Definition
  • Scrum overview
  • XP overview
  • What agile is not

Chapter 2. Product Thinking vs Project Thinking

  • Project definition
  • Attributes of project-based organizations
  • Product definition
  • Attributes of product-based organizations

Chapter 3. Impact of Architecture and Software Development Practices

  • The draw backs of monolithic architecture
  • Microservices
  • Quality isn’t just for QA
  • TDD
  • BDD

Chapter 4. Lean Startup

  • Purpose
  • Who is the customer?
  • Lean Canvas
  • Build-Measure-Learn
  • The MVP
  • Pivot of persevere
  • Development practices

Chapter 5. Design Thinking

  • Definition
  • Empathize
  • Define the problem
  • Ideate
  • Prototype
  • Test

Chapter 6. Applying product thinking to agile

  • Self organization
  • Component teams vs feature teams
  • Dual track agile
  • Discovery phase
  • Implementation phase

Chapter 7. DevOps

  • Principles
  • The value stream
  • Automate everything
  • Feedback loops
  • Tools







We regularly offer classes in these and other cities. Atlanta, Austin, Baltimore, Calgary, Chicago, Cleveland, Dallas, Denver, Detroit, Houston, Jacksonville, Miami, Montreal, New York City, Orlando, Ottawa, Philadelphia, Phoenix, Pittsburgh, Seattle, Toronto, Vancouver, Washington DC.