Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Java Java Data Structures Efficiency! Map Out the MVP

Why is a Backlog list even needed?

Since everything in the Backlog gets placed in the To Do column, because it has to be done, what is the purpose of having a Backlog at all? Why not just start out with a To Do list and finished? Thank you.

1 Answer

Craig Dennis
Craig Dennis
Treehouse Teacher

Hi Adiv,

The backlog is usually filled with other stories that will be completed in future sprints if we decide on that. I kept it there for consistency sake. If we run into something that is outside of the current sprint we are working on, we can drop it in the backlog for future sprints.

That make sense?

Thank you. It does make more sense to me now that I understand that the purpose of the backlog is to contain items currently being processed as well as items which might be processed at a later time, outside the current development cycle. Thanks!