Hi Pooja,
I wish there was a step by step guide :-) This is such a complex subject
that it is impossible to give an answer without knowing your
organization, environment, culture and context.
In general:
* Learn about Scrum. Not just the practices, but the values and
principles behind them.
* Choose a small project
* Implement Scrum on this project as a trial
At this point you will run into a various issues, impediments and
bottlenecks depending upon your organization environment. Each of these
will require some resolving.
Once you have resolved them, you can expand Scrum in the organization.
Here are some things to watch out for. You will invariably run into one
or more of these -
* Executive support - Does upper management believe and support the
transition
* Developer support - Do developers, testers, ... support the transition
* Cultural concerns - Do you need to migrate culture to a more open and
trusting one
* Management style - Do you need to migrate from command and control to
a self organized style
* Functional silos - Can you break down department barriers and create
cross functional whole teams
Transitioning can be easy all the way up to very hard. It just depends
on how comfortable everyone involved with getting out of old habits and
learning new ones.
The biggest issue in transitioning is to manage the social and cultural
changes that will be required.
For example,
* PMs may feel threatened that their role is reduced
* Executives may feel a loss of control
* Customers may feel that they need to be too involved
* Developers may feel that they are under scrutiny
Due to all these factors there may be resistance to the change. There
will be an uncomfortable transition period when this happens.
This transition period could be as short as a week or two, or as long as
a couple of years. It depends on how much everyone has bought into
Scrum, how open they are to change, and how accepting the organization
culture is.
--
Siddharta Govindaraj
Agile Tools For Agile Teams - http://www.ToolsForAgile.com
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
>