<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: business requirements in Webmasters and Developers</title>
<link>http://www.dslreports.com/forum/r21708597</link>
<description></description>
<language>en</language>
<pubDate>Tue, 01 Dec 2009 03:55:08 EDT</pubDate>
<lastBuildDate>Tue, 01 Dec 2009 03:55:08 EDT</lastBuildDate>

<item>
<title>Re: business requirements</title>
<link>http://www.dslreports.com/forum/remark,21713692</link>
<description><![CDATA[<A HREF="/useremail/u/254200"><b>tao</b></A> : nm]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21713692</guid>
<pubDate>Fri, 09 Jan 2009 23:13:43 EDT</pubDate>
</item>

<item>
<title>Re: business requirements</title>
<link>http://www.dslreports.com/forum/remark,21709071</link>
<description><![CDATA[<A HREF="/useremail/u/449413"><b>jayco437</b></A> : I don't know that there is a single standard for this.<br><br>Some project management articles listed here however:<br><br>&raquo;<A HREF="http://tc.eserver.org/dir/Design/Web-Design/Project-Management" >tc.eserver.org/dir/Design/Web-De&middot;&middot;&middot;nagement</A><br><br>If you're the business person and you're writing it for developers within your own company you might want to find out from the development supervisor what kind of development cycle the team uses and maybe you could cater to that.<br><br>Here's a nice short article on the beginning part of the development process:  &raquo;<A HREF="http://www.alistapart.com/articles/Process" >www.alistapart.com/articles/Process</A><br><br>Never used it before myself (or even know anyone that has), but if time = money for you, you could look at this: &raquo;<A HREF="http://www.proposalkit.com/" >www.proposalkit.com/</A><br><br>If it's in-house you could try something as simple as this: &raquo;<A HREF="http://en.wikipedia.org/wiki/Statement_of_work" >en.wikipedia.org/wiki/Statement_of_work</A><br><br>I used it at one of my jobs, coupled with weekly e-mail updates and bi-weekly phone meetings.  Its pretty simple because you just say what you're going to do, when it will be done, and what your customer will get when its over.  We really did it mostly to define goals and eliminate scope creep.]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21709071</guid>
<pubDate>Fri, 09 Jan 2009 10:51:20 EDT</pubDate>
</item>

<item>
<title>Re: business requirements</title>
<link>http://www.dslreports.com/forum/remark,21708597</link>
<description><![CDATA[<A HREF="/useremail/u/825167"><b>johnnyboyct</b></A> : Id LOVE to see some kind of actual documents of this type :)]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21708597</guid>
<pubDate>Fri, 09 Jan 2009 09:28:50 EDT</pubDate>
</item>

<item>
<title>business requirements</title>
<link>http://www.dslreports.com/forum/remark,21707626</link>
<description><![CDATA[<A HREF="/useremail/u/164867"><b>inGearX</b></A> : What are the industry standards / templates for the business requirements that non tech people write - before handing in a request and etc to developers...<br><br>Thank you...]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,21707626</guid>
<pubDate>Fri, 09 Jan 2009 01:11:23 EDT</pubDate>
</item>

</channel>
</rss>
