AGILE (SCRUM) Prerequisite
Every seminars, conference, sessions or
forums i have gone through about AGILE (SCRUM), one of the very common questions
I noticed is "how long will it take an organization to completely adapt
the AGILE (SCRUM) way of development?”
And the answer is: minimum 4 -5 years.
Every-time i hear and read this answer, I
begin asking questions to myself, why does it take that long time? This really
surprises me because almost every organization, groups of developer i came
across with I found are so interested, curious and enthusiast about AGILE
(SCRUM) way of software development. People are talking about it, wants to know
about it, learn about it then why will it takes 4-5 years to implement
something that everyone are so enthusiast about.
Even if we take a look about the things
that we need to know to understand the SCRUM framework, a day of time should be
enough to explain and understand the:
- Roles- Product Owner- Development Team- Scrum Master
- Events - Sprint - Meetings (Sprint planning, Daily Scrum, Sprint Review and Sprint Retrospective)
- Artifact - Product Backlog - Sprint Backlog - Product Increment - Burn-down chart
Or to know about the AGILE development.
While
trying to implement the SCRUM, the kind of the difficulty i faced while
explaining the SCRUM to my development team is to make the team understand the
poker planning. Estimation seems impossible for most of the people in the
beginning without thinking about hours or day or week. Beside this all
other (roles, events, and artifacts) are well understood by the team in no
time. But still SCRUM
implementation was not working as it was expected to be. From my experience i
came to know that it is not the framework or methodology which is difficult to
understand. Actually it is people to make them ready to work under the
framework, correct their attitude, make then believe and realize the power of
SCRUM.
From my experience I have listed out the
following are the pre-requisite of SCRUM. Before start we must have:
Belief:
First and the foremost important are to
have belief on SCRUM. It is not there to amuse or confuse anyone. Each must
belief it is there for improvement, betterment of over work process and output
quality. To feel the magic of it one must believe that it will bring magic.
Positivity:
Positive nature or can do attitude.
Trust:
Each member of the development team has
the good trust on each other with their capabilities.
Respect & Appreciation:
Each member must respect the ideas,
suggestions of every other member of the team. There must be an appreciation
for each individual’s effort, and only a very healthy
competition instead of envy and jealousy.
Habit of Improvement:
One must have self-challenging attitude.
Challenging own-self each day to make own-self better every day. Obsession of
improving working process, attitude of "we can do better than this".
not afraid of adapting changes.
Out of the box:
Mostly developments teams are so used to
of working in same way and pattern that they have been following from years.
But technology on the other hand is changing or advancing every day. And to
solve or tackle the problems and issues of the ever changing environment it is
not effective always to think and deal with things in same manner. One must be
able to think things in totally different dimension.
If you have the team rich with above
points, you can implement the SCRUM from the very first day.
Do you agree with me?
0 comments: