|By Michael Nir||
|June 23, 2014 02:16 PM EDT||
In order to create the combination between top-down problem-decisions (waterfall like approaches)and local problem-decisions (Agile project approach) here are practical guidelines to pursue
Three practical complex decision-problems guidelines:
- Simple local rules
- Strategic top down rules
- Visual problem view
We describe in detail, each practical guideline, below.
Simple local rules
This cannot be overstated. Local rules must be easy to follow. Whether these are rules for: a machine operator, traveling salesperson, a project coordinator, or you packing your bags.
The local decision rules are the ones mostly used, they must be easy to follow, understandable, and unequivocal. Consider the warehouse forklift operator who is re- stocking raw material. If she needs to follow a complex decision protocol for placing newly arrived material in the warehouse, it would result in chaos.
Instead, we need to equip her with an easy to follow mechanism for stocking the warehouse.
One such mechanism is FIFO - First In First Out. This is also the rule, you're following when stocking your fridge with groceries, if you don't want dairy products to go sour.
Supermarkets also follow this rule when their organizing their product shelves. At least, they're supposed to follow this rule, otherwise they will have outdated products on display.
The modern big supermarkets actually stock fresh items from the back, ascertaining this way, that older items are pushed forward.
Sly consumers will then pick up dairy products from the back of the shelf if they want to make sure that it is the freshest available.
There is even an acronym that goes along with local rule simplicity which is: KISS - and stands for: keep it simple and straightforward.
The Japanese KANBAN approach which we've previously mentioned, implements an easy to follow rule of thumb.
It is: when you're operating a manufacturing machine, you should only produce when the physical container carrying a finished product in front of you, is empty. In practice this was actualized by using Kanban cards. Kanban is the Japanese word for card.
For manufacturing purposes it much easier for operators to follow this simple rule. However, ordinarily in production floors, operators follow a complex weekly/daily production plan that is very confusing. This is the opposite of simple.
Make your local decision-problem rules are simple
- Travel to the next cheapest destination
- Pack the smallest item first
- Work on the easiest element first
- Stock according to FIFO
Strategic top down rules
The strategic top down rule which we select for our decision-problem has to constrain our decision space.
Consider for example a hospital's most expensive resource - the surgery room. Each such room has to be utilized as much as possible.
Reaching 100% utilization is not feasible - this can be proved using queuing theory; however 85%-90% utilization is desirable. The reason we require high utilization is for the pay back on the investment. The hospital invested money for the equipment in building and equipping the room and wishes to receive a return on the investment.
Hospitals' surgery rooms are generally a resource in shortage, hence there will always be patients requiring the room. It seems logical that the 85%-90% utilization will be easily achieved. This is not that case - the rooms are approximately 65% utilized in many cases - and it is driving the financial officers of hospitals crazy.
It drives them crazy almost to the point that they require ulcer treatment and have to wait in line for the surgical procedure - and yet the operation room is only 65% utilized.
The situation described of having lower utilization than expected and desired has to do with selecting an unsuitable top down problem-decision rule. The hospital schedules surgical procedures, utilizing the operation rooms, by using a monthly plan, as we've illustrated before, the top down plan fails because of many small changes.
What are these small changes and why do they occur?
In order to perform a surgical procedure in the operation room, the room has to be ready - i.e., cleaned, sterilized and with the proper equipment. The surgeon and his staff also have to be ready.
What happens if the surgeon and his staff are ready and waiting, however the room isn't prepped and cleaned?
The impact: we have very expensive employees (the physician, surgeon and others in the team) and a very expensive resource (the surgery room) as well as a prepped patient - all waiting for the room to be cleaned.
Wait a minute - this doesn't make sense you say! Didn't the top-down plan specify that maintenance personal have to be cleaning, equipping and readying the room?
The plan might have have designated and scheduled the cleaning to be performed, however the cleaning staff is currently working in another location and are unavailable for cleaning the specific room.
Crazy - we have two very expensive resources waiting for important yet cheaper staff.
Why aren't there enough cleaning staff?
Because the top down rule, that the ulcer stricken financial officer defined, is based on efficient planning and budgeting of resources. In this plan, it makes no logical sense hoarding on maintenance staff when we can fire them and save...
Thus, selecting the wrong top down planning, decision mechanism leads to an ineffective use of the hospital's expensive resources.
The depicted hospital scenario is quite common in many industries. Eli Goldratt, a physicist by education, claimed that we wrongly select the top down rules to manage our complex systems and to make decisions. Since the top down plan will fail, we won't be using the critical resources in our system optimally. He suggested an alternative top down rule which he presents in five books. The rule he devised is known as the theory of constraints, and in each book he applies it to different departments within a company. In each department the fundamental concept is to analyze the critical resource from the system perspective and utilize it optimally.
The theory of constraints top down problem-decision rule: always protect the most limited and expensive resource. Protect its time, utilization, and allocation.
In the hospital scenario, the top down rule would translate into constructing the plan around the surgery rooms and expert physicians, making sure that the cleaning staff is always ready before time, catering to the room.
The approach translates into a seemingly surplus of maintenance employees, at times wallowing around the corridors having an extra Latte, and contributing to the financial officer's ulcer. The alternative though is worse, unacceptable mediocre utilization of surgery rooms.
There have been many academic critics of Goldratt's approach. However, most demonstrated that his approach fails in extreme conditions. For most business purposes, Goldratt offers a straight forward, intuitive, top down constraining, problem-decision rule.
An alternative to Goldratt's rule in production environment and in project portfolio management can be to limit the overall time or products that are processed. In other words, limit the WIP - work in process.
How would that rule operate in project portfolio management?
The IT or software departments will only accept new project, when their total work in progress is below a certain threshold. The underlying mechanism is of Pull - new projects are pulled into a work status from a backlog waiting queue based on the total number of projects that are at present, concurrently managed.
The constant work in process is an easier to manage rule, however it is difficult to figure the threshold and to commit to it, without surrendering to requests from top management. More on that, later.
Select a resource constraining top down rule, instead of planning the entire system.
Visual problem presentation
‘If we don't see it it's not there'
We assess the world around us through our eyes.
‘A picture is worth 1000 words'
The fundamental principle is that we rather see a graphical representation rather than a list.
‘Seeing is believing'
Philosophically speaking visual presentations can lead sometimes to mistaken results, however more often they DO enable us to clearly see the overall problem.
Since we use our eyes as the tool to capture the world, it is crucial that we inspect and evaluate decision-problems in the same way.
Visual representations of decision-problems enable us to better grasp, the problem, assumptions, constraints, options and solutions.
Reflect for minutes on the traveling salesperson problem. It's much easier to explore a tangible map of 10, 15 or even 30 destinations and analyze possible routes, rather than assess the problem using a table or spreadsheet.
The same is true for production environments. It is easier to solve the complexity of production machine allocations, using visual signals such as Kanban boards and cards, rather than using a computer-generated paper output of production orders.
One of the challenges we've witnessed in managing multi projects in virtual global companies, is that we lacked the visual representation of the activities and projects allocated to resources and people.
Use any relevant tool to display the decision-problem visually.
For example: During a project at a petrochemical plant, we created a war room for the intense 4 months, construction stage. While we had a detailed Gantt chart with over 2000 entrees for specific activities of construction, it made more sense to create huge visual boards depicting daily tasks with resource and people allocated, to display overall allocations, possible collision points, impacts, deadlines, opportunities, and threats.
The strategic top-down rule has to be shown in the visual representation of the problem. Hence, it is not enough to portray the problem using a visual approach, it is also important to superimpose the strategic top-down rule on the visual presentation of the problem.
How can we illustrate the strategic top-down rule on the visual image?
- Using computers this would be done adding an extra layer on top of the decision problem.
- In our physical war room example this was actualized by different colors, stickers and other visual tools to depict the strategic decision rule visually.
- In production floors this would be achieved by adding physical signals, drawing signs and images around and in front strategic human operators, machines and other facilities within the production floor.
Create a visual representation of the complex decision-problem. Use visual methods to illustrate the top-down strategic decision rule
Two more rules:
- Realignments feedback mechanism
• Enforce consistency through publicity
Are presented in the best seller: D-side - practical decision making business Guide
You will also find there more about decision making, it is a a humoristic practical approach to understanding why decisions are so complex and what can be done about it
The cloud has transformed how we think about software quality. Instead of preventing failures, we must focus on automatic recovery from failure. In other words, resilience trumps traditional quality measures. Continuous delivery models further squeeze traditional notions of quality. Remember the venerable project management Iron Triangle? Among time, scope, and cost, you can only fix two or quality will suffer. Only in today's DevOps world, continuous testing, integration, and deployment upend...
Jul. 1, 2015 03:00 PM EDT Reads: 1,895
Discussions about cloud computing are evolving into discussions about enterprise IT in general. As enterprises increasingly migrate toward their own unique clouds, new issues such as the use of containers and microservices emerge to keep things interesting. In this Power Panel at 16th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the state of cloud computing today, and what enterprise IT professionals need to know about how the latest topics and trends affect t...
Jul. 1, 2015 02:30 PM EDT Reads: 1,148
Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Arch...
Jul. 1, 2015 02:21 PM EDT Reads: 390
Summer is finally here and it’s time for a DevOps summer vacation. From San Francisco to New York City, our top summer conferences list is going to continuously deliver you to the summer destinations of your dreams. These DevOps parties are hitting all the hottest summer trends with Microservices, Agile, Continuous Delivery, DevSecOps, and even Continuous Testing. Move over Kanye. These are the top 5 Summer DevOps Conferences of 2015.
Jul. 1, 2015 01:00 PM EDT Reads: 794
Sharding has become a popular means of achieving scalability in application architectures in which read/write data separation is not only possible, but desirable to achieve new heights of concurrency. The premise is that by splitting up read and write duties, it is possible to get better overall performance at the cost of a slight delay in consistency. That is, it takes a bit of time to replicate changes initiated by a "write" to the read-only master database. It's eventually consistent, and it'...
Jul. 1, 2015 12:00 PM EDT Reads: 1,701
"Plutora provides release and testing environment capabilities to the enterprise," explained Dalibor Siroky, Director and Co-founder of Plutora, in this SYS-CON.tv interview at @DevOpsSummit, held June 9-11, 2015, at the Javits Center in New York City.
Jul. 1, 2015 11:45 AM EDT Reads: 993
Containers are changing the security landscape for software development and deployment. As with any security solutions, security approaches that work for developers, operations personnel and security professionals is a requirement. In his session at DevOps Summit, Kevin Gilpin, CTO and Co-Founder of Conjur, will discuss various security considerations for container-based infrastructure and related DevOps workflows.
Jul. 1, 2015 10:30 AM EDT Reads: 768
Cloud Migration Management (CMM) refers to the best practices for planning and managing migration of IT systems from a legacy platform to a Cloud Provider through a combination professional services consulting and software tools. A Cloud migration project can be a relatively simple exercise, where applications are migrated ‘as is’, to gain benefits such as elastic capacity and utility pricing, but without making any changes to the application architecture, software development methods or busine...
Jul. 1, 2015 10:00 AM EDT Reads: 1,911
Data center models are changing. A variety of technical trends and business demands are forcing that change, most of them centered on the explosive growth of applications. That means, in turn, that the requirements for application delivery are changing. Certainly application delivery needs to be agile, not waterfall. It needs to deliver services in hours, not weeks or months. It needs to be more cost efficient. And more than anything else, it needs to be really, dc infra axisreally, super focus...
Jul. 1, 2015 10:00 AM EDT Reads: 1,967
The most often asked question post-DevOps introduction is: “How do I get started?” There’s plenty of information on why DevOps is valid and important, but many managers still struggle with simple basics for how to initiate a DevOps program in their business. They struggle with issues related to current organizational inertia, the lack of experience on Continuous Integration/Delivery, understanding where DevOps will affect revenue and budget, etc. In their session at DevOps Summit, JP Morgenthal...
Jul. 1, 2015 09:32 AM EDT Reads: 535
Overgrown applications have given way to modular applications, driven by the need to break larger problems into smaller problems. Similarly large monolithic development processes have been forced to be broken into smaller agile development cycles. Looking at trends in software development, microservices architectures meet the same demands. Additional benefits of microservices architectures are compartmentalization and a limited impact of service failure versus a complete software malfunction. ...
Jul. 1, 2015 09:00 AM EDT Reads: 844
Containers have changed the mind of IT in DevOps. They enable developers to work with dev, test, stage and production environments identically. Containers provide the right abstraction for microservices and many cloud platforms have integrated them into deployment pipelines. DevOps and Containers together help companies to achieve their business goals faster and more effectively. In his session at DevOps Summit, Ruslan Synytsky, CEO and Co-founder of Jelastic, reviewed the current landscape of...
Jun. 30, 2015 01:30 PM EDT Reads: 2,146
Conferences agendas. Event navigation. Specific tasks, like buying a house or getting a car loan. If you've installed an app for any of these things you've installed what's known as a "disposable mobile app" or DMA. Apps designed for a single use-case and with the expectation they'll be "thrown away" like brochures. Deleted until needed again. These apps are necessarily small, agile and highly volatile. Sometimes existing only for a short time - say to support an event like an election, the Wor...
Jun. 30, 2015 12:30 PM EDT Reads: 1,581
DevOps tends to focus on the relationship between Dev and Ops, putting an emphasis on the ops and application infrastructure. But that’s changing with microservices architectures. In her session at DevOps Summit, Lori MacVittie, Evangelist for F5 Networks, will focus on how microservices are changing the underlying architectures needed to scale, secure and deliver applications based on highly distributed (micro) services and why that means an expansion into “the network” for DevOps.
Jun. 30, 2015 08:30 AM EDT Reads: 2,421
Many people recognize DevOps as an enormous benefit – faster application deployment, automated toolchains, support of more granular updates, better cooperation across groups. However, less appreciated is the journey enterprise IT groups need to make to achieve this outcome. The plain fact is that established IT processes reflect a very different set of goals: stability, infrequent change, hands-on administration, and alignment with ITIL. So how does an enterprise IT organization implement change...
Jun. 29, 2015 12:45 PM EDT Reads: 2,803
While DevOps most critically and famously fosters collaboration, communication, and integration through cultural change, culture is more of an output than an input. In order to actively drive cultural evolution, organizations must make substantial organizational and process changes, and adopt new technologies, to encourage a DevOps culture. Moderated by Andi Mann, panelists discussed how to balance these three pillars of DevOps, where to focus attention (and resources), where organizations migh...
Jun. 28, 2015 05:00 PM EDT Reads: 2,039
At DevOps Summit NY there’s been a whole lot of talk about not just DevOps, but containers, IoT, and microservices. Sessions focused not just on the cultural shift needed to grow at scale with a DevOps approach, but also made sure to include the network ”plumbing” needed to ensure success as applications decompose into the microservice architectures enabling rapid growth and support for the Internet of (Every)Things.
Jun. 28, 2015 01:00 PM EDT Reads: 1,907
Mashape is bringing real-time analytics to microservices with the release of Mashape Analytics. First built internally to analyze the performance of more than 13,000 APIs served by the mashape.com marketplace, this new tool provides developers with robust visibility into their APIs and how they function within microservices. A purpose-built, open analytics platform designed specifically for APIs and microservices architectures, Mashape Analytics also lets developers and DevOps teams understand w...
Jun. 27, 2015 11:00 AM EDT Reads: 1,940
Buzzword alert: Microservices and IoT at a DevOps conference? What could possibly go wrong? In this Power Panel at DevOps Summit, moderated by Jason Bloomberg, the leading expert on architecting agility for the enterprise and president of Intellyx, panelists peeled away the buzz and discuss the important architectural principles behind implementing IoT solutions for the enterprise. As remote IoT devices and sensors become increasingly intelligent, they become part of our distributed cloud envir...
Jun. 26, 2015 12:00 PM EDT Reads: 2,241
Sumo Logic has announced comprehensive analytics capabilities for organizations embracing DevOps practices, microservices architectures and containers to build applications. As application architectures evolve toward microservices, containers continue to gain traction for providing the ideal environment to build, deploy and operate these applications across distributed systems. The volume and complexity of data generated by these environments make monitoring and troubleshooting an enormous chall...
Jun. 26, 2015 12:00 PM EDT Reads: 1,547