title: Implementing User Stories the Agile Way
body: <p>I'm a newbie to the Agile/TDD world and trying to get my head around some of the basics.
  This is related to the way I should go about implementing user stories.</p>
  
  <p>For e.g. lets assume I have below 2 user stories to start with for a hypothetical content management system:</p>
  
  <p>Story 1:<br />
  <strong>As a</strong> Content Author <br />
  <strong>I need to</strong> be able to create News Articles<br />
  <strong>so that</strong> they can be used to attract users to the web site<br /><br /></p>
  
  <p>Story 2: <br />
  <strong>As an</strong> Editor<br />
  <strong>I need to</strong> be able to view existing articles<br />
  <strong>so that</strong> I can review them to improve the quality<br /></p>
  
  <p>The way I would approach this is, <br/> </p>
  
  <ul>
  <li>I would grab one of these user stories   </li>
  <li>break the <strong>I need to</strong> part of the user story into smaller pieces of tasks  </li>
  <li>Grab these tasks one by one and come up with Tests to cover the specific task  </li>
  <li>Implement tasks the TDD way  </li>
  </ul>
  
  <p>Area where my dilemma is about the <strong>As a</strong> part of the user story. <br/>
  Specially in these examples they indirectly imply some <strong>Authentication,Authorization</strong> related requirments to me since the user stories mention about two user categories.</p>
  
  <p>So my question is, whether I should have any tasks/tests that control Authentication/Authorization to the system to complete these user stories <br/>
  Or <br/>should I only focus on the <strong>I need to</strong> part of the user stories in trying to implement the functionality, and wait for any user stories that specifically mention about <strong>Authentication,Authorization</strong> related requirments?</p>
  
  <p>All your inputs are highly appreciated.</p>
  
  <p>Cheers.</p>