Good examples for teaching software estimation (size, schedule, effort)? [closed]
Closed 9 years ago.
How can I estimate projects when I need to include a learning curve for new technology?
Sometimes, there are research and development projects where nothing is known in advance about the technology, concepts, and client. However, the manager still needs time estimates. What can I do to produce useful estimates?
Estimating time for planning and technical design using Evidence Based Scheduling
I’m at the beginning of a development project in a large organization.
How to add a new developer to the team
I run a small company composed of only 2 developers. We are building a very big application for one of our clients. Development on this project has gone on for 1.5 years.
Finishing an iteration early
I’d like some input on this on those working with agile methodologies…
Metrics / Methodology for estimating resource utilization for software in planning stage
I’m looking for approaches to estimate the resource utilization of an (web-)application in a JEE environment. The overall target is to get a forecast for hardware/software requirements while the application is still under development or even in planning stage.
Is this task too complex (many different factors) to get a fairly reliable proposition without spending too much time?
How long to spend estimating programming tasks?
For example, if I break a project into n discrete work products (say classes or functions or components) is there a time t such that n*t is a suitable amount of time to spend on estimation?
Estimation Techniques for Linux Kernel Development
I am working in Linux Kernel area and my work includes:
code study / Understanding
Porting (say from one kernel version to another kernel version)
Implementation of new kernel module / Device driver
Should you promise to deliver a feature that you aren’t sure if its implementable?
In an article from HN, I came across the following advice:
Using Completed User Stories to Estimate Future User Stories
In Scrum/Agile, the complexity of a user story can be estimated in story points. After completing some user stories, a programmer or team of programmers can use those experiences to better estimate how much time it might take to complete a future user story.