Course Description

As with life in general, there is more to do than time to do it, so we have to prioritize to suit the participants

Objectives


Topics Covered

* = Required for certification

* Product Ownership

  • Your organization may encounter challenges to product ownership
  • The Product Owner job has three main dimensions that make it a very large job for one person

* Opening

  • The overall objectives of the course are listed
  • The course materials include too much information for the time available. What shall we do?

* Scrum Planning

  • Scrum planning is continuous
  • Scrum planning happens at 5 levels, each with a different time horizon
  • The Product Backlog is the primary source of work to be completed and value to be delivered

* Product Vision

  • The Vision describes the purpose of the product to be created or enhanced
  • There are several ways to present the vision as a common goal for the Scrum Team
  • The Vision is the inspiration for the Product Backlog

Product Roadmap

  • Roadmapping is a tool for creating a longer term release strategy
  • Roadmaps describe the product in very high level terms

* User Stories

  • User Stories are simple descriptions of desired functionality
  • Stories are elaborated just-in-time for implementation
  • Stories are used for planning
  • The INVEST Criteria help us write good stories

* Prioritization

  • Priorities help the Scrum Team decide what to do next
  • Priorities help with long term planning
  • Prioritization can be done in many ways, based on many criteria

Estimation

  • Agile estimation is done at both the high level and the low level
  • Estimates are used for planning and for tracking progress
  • Estimates are done quickly, by the Development Team
  • Estimates are not commitments

* Just in Time Elaboration

  • Story elaboration is done just in time to reduce wasted time defining details that may never get used
  • Details are provided to the Dev Team as conversations, acceptance criteria and speclets
  • Details may also lead to story splits

* Release Planning

  • There are two basic product release strategies based on time and scope
  • Risk is reduced by including slack in the plan
  • Release tracking and forecasting are based on real data about actual product completed

FAQ/Parking Lot

  • What questions remain?

Product Ownership Review

  • The Product Owner is a navigator in the world of profit-making
  • What skills would you look for in a Product Owner?

* Closing

  • More information for Product Owners
  • Wrapping up

* Agile Principles

  • Agile software development implements Lean principles and dynamics
  • The primary driver of Agile work is Value
  • Scrum is one form of Agile, designed initially for software development, but applicable to other kinds of work

* Scrum Framework

  • Scrum has 4 meetings and 3 artifacts
  • Scrum has 3 roles that share the responsibility of creating value in small increments
  • The roles complement each other to create a balanced team

Story Splitting

  • Smaller stories are easier to work with and enhance flow
  • Smaller stories gives us more options to reduce scope

* Working with the Dev Team

  • The Dev Team may propose stories for the Product Backlog
  • Teams take time to mature
  • The Dev Team is self-organizing
  • Awareness of effective motivators can help build a high performance team

Working with the ScrumMaster

  • The ScrumMaster is your partner in achieving a smooth flow and continuous improvement
  • The ScrumMaster is a productivity multiplier for the Team

Working with Stakeholders

  • Customers are not your only Stakeholders
  • You can’t please everyone all the time

Agile Testing

  • Testing during the Sprint
  • Agile testing practices
  • Roles/responsibilities in testing:

* Scrum Meetings

  • Scrum organizes work into 1-4 week time boxes called Sprints
  • Each Sprint has 4 primary meetings
  • The bulk of the time is spent creating value in the form of a product

* Product Backlog Management

  • A well-managed Product Backlog keeps the Development Team running smoothly
  • A 1-sprint look-ahead on stories will help the flow
  • The Team needs details Just In Time
  • Defining Ready and Done will dramatically reduce time waste

Electives

  • Where do Stories Come From?
  • Agile Teams may build product faster than traditional methods can discover user needs
  • There are few more Agile methods for finding customer needs

Budget and Finance

  • Budgeting relies on Release Planning
  • Velocity is the primary unknown in budget requests
  • Some organizations are moving to more Agile budgeting models

Scaling Scrum Up and Out

  • Scrum can scale to many Teams
  • Distributed Scrum is constrained by the laws of physics but there are patterns that can help

Portfolio Management

  • Agile and Scrum concepts can be applied at the product portfolio level

Homework

  • Read 2 articles
  • Discuss one

Focus and Flow

  • Scrum works best when the Team achieves a smooth flow of work
  • Scrum dynamics are based on the mathematics of queuing theory that we use to manage the Internet
  • Continuous improvement is an underlying goal of Scrum

Other Prioritization Tools

  • Relative Weighting can be applied to Stories
  • Financial Projection can be applied to Releases and Features
  • Innovation Games can quickly get input from your customers

Action Plan (Private classes only)

  • What concrete actions can we take to incorporate these concepts in our Scrum work?

Audience and Certification Details

This course is intended for anyone who will actively participate in a project using this approach. People on the edges of the project (secondary customers, management staff, and participants in related processes) will also benefit. Project teams are encouraged to attend as a group.

Prerequisites

None.

Duration

2 Days

Price

Call (636) 530-7776 ext 803 for private, on-site training.

Not sure where to start? We provide phone and on-site assessments.

Learn more

Training Course Feedback