title: How to estimating stories that are "less complex" but "effor is more"
body: <p>In Agile process <strong>story points are a measure of complexity and not of time</strong>. How does this holds good for a story which is less complex but more time tacking to complete.</p>
  
  <p>Let me take an example,</p>
  
  <p><b>Story 1</b>: Save the user details. </p>
  
  <pre><code>Story points = 2. Typically Takes about 1 day to complete.
  </code></pre>
  
  <p><b>Story 2:</b> The Company name has been changes from X to Y, and this needs to be updated in application. There are about 40 screen, 10 reports, Legal Notice all these should change.</p>
  
  <p>This is typical example of a simple tasks but it will take a lot of time to implement (considering a localized application, even after following the proper standards of development) and test.</p>
  
  <p>If I go by the traditional definition, I will give Story point 1, but then I am looking at a wrong velocity, the velocity will be down even after good work. I have seen this article which speak about the problem.</p>
  
  <p><code>My question is how this task can be compared to the first story and should the effort be included in story point estimation?</code></p>
  
  <p>I am almost convinced with this idea but would like to know the best practices used in such cases or if there is any good <a href="http://www.mountaingoatsoftware.com/blog/its-effort-not-complexity" rel="nofollow">article</a> I can read about it?</p>