Portal Project Overview

Focus on Outcomes

Now

Later

Features

Output

Software

Minimize

Maximize

• Valuable Intellectual Property

• Happy Employees

• Increased Efficiency

• Integrated Business Processes

• New Business Opportunities

• Eliminate Manual Processing

• Critical Redundancies

• Increased Revenue

• Decreased Costs

• Increased Reliability

• Satisfied Customers

• Satisfied Dealers

• Increased Confidence

• Reduced Risks

What

Updated User Experience

• Focus on -ilities (Usability, Stability, Reliability)
• Additional Platforms (If identified as driving outcomes)
• New Features
• Improve Existing Features
• Multi-Tier Architecture
  • Update to .NET Core 8
  • Migrate integrated services to REST API's
  • Utilize our new framework libraries
    • Common Interfaces
    • Fast Database Access
    • Unit of Work
    • Policy Based Security
    • Modular Front-End Applications

What is Success?

How do we succeed?

(When the risk of failure is high)

Fat Tail

Minimizing Risk

• Think Slow, Move Fast
• Modularity
  • Well defined, repeatable processes
  • Reusable Code
  • Isolated and Focused Code Modules
• Iterative
  • Repeatable
  • Incremental

Agile

(Done the right way)

What's Missing?

Shared Understanding

User Stories and the 3 C's

Conversations

• Conversations and Collaboration are the secret sauce that distinguishes Agile from traditional methodologies
• We tell stories in the same way we would talk about existing features
• User Stories get their name from how we use them, not how we write them
• Story Maps facilitate breaking down complexity into small, understandable components without losing the context (Forest vs Trees)

Story Maps

• Left to Right Narrative
• Top to Bottom Decomposes Complexity

• Do not reflect complex branching and workflows
• A card is a placeholder for a conversation

Product Team

• Stakeholders
• Product Owner
• Product Experts
• Engineers
• UX

Plan

• Project Kickoff (1 hr)
  • Who?
    • Entire Product Team
  • What?
    • Process Presentation
    • Identify Users

• Discovery Workshop (1-2 hr)
  • Who?
    • Product Owner, Stakeholder, Product Expert
  • What?
    • Mile-wide and inch deep
    • Identify Activities and User Stories

Plan

• Story Workshop (1-2 hr)
  • Who?
    • Product Owner, Stakeholder, Product Expert, Engineering, UX
  • What?
    • Drill into selected stories
    • What-ifs
    • Technical Approaches

• Backlog Refinement (1 hr)
  • Who?
    • Product Owner, Stakeholder, Product Expert, Engineering, UX
  • What?
    • Acceptance Criteria
    • Split Stories
    • Size
    • Validation Requirements

Plan

• Sprint Planning
  • Who?
    • Product Owner, Stakeholder, Engineering
  • What?
    • Review Stories
    • Identify Blockers and Unknowns
    • Assign Stories to Sprint

• Backlog Refinement (1 hr)
  • Who?
    • Product Owner, Stakeholder, Product Expert, Engineering, UX
  • What?
    • Acceptance Criteria
    • Split Stories
    • Size
    • Validation Requirements

Plan

• Sprint Review & Retrospective (1 hr)
  • Who?
    • Product Owner, Engineering
  • What?
    • Review Work (Completed, Started, Not Started)
    • What went well?
    • Where can we improve?
    • Metrics (Velocity, Completion)

• Demo (30 min)
  • Who? Anyone
  • What?
    • Show Completed Stories
    • Is it what was expected?
    • Are there changes?

Rinse & Repeat