A look back at the best from a year ago.
Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases
Posted on:
Software Cost Estimation With Use Case Points – Actor Analysis
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
Posted on:
Software Cost Estimation With Use Case Points – Use Case Analysis
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 / Project Management / Requirements / Requirements Models / Use Cases
Posted on:
Software Cost Estimation With Use Case Points – Environmental Factors
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.
Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases
Posted on:
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.
Business Analysis / Product Management / Project Management / Requirements / Requirements Models / Use Cases
Posted on:
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
Posted on:
Flashback: A Year Ago This Week on Tyner Blain [2006-02-10]
A look back at the best from a year ago
Marketing / Polls / Product Management
Posted on:
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.
Lists / ROI
Posted on:
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…