BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ

Topics

Choose your language

InfoQ Homepage Customers & Requirements Content on InfoQ

  • Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"

    Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.

  • The Agility Challenge

    To be successful, a company needs to become an agile enterprise. In this article Dragan Jojic explores “the agility challenge”: A company where employees are able to sense and respond to external inputs without managers having to tell them what to do, know what they are trying to achieve, understand why, be able to decide by themselves how to best do it and genuinely care that it gets done.

  • What Makes Joy,Inc Work? Part 3 – High-Tech Anthropology®

    This is the last of three articles exploring the culture and practices that makes Menlo Innovations such a joyous workplace. This article examines their approach to user experience and requirements - a set of practices they call High Tech Anthropology®

  • Innovation at Telefónica with Lean Startup

    Creating digital products is different from building traditional telco products: the uncertainty is much higher, the way of creating value for the customer is totally different and lifecycle is much faster says Susana Jurado Apruzzese. Telefónica adapted Lean Startup to their processes, culture and organization to make it work.

  • Q&A on the Book Agile Impressions

    Gerald Weinberg shares his observations of the agile movement "where it came from, where it is now, and where it's going" in the book Agile Impressions. In the book he explores the agile basics and principles, discusses how he has seen them being violated, and offers ideas and examples for applying the agile principles.

  • The Hierarchy of Needs

    What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.

  • Q&A on the Book Scenario-Focused Engineering

    The book Scenario-Focused Engineering describes a customer-centric lean and agile approach for developing and delivering software-based products. It provides ideas to understand customer needs based upon end-to-end experiences and for designing products in a customer-focused way using a fast feedback cycle.

  • Yes, Hardware Can Be Agile!

    “You can’t do 2-week iterations with hardware!” This is the first thing you’ll hear when talk turns to Agile methods in hardware-software product development. A mix of existing robust hardware development ideas, plus a few newly taken from Agile software are being used now by real teams, even to get around - or through - the challenge of doing fast iterations.

  • Q&A on Agile! The Good, the Hype and the Ugly

    The book "Agile! The Good, the Hype and the Ugly" by Bertrand Meyer provides a review of agile principles, techniques and tools. It explores the agile methods Extreme Programming, Lean Software, Scrum and Crystal and provides suggestions on what to use or not to use from them, based on software engineering principles and research and personal experience of the book author.

  • Visual Portfolio Management: Collaboratively Aligning Your Company

    To exploit agile advantages like speed, flexibility, and fast feedback, companies need to work on the right things. The three-horizons model explains how companies need to work to ensure sustainable growth. Visual portfolio management can integrate the different types of work into a coherent system.

  • How to Remain Agile When You Have to Sign a Contract?

    Agile development based on a contract that has been accepted by lawyers seems impossible. The nature of traditional purchasing and contracting processes does not match the Agile principles. This is a case story of how a supplier cooperated with a client to develop a huge project in an Agile way, by cutting it into smaller pieces and prepare a matching contract based on mutual trust.

  • Getting RID of Risk with Agile

    One of the largest areas of waste in development are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste, as well as examining how this can fit into your current planning and estimation workflow via the underused ‘definition of ready’. It’s a very actionable concept that you can apply immediately.

BT