Course Description
Do you consider yourself a key stakeholder when it comes to delivering agile projects? Do you find that you are often required to provide the vision of what needs to be created or built? If you are nodding yes, then you are fulfilling the role of product owner when it comes to agile projects. Agile sounds great, but you have questions about how it will work for you and your project team/ organization. There are technical and general issues that need to be addressed, and that is what this course was designed to do.
You will discuss the business value of using Agile and why you will have to collaborate with IT. The course also addresses who the product owner is, how to be effective in that role, and what that role entails as well as what the new expectations will be. You will learn what user stories are and how to write them. The course touches on the roles of the users and business SMEs as well as acceptance test, how to identify them, and when to use them.
This course provides you with real world best practices and offers tips on how to use them to motivate your team. It is also an objective of this course to prepare you for your leader role in this Agile project process.
- Explain the history of the Waterfall development
- Explain why Agile and the Value proposition
- Describe Agile values and principles
- Explain Scrum and the roles and processes associated with it
- Define the product owner roll (in-depth)
- Define expectations from you
- Describe time management for the busy project owner
- Explain your expectations of the team
- Describe the roles of business users and SMEs
- Explain vision and conditions of satisfaction
- Practice building a story backlog
- Explain best practices for identifying and writing stories
- Describe how to write an acceptance test
- Explain how to do User acceptance testing
- Describe how to be a leader and set goals
- Motivate high performing teams
Agenda
Agile for Product Owners
Agile for Product Owners
About Me
Organizing Tools
Purpose of this Course
About You
Agenda
Overview of Agile
Overview of Agile
The Traditional Way
The Agile Way
With an Agile Approach…
Waterfall vs. Agile
The Agile Manifesto – 2001
Agile Principles
What is Agile?
The Iterative Process
Requirements: Incomplete and Otherwise
Requirements Myth
The Requirements Disconnect
The Requirements Reality
The Agile Team
The Agile Team
The Leadership Triangle
Agile Roles- Product Owner
Agile Roles- ScrumMaster
Agile Roles- Architect
Agile Roles- The Team
Generalizing Specialist
Agile Roles- Sponsors and Stakeholders
Agile Roles- Management
Real World Role Challenges
Agile Team Best Practices
Deep Dive into the Product Owner Role
Deep Dive into the Product Owner Role
The Agile Product Owner Cheat Sheet
Engaging Through the Lifecycle
Sample: Minimum Product Owner Time
Pre-Planning for Next Iteration
Successful Time Management for Bust Product Owners
Product Owner Proxies/Vacant Owners
Leading to Self-Organizing Teams
Shifting Towards Servant Leadership
Identify Your Stakeholders/Users
Stakeholder Context Diagram
Stakeholder Engagement
Understanding the Decision Types
Lean Portfolio Management
Lean Portfolio Management
The Multi-Tasking Name Game
Multi-Tasking
Allocating Projects Beyond Capacity
Single Team
Multi-Team Program
Portfolio View
From Portfolio Ideas to Team Backlog
What Makes an Idea Worth Initiation?
Agile Idea Qualification Checklist
Common Problems with Idea Qualifications
Root Cause
Project Initiation Goals
6 Steps for Measuring Value
Actually Measuring Value Post Release
Alternative Solution Analysis
The Agile Delivery Process
The Agile Delivery Process
6 Levels of Agile Planning
Agile Requirements Levels
Product Themes
Building a Product Roadmap
What is ‘Just Enough’ Planning?
Project Vision
Project Vision
Product Vision
What’s in a Charter
Vision Statement
Vision Box
Sample: Front of the Box
Sample: Back of the Box
Defining Conditions of Satisfaction
Sample Project ‘Done’ Criteria
User Personas
User Personas
User Roles
Organizing Roles
Refining Roles
User Personas
Sample Persona
Sample Persona 2
User Stories
User Stories
What is a Story?
User Stories: Examples
Guidelines for User Stories
User Stories: I.N.V.E.S.T
Sample Backlog
Story Grouping by Feature
Example Requirements Levels
Feature/EPIC
Story
Acceptance Criteria- Example
Principles for Identifying Stories
Identifying Features/Stories
Story Writing Workshops
Story Mapping
Story Map Example
Finding Additional Stories
User Stories: What to Watch For
Scaling the Product Backlog
Documenting Acceptance Criteria
Documenting Acceptance Criteria
Acceptance Criteria
Why Acceptance Criteria?
Identifying Acceptance Criteria
What are good Acceptance Criteria?
Acceptance Criteria- Example
Acceptance Criteria
Breaking Down EPICS
Breaking Down the EPICS
Breaking L:arge Stories into Smaller Chunks
Sample Compound Stories
Sample Complex Stories
Techniques for Slicing Stories
Process Based Breakdown
User or Platform Based Breakdown
EPIC Example
Backlog Prioritization
Backlog Prioritization
It’s All About Prioritization!
Sequencing/Dependency Chart
Estimating – Business Value
Prioritizing Requirements Using Business Value Buckets
Kano Analysis
Kano Modeling
Sequencing Chart
Prioritization
Estimating & Sizing
Estimating & Sizing
Estimating
Sizing Stories
Why Story Points?
Using Story Points
Story Points – Fibonacci Scale
Story Points Scale for EPICS
Planning Poker
Building a Release Plan
Building a Release plan
Team Velocity
Sample Point and Cost Burn Up Chart
Release Planning
Sample Agile Release Plan
Pre-Planning
Pre-Planning
Backlog Grooming
Pre-Planning for the Next Sprint
Story Elaboration – Methods
Model Storming
Writing Acceptance Tests
Why Acceptance Test?
Acceptance Tests
Business Rules
Sample UI Prototypes
Do You Really Need Pre-Planning?
The Traceability Questions
Iteration Planning
Iteration Planning
The Team’s Definition of ‘Done’
Tasks
Iteration Execution
Iteration Execution
Sample Agile Calendar
Daily Scrum “The Daily Standup”
Daily Standup
Taskboard
Visual Taskboards
Closing Out the Iteration
Closing Out the Iteration
Iteration Review
Demos
Retrospectives
Best Practices for Retrospectives
We Should Try…
Bringing It All Together
Bringing It All Together
Things to Remember
Resources
Agile Transformation, Inc