Solving Customer Problems in an Agile Enterprise

Governance and Process are two words that would raise a lot of eyebrows in the Agile world, but they are needed

  1. A Product Team – its a simple strategy, you can start by defining a structure and overlay a set of practices. By constant retrospection and learning the mindset of agility will emerge soon
  2. A Program Team – it’s no longer simple anymore, because now we are either dealing with one large product or multiple products with interdependencies. It is just not sufficient to follow a set of ceremonies for a single team, but also required to synchronise or orchestrate across teams or products. Inorder to still retain autonomy to the extent possible, teams need to be aligned
  3. A Portfolio Team – it could consist upto 500+ people, and when you look at possible dependencies or lack of alignment of the prioritisation needed. It could derail whole programs or even impact an organisation‘s strategic investment, if the time to market is a critical factor.
  • User stories – Product teams
  • Features – Product teams
  • Epics / Feature Packs – Program teams
  • Themes – Portfolio teams
  • Investment Decisions
Top-down Demand Breakdown

In large organisations, how can you change strategy and ensure your teams also focus towards solving the most important problem



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Sasi K Bejjavarapu

Sasi K Bejjavarapu


Sasi is a non-linear thinker and expert in strategic and operational execution of IT Projects. He loves sharing and engaging about Agile Transformations