Understanding the expected value of a possible future event allows us to make mathematically sound decisions. We can decide if we want to make an investment. We can assign a reasonable price for our services. We can prioritize requirements. Expected value is a calculation that should be used when calculating ROI.
Software Testing Series: Top Three Measurements of Quality
The three most important things to understand about the quality of your software are the three things most relevant to your business and your stakeholders (and arguably, your boss).
Top three measurements of software quality
1. How do people perceive our quality?
2. How big of a problem is our quality?
3. How bad is our software, really?
Why Incremental Delivery Is Good
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.
Definition of ROI – Return on Investment
We talk about ROI all the time – what is it, in layman’s terms? ROI is the acronym for return on investment. Another way to think of it is “How much profit will we make if we invest in this project?” Profit is revenue minus costs. Technically, the question should […]
iRise – software prototyping tool
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 […]
Dilbert does product managers
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, […]
Five Measures of Product Manager Performance
Joy posted a really good article last week at Seilevel’s requirements defined blog, Measuring product manager performance on internal system products. Her post is a followup to an extensive and heated debate that happened last fall on the Austin PMM forum. It’s a great forum to subscribe to – a […]
Tyner Blain in the Google Toobar
Tyner Blain can now be viewed thru the Google Toolbar! In the top of the sidebar (on the right) is a link to automatically add Tyner Blain to your Google Toolbar. As of today, it is only supported for IE users, but Google is now a supporter of firefox, so […]
Describing the Software Development Process
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.