Having problems with message search?
Best practices : Scrum is a process framework, not a methodology. You need to follow it by the book, keep improving it as you go along and tune it to your needs. Let it evolve by careful observation.
Scrum benefits, quality improvement - there is enough material you can google.
Pay back time : All depends on your situation , what you mean by 'payback'. If you are looking at immediate benefits, I think they can be seen after a few iterations, say 6-8. Initial set of iterations is spent in understanding 'what is Scrum and how is it different than what we have been doing?'. The thing about the lean and agile methodologies is that they give you those 'aha' (sounds banal, but it's actually true) moments, when you see and experience that it really works well and feels more natural.
All the best !
Manu
On Fri, Jul 3, 2009 at 7:29 PM, poojawandile <poojawandile@...> wrote:
Hi,
Please share your experience/thoughts on following:
What should be the approach/step by step method if a company wants to transition from Traditional dev to Scrum. Any case study? What challenges, best practices, etc. Why Scrum, benefits, metrics (productivyt/quality improvement), what could be the pay back time, advantages over traditional, etc. Here I am thinking of a scenario "why and how a traditional dev based company can transition to Scrum org"
Cheers
Pooja
Offline 
Send Email