Hi,
I usually use a MoSCoW Analysis.

http://en.wikipedia.org/wiki/MoSCoW_Method

>From then on, I move into detailing each needs.
The S - Should have and C - could have parts are rather tricky if you are new 
to it.

So far this method has saved me more than once in many projects.

The most important aspects are the Must Have (which you should implement at all 
cost in the development cycle) and the Wont Have.
Correctly defining the Wont Haves is a must.
You won't like to have to re-do your whole development simply because you 
forgot to point out that there "Wont have" multiple languages.
Or that there "Wont Have" a forum in this version.

One little trick that I used now is the following point in the Won't Have 
section. " Any not mentioned above" as default.


Dummy Site                      
Version 1.X             
MoSCoW Analysis                 
                        
Must Have Features                      
1       Registration Feature    Allows user to register to website
2       Login Feature   Allows user to login to website - Requires registration
3       Recover Pwd Feature     Allows user to reset his password       "- 
Unique email required - mail() function - Overwrite pwd with a random pwd - 
Send hash MD5"
4       Search  Allows users to search for posts        "- basic search - 
advanced search"
5       Product display
6       Add Products
7       Display latest news                     
                        
Should Have Features                    
1       Profile Updates Allows users to update their profiles.  "- Change 
password
- Change display name
- Change information details
- Cannot change email"
                        
Could Have Features                     
1       Forum
2       Chat
                        
Wont Have Features                      
1       Any not mentioned above         
2       Multiple Languages              
                                        

Xavier de Lapeyre
Web Developer

Please consider the environment before printing this mail note. 


-----Original Message-----
From: Jason Pruim [mailto:[EMAIL PROTECTED] 
Sent: mardi 12 février 2008 19:50
To: PHP-General General
Subject: [PHP] Question about development

Hi Everyone,

I know this isn't 100% on topic... But when is any post to this list  
100% on topic? :)

I've been doing some googling trying to find info on how to plan for  
what a website needs. Stuff like Does it need a forum, live support,  
database driven etc. etc. Does anyone have a form that they use to  
give to the client asking them to outline some ideas that they have  
about the website?

What I'm looking for is something that I could give to a potential  
client and ask them to describe some basic aspects of their target  
audience, a rough idea of what they want it to look like, or at least  
other sites that they like. Stuff like that..

Even if you don't have such a form, I'm sure you all have standard  
questions you ask each client before giving a quote :)

Anyone want to share with the class?

If there is interest, I may even put it together on a webpage to help  
future people :)
--

Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
3251 132nd ave
Holland, MI, 49424
www.raoset.com
[EMAIL PROTECTED]

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to