#DEFINE SILO SOFTWARE#

#DEFINE SILO SOFTWARE#

For example, the primary responsibility of software development is to develop software. This is simply because each silo has its own primary responsibility.

No matter what the silo or the issue, without a firm understanding and agreement on performance, responsiveness, authorities and responsibilities, there will always be finger pointing and communications issues. This вЂњsilo mentalityвЂќ appears when each IT silo reports that all is well, but the Users complain of inadequacies because of miscommunications and lack of orchestration between silos. This difference in views - IT with a technology focus and Users with an end-to-end focus - often results from the вЂњsilo mentalityвЂќ of IT. Users perceive IT services as end-to-end structures. Users of services do not see IT technology silos, and they do not perceive IT services as composed of silos. Classic examples are the battles between network and mainframe. Another common complaint is trying to get вЂњmind shareвЂќ from other departments. It is common for the Problem to вЂњdisappearвЂќ without any paper trail or notification back to the Service Desk. A common example is a Problem escalated from the Service Desk into a technical functional group, for example, software development. It becomes even more difficult with distributed organizations. Support groups often reside in different departments and locations. However, this is not the case in many IT organizations. For ITIL to succeed, the entire IT organization, including the staff and management of all silos must work together as a service-delivery chain. Successful ITIL adoption depends upon cross-silo process interaction and shared responsibilities.

Define silo