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

  • Applying Use Cases in Agile: Use Case 2.0, Slicing and Laminating

    To incrementally develop and deliver products using agile software development, requirements are gathered and organized into a product backlog. A requirement technique that is used in agile software development is use cases. Some techniques to apply use cases for managing product requirements in agile are use case 2.0, slicing and laminating.

  • Documentation in Agile: How Much and When to Write It?

    The Manifesto for Agile Software Development values "working software over comprehensive documentation". This core value asks us to think about how much and which kinds of documents are needed and when they need to be written.

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

  • Behaviour-Driven Development: Value through Collaboration

    The goal of a software project is to deliver value to stakeholders and Behaviour-Driven Development, (BDD), is designed for that, Viktor Farcic, a software developer working on transitions from waterfall to agile processes, states in the first of four blog posts describing his view on BDD.

  • Balancing Demand and Capability with Kanban

    Kanban helps organizations to get insight into their work-in-progress, and establish a pull system where demand and capability can be balanced. A first step is to find out what the real capability is and visualize the flow. InfoQ interviewed Florian Eisenberg about evolutionary change and how you can balance demand and capability in organizations.

  • How to Scale the Product Owner Role

    The product owner role from Scrum is used to interface between the business and development. In larger organization with complex products and many decisions that need to be made, having this role filled in by one person is often not feasible. InfoQ did an interview with Timo Punkka about the role of the product owner, lean portfolio management, and customer collaboration.

  • Reduce Waste by Changing from Waterfall to Agile

    Organizations adopt agile to be able to handle changes. Agile helps teams to deliver products that satisfy the needs of customers; products which do not contain unneeded (and unused) features. Lean software development says: everything not adding value to the customer is considered to be waste. How can a transition from waterfall to agile software development help organizations to reduce waste?

  • Benefits of Combining Agile and Lean Startup

    Enterprises want to increase their capability to deliver value to customers in less time. Many adopt agile software development to iteratively develop and deliver software solutions. Lean startup aims to support developing new businesses and products. Several authors shared their views on how combining agile and lean startup methods can be beneficial.

  • How Individuals Can Adopt an Agile Way of Working

    Organization mostly do an agile transformation for a whole team, project, or organizational unit, given that agile is a team driven approach. But there are also professionals who start using agile practices individually, or who are working agile as a one person team. How can individuals adopt agile, and what kind of benefits can it give them?

  • The Flexibility of Agile: Flaw or Strength?

    The principle of “responding to change over following a plan”, is it a strength or a flexibility that can’t work in practice? For example, what about agile projects that had difficulties managing changes and customers who expect too much flexibility? Can agile not live up to its promises, or is it the way that teams and organizations have adopted agile that is causing the problems?

  • Pivoting when Using Lean Startup for Product Development

    There are different types of pivots possible in lean startup, which help you to decide whether to persevere or pivot during product development. They each with their own purpose and ways to use them. Let’s explore some of them to see when and how you can pivot? Or maybe have to decide that it’s better to quit?

  • Remove Waste From Your Backlog with the Priority Game

    The priority game is an exercise which Michael Franken did at the GOTO Amsterdam 2013 conference, to make large backlogs manageable. He showed how Scrum can help you to focus and remove waste by not making things that are probably never used by customers.

  • Experiences from Educational Technology Startups

    Educational technology is developing itself, and startups are entering markets with new apps and creative commons content. Speakers shared their experiences on education and gaming and finding the right fit for an EdTech startup, at the GOTO Amsterdam 2013 conference.

  • IRQA - A Requirements Definition and Management Solution for Systems Engineering Projects

    Visure Solutions recently announced the availability of IRQA which denotes a solution for requirements definition and management (RDM). A sound process using professional tools is important for ensuring the quality of product and solution development with respect to the requirements specification.

  • Jolt Award 2011 for Design, Planning, and Architecture Tools

    On October 26th, The Jolt Judges announced the awards for 2011 in the category “Design, Planning, and Architecture Tools”. In detail, the Jolt hall of fame now includes the products Paradigm for UML, Restructure 101, and Requirements Center 2010.

BT