By Avonelle Lovhaug
Publication Date: 11/12/2008 4:13:38 PM
In part 1, I described some of the causes of software development scope creep.
So now the $64,000 question is: what can we do to prevent scope creep?
Unfortunately, there is no bulletproof, 100% guaranteed method of eliminating scope creep for your software project. That doesn’t mean that the requirements will definitely change, but it does mean that no one can promise you it won’t happen. (If they are promising that, they are selling you a bill of goods.) However, there are some things you can do to decrease the likelihood that creep will derail your project.
Document requirements (and periodically ...
Read More
Comments (0)
Publication Date: 11/11/2008 9:49:57 PM
If you are involved in a programming project, sooner or later you will hear about creep – scope creep, that is. Typically, the conversation happens about half-way through the project, and it is an ugly feeling.
You: It is important that the system include the [abc] functionality.
Programmer: [ABC] feature wasn’t included in the proposal/requirements/design that you approved, so this is scope creep. Pay me more money for this feature.
You (mumbling): Now I know who the creep is!
This is a very common problem – more common than any of us would like to admit. And it can leave ...
Comments (2)
Publication Date: 11/10/2008 10:57:42 PM
A lot. Believe me.
No one wants to anticipate the worst. But actually thinking about what can go wrong can help you to better prepare for and prevent problems.
Here are some of the common problems that happen on software development projects, and what you can do to prevent them.
The estimate is wrong, and the project will take longer and/or cost more.
This is the #1 problem that occurs on software development projects. What to do? Don’t panic. Evaluate the situation. Could this have been prevented? Is this a one-off, or indicative of a larger problem? How to prevent? The best ...
Comments (1)
Publication Date: 9/21/2008 5:00:00 PM
One of the biggest challenges in hiring a programmer (for a single project or as an employee) is finding them. If you are not technical, you don’t hang out in newsgroups where programmers chat about all things geek. So, where do you look?
Use your network! Ask your friends, relatives, colleagues, and acquaintances. Do they know a programmer who they have worked with in the past? Do they know someone who knows someone? Just like hiring a building contractor, referrals are the best way to find a programmer.
Related to this, what about your LinkedIn profile? Even if you have only a ...
Publication Date: 9/11/2008 5:00:00 PM
My friend was telling me about a programmer she used to work with. He was a junior developer, and he had been assigned the task of producing some reports. Reports are a very visible, important part of many applications, but often programmers find them dull. This programmer was no exception. He didn't spend time right aligning the numbers. Empty date values were showing as "01/01/01" instead of blank. Monetary values didn't include a currency symbol.
When he was asked to fix these problems, he only did what was pointed out to him. He didn't take the time to review all of his reports ...
Top 5 Programmers to Avoid
What everyone should know about bugs
How to tell if an estimate sucks
The Secret to Building a Crappy User Interface
The Problem with Selecting the Lowest Bidder
5 Ways to Control Software Development Costs
Avonelle has been a pleasure to work with. Working with someone that you know will always deliver is tremendous.
Mark McNamee @ Renewal by Andersen
Sitefinity ASP.NET CMS