Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Actor Analysis

Posted on:

Software project cost estimation using use case points takes the approach of estimating the amount of effort based upon what the software is being asked to do – not an analysis of how someone chooses to do it. We’ve looked at technical and environmental factors that influence our estimate. And we’ve done a use case analysis to quantify how much work the software is being asked to do. The last area of analysis focuses on the users of the software.

Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Use Case Analysis

Posted on:

Software cost estimation with use case points is primarily driven by use case analysis. You take into account environmental and technical factors, but they are ultimately only modifiers of the analysis done on the use cases. Each use case contributes to the project cost estimate, and use cases of varying complexity have a varying influence on the cost estimate.

Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Technical Factors

Posted on:

The technical factors are the first thing you assess when doing a use case point analysis. Technical factors describe the expectations of the users for the delivered software. Generally, it is an assessment of non-functional requirements. There are 13 technical factors that you have to analyze. Read on to see how.

Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases

Software Cost Estimation With Use Case Points – Introduction

Posted on:

Estimating the amount of work required to deliver software is hard. Estimating the amount of work in the very early stages of a project is even harder. A method was developed to estimate the amount of work required by analyzing what the system will allow its users to do. That method is called Estimating With Use Case Points. This article is an introduction to the concept.

Marketing / Polls / Product Management

Product Manager Role Details and Survey Results

Posted on:

Pragmatic Marketing runs an annual survey of product managers. We looked at 440 results from the 2006 Product Manager Survey to uncover the trends in how different product manager roles are defined. The survey involved questions breaking down the allocation of time to different activities. In this article we look at how those activities varied for product managers, product marketing managers, segment / market managers, and technical product managers.

Business Analysis / Prioritization / Product Management / Requirements / ROI

Prioritization With ROI and Utility

Posted on:

Prioritization with ROI is generally thought of as a quantitative analysis. For hard ROI, that is true. For soft ROI, it is anything but true. You have to make a prediction of the utility of the requirement or feature. That predicted utility is based on our expected utility, which is based on your past experiences. Your past experiences are reflected in remembered utility, which is a function of experienced utility. How can you know with certainty, and use that to prioritize requirements or features?

Prioritization / Product Management

Differentiate Your Product – Circumvent Comparisons

Posted on:

Look Ma! Me Too! The temptation to compete against a checklist can be overwhelming. When we have a competitor who provides 100 of this or 200 of that, it might seem smart to offer 200 of this and 300 of that. We’ll be better off if we focus instead on creating the other thing. The best way to compete is to valuably differentiate our product, not outdo our competition.

More is better features are just that – more is better. But more of the same old thing is worth a whole lot less than some of something else.