> Some clarification here. The "Change Management Lead" is leading the people aspect of the project - training development, business impact assessment, marketing buzz, other production readiness things like data quality, etc.
> If I were to include them in the scrum, I agree they need to be chickens and not pigs. However, there are "pigs" in the sense of being ready for a product launch that doesn't involve writing or testing code. With more thought, I'm wondering if a separate scrum would be suitable.
Why isn't the change lead a member of the team? The team should be cross-functional, including the deployment and change aspects.
Process Development Manager, Agile Coach (CST)
Digia Plc., Finland