Published Sep 3, 2019

Episode 64: Luke Hohmann on Architecture and Business

Luke Hohmann illuminates the transformative power of innovation games for customer insight and creativity, while dissecting the strategic interplay between software architecture and business objectives, emphasizing adaptability and alignment in product development and deployment.
Episode Highlights
Software Engineering Radio - the podcast for professional software developers logo

Popular Clips

Episode Highlights

  • Roadmapping

    Strategic roadmapping in product development is crucial for aligning with market needs and technological changes. emphasizes the importance of moving beyond simple release schedules to understand why a release is significant and how it fits into the market's rhythm. He explains that a well-constructed roadmap allows technical architects to communicate necessary changes due to evolving technology, fostering collaboration between technical and business teams.

    A well-constructed roadmap is going to give the technical architect an opportunity to communicate their understanding of how things are going to evolve.

    ---

    This approach, known as market-driven roadmaps, helps link teams together, enhancing productivity and meeting market demands 1.

       

    Software vs. Physical

    The development and lifecycle management of software products differ significantly from physical products. highlights the unique challenges posed by intellectual property and licensing in software, which do not apply to physical goods. Unlike physical products, software does not degrade physically but loses relevance as technology and market needs evolve.

    Software bits don't degrade. They last forever, where chairs and physical objects degrade, but the relevancy of the bits degrades.

    ---

    This distinction underscores the dynamic nature of software development and the need for continuous adaptation 2.

       

    Product Management

    Product management in software development involves distinct challenges compared to IT project management. explains that while both involve transforming ideas into working software, product management focuses on creating value that can be monetized. This requires a strategic approach to versioning and distribution, unlike IT projects, which focus on internal deployment and usage.

    The transformational sequence to me is the same. It's what you do when the software is done that makes all the difference.

    ---

    This distinction highlights the complexities of product management, including the need for explicit release plans and market strategies 3.

Related Episodes