BT

InfoQ Homepage Business Analysis Content on InfoQ

Articles

RSS Feed
  • Author Q&A on the Book Business Analysis Agility

    James and Suzanne Robertson have written a book titled Business Analysis Agility - Solve the Real Problem, Deliver Real Value. They address the fact that despite the adoption of agile approaches a lot of time, effort and money is wasted building the wrong product. They explore the challenges faced undertaking analysis in agile environments and address some of the common mistakes.

  • What Does Company-Wide Agility Imply?

    Self-organization, transparency, constant customer focus, and continuous learning: these are the four values that drive company-wide agility. InfoQ interviewed Jutta Eckstein and John Buck about how to apply a combination of Beyond Budgeting, Open Space, and Sociocracy to support these agile values, and what benefits this approach can bring.

  • WTF requirements in Agile Product Development

    The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.

  • Waterfall Requirements in Agile Product Development

    The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.

  • User Stories Are Placeholders for Requirements

    It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.

  • The Lean Business Analysis Manifesto Explained

    David Morris explains how Lean Business Analysis responds to the ever-increasing pace of change in an age of digital disruption. We no longer have business as usual, so why would we do business analysis as usual? The Lean Business Analysis Manifesto helps put order into the chaos that exists in many of today’s organisations.

  • 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®

  • F# Deep Dives Review and Author Q&A

    F# Deep Dives, edited by Tomas Petricek and Phillip Trelford, is a new book aimed at showing what is the business value that using F# brings in practice. The book presents 11 real industrial scenarios and the way F# allowed field experts to solve them using a functional-first approach. InfoQ has interviewed Tomas Petricek, co-editor of the book.

  • 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.

  • #NoEstimates Project Planning Using Monte Carlo Simulation

    Customers come to us with a new product idea and they always ask the questions - how long will it take and how much will it cost us to deliver? Reality is uncertain, yet we as software developers are expected to deliver new products with certainty. This article shows how to do planning using reference class forecasting with the #NoEstimates paradigm which promises more accuracy in forecasts.

  • Stats Anomalies Detector

    The article describes the general outline of the Stats Anomalies Detector we developed at MyHeritage and provides a detailed explanation of how to enhance the code (will be available soon at MyHeritage GitHub) to meet your company’s needs.

  • MLConf NYC 2014 Highlights

    The MLConf conference was going strong in NYC on April 11th and was a full day packed with talks around Machine Learning and Big Data, featuring speakers from many prominent companies.

BT

Is your profile up-to-date? Please take a moment to review and update.

Note: If updating/changing your email, a validation request will be sent

Company name:
Company role:
Company size:
Country/Zone:
State/Province/Region:
You will be sent an email to validate the new email address. This pop-up will close itself in a few moments.