Final answer:
In adopting Agile, Support and Maintenance teams have to become accustomed to working with a product backlog, which is a significant shift from traditional maintenance methods. This involves being flexible and responsive to prioritize and address backlog items in an iterative manner.
Step-by-step explanation:
In adopting Agile, Support and Maintenance teams have to primarily become used to working with a product backlog. This is a prioritized list of tasks that need to be completed, which could include new features, bug fixes, and other maintenance tasks. Unlike more traditional maintenance teams that may work based on a strict schedule or service-level agreements (SLAs), Agile teams need to be flexible and responsive to changes in the product backlog. While SLAs, reviewing bugs, and creating maintenance documentation are also part of their responsibilities, the product backlog is unique to Agile and represents a shift from a purely reactive maintenance model to a more proactive and iterative approach.