Process Improvement / Software development

Why Incremental Delivery Is Good

Posted on:

Incremental delivery is a key component of most software projects today – it allows us to deliver the most valuable elements of a system first, which allows our customers to start getting benefit from the system earlier. As additional features are developed, and additional use cases are enabled, they are delivered to the customers, who get incremental value from those features. This can have a significant impact on ROI projections for a project – and can be the difference between getting the deal and losing it.

Austin TX / Process Improvement / Requirements / Requirements management software / Software development / Software requirements specification / UX

iRise – software prototyping tool

Posted on:

We received a comment from Tom Humbarger at iRise on an earlier post, which led us to take a look at their site. iRise provides a tool for rapid prototyping of web-based applications, and there’s an overview of the products available. They have iRise Studio which allows people to create […]

Requirements / Slightly off-topic

Dilbert does product managers

Posted on:

http://www.dilbert.com/comics/dilbert/archive/dilbert-20060129.html We won’t copy the image of the cartoon – but we’ll tell you that it opens with Alice: “I’ll need to know your requirements before I start to design the software.” ObRelatedTopic: How to interview when gathering requirements Great Dilbert products The latest book (Nov 2005) from Scott Adams, […]

Design / Process Improvement / Requirements / Software development

Describing the Software Development Process

Posted on:

Software development involves determining what to develop, documenting this decision, determining how to develop it, and actually developing it.We present a framework for describing this process in terms of layers of activity. Many people use pyramid analogies, which show the magnitude of effort in each layer (lines of code versus lines of requirements, for example). Many other people use inverted pyramids to reflect the importance (or impact) of work done at different layers (a sentance defining a strategy has more impact than a line of code). Some people show PERT diagrams of waterfalls or pretty circular arrows charts showing iterative lifecycles, or any of many good analogies.