Welcome!

Microservices Expo Authors: John Worthington, Pat Romanski, Stackify Blog, Automic Blog, Simon Hill

Related Topics: Microservices Expo, Java IoT, Linux Containers, Containers Expo Blog, @DXWorldExpo, 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.

@MicroservicesExpo Stories
identify the sources of event storms and performance anomalies will require automated, real-time root-cause analysis. I think Enterprise Management Associates said it well: “The data and metrics collected at instrumentation points across the application ecosystem are essential to performance monitoring and root cause analysis. However, analytics capable of transforming data and metrics into an application-focused report or dashboards are what separates actual application monitoring from relat...
While some developers care passionately about how data centers and clouds are architected, for most, it is only the end result that matters. To the majority of companies, technology exists to solve a business problem, and only delivers value when it is solving that problem. 2017 brings the mainstream adoption of containers for production workloads. In his session at 21st Cloud Expo, Ben McCormack, VP of Operations at Evernote, discussed how data centers of the future will be managed, how the p...
DevOps teams have more on their plate than ever. As infrastructure needs grow, so does the time required to ensure that everything's running smoothly. This makes automation crucial - especially in the server and network monitoring world. Server monitoring tools can save teams time by automating server management and providing real-time performance updates. As budgets reset for the New Year, there is no better time to implement a new server monitoring tool (or re-evaluate your current solution)....
The benefits of automation are well documented; it increases productivity, cuts cost and minimizes errors. It eliminates repetitive manual tasks, freeing us up to be more innovative. By that logic, surely, we should automate everything possible, right? So, is attempting to automate everything a sensible - even feasible - goal? In a word: no. Consider this your short guide as to what to automate and what not to automate.
Cavirin Systems has just announced C2, a SaaS offering designed to bring continuous security assessment and remediation to hybrid environments, containers, and data centers. Cavirin C2 is deployed within Amazon Web Services (AWS) and features a flexible licensing model for easy scalability and clear pay-as-you-go pricing. Although native to AWS, it also supports assessment and remediation of virtual or container instances within Microsoft Azure, Google Cloud Platform (GCP), or on-premise. By dr...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Enterprises are adopting Kubernetes to accelerate the development and the delivery of cloud-native applications. However, sharing a Kubernetes cluster between members of the same team can be challenging. And, sharing clusters across multiple teams is even harder. Kubernetes offers several constructs to help implement segmentation and isolation. However, these primitives can be complex to understand and apply. As a result, it’s becoming common for enterprises to end up with several clusters. Thi...
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
The nature of test environments is inherently temporary—you set up an environment, run through an automated test suite, and then tear down the environment. If you can reduce the cycle time for this process down to hours or minutes, then you may be able to cut your test environment budgets considerably. The impact of cloud adoption on test environments is a valuable advancement in both cost savings and agility. The on-demand model takes advantage of public cloud APIs requiring only payment for t...
High-velocity engineering teams are applying not only continuous delivery processes, but also lessons in experimentation from established leaders like Amazon, Netflix, and Facebook. These companies have made experimentation a foundation for their release processes, allowing them to try out major feature releases and redesigns within smaller groups before making them broadly available. In his session at 21st Cloud Expo, Brian Lucas, Senior Staff Engineer at Optimizely, discussed how by using ne...
While we understand Agile as a means to accelerate innovation, manage uncertainty and cope with ambiguity, many are inclined to think that it conflicts with the objectives of traditional engineering projects, such as building a highway, skyscraper or power plant. These are plan-driven and predictive projects that seek to avoid any uncertainty. This type of thinking, however, is short-sighted. Agile approaches are valuable in controlling uncertainty because they constrain the complexity that ste...
"We're developing a software that is based on the cloud environment and we are providing those services to corporations and the general public," explained Seungmin Kim, CEO/CTO of SM Systems Inc., in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
"This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
"CA has been doing a lot of things in the area of DevOps. Now we have a complete set of tool sets in order to enable customers to go all the way from planning to development to testing down to release into the operations," explained Aruna Ravichandran, Vice President of Global Marketing and Strategy at CA Technologies, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
We just came off of a review of a product that handles both containers and virtual machines in the same interface. Under the covers, implementation of containers defaults to LXC, though recently Docker support was added. When reading online, or searching for information, increasingly we see “Container Management” products listed as competitors to Docker, when in reality things like Rocket, LXC/LXD, and Virtualization are Dockers competitors. After doing some looking around, we have decided tha...
Agile has finally jumped the technology shark, expanding outside the software world. Enterprises are now increasingly adopting Agile practices across their organizations in order to successfully navigate the disruptive waters that threaten to drown them. In our quest for establishing change as a core competency in our organizations, this business-centric notion of Agile is an essential component of Agile Digital Transformation. In the years since the publication of the Agile Manifesto, the conn...
"Codigm is based on the cloud and we are here to explore marketing opportunities in America. Our mission is to make an ecosystem of the SW environment that anyone can understand, learn, teach, and develop the SW on the cloud," explained Sung Tae Ryu, CEO of Codigm, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
Many enterprise and government IT organizations are realizing the benefits of cloud computing by extending IT delivery and management processes across private and public cloud services. But they are often challenged with balancing the need for centralized cloud governance without stifling user-driven innovation. This strategy requires an approach that fundamentally reshapes how IT is delivered today, shifting the focus from infrastructure to services aggregation, and mixing and matching the bes...