We can’t always be Agile...And we can’t just change our technical architecture on a dime without considering business model impacts. Likewise, we can’t change the business model without understanding architectural impacts.

This workshop thoroughly examines the linkage between business models, technical architectures, Agility and the implications of change to make faster pivot decisions. Further, this session will explain how business model or architectural changes can constrain Agility.

This session for product owners, product managers, and leaders ventures far beyond backlog prioritization. Through an interactive case study format, attendees will receive a model for understanding the interrelationship between business models and architectures and limitations on Agility. This model will help attendees avoid countless hours grappling with tough decisions.

 
1 favorite thumb_down thumb_up 2 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

This will be a fast-paced workshop based on a case study that flows through the session. Attendees will receive a handout to support minimal displays of information on the screen, i.e., Lean Startup framework, business model framework, market-driven roadmap, etc. The outline below summarizes the flow at a high level.

  • Introduction to set the stage - "Pivot and persevere" are in vogue. But what happens to Agility during a pivot?
  • Context 1 - Review business model frameworks and their generation
  • Context 2 - Examine a value exchange model and its relationship to architecture
  • Exercise - What can and cannot be Agile about changes to business models and/or architectures
  • Exercise - Use collaborative roadmapping to manage business model or architectural changes
  • Exercise - Connect roadmap changes to backlog refinement
  • Summary and feedback

Prerequisite Knowledge:

  • Understanding of Agile values and principles
  • Knowledge of product development lifecycle
  • Familiar with Lean Startup principles, specifically pivot or persevere
  • General knowledge of software architecture, i.e., n-tier
  • Basic understanding of business models

Learning Outcome

  • Apply a business model generation framework.
  • Practice mapping business models to the generation framework.
  • Identify value exchange models and their relationship to architecture.
  • Describe what can and cannot be Agile about business model and architectural changes.
  • Manage architectural change through collaborative roadmapping.
  • Determine how business model change influences product roadmaps.
  • Manage business model change.
  • Describe how product owners and product managers leverage this model to manage backlogs of features and epics.

Target Audience

Product Managers, Product Owners, Portfolio Managers, Entrepreneurs, Leaders

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • George Dinwiddie
    By George Dinwiddie  ~  1 year ago
    reply Reply

    The link to the slides gives a 404.

    • Jason Tanner
      By Jason Tanner  ~  1 year ago
      reply Reply

      Sorry about that, George. I clicked through this one so it should work for you, too.

      http://2015conf.agileaustin.org/sites/default/files/presentations/KAA2015-JasonTanner.pdf

      Thanks,

      Jason