The environmental factors that describe your development team and environment are the second thing you assess when doing project cost estimation with use case points. Environmental factors primarily focus on the capabilities of your team, but also touch on your process.
Software Cost Estimation With Use Case Points – Technical Factors
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.
Software Cost Estimation With Use Case Points – Introduction
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.
Flashback: A Year Ago This Week on Tyner Blain [2006-02-10]
A look back at the best from a year ago
Product Manager Role Details and Survey Results
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.
5 Return On Investment Calculation Tips
Return on investment calculation is critical to using ROI for prioritizing requirements. We’ve discussed how to forecast return on investment by estimating costs and predicting benefits. Here are five tips to help you when calculating return on investment.
The following ROI calculation tips are detailed in this article:
1. Recognize the Risks
2. Discount Future Cash Flows
3. Separate Sales From Expenses
4. Overcome Ozymandias Syndrome
5. Ignore Infinite Elvises
Read on for the details…
Prioritization With ROI and Utility
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?
Foundation Series: Intro To Utility Curves
Utility is an abstract concept usually relegated to economics. What is it? How does it work?
How To Measure Costs When Calculating ROI
At a high level, it is easy to describe ROI – the return on the investment. But how do we measure the investment? There’s a problem when we have to go to the next level. Some costs are obviously incurred as part of our actions, and some costs happen even if we don’t take the action. We have to allocate those costs across all our actions or we won’t have an accurate reflection of our investment. Without an accurate model of our investment, we can’t calculate the return on our investment.