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

Re: How to fit testing in a sprint?

Expand Messages
  • JackM
    Agreed. Encourage the team to break the stories down even further. Not only will this help with the testing but it will have a huge impact on the teams ability
    Message 1 of 16 , Jun 9, 2011
    • 0 Attachment
      Agreed. Encourage the team to break the stories down even further. Not only will this help with the testing but it will have a huge impact on the teams ability to become more predictable and reach optimal velocity sooner!

      Jack
      www.agilebuddy.com
      blog.agilebuddy.com



      --- In scrumdevelopment@yahoogroups.com, Charles Bradley - Scrum Coach CSM PSM I <chuck-lists2@...> wrote:
      >
      > Kevin,
      >
      > What you describe is a well documented ScrumBut or Anti-Pattern, though I'm having trouble finding my favorite web site that describes the evil disadvantages of testing a sprint behind.
      >
      > I believe the short answer to how to fix your situation is:
      > 1.  Slice stories small.  Then slice them smaller.  Ideally, in a 2 week sprint, the first story would be finished in the first 2-3 days of the sprint.
      > More on Story Slicing here: 
      >
      > http://www.infoq.com/news/2011/04/how-to-split-user-stories
      > http://www.mountaingoatsoftware.com/articles/44-agile-teamwork
      >
      >
      > 2.  Do more test automation.  Ideally, while your devs are coding the first few stories, your testers are automating the tests for those stories, so that as soon as those stories are coded, the tests can be run almost instantly and have results in just a few minutes.
      >
      > More on test automation here: 
      > http://blog.mountaingoatsoftware.com/reduce-manual-test-techcnical-debt
      > http://blog.mountaingoatsoftware.com/the-forgotten-layer-of-the-test-automation-pyramid
      >
      > I realize my answer is somewhat short, but feel free to pose more questions.
      >
      >  
      > -------
      > Charles Bradley, CSM, PSM I
      > Experienced Scrum Coach
      > My blog: http://scrumcrazy.wordpress.com/
      >
      >
      > >________________________________
      > >From: kevinkrac <kkrac78@...>
      > >To: scrumdevelopment@yahoogroups.com
      > >Sent: Tuesday, June 7, 2011 8:40 AM
      > >Subject: [scrumdevelopment] How to fit testing in a sprint?
      > >
      > >My question is how to fit testing in scrum? While coding takes place? During next sprint?
      > >I would like to hear different opinions based on your past experiences.
      > >Is the following way the right way to do it? How would you do it differently?
      > >
      > >1) In the first sprint the development team spends time coding the stories agreed for the first sprint.
      > >2) Testing people, on the other hand, has no real testing to do, they may work on writing testing cases yes, but no real testing takes place.
      > >3) At the end of those first 2 weeks, the Review Meeting takes place, moment in which the stories would be hopefully "done" (not done-done yet), so they are in the "In BA Review" status. If everything goes OK, stories move to "Ready for Testing" status, so as to start testing phase during next sprint.
      > >4) The following week, testers start testing ("Ready for Testing" -> "In Testing") the stories worked during the past 2 weeks. Whereas devs work on the stories agreed for the second sprint.
      > >5) At the end of those two weeks, the Review meeting takes place again in which the stories agreed for the 2nd sprint are reviewed by business ("In BA Review") and stories from the first sprint are shown once again to Business so as to be "Accepted" (done-done).
      > >6) If a story fails a test, a defect is created to fix it (does not necessarily mean business people will not Accept the story).
      > >7) If a story is not "Accepted" by business people, it is moved back to the backlog, and it is re-prioritized, re-analyzed and re-estimated if necessary.
      > >
      > >Process repeats itself for next iteration and so on...
      > >
      > >So, in conclusion, although here we have 2-week sprints, the sprints could actually be considered of 4 weeks, since stories are not done-done until the end of the next sprint, that is when they are approved by testers and ready to be "Accepted" by business people.
      > >
      > >Does anyone do it this way? Drawbacks? Alternatives?
      > >
      > >
      > >
      > >------------------------------------
      > >
      > >To Post a message, send it to:  scrumdevelopment@...
      > >To Unsubscribe, send a blank message to: scrumdevelopment-unsubscribe@...! Groups Links
      > >
      > >
      > >
      > >
      > >
      > >
      >
    Your message has been successfully submitted and would be delivered to recipients shortly.