Baby Step Technique (BST)
Have you seen a baby when he starts walking at his initial stage? The baby firmly puts one step further and wait until his first step made a solid landing in the ground. Unless and until, he is sure that his first step is placed and planted properly in the ground, he started moving his second step for further walk. This way he is ensuring that his first step should not be uprooted when he is moving his second step. The baby always worked in this way and covers the initial distance in a long span of time. He is not getting success at every attempt that he is doing. But he understands that efforts may fail, but one should not fail to make efforts.
Who told this little angel to behave like this? Who told him about the risks of putting steps? How he is ensuring that his first step landed safe in the ground? What is the timeframe for him to decide his second step movement?
Well, the questions are many, but the answer is simple, “God is great”.
I always appreciate this awesome technique and would like to name it as “BST – Baby Step Technique”.
What I learn from the textbooks is just for my resume, I believe more in informal learning, I learn more from the newspapers. I read books and articles about testing and quality. I question and critique everything aggressively. I write articles on my blog site regularly about my previous and current testing and quality experiences and encounters. I read books and articles that are NOT about testing and quality. And I notice babies also.
Now, let’s come out from this baby world and fit this BST in our Software Industry.
Throughout my carrier so far, I always saw that good people do not need laws to tell them to act responsibly, while bad people will find a way around the laws. There are many who wants to make a difference but don’t know where to start. BST is the best example to start. Baby Steps Technique (BST) works in a similar way in IT as it works for a baby.
In our industry, we always messed up with different issues / concerns / doubts. But if you do not want to create a loaded and messy environment within your group, BST is for you only. In BST, one should split his/her tasks in small pieces of chunks and try to fix and close it before you are going to move in another task. "Establish time boxes" and "Finish partly done work" are two child techniques of BST. Instead of big bang approach, one should take small, incremental steps that maximize discovery.
Establish time boxes means that one should decide the completion time of each and every activity (irrespective of small and big one). Defining a completion date creates a time box for you and you will become conscious about the deadlines.
Finish partly done work. One should not keep the status of any action item as pending. Try to work in binary mode. Either one or zero. Making the status of any task as pending for more than a week is not recommended. BST can be failure for these guys who have a regular practice of doing so.
I am working on these two (or would say working with these two) from the last three years. From manager’s point of view, assigning time to complete, help team to complete timely and resolve obstacles quickly are the three basic activities that should be performed to make BST a successful technique.
BST always asks a question from its followers - Are you doing even one percent of what you think must be done?
I do agree that one of the easiest things to do in life is to come up with solutions, but one of the hardest is to actually implement them. But BST is a technique which can be implanted on large scale as well as small scale, with a baby steps.
Breaking the tasks into smaller one will always make your activities good, fast and efficient. And this is all BST is based on.
-- Sanat Sharma