How do I define success factor(s) for a scrum implementation process that is yet to kick-off?
My domain lead want me to come up with list of success factors, I can easily come up with things like: reduced risk, increased product quality, quick feedback loop, business involvement, etc. But I'm not a salesman and I don't want to come up wish lists which could be difficult to meet within few weeks. How can this be managed?
Context - This is a transition from a rigid waterfall approach to Agile, with loads of gates and obstacles etc.and the transition is being driven by the IT dept though business pretend to be involved. I honestly believe measuring success in a few weeks will be difficult.
In an earlier post, Ian Mitchell affirmed successful delivery every sprint is a key factor, I do not disagree but that will likely be the case in an organisation where there is "Agile Consciousness" and the change is led by the business with alignment with IT and not just following Agile for the sake of doing it, ow where the change is one way led.
Ongoing delivery is the same essential success factor regardless of whether the organization has achieved "agile consciousness" or not.
If they haven't achieved it, then they are presumably more likely to fail, but that is hardly a reason to seek a different criterion. The sooner any such failure can be evidenced the better.
Thanks for you comment Ian.