Click here to close now.

Welcome!

MICROSERVICES Authors: John Wetherill, Elizabeth White, Liz McMillan, Brian Vandegrift, XebiaLabs Blog

Related Topics: MICROSERVICES, Java, Linux, Virtualization, Big Data Journal, SDN Journal

MICROSERVICES: 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
It's 2:15pm on a Friday, and I'm sitting in the keynote hall at PyCon 2013 fidgeting through a succession of lightning talks that have very little relevance to my life. Topics like "Python code coverage techniques" (ho-hum) and "Controlling Christmas lights with Python” (yawn - I wonder if there's anything new on Hacker News)...when Solomon Hykes takes the stage, unveils Docker, and the world shifts. If you haven't seen it yet, you should watch the video of Solomon's Pycon The Future of Linux C...
OmniTI has expanded its services to help customers automate their processes to deliver high quality applications to market faster. Consistent with its focus on IT agility and quality, OmniTI operates under DevOps principles, exploring the flow of value through the IT delivery process, identifying opportunities to eliminate waste, realign misaligned incentives, and open bottlenecks. OmniTI takes a unique, value-centric approach by plotting each opportunity in an effort-payoff quadrant, then work...
SYS-CON Events announced today that MangoApps will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY., and the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. MangoApps provides private all-in-one social intranets allowing workers to securely collaborate from anywhere in the world and from any device. Social, mobile, and eas...
SYS-CON Events announced today that Solgenia will exhibit at SYS-CON's 16th International Cloud Expo®, which will take place on June 9-11, 2015, at the Javits Center in New York City, NY, and the 17th International Cloud Expo®, which will take place on November 3–5, 2015, at the Santa Clara Convention Center in Santa Clara, CA. Solgenia is the global market leader in Cloud Collaboration and Cloud Infrastructure software solutions. Designed to “Bridge the Gap” between Personal and Professional S...
When it comes to microservices there are myths and uncertainty about the journey ahead. Deploying a “Hello World” app on Docker is a long way from making microservices work in real enterprises with large applications, complex environments and existing organizational structures. February 19, 2015 10:00am PT / 1:00pm ET → 45 Minutes Join our four experts: Special host Gene Kim, Gary Gruver, Randy Shoup and XebiaLabs’ Andrew Phillips as they explore the realities of microservices in today’s IT worl...
This month I want to revisit supporting infrastructure and datacenter environments. I have touched (some would say rant) upon this topic since my post in April 2014 called "Take a Holistic View of Support". My thoughts and views on this topic have not changed at all: it's critical for any organization to have a holistic, comprehensive strategy and view of how they support their IT infrastructure and datacenter environments. In fact, I believe it's even more critical today then it was a year ago ...
The world's leading Cloud event, Cloud Expo has launched Microservices Journal on the SYS-CON.com portal, featuring over 19,000 original articles, news stories, features, and blog entries. DevOps Journal is focused on this critical enterprise IT topic in the world of cloud computing. Microservices Journal offers top articles, news stories, and blog posts from the world's well-known experts and guarantees better exposure for its authors than any other publication. Follow new article posts on T...
Hosted PaaS providers have given independent developers and startups huge advantages in efficiency and reduced time-to-market over their more process-bound counterparts in enterprises. Software frameworks are now available that allow enterprise IT departments to provide these same advantages for developers in their own organization. In his workshop session at DevOps Summit, Troy Topnik, ActiveState’s Technical Product Manager, will show how on-prem or cloud-hosted Private PaaS can enable organ...
Cloud computing is changing the way we look at IT costs, according to industry experts on a recent Cloud Luminary Fireside Chat panel discussion. Enterprise IT, traditionally viewed as a cost center, now plays a central role in the delivery of software-driven goods and services. Therefore, companies need to understand their cloud utilization and resulting costs in order to ensure profitability on their business offerings. Led by Bernard Golden, this fireside chat offers valuable insights on ho...
Microservice architectures are the new hotness, even though they aren't really all that different (in principle) from the paradigm described by SOA (which is dead, or not dead, depending on whom you ask). One of the things this decompositional approach to application architecture does is encourage developers and operations (some might even say DevOps) to re-evaluate scaling strategies. In particular, the notion is forwarded that an application should be built to scale and then infrastructure sho...
SYS-CON Events announced today the IoT Bootcamp – Jumpstart Your IoT Strategy, being held June 9–10, 2015, in conjunction with 16th Cloud Expo and Internet of @ThingsExpo at the Javits Center in New York City. This is your chance to jumpstart your IoT strategy. Combined with real-world scenarios and use cases, the IoT Bootcamp is not just based on presentations but includes hands-on demos and walkthroughs. We will introduce you to a variety of Do-It-Yourself IoT platforms including Arduino, Ras...
Even though it’s now Microservices Journal, long-time fans of SOA World Magazine can take comfort in the fact that the URL – soa.sys-con.com – remains unchanged. And that’s no mistake, as microservices are really nothing more than a new and improved take on the Service-Oriented Architecture (SOA) best practices we struggled to hammer out over the last decade. Skeptics, however, might say that this change is nothing more than an exercise in buzzword-hopping. SOA is passé, and now that people are ...
Microservices are the result of decomposing applications. That may sound a lot like SOA, but SOA was based on an object-oriented (noun) premise; that is, services were built around an object - like a customer - with all the necessary operations (functions) that go along with it. SOA was also founded on a variety of standards (most of them coming out of OASIS) like SOAP, WSDL, XML and UDDI. Microservices have no standards (at least none deriving from a standards body or organization) and can be b...
Right off the bat, Newman advises that we should "think of microservices as a specific approach for SOA in the same way that XP or Scrum are specific approaches for Agile Software development". These analogies are very interesting because my expectation was that microservices is a pattern. So I might infer that microservices is a set of process techniques as opposed to an architectural approach. Yet in the book, Newman clearly includes some elements of concept model and architecture as well as p...
You hear the terms “subscription economy” and “subscription commerce” all the time. And with good reason. Subscription-based monetization is transforming business as we know it. But what about usage? Where’s the “consumption economy”? Turns out, it’s all around us. When most people think of usage-based billing, the example that probably comes to mind first is metered public utilities — water, gas and electric. Phone services, especially mobile, might come next. Then maybe taxis. And that’s ab...
SYS-CON Events announced today the DevOps Foundation Certification Course, being held June ?, 2015, in conjunction with DevOps Summit and 16th Cloud Expo at the Javits Center in New York City, NY. This sixteen (16) hour course provides an introduction to DevOps – the cultural and professional movement that stresses communication, collaboration, integration and automation in order to improve the flow of work between software developers and IT operations professionals. Improved workflows will res...
As a group of concepts, DevOps has converged on several prominent themes including continuous software delivery, automation, and configuration management (CM). These integral pieces often form the pillars of an organization’s DevOps efforts, even as other bigger pieces like overarching best practices and guidelines are still being tried and tested. Being that DevOps is a relatively new paradigm - movement - methodology - [insert your own label here], standards around it have yet to be codified a...
Microservices, for the uninitiated, are essentially the decomposition of applications into multiple services. This decomposition is often based on functional lines, with related functions being grouped together into a service. While this may sound a like SOA, it really isn't, especially given that SOA was an object-centered methodology that focused on creating services around "nouns" like customer and product. Microservices, while certainly capable of being noun-based, are just as likely to be v...
Containers and microservices have become topics of intense interest throughout the cloud developer and enterprise IT communities. Accordingly, attendees at the upcoming 16th Cloud Expo at the Javits Center in New York June 9-11 will find fresh new content in a new track called PaaS | Containers & Microservices Containers are not being considered for the first time by the cloud community, but a current era of re-consideration has pushed them to the top of the cloud agenda. With the launch ...
An explosive combination of technology trends will be where ‘microservices’ and the IoT Internet of Things intersect, a concept we can describe by comparing it with a previous theme, the ‘X Internet.' The idea of using small self-contained application components has been popular since XML Web services began and a distributed computing future of smart fridges and kettles was imagined long back in the early Internet years.