Skip to main content

Does your app have requirements?



Sometimes I think I should simply have an automated link to Eric's blog because in most cases, whenever he writes something as he just did with Requirements, it ends up being something that everyone, including those in Project Management and software development, should read.



I especially like "The only way we ever know that a
feature absolutely must be in the product is when one of our Sales Guys calls
up and tells us that he already promised it."



Especially valuable is his explanation of what a spec should be, could be and usually really is.











Powered by ScribeFire.

Comments

Tod McKenna said…
In the past, I used to work off of a worksheet of 'features' to be added to the next release of the software. These were not necessarily functional requirements but more like general ideas.

A lot of hours were wasted on prototype/iterate cycles as I attempted to get the 'new feature' to look and feel like what the client (and my boss) wanted.

Today, (and to answer your question) I always use a requirements document. The document is non-technical and is usually drafted by business owners (not engineers). I find that forcing everyone (read: the business owners and managers) to think hard about a new feature up front can save engineers and quality staff many many hours of work. Even for small projects, a requirements document can be very handy.

I recommend creating a special page that lists each stakeholder with a space for a signature. The project will only get a green light once all stakeholders sign and date. Any change to the requirements after that point will require a special change request.

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site: http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older. Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments. But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward. FoxPro VFP

5 Great Reasons to attend Virtual FoxFest

What's coming up? Virtual FoxFest is coming up soon (sessions start October 14th). Like last year, the conference is entirely virtual yet includes great breakdown rooms and sessions to add that nice one-on-one feel that you get in person. It's also staggered so you can choose which days you want to attend - October 14th, 20th and 26th. This is great if you can't break away for a consecutive three days. But really, I've gone through the sessions and I see five great sessions that I'm eager to check out. 1. A Decade of Thor (Rick Schummer) Thor has been an extension for Visual FoxPro that many developers swear by, yet many don't know even exists. Visual FoxPro's built-in extensions are great but Jim Nelson's Thor supercharges your IDE. I can't believe it's been ten years - so Rick's session should be able to not just whet your appetite but give you all the reasons you should be using it. 2. VFP C++ compiler.  Last year, we saw DotNetX as well