Bugs, defects, customer requested enhancements, competitive product functionality, competitive edge functionality, and technology upgrades are backlog items. Product components or objects that must be changed to implement a backlog item into a new release. Changes that must occur to a packet to implement a backlog item. The team that works on the new release includes full time developers and external parties who will be affected by the new release, such as marketing, sales, and customers. The Scrum approach, however, welcomes and facilitates their controlled involvement at set intervals, as this increases the probability that release content and timing will be appropriate, useful, and marketable.
Management deals with backlog and issues.
Development teams are small, with each containing equal numbers of developers, documenters and quality control staff. Multiple teams of between three and six people may be used. The team defines changes required to implement the backlog item in the packets, and manages all problems regarding the changes. The members of each team are selected based on their knowledge and expertise regarding sets of packets. Interaction with these variables defines the end of development cycles.