Loading ...
Sorry, an error occurred while loading the content.

RE: [scrumdevelopment] Metrics to report up

Expand Messages
  • Roy Morien
    I see ... that seems pretty clear. Thanks George. :)
    Message 1 of 57 , Nov 2, 2010
    • 0 Attachment
      I see ... that seems pretty clear. Thanks George. :)

      > To: scrumdevelopment@yahoogroups.com
      > From: lists@...
      > Date: Tue, 2 Nov 2010 09:11:04 -0400
      > Subject: Re: [scrumdevelopment] Metrics to report up
      > On 11/2/10 4:36 AM, Roy Morien wrote:
      > > I see one probably totally irrelevant little flaw in the arithmetic
      > > ... I hesitate to mention it ... How do you calculate the lines of
      > > code in your system before any code has been written?
      > Easy! You do it the same way you predict cost and schedule. You guess a
      > number, and then reward people for being within +/- 3% of that number,
      > and punish them for being outside +/- 5%. They'll hit that number.
      > - George
      > --
      > Nov 15-16 Agile Testing Workshop in Orlando
      > http://www.sqe.com/AgileDevPracticesEast/Workshop/
      > ----------------------------------------------------------------------
      > * George Dinwiddie * http://blog.gdinwiddie.com
      > Software Development http://www.idiacomputing.com
      > Consultant and Coach http://www.agilemaryland.org
      > ----------------------------------------------------------------------
      > ------------------------------------
      > To Post a message, send it to: scrumdevelopment@...
      > To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links
      > <*> To visit your group on the web, go to:
      > http://groups.yahoo.com/group/scrumdevelopment/
      > <*> Your email settings:
      > Individual Email | Traditional
      > <*> To change settings online go to:
      > http://groups.yahoo.com/group/scrumdevelopment/join
      > (Yahoo! ID required)
      > <*> To change settings via email:
      > scrumdevelopment-digest@yahoogroups.com
      > scrumdevelopment-fullfeatured@yahoogroups.com
      > <*> To unsubscribe from this group, send an email to:
      > scrumdevelopment-unsubscribe@yahoogroups.com
      > <*> Your use of Yahoo! Groups is subject to:
      > http://docs.yahoo.com/info/terms/
    • Hariprakash Agrawal
      I have come across this scenario very often (almost 95% products/projects) in which defects escape and I have seen this irrespective of methodologies (or
      Message 57 of 57 , Dec 13, 2010
      • 0 Attachment
        I have come across this scenario very often (almost 95% products/projects) in which defects escape and I have seen this irrespective of methodologies (or practices) used. Human can make mistakes (at every phase/activity) for various reasons however we would like to keep improving ourselves continuously. We measure 'defects escaped' and take it seriously, means, we get to the root cause and invest in required trainings/expectations.

        We focus on design & code quality metrics, like, cyclomatic complexity, fan-in, fan-out, depth (inheritance) and run some code quality tools to check coding standard compliance and other parameters (like, memory leakage etc). We report this to management as well to keep them in loop. We measure test related metrics, like, # of test cases (manual vs automated), first time pass ratio, # of defects (open, fixed, closed, postponed) etc.

        We do not focus much on velocity, thanks to this forum. We track release burn down, # of stories committed / # of stories achieved (to keep improving team's commitment level), # of demos accepted/ rejected by PO, # of times team got changes in middle of sprint (it is minimal but not zero yet, this helps in deciding sprint length, puts back-pressure on PO) and few more (customer satisfaction and employee satisfaction).

        For us, agile is mix of Scrum and XP practices hence we focus on both.

        Hariprakash Agrawal (Hari),
        Managing Director | Agile Coach | http://opcord.com | http://www.linkedin.com/in/hariprakash
        Software Testing (QTP, Selenium, JMeter, AutoIT, Sahi, NUnit, VB/Java Script, Manual) || Consulting / Trainings (Agile, CMMi, Six Sigma, Project Management, Software Testing

        On Mon, Dec 13, 2010 at 9:11 PM, Ron Jeffries <ronjeffries@...> wrote:

        Hello, woynam. On Monday, December 13, 2010, at 10:12:25 AM, you

        > Sorry, but I don't see how "defects" can escape. If you're
        > writing automated tests for every story, an "escaped" defect means
        > that you ignored the failing test. Is that really that common?

        It is possible, and not all that unlikely, to miss a test or write
        one incorrectly. It would be possible, I suppose, to define Done as
        "passes whatever tests we wrote" but that strikes me as a bit too

        So an escaped defect would be something we didn't like, that we
        agree we understood and somehow failed to get implemented and

        Ron Jeffries
        Sorry about your cow ... I didn't know she was sacred.

      Your message has been successfully submitted and would be delivered to recipients shortly.