BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Product Development Content on InfoQ

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

    At the fifth ‘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 messages included the need for the more rigorous use of the scientific method throughout the software delivery lifecycle, and the benefits provided by applying agile principles to product development.

  • Innovation at AXA's Digital Agency

    The AXA Digital Agency deploys the Lean Startup approach, using design thinking, minimum viable product development and growth hacking, to innovate and support the digital transformation at AXA. An interview with Yves Caseau about the importance of innovation, adopting a lean startup approach, learnings from minimum viable products and growth hacking and advice for starting an innovation journey.

  • Software – Is it "Engineering" Yet?

    At the GOTO Amsterdam 2015 conference Mary Shaw talked about progress towards an engineering discipline of software. She explored what it means to have an engineering discipline, how far we have progressed toward having one for software, and what can be the next steps.

  • Deploying Scrum and SAFe at Philips Lighting

    InfoQ interviewed Frank Penning, PMO manager from Philips Lighting, about the main challenges that Philips Lighting is facing in product development, why Scrum is not enough, how they apply SAFe, and the benefits that they have gained from deploying agile methods for product development.

  • Managing Technical Debt Using Total Cost of Ownership

    Total Cost of Ownership (TCO) can be used for investment decisions and financial benefit analysis. When applied to software it covers the initial development costs and subsequent maintenance costs until phase out of a product. TCO can support architectural decisions and management of technical debt.

  • Adoption of SAFe at TomTom

    InfoQ interviewed Hans Aerts, vice president software development and agile coach at TomTom, about why they decided to adopt SAFe and how it was introduced and used to simplify the organizational structure and stop doing projects, why they focus on throughput rather than output, how they modified SAFe for Custom Systems, and what using SAFe has brought TomTom.

  • Improving Quality and Delivery Speed with DevOps Teams

    You can increase the quality of products by constantly increasing the level of automation of the delivery process and working with DevOps teams who constantly deliver small features to get quick customer feedback. A case story from ING Lease explaining the problems they had, experiences from the first steps of their agile and DevOps journey and exploring what they want to achieve in the future.

  • Managing Dependencies Between Product Backlog Items

    This post talks about the strategies to manage dependencies between product backlog items.

  • Using the "Worse is Better" Concept with Agile and Lean

    Less functionality can make a better product according to the “Worse is Better” concept described 25 years ago by Richard P. Gabriel. According to Kevlin Henney and Frank Buschmann we can learn from the worse is better concept for development and architecture with agile and lean.

  • Experiences and Good Practices from Hackathons

    Hackathons are events where developers work together during a fixed period to collaboratively develop software. They provide learning opportunities and space for developers and organizations sponsoring the hackathons to network and have some fun.

  • Product Roadmap Creation Using Different Views

    Scott Sehlhorst, product management and strategy consultant describes two views of the product roadmap.

  • Defining the Value of Software Products Precisely and Quantitatively

    The real requirements of a product are not the functions that are needed, or user stories that have to be delivered. It is the possible improvement of performance that customers can get from using the product said Matteo Vaccari. At the XP Days Benelux 2014 conference he facilitated a workshop together with Antonio Carpentieri about defining the value that is needed by customers.

  • Using Scrum of Scrums with Agile Teams to Coordinate and Collaborate

    Scrum of scrums can be used to scale the daily stand-up meeting when multiple teams are involved. Its purpose is to support agile teams in collaborating and coordinating their work with other teams. Several authors have shared views on scrum of scrums, with experiences of using them.

  • Balancing Experiments and Deliveries in Product Development

    Experimentation using for instance lean startup can help you learn about your customers and find out which features and product would be valuable. The value however comes from building products and actually delivering them to customers. You need to find ways to balance between experimentation and delivery.

  • Upcoming Book by Gojko Adzic on Improving User Stories

    Would better user stories improve software delivery? Gojko Adzic thinks applying small changes to the way teams manage their user stories can have a huge impact on the actual outcomes of their software delivery. He announced that he wants to write a book about improving user stories if at least 5000 people show that they are interested by pre-registering themselves in January.

BT