Welcome!

Related Topics: Microservices Expo, Java IoT, Linux Containers, Containers Expo Blog, @BigDataExpo, SDN Journal

Microservices Expo: Article

Agile 101 - Three Practical Guidelines for Business Decisions

A humorous and practical approach to understanding why decisions are so complex

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

Such as:

  • 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

 

More Stories By Michael Nir

Michael Nir - President of Sapir Consulting - (M.Sc. Engineering) has been providing operational, organizational and management consulting and training for over 15 years. He is passionate about Gestalt theory and practice, which complements his engineering background and contributes to his understanding of individual and team dynamics in business. Michael authored 8 Bestsellers in the fields of Influencing, Agile, Teams, Leadership and others. Michael's experience includes significant expertise in the telecoms, hi-tech, software development, R&D environments and petrochemical & infrastructure industries. He develops creative and innovative solutions in project and product management, process improvement, leadership, and team building programs. Michael's professional background is analytical and technical; however, he has a keen interest in human interactions and behaviors. He holds two engineering degrees from the prestigious Technion Institute of Technology: a Bachelor of civil engineering and Masters of Industrial engineering. He has balanced his technical side with the extensive study and practice of Gestalt Therapy and "Instrumental Enrichment," a philosophy of mediated learning. In his consulting and training engagements, Michael combines both the analytical and technical world with his focus on people, delivering unique and meaningful solutions, and addressing whole systems.

Latest Stories
Identity is in everything and customers are looking to their providers to ensure the security of their identities, transactions and data. With the increased reliance on cloud-based services, service providers must build security and trust into their offerings, adding value to customers and improving the user experience. Making identity, security and privacy easy for customers provides a unique advantage over the competition.
SYS-CON Events announced today that Venafi, the Immune System for the Internet™ and the leading provider of Next Generation Trust Protection, will exhibit at @DevOpsSummit at 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. Venafi is the Immune System for the Internet™ that protects the foundation of all cybersecurity – cryptographic keys and digital certificates – so they can’t be misused by bad guys in attacks...
Whether your IoT service is connecting cars, homes, appliances, wearable, cameras or other devices, one question hangs in the balance – how do you actually make money from this service? The ability to turn your IoT service into profit requires the ability to create a monetization strategy that is flexible, scalable and working for you in real-time. It must be a transparent, smoothly implemented strategy that all stakeholders – from customers to the board – will be able to understand and comprehe...
"Tintri was started in 2008 with the express purpose of building a storage appliance that is ideal for virtualized environments. We support a lot of different hypervisor platforms from VMware to OpenStack to Hyper-V," explained Dan Florea, Director of Product Management at Tintri, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
"There's a growing demand from users for things to be faster. When you think about all the transactions or interactions users will have with your product and everything that is between those transactions and interactions - what drives us at Catchpoint Systems is the idea to measure that and to analyze it," explained Leo Vasiliou, Director of Web Performance Engineering at Catchpoint Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York Ci...
"Avere Systems is a hybrid cloud solution provider. We have customers that want to use cloud storage and we have customers that want to take advantage of cloud compute," explained Rebecca Thompson, VP of Marketing at Avere Systems, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
SaaS companies can greatly expand revenue potential by pushing beyond their own borders. The challenge is how to do this without degrading service quality. In his session at 18th Cloud Expo, Adam Rogers, Managing Director at Anexia, discussed how IaaS providers with a global presence and both virtual and dedicated infrastructure can help companies expand their service footprint with low “go-to-market” costs.
For basic one-to-one voice or video calling solutions, WebRTC has proven to be a very powerful technology. Although WebRTC’s core functionality is to provide secure, real-time p2p media streaming, leveraging native platform features and server-side components brings up new communication capabilities for web and native mobile applications, allowing for advanced multi-user use cases such as video broadcasting, conferencing, and media recording.
IoT generates lots of temporal data. But how do you unlock its value? You need to discover patterns that are repeatable in vast quantities of data, understand their meaning, and implement scalable monitoring across multiple data streams in order to monetize the discoveries and insights. Motif discovery and deep learning platforms are emerging to visualize sensor data, to search for patterns and to build application that can monitor real time streams efficiently. In his session at @ThingsExpo, ...
Ovum, a leading technology analyst firm, has published an in-depth report, Ovum Decision Matrix: Selecting a DevOps Release Management Solution, 2016–17. The report focuses on the automation aspects of DevOps, Release Management and compares solutions from the leading vendors.
"This week we're really focusing on scalability, asset preservation and how do you back up to the cloud and in the cloud with object storage, which is really a new way of attacking dealing with your file, your blocked data, where you put it and how you access it," stated Jeff Greenwald, Senior Director of Market Development at HGST, in this SYS-CON.tv interview at 18th Cloud Expo, held June 7-9, 2016, at the Javits Center in New York City, NY.
When it comes to cloud computing, the ability to turn massive amounts of compute cores on and off on demand sounds attractive to IT staff, who need to manage peaks and valleys in user activity. With cloud bursting, the majority of the data can stay on premises while tapping into compute from public cloud providers, reducing risk and minimizing need to move large files. In his session at 18th Cloud Expo, Scott Jeschonek, Director of Product Management at Avere Systems, discussed the IT and busin...
There will be new vendors providing applications, middleware, and connected devices to support the thriving IoT ecosystem. This essentially means that electronic device manufacturers will also be in the software business. Many will be new to building embedded software or robust software. This creates an increased importance on software quality, particularly within the Industrial Internet of Things where business-critical applications are becoming dependent on products controlled by software. Qua...
Continuous testing helps bridge the gap between developing quickly and maintaining high quality products. But to implement continuous testing, CTOs must take a strategic approach to building a testing infrastructure and toolset that empowers their team to move fast. Download our guide to laying the groundwork for a scalable continuous testing strategy.
As companies gain momentum, the need to maintain high quality products can outstrip their development team’s bandwidth for QA. Building out a large QA team (whether in-house or outsourced) can slow down development and significantly increases costs. This eBook takes QA profiles from 5 companies who successfully scaled up production without building a large QA team and includes: What to consider when choosing CI/CD tools How culture and communication can make or break implementation