|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
Contrary to mainstream media attention, the multiple possibilities of how consumer IoT will transform our everyday lives aren’t the only angle of this headline-gaining trend. There’s a huge opportunity for “industrial IoT” and “Smart Cities” to impact the world in the same capacity – especially during critical situations. For example, a community water dam that needs to release water can leverage embedded critical communications logic to alert the appropriate individuals, on the right device, as...
Sep. 1, 2015 09:00 AM EDT
U.S. companies are desperately trying to recruit and hire skilled software engineers and developers, but there is simply not enough quality talent to go around. Tiempo Development is a nearshore software development company. Our headquarters are in AZ, but we are a pioneer and leader in outsourcing to Mexico, based on our three software development centers there. We have a proven process and we are experts at providing our customers with powerful solutions. We transform ideas into reality.
Sep. 1, 2015 08:45 AM EDT Reads: 549
The web app is agile. The REST API is agile. The testing and planning are agile. But alas, data infrastructures certainly are not. Once an application matures, changing the shape or indexing scheme of data often forces at best a top down planning exercise and at worst includes schema changes that force downtime. The time has come for a new approach that fundamentally advances the agility of distributed data infrastructures. Come learn about a new solution to the problems faced by software organ...
Sep. 1, 2015 08:30 AM EDT
SYS-CON Events announced today the Containers & Microservices Bootcamp, being held November 3-4, 2015, in conjunction with 17th Cloud Expo, @ThingsExpo, and @DevOpsSummit at the Santa Clara Convention Center in Santa Clara, CA. This is your chance to get started with the latest technology in the industry. Combined with real-world scenarios and use cases, the Containers and Microservices Bootcamp, led by Janakiram MSV, a Microsoft Regional Director, will include presentations as well as hands-on...
Sep. 1, 2015 08:15 AM EDT Reads: 354
With the Apple Watch making its way onto wrists all over the world, it’s only a matter of time before it becomes a staple in the workplace. In fact, Forrester reported that 68 percent of technology and business decision-makers characterize wearables as a top priority for 2015. Recognizing their business value early on, FinancialForce.com was the first to bring ERP to wearables, helping streamline communication across front and back office functions. In his session at @ThingsExpo, Kevin Roberts...
Sep. 1, 2015 08:00 AM EDT
While many app developers are comfortable building apps for the smartphone, there is a whole new world out there. In his session at @ThingsExpo, Narayan Sainaney, Co-founder and CTO of Mojio, will discuss how the business case for connected car apps is growing and, with open platform companies having already done the heavy lifting, there really is no barrier to entry.
Sep. 1, 2015 08:00 AM EDT Reads: 145
As more intelligent IoT applications shift into gear, they’re merging into the ever-increasing traffic flow of the Internet. It won’t be long before we experience bottlenecks, as IoT traffic peaks during rush hours. Organizations that are unprepared will find themselves by the side of the road unable to cross back into the fast lane. As billions of new devices begin to communicate and exchange data – will your infrastructure be scalable enough to handle this new interconnected world?
Sep. 1, 2015 08:00 AM EDT Reads: 166
WebRTC has had a real tough three or four years, and so have those working with it. Only a few short years ago, the development world were excited about WebRTC and proclaiming how awesome it was. You might have played with the technology a couple of years ago, only to find the extra infrastructure requirements were painful to implement and poorly documented. This probably left a bitter taste in your mouth, especially when things went wrong.
Sep. 1, 2015 03:00 AM EDT Reads: 463
Skeuomorphism usually means retaining existing design cues in something new that doesn’t actually need them. However, the concept of skeuomorphism can be thought of as relating more broadly to applying existing patterns to new technologies that, in fact, cry out for new approaches. In his session at DevOps Summit, Gordon Haff, Senior Cloud Strategy Marketing and Evangelism Manager at Red Hat, discussed why containers should be paired with new architectural practices such as microservices rathe...
Sep. 1, 2015 01:00 AM EDT Reads: 409
SYS-CON Events announced today that G2G3 will exhibit at SYS-CON's @DevOpsSummit Silicon Valley, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Based on a collective appreciation for user experience, design, and technology, G2G3 is uniquely qualified and motivated to redefine how organizations and people engage in an increasingly digital world.
Aug. 31, 2015 11:00 PM EDT Reads: 502
Any Ops team trying to support a company in today’s cloud-connected world knows that a new way of thinking is required – one just as dramatic than the shift from Ops to DevOps. The diversity of modern operations requires teams to focus their impact on breadth vs. depth. In his session at DevOps Summit, Adam Serediuk, Director of Operations at xMatters, Inc., will discuss the strategic requirements of evolving from Ops to DevOps, and why modern Operations has begun leveraging the “NoOps” approa...
Aug. 31, 2015 10:30 PM EDT Reads: 404
Too often with compelling new technologies market participants become overly enamored with that attractiveness of the technology and neglect underlying business drivers. This tendency, what some call the “newest shiny object syndrome,” is understandable given that virtually all of us are heavily engaged in technology. But it is also mistaken. Without concrete business cases driving its deployment, IoT, like many other technologies before it, will fade into obscurity.
Aug. 31, 2015 09:00 PM EDT Reads: 372
Organizations from small to large are increasingly adopting cloud solutions to deliver essential business services at a much lower cost. According to cyber security experts, the frequency and severity of cyber-attacks are on the rise, causing alarm to businesses and customers across a variety of industries. To defend against exploits like these, a company must adopt a comprehensive security defense strategy that is designed for their business. In 2015, organizations such as United Airlines, Sony...
Aug. 31, 2015 07:15 PM EDT Reads: 486
The Internet of Things is in the early stages of mainstream deployment but it promises to unlock value and rapidly transform how organizations manage, operationalize, and monetize their assets. IoT is a complex structure of hardware, sensors, applications, analytics and devices that need to be able to communicate geographically and across all functions. Once the data is collected from numerous endpoints, the challenge then becomes converting it into actionable insight.
Aug. 31, 2015 07:00 PM EDT
Puppet Labs has announced the next major update to its flagship product: Puppet Enterprise 2015.2. This release includes new features providing DevOps teams with clarity, simplicity and additional management capabilities, including an all-new user interface, an interactive graph for visualizing infrastructure code, a new unified agent and broader infrastructure support.
Aug. 31, 2015 06:30 PM EDT Reads: 523