Building the right product vs Building the product right
https://www.liquidcat.org/en-us/green-architecture-the-future-of-real-estate/

Building the right product vs Building the product right

So should we build the right product or should we build the product right?

What do I mean by building the right product? The right product is one that addresses the user problems in the right context and provides a proper solution. This is the key function of the product department.

What do I mean by building the product right? Building the product right is defining a perfect architecture, addressing all the technical debts, and making the solution reliable, scalable, highly available, performance efficient etc. etc. This is the key function of the engineering department.

These are not two different ends of a thread but the key attributes for any successful product/project. Actually, there is another dimension to a successful product, which is building it fast.

What do I mean by building fast? A product definition or development cannot be eternal. It has to be planned well to be continuously developed, shipped, delivered, managed for successful delivery, and for a customer to reap value. This the key function of an Agile Coach.

Often the role of an Agile Coach is underestimated in most organizations. Or some over enthusiast from the product or engineering team owns up the role of a scrum master and runs scrum ceremonies in the name of agile. But what I have mentioned here is more than just being a scrum master.

To reiterate; the key tenets of a successful project are

  • Building the right product
  • Building the product right
  • Building it fast.
No alt text provided for this image

It is key to figure out the right balance; for a product and subsequently a business to be successful. Otherwise, we may end up in a product which no one uses, or a product with a lot of bugs, or we lose the first scaler or the critical competitive advantage.

It is quite astounding to know & see how Spotify is able to build such a great product , great culture within their community. There is minimal handshake, great amount of autonomy and alignment across the organization, enables them to be mutually exclusive but collectively exhaustive!!!

I'm one of those over enthusiasts who strive to formulate a proper product requirement, put a definite plan, and deliver a quality deliverable. I have been successful to a great extent with some failures. Great insights from Spotify!! Kudos!!!

Would happy to hear others experience as well!!!!

Thanks & Regards

Mk

Source:


Prince Christopher

Enterprise Architect | Principal Solutions Architect | Agile Architecture | Solution Design | Contact Centre | Omni Channel | Cloud Computing | Azure

3 年

Well articulated mukund, keep writing, knowledge sharing is infinite so will be the benefits and beneficiaries

要查看或添加评论,请登录

Mukundaraman V的更多文章

  • DoR vs DoD

    DoR vs DoD

    Definition of Ready vs Definition of Done I have tried my best to apply Agile principles and scrum at a lot of…

    1 条评论
  • Explorers vs Exploiters

    Explorers vs Exploiters

    This is in continuation to my previous article where Mr. Ram Shivakumar of #chicagobooth shares great insights on…

    4 条评论
  • Companies die of indigestion than starvation!!!

    Companies die of indigestion than starvation!!!

    Well, this is in continuation to my previous post https://www.linkedin.

  • Change of course

    Change of course

    I came across a great article from Mr. Ram Shivakumar of ChicagoBooth where various companies pivoted to become much…

  • My 2nd golang program

    My 2nd golang program

    I have another draft blog which says "My 1st golang program not a hello world" . There are a few pending work, hence I…

    2 条评论

社区洞察

其他会员也浏览了