BT

Facilitating the spread of knowledge and innovation in professional software development

Contribute

Topics

Choose your language

InfoQ Homepage Design Thinking Content on InfoQ

News

RSS Feed
  • PayPal Engineering Teams Implement Premortem Analysis

    In a recent blog post, the PayPal engineering team published how it uses premortem analysis as part of its regular software design process. The team adopted a customized version of premortem analysis last year, which highly benefited PayPal engineering. Premortem is a strategy in which a team imagines that a project failed and then works backward to determine what could lead to this failure.

  • How ThoughtWorks Applied User Centered Design to Drive Digital Transformations

    At Agile India 2019, ThoughtWorks presented how design thinking enabled various industries to disrupt their technology and their business model. Product and technology teams need to interact differently and develop new customer centric skills. Based on how user centricity is changing business models and organizations, ThoughtWorks proposed a new version of the Agile Manifesto.

  • Driving Innovation at Switzerland's Largest Bank

    Jelena Laketic, head of asset management SWAT (SoftWare Action Team) at UBS, spoke at the DevOps Enterprise Summit London about some of the lessons she has learned driving innovation at the largest bank in Switzerland. InfoQ reached out to Laketic in order to get her view on the particular challenges and successes around her SWAT journey and what innovation means at UBS.

  • From "Doing the Things Right" to "Doing the Right Things"

    Peter Jacobs, CIO of ING Netherlands, gave a talk at Agile India 2018 in which he explained how fostering and practicing an Agile approach has been helping the organization do things right, and the challenges they are currently facing to guarantee that they actually do the right things.

  • Eric Evans: Domain-Driven Design Even More Relevant Now

    Eric Evans, author of Domain-Driven Design, said the concepts in the book he wrote in 2003 are even more relevant now than they were 14 years ago. As the range of tools and technologies has expanded, some lend themselves to the principles of DDD better than others we've had in the past. Evans said, "DDD is not about technology, but is not indifferent about technology."

  • Key Takeaways from the 'Agile on the Beach' 2016 Conference: Day One

    At the sixth ‘Agile on the Beach’ conference, held in Cornwall, UK, several leading practitioners of agile software delivery presented the state-of-the-art and emerging trends within this domain. Key takeaways included the value of the scientific method to drive change; the use of Continuous Delivery (CD) for improving safety and speed; and the power of cognitive bias during the user testing.

  • Building an Empathy Driven Product Vision

    Savita Pahuja and Mirana Kerner, agile coaches at Palo-IT in Singapore, ran a workshop at the Agile Tour Singapore conference on the importance of creating an emotional connection when preparing a product vision, and how visualisation techniques can help. The talk covered Empathy Driven Product Vision – the art of creating an impactful product vision using emotions and magic of visual effects.

  • Shane Hastie on Applying the Agile Mindset to Tough Business Challenges at Agile Tour Singapore

    Shane Hastie gave a keynote talk at Agile Tour Singapore Conference 2015 in which he discussed Agile mindset and how it can be helpful in solving tough business problems.

  • Implementing Design Thinking Approach Using Various Tools.

    This post covers the usage and importance of design thinking approach using various tools. It also gives an overview of using Lego Serious Play for design thinking.

  • Don’t Share Code Between Microservices

    Reasons for building microservices are often about using isolation as a means to handle change. Sharing code between services couples your services to each other reducing the effectiveness of the isolation and the ability to handle change, David Dawson writes in a series of blog posts questioning the Don’t Repeat Yourself (DRY) principle in connection with microservices.

BT