title: User Stories - Problems that can't be made user stories
body: <p>I am from an XP background. I know the process very well and have solid working experience with it. I have found it to be the best way to develop software. </p>
  
  <p>I find myself in the position of a process doctor of sorts and this creates much self examination and revaluation of my own understandings. </p>
  
  <p>A very common thing I hear is that some work can’t be made into stories. I personally don’t believe this. The excuses include</p>
  
  <ol>
  <li>Its too big (The developer will have nothing to show until the end of 5 weeks).</li>
  <li>it’s a complicated algorithm or abstract concept (will take 5 weeks to write and nothing to show).</li>
  </ol>
  
  <p>This question is to get hints, tips or suggestions.</p>
  
  <p>I am looking for hints, tips, and suggestions as to how to address these and similar perceived problems (and more if you can think of them).</p>
  
  <p><em>I will mark the answer that has the most information on how to get around users/developers who wont write stories and address their many excuses as to why not (I have only listed a few and there are many more).</em></p>