[3 Reasons Agile Teams Only Count Work that Is Done](https://www.mountaingoatsoftware.com/blog/why-agile-teams-put-so-much-emphasis-on-being-done-each-iteration) > All work is put into one of two states: done or not started. > > For work to be considered done, it must fulfill the team’s definition of done. Any work that is not done might as well not have been started as far as tracking progress is concerned. Read later: - https://www.mountaingoatsoftware.com/search?keywords=definition+of+done - https://www.mountaingoatsoftware.com/blog/why-agile-teams-put-so-much-emphasis-on-being-done-each-iteration - https://www.mountaingoatsoftware.com/blog/multiple-levels-of-done - https://www.mountaingoatsoftware.com/blog/establishing-a-common-baseline-for-story-points - [agile - Help me understand how QA works in Scrum - Stack Overflow](https://stackoverflow.com/questions/155250/help-me-understand-how-qa-works-in-scrum) - [Is QA involved in your scrum meetings and sprint planning? : agile](https://www.reddit.com/r/agile/comments/5e1nju/is_qa_involved_in_your_scrum_meetings_and_sprint/) - [Why having a separate week of QA in your sprint is not agile | by Lauren St.Jean | Medium](https://medium.com/@lauren.stjean/why-having-a-separate-week-of-qa-in-your-sprint-is-not-agile-41623f2cfa25)