Scrum sometimes does not seem to cater to specialized resources very effectively. For example, in major organizations, there is often a shared community of expert resources such as architects, usability engineers, QA, the performance and scalability team, who serve many project teams. These resources have to be committed well in advance and have specific deliverables, which also becomes an additional dependency to track. It cannot simply be assumed that these specialized resources would be available for every sprint, forget about every stand-up meeting. (AgileScout.com)
Vijay will present some scenarios that he has encountered and some of the challenges that teams he has worked with have faced. This will be followed by an open forum where attendees can discuss experiences they have had and what they have done that works or doesn’t work. The goal is to walk away with an outline of best practices and patterns.