When you estimate, what do you produce? Do you figure out how long things will take, or do you go straight to a dollar figure and a finish date?
Hopefully you produce an estimate for effort first, and the project cost and the delivery dates are worked out after that. Effort, elapsed time and project cost are valuable concepts and keeping them straight can help you and your project stay on the path to success.
Projects fail every day and failure is often preventable. By taking a moment to identify possible problems and manage them, you’re helping establish a foundation for project success and encourage realistic expectations of both your team and the client’s.
Let’s talk about risk management!
Friday roundup! Javascript gauges with Raphaeljs, content strategy, Webkit inspector, jquery functions, software development and scientific method
This is an update to my original post Dynamic Robots with ASP.NET 2.0, which was written for IIS6. IIS7 makes this process even easier! Use this approach to deliver different robots.txt files depending on whether you site is being crawled in http or https (or just to present your robots.txt file programatically).
Let’s take a look…
Without explicit requirements, how do you decide what features and functionality to put in and leave out of an estimate?
This post kicks off my long overdue series on estimation techniques for developers. Each week I’ll be sharing something I’ve learnt over the last 12 years of estimation in small-medium private sector web development teams. Some will be longer than others but hopefully you’ll find a few useful at least. This is “Part 1: Key Concepts in Estimation”.
