LinkedInFeeds

The Toyota Way – Types of Wastes – IT industry

By

 



The very first piece, I wish to clear the misconception that, the Lean management is applicable for Manufacturing. No beloved readers! It is not true; the Lean management can be applied in any industry even in the personal events.

Let’s see the type of mistakes that are mostly applied, experienced in the IT industry, referring to Lean Management genre.


1) Overproduction

This can be termed effectively as faster than the necessary pace. Specifically, in the Business analysis, the faster inferring the solution without validating the assumptions, specifications will havoc and down run the entire project life cycle.

Overproduction (Faster than the necessary pace) is observed in all the project life cycle.

2) Waiting

The Business analysis activities are completed, and development were not started due to various reasons.

I would say this as proper fitment of pipeline. If there is spills in the pipeline in movement of activities, the efforts are required to re-order/ re-align. It should not be over production / under production.

3) Conveyance

In IT industry, there is not any physical movement of goods. In orderly, it is the communication to the relevant stakeholders at the right time at right mode of communication.

Choosing irrelevant stakeholders will obstruct the actual response required. This looks simple but it is the real hero for the project life.

4) Processing

The poor layout of the processing standards, approvals, communications etc., will not only derail the project, will affect the morale, and will have the ripple effect for the overall organisations.

In the new era, the decisions power and accountability to spread across the horizontal functions to take swift decisions. Time is the superior power my friend.

5) Excess Stock

Excess stock of the resources in a delivery which is not an actual requirement will engage you in poor planning. This is the additional planning strategies, excessive dependencies will result in greater lead time.

6) Correction of Mistakes

This is the biggest enemy of the IT Organization's.

Correcting a single error, the error may be process or the development errors will involve more efforts on the actual developments. Manifesto that shall engage is Fail Fast and Fail Cheap.

Here comes, the solution should be scalable and interoperable.


I tried to list out the common examples of the above mistakes, there could be multiple examples for each mistake that has most impacts in the projects.

Thanks for reading. Requesting to fill in all the common mistakes and the lesson learnt may help other readers to leverage your experiences.

Comments

Post a Comment

Popular posts from this blog

Wireframe a Prime part in Design

By
Image
Wire frame using pencil drawings                                                                                                Why Wireframe is Important? The timely feedback from the project stakeholders is most important. The early feedback from stakeholders will boost the satisfactory solutions to the problem identified or goal in a project. Never expect anyone to read through hundreds of pages of text only specifications. Instead, the better is to provide any visual representation to which they can refer and react or post any suggestions or comments for better solution which will be delighted and expected for the goal achievement. Wireframes provide an excellent solution to this problem in a web based platform / window based in a designed view of pages / screens. What is Wireframe? Wireframes are created for arranging the elements to best accomplish a particular goal or purpose. It mainly explains the page layout or the place / arrangement of website’s content. It
Read more

SpeckBook in requirement elicitation

By
Image
SpecBook Do you know what SpecBook is? It is specifications book. Spec Book - Requirement Elicitation This is traditional method of requirement elicitation technique. This is also widely used now. SpeckBook will contain list of questions about a function, feature or any component. It is a drilled down approach. You should not end this process till no further question can be asked. This can be also said as granular approach. In the SpeckBook, it is not like all questions have to be posted on your client. On basis of discussion and requirement gathering few questions can be answered by you and some questions will answer by itself. The Missed questions can be always posted at client. Questions can also ask to multiple stakeholders to get detailed / required information. Things to look on while preparing the questions a. Questions should be simple and understandable. b. It should be mapped to any of the Business requirements. c. It should not cross the s
Read more

Writing Requirements - Consider Some Points For Success

By
Be specific In Requirements      When stakeholders are be very clear in their need, Business Analyst should not consider that it is final requirement and write it down on paper. There is still more specific in requirements. Ask more questions to business users to make requirements more specific. The other trap is you should identify the correct user to question on requirements. To be more specific, i have stated a below example for better understanding Need identified is : I need a invoice report every month. Other Questions to be asked to stakeholders are : Why you need, When you need, How you need, Which time you need, In which format you need and still more. Drill down to become the requirements more specific. Bring Your Testers Early In project     Every requirement should be testable, reliable. For each requirement translate in to a test case. Quality is very important in meeting the Business need. Success Factors Of A Project     We cannot say provid
Read more