Breaking the Functional Mind Set in Process Organizations. Thousands of businesses have reengineered work in order to focus employees on processes that clearly provide value to customers. They have done away with their functional silos and created new organizational structuresprocess complete departmentseach able to perform all the cross functional steps or tasks required to meet customers needs. Although many of these efforts have paid off in the form of lower costs, shorter cycle times, and greater customer satisfaction, many others have resulted in disappointment companies have endured the trauma of reengineering only to discover that their performance is no betterand in some cases actually worsethan before. What caused things to go wrong There certainly are a variety of possibilities, among them a failure to focus on parts of the business that were significant to customers and a failure to integrate autonomous, functionally focused information systems into a shared, process focused database and network. Senturus comprehensive library of Cognos and Business Intelligence presentations and information. All of them are free and we add new resources regularly. The birth of Agile. Traditionally, the socalled Waterfall process dominated software development. Work trickled down through organizational silos in sequential fashion. Personal site of authoreditor Pat McNees, personal historian and medical historian, bringing a light touch to heavy subjects, helping people and organizations tell. Breaking The Functional Mindset In Process Organizations Pdf' title='Breaking The Functional Mindset In Process Organizations Pdf' />But something else that is often overlooked is the tendency of managers and reengineering teams to underestimate the actions required to transform the way employees behave and work with one another. They assume that simply changing their organizational structures from functional units into process complete departments will cause people to shed their functional mind sets and will forge them instantly into a team intent on achieving common goals. Over the last three years, we conducted a study of U. BR0311_500.png' alt='Breaking The Functional Mindset In Process Organizations Pdf' title='Breaking The Functional Mindset In Process Organizations Pdf' />S. At each of the companies, which ranged in size from small concerns to such corporate giants as Texas Instruments, Hewlett Packard, and Unisys, we examined a department whose responsibilities included manufacturingor, to be more specific, assembling a printed circuit board, inserting the board into an electronic commercial product, or both. Each manufacturing department had been identified by management as the one with the best practices in the company. Each had fewer than 3. We chose these departments because they were sufficiently homogeneousin terms of their production processes, their national cultural influences, and the market conditions they facedto permit a comparison of their performances. Of the 8. 6 departments, 3. Those responsibilities included creating the schedule acquiring the orders and the needed parts and people training workers moving parts setting up, maintaining, and repairing equipment transforming the parts into a final product inspecting and reworking the product delivering the finished product to customers obtaining feedback from customers and making modifications in the product to meet their needs and evaluating and improving the process. Reengineering experts such as Michael Hammer and James Champy would call this set of jobs the order fulfillment process. We classified the remaining 5. We obtained data on cycle times, conducted detailed work flow analyses, identified who was responsible for each step in the process, documented the organizational structure, observed how the department coordinated work, and interviewed managers and workers. We interviewed more than 1,5. To compare performances, we focused mainly on cycle times, for three reasons. First, cycle times are a major competitive factor in the electronics industry, and many companies in our sample embraced process centered structures specifically to shorten their cycle times. Second, it was possible to compare cycle times in a uniform fashion. Finally, cycle times included time spent reworking parts and therefore could serve as a process quality metric, too. To our surprise, we found that process complete departments did not necessarily have faster cycle times than functional departments. In fact, the only ones that did were those whose managers had taken steps to cultivate a collective sense of responsibility among workers that went beyond merely changing the organizations structure. We found that such collective responsibility could be fostered in a variety of ways by structuring jobs with overlapping responsibilities, basing rewards on group performance, laying out the work area so that people can see one anothers work, and designing procedures so that employees with different jobs are better able to collaborate. Departments can reduce cycle times by designing jobs with overlapping responsibilities. Interestingly, the particular method or number of methods employed did not seem to matter. Process complete departments that had adopted all four methods did not have significantly faster cycle times than those that had adopted only one or two. What did matter was whether a company had embraced any of the methodswhether the company recognized that it needed to do more than merely restructure the organization to foster a collaborative culture. And it mattered considerably. See the exhibit How Ways of Promoting Collaboration Improve Cycle Times. Process complete departments that had acted on the insight had cycle times as much as 7. Even more startling, the latter departments had much longer cycle timesas much as 3. The process complete departments with longer cycle times had one or several of the following critical deficiencies jobs with narrow responsibilities, employees with many different titles, rewards based solely on individual performance, physical layouts that discouraged people from seeing one anothers work, and no explicit procedures for knitting employees together. In other words, those departments maintained functional distinctions and a narrow focus on specific tasks, thereby negating the potential benefits of a process focused structure. How Ways of Promoting Collaboration Improve Cycle Times Changing the Culture In the course of conducting this study and other research, we have asked many managers who are reengineering their businesses to explain why they are moving toward process complete departments. They always answer that such a change will reduce the time and effort required to integrate and monitor the work of autonomous units, thereby reducing cycle times and instilling in workers a common understanding of what they have to do to satisfy customers. But when we ask managers to describe the changes that must take place for their organizations to achieve those objectives, they speak mainly of melding multiple functions into customer focused teams responsible for an entire process. Most of the managers assume that this structural change will naturally create a common understanding of, and a collective sense of responsibility for, customers needs. Surprisingly few can define the type of collaboration they want employees to achieve, let alone the means they might employ to encourage such collaboration. For example, one organization had restructured procurement and manufacturing engineering by melding the two functions into customer focused teams responsible for the entire processfrom the initial price quotation to the customer to the delivery of the product. The individual jobs of the manufacturing engineers and the procurement officers on the teams were broadened but did not overlap. Dev. Ops Wikipedia. Dev. Ops a clipped compound of development and operations is a software engineering culture and practice that aims at unifying software development Dev and software operation Ops. The main characteristic of the Dev. Ops movement is to strongly advocate automation and monitoring at all steps of software construction, from integration, testing, releasing to deployment and infrastructure management. Dev. Ops aims at shorter development cycles, increased deployment frequency, more dependable releases, in close alignment with business objectives. Definitions and HistoryeditAt the 2. The Oregon Trail Flash Game. Agile Toronto conference, Andrew Shafer and Patrick Debois introduced the term in their talk on Agile Infrastructure. From 2. Dev. Ops term has been steadily promoted and brought into more mainstream usage through a series of devopsdays,6 which started in Belgium and has now spread to other countries too. The term Dev. Ops has been used in multiple different contexts. A definition proposed by Bass, Weber, and Zhu, is Dev. Ops is a set of practices intended to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality. In recent years, more tangential Dev. Ops initiatives have also evolved, such as Ops. Dev,1. 0Win. Ops,1. Biz. Dev. Ops. 1. Dev. Ops toolchainedit. Illustration showing stages in a Dev. Ops toolchain. As Dev. Ops is intended to be a cross functional mode of working, rather than a single Dev. Ops tool there are sets or toolchains of multiple tools. Such Dev. Ops tools are expected to fit into one or more of these categories, reflective of key aspects of the development and delivery process 1. Code code development and review, source code management tools, code merging. Build continuous integration tools, build status. Test continuous testing tools that provide feedback on business risks. Package artifact repository, application pre deployment staging. Release change management, release approvals, release automation. Configure infrastructure configuration and management, Infrastructure as Code tools. Monitor applications performance monitoring, enduser experience. Some categories are more essential in a Dev. Ops toolchain than others especially continuous integration e. Jenkins and infrastructure as code e. Puppet. 1. 61. Relationship to other approacheseditThe need for Dev. Ops arose from the increasing success of agile software development, as that led to organizations wanting to release their software faster and more frequently. As they sought to overcome the strain this put on their release management processes, they had to adopt patterns such as application release automation, continuous integration tools, and continuous delivery. Continuous deliveryeditContinuous delivery and Dev. Ops have common goals and are often used in conjunction, but there are subtle differences. While continuous delivery is focused on automating the processes in software delivery, Dev. Ops also focuses on the organization change to support great collaboration between the many functions involved. Dev. Ops and continuous delivery share a common background in agile methods and lean thinking small and frequent changes with focused value to the end customer. They are well communicated and collaborated internally, thus helping achieve faster time to market, with reduced risks. Data. OpseditThe application of continuous delivery and Dev. Ops to data analytics has been termed Data. Ops. Data. Ops seeks to integrate data engineering, data integration, data quality, data security, and data privacy with operations. It applies principles from Dev. Ops, Agile Development and the statistical process control, used in lean manufacturing, to improve the cycle time of extracting value from data analytics. Site reliability engineeringeditIn 2. Google developed site reliability engineering, a new approach for releasing new features continuously into large scale high availability systems while maintaining high quality end user experience. While SRE predates the development of Dev. Ops, they are generally viewed as independent trends. Some aspects of Dev. Ops have taken a similar approach. Systems administrationeditDev. Ops is often viewed as an approach to applying systems administration work to cloud technology. The goals of Dev. Ops span the entire delivery pipeline. They include Improved deployment frequency Faster time to market Lower failure rate of new releases Shortened lead time between fixes Faster mean time to recovery in the event of a new release crashing or otherwise disabling the current system. Simple processes become increasingly programmable and dynamic, using a Dev. Ops approach. 2. 8 Dev. Ops aims to maximize the predictability, efficiency, security, and maintainability of operational processes. Very often, automation supports this objective. Dev. Ops integration targets product delivery, continuous testing, quality testing, feature development, and maintenance releases in order to improve reliability and security and provide faster development and deployment cycles. Many of the ideas and people involved in Dev. Ops came from the enterprise systems management and agile software development movements. Views on the benefits claimed for Dev. OpseditCompanies that practice Dev. Ops have reported significant benefits, including significantly shorter time to market, improved customer satisfaction, better product quality, more reliable releases, improved productivity and efficiency, and the increased ability to build the right product by fast experimentation. However, a study released in January 2. F5 of almost 2,2. IT executives and industry professionals found that only one in five surveyed think Dev. Ops had a strategic impact on their organization despite rise in usage. The same study found that only 1. Dev. Ops as key, well below software as a service 4. Cultural changeeditDev. Ops is more than just a tool or a process change it inherently requires an organizational culture shift. This cultural change is especially difficult, because of the conflicting nature of departmental roles Getting these groups to work cohesively is a critical challenge in enterprise Dev. Ops adoption. 3. 43. Dev. Ops as a job titleeditWhile Dev. Alaska Grown Restaurant Rewards Program'>Alaska Grown Restaurant Rewards Program. Ops describes an approach to work rather than a distinct role like system administrator, job advertisements are increasingly using terms like Dev. Email Attachment Programs. Ops Engineer. 3. While Dev. Ops reflects complex topics, the Dev. Ops community uses analogies to communicate important concepts, much like The Cathedral and the Bazaar from the open source community. Cattle Pets the paradigm of disposable server infrastructure. Flickr adopting Dev. Ops. Building a Dev. Ops cultureedit. Dev. Ops T shirt worn at a computer conference. Dev. Ops principles demand strong interdepartmental communicationteam building and other employee engagement activities are often usedto create an environment that fosters this communication and cultural change, within an organization. Teambuilding activities can include board games, trust activities, and employee engagement seminars. DeploymenteditCompanies with very frequent releases may require a Dev. Ops awareness or orientation program. For example, the company that operates the image hosting website Flickr developed a Dev.