Editing Agile software development (section)

====Assigning tasks====
One of the intended benefits of agile software development is to empower the team to make choices, as they are closest to the problem. Additionally, they should make choices as close to implementation as possible, to use more timely information in the decision. If team members are assigned tasks by others or too early in the process, the benefits of localized and timely decision making can be lost.<ref name="Effective Sprint Planning">{{cite web|last1=May |first1=Robert |title=Effective Sprint Planning |url=http://www.agileexecutives.org/Blogs/tabid/66/EntryId/18/Effective-Sprint-Planning.aspx |website=www.agileexecutives.org |access-date=2014-06-14 |url-status=dead |archive-url=https://web.archive.org/web/20140628102810/http://www.agileexecutives.org/Blogs/tabid/66/EntryId/18/Effective-Sprint-Planning.aspx |archive-date=28 June 2014 }}</ref>

Being assigned work also constrains team members into certain roles (for example, team member A must always do the database work), which limits opportunities for cross-training.<ref name="Effective Sprint Planning"/> Team members themselves can choose to take on tasks that stretch their abilities and provide cross-training opportunities.