Published: Nov 29, 2008 - 07:02 am
Story Found By: cre8pc 1275 Days ago
Category: Usability
6 Comments
6 Comments
Search Engine Land produces SMX, the Search Marketing Expo conference series. SMX events deliver the most comprehensive educational and networking experiences - whether you're just starting in search marketing or you're a seasoned expert.
Join us at an upcoming SMX event:
Learn more about search marketing with our free online webcasts and webinars from our sister site, Search Marketing Now. Upcoming online events include:
Comments
<h3 class="r">Plan!? We dont need no Stinkin Plan!</h3>A bright idea, a quick hack or three, some tricky seat of the pants manoeuvering, and the intertubes belong to me, baby!Requirements? Nah.Perpertual beta and iterate to buy-out!Let the buyer worry about requirements and revenue.Business models are for suits not rockstars!Sadly there are none so blind as those who will not see.None so deaf as those who will not listen.Keep up the good fight, Kim.
Pink Floyd is running in my head, thanks to you, "iamlost"..."We dont need no education....we dont need no thought control"I think I just yelled at myself, didnt I.
Good post, Kim. Id say that anyone (or any company) that launches into developing a website without requirements (what will be included) in writing is probably asking for a longer, drawn out development process.At the very least, a requirements list (or list of what the website will consist of) gives you a starting chance at determining what issues there might be, what will need to be resolved, and the general scope of the project. Without this, youre setting yourself to walk right into "scope creep".Mind you, theres nothing wrong with expanding projects, but its important to know *when* its being expanded by new additions, as opposed to whether something is technically part of the original project.
Basically anything that you are working on can be viewed as a "project" and basic project management skills like requirement mangement, scope planning, WBS and others will always be handy.
DianeV makes an excellent point about expansion. There is a way to do this with a formal Requirements Document, and that is to begin by calling it REV 1.0. Later enhancements are tracked in updated versions of the same document, such as REV 1.2, 1.3, etc.In QA, there is software used to track many areas, including decisions made on enhancements, who signed off on it, etc. Larger web sites with many functions need this backup. Not to mention, any way to CYA (cover your ass) is worth investing a little effort in :)
Its a good article, Kim, and it helps to let people know what kinds of issues can arise — and how to plan for them ahead of time.