When teams and projects are small then dividing the work between developers can be informal and easy. As the team and project grows then this process becomes more difficult and more important. The lines of communication between developers increases exponentially as the number of people grows. If work isn't divided properly some downsides can be development silos, decreased ownership by developers, and lack of work ready to demo at sprint close. We'll talk about best practices for breaking stories and tasks into manageable pieces and assigning them to teams or team members. I'll share examples of dividing stories and tasks in different ways to help make the best practices memorable.