20171215_Seven-Types-of-Wastages-During-Software-Development-Process_2

Seven Types Of Wastage During Software Development Process

Seven Types Of Wastage During Software Development Process

Friends we will discuss step by step improvements that helps the developer for either his better carrier or for an entire firm for better growth. 

>> Wastages are that holes from which the firms losses it’s money. But no one can notice it except a good manager. If you are freelancer, then also it becomes very important to save your time and energy by knowing the wastages. Let’s discuss the types of wastages, the sources and the remedies.

>> Mr.Shingoidentified 7 major types of wastages in manufacturing processes. Following his way Marry and Tom translated these 7 wastages in form of software development process.

>> To managers who want to achieve more, I would recommend to read the book written by Marry and Tom on same topic.

>> At collonmade we take extreme care to minimize these wastages.

>> For that we have developed special training program for our employees continuous improvements.

>> One should note that this is not once read and became capable type of thing. It requires continuous effort by a firm and by an individual too, to achieve it.

>> To remember these wastages types we will use common word TIMWOOD(Cricketer). (T)– Task switching (I)-Incomplete work (M)-Motion (Hands off) (W)-Waiting (Delay) (O)-Over production (extra features) (O)-Over learning (Re work) (D)– Defects.

Let’s see understand each topic with reason of existence and some hints to eliminate them.

1. Task Switching

Team member moving from one task to another task without completing first task

Why it happens :

>> The biggest and common reason is team leader or project manager has not understood the client requirement well and not has developed the project charter ( or say big picture/map of the project). So, in confusion they simply ask to do the work to developer whatever they feel right.

>> Developer might have been assigned many tasks by his project manager.

>> Some issues or interruptions in present tasks can also lead to developer to shift to another task.

>> Lack of proper coordination or lack of information available from client to developer.

How we can eliminate it :

>> Simply training (yes no other option!!!) the team leader or project manager about how develop project charter, project schedule, project life cycle and train them to minimize the commands related to switching the tasks to their developers without affecting the project quality and client requirements. In one line – they need to be good team coordinator not leader.

>> IF command comes from top the developer will not have other option. Team leader or manager need to understand the drawback of this and needs to reduce it.

>> Developer needs to understand that there will be always some issues with present developments; it doesn’t mean to leave that task. Enjoy the challenges. Switching will waste your time. Or developer can take 5 minutes break to make his mood fresh. This seems small but it is effective.

>> Lack of coordination or lack of information between client and developer will cause the ambiguity and ultimately leading to waste of time. Better to make developer available from the first day of client technical discussion meetings. Command to developer should come from only one person.

2. Incomplete Work

Partially work done is work which is pending to complete and due to that either you cannot show it to your client or no other developer can start his next decided task on the same which he has to complete after your work.

Why it happens :

>> Technical complexity which was not analyzed during earlier planning.

>> The developer doing the work suddenly not available, either because he left the job or due to some other reasons like sickness.

>> One developer has done his job and now the work is pending due to other who supposed to work on it is busy with other task.

How we can eliminate it :

>> To understand and evaluate the technical complexity of the task is very important not only from the angle of the development but also up to some extents, it affects the commercial terms also. Better is to arrange all team members meet who will take part in the development and ask them about the future technical complexity that might come during development of the project. It will give 360 views to the project and will help.

>> It is the most common fear and most common scenario that confuse all the team members when happen. Practically you cannot avoid the same so; you have to be ready to encounter it when happen. The possible solution is daily morning or noon meeting of all the project team members and asking them to tell about the development that happened during previous day. It is about to listening and to making note of the same by team leader. So, when the next day he know that someone is not available for many days then he can transfer the work to other by giving first developers activity from beginning to till date.

>> Proper coordination between the teams and accurate prediction of timing for the next task is the only key which can eliminate this problem.

3. Motion (hands off)

Passing the work from one person to another after completing the first person work.

Why it happens :

>> Due to nature of the task that require different kind of expertise. Team members working from different locations.

>> Lack of visibility and information and so, tasks move from one hand to another then again go back to first person’s hand.

How we can eliminate it :

>> If task requires different kind of expertise then you cannot avoid it but here the matter is you should not increase the hands off by dividing the tasks into more small pieces. Keep the number of pieces of the task exactly equal to the requirement of the expertise in that project. Not more than it.

>> In the case of one developer working at client’s location and one at his office, there will be too many hands off between these two (or more if involved in the same fashion) developers. So, first task is selecting the developers who are more comfortable with each other. The next is giving them the time line for the work and also, take the progress report from them on regular basis. All developers must be trained about the drawbacks of the hands off and how they can reduce them.

>> In the daily project meeting most of the problems related to the visibility and information can be encountered. Only the rule is there must be proper documentation of the meeting discussion with each member of the meeting related to his own work.

Related Posts