The Artima Developer Community
Sponsored Link

Agile Buzz Forum
7 Reasons Why You Don’t Get to Done

0 replies on 1 page.

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 0 replies on 1 page
Franco Martinig

Posts: 5631
Nickname: martinig
Registered: Apr, 2003

Scrum Expert
7 Reasons Why You Don’t Get to Done Posted: Oct 23, 2012 5:48 PM
Reply to this message Reply

This post originated from an RSS feed registered with Agile Buzz by Franco Martinig.
Original Post: 7 Reasons Why You Don’t Get to Done
Feed Title: Scrum Expert
Feed URL: http://feeds.feedburner.com/ScrumExpert
Feed Description: Resources, News and Tools for the ScrumMasters, Product Owners and Agile Developers
Latest Agile Buzz Posts
Latest Agile Buzz Posts by Franco Martinig
Latest Posts From Scrum Expert

Advertisement
In this article, Faisal Mahmood discusses seven reasons why a Scrum team cannot get to done at the end of a sprint. In Scrum, “done” is often defined as producing a potentially shippable product. According to Faisal, the seven reasons that lead Scrum teams not getting to done 1.Team is not cross functional 2.Unclear or absent Definition of Done 3.Technical debt 5.Late integration 6.Change of scope during Sprints 7.Ineffective planning Each reason is then discussed in details in the article.

Read: 7 Reasons Why You Don’t Get to Done

Topic: Agile Architecture: Design For Replaceability. Previous Topic   Next Topic Topic: Early Feedback Reduces Anger and Frustration

Sponsored Links



Google
  Web Artima.com   

Copyright © 1996-2019 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use