• Skip to main content
  • Skip to primary sidebar

This view of service management...

On the origin and the descent of managing services. We put meat on the bones.

  • Kanban Software
  • Services
    • Kanban Software Solutions
    • Consulting & Coaching
    • Training and Seminars
  • Posts
  • Events
    • Events – Agenda View
    • Events – Calendar View
  • Publications
    • Our Publications
    • Notable Publications
    • Quotes
  • About us

A Manifesto for Service Management Agility—Summary

24 November 2017 by Robert Falkowitz 3 Comments

Over the past few months I have analyzed the propo­sitions of the Manifesto for Agile Software Development in the context of the issues specific to service management. On this basis, I have proposed revised propositions intended to address the question of agility in service management and have added a fifth proposition. These new propositions constitute a pro­posed Manifesto for Service Management Agility.

Agile Software Development

Individuals and interactions over processes and tools

Working software over comprehensive documentation

Customer collaboration over contract negotiation

Responding to change over following a plan

Service Management Agility

Emotional intelligence over too detailed processes

Services fit for purpose and for use over meeting specifications

Flexible engagement over fixed agreements

Planning for change over following a plan

Distributed decision-making authority over immediate reduction in direct costs

Of what use is such a manifesto?

Why bother? Agility is an old story already, even if many organizations remain sclerotic. I have several reasons for wanting to reinvigorate the subject, even if I am not teaching old dogs any new tricks.

Support achieving the goals of service management agility

Agility is not a goal in and of itself. It is merely a means for achieving the goals of good management of services. First and foremost, a clearly arti­culated manifesto would sup­port achieving those goals.

Make it clear what we mean by "service management agility"

The whole purpose of a manifesto is obviously to make manifest certain ideas, beliefs, values and informa­tion. This has been true for the Com­munist Manifesto, the Futurist Mani­festo (how­ever obscure its language might be) and the Manifesto for Agile Software Deve­lop­ment. The problem is that terms tend to gain new layers of meaning and lose original meanings very rapidly. For example, a very large number of people really mean “scrum” when they say “agile”. Although such hi­jack­ing of terms is in­evit­able, we try to maintain a semantic center by clearly defining concepts in a manifesto.

Make it easy for practitioners to recall principles and values

It is unlikely that most service management practitioners will read extensively about agility. Nor are they likely to undergo any specific training in an agile method. But, if there is a very short list of easily learned principles, it could help guide those practitioners in making de­ci­sions that support the goals of agility.

Define a framework for further analysis and improvement

Any approach to agility must be…well…agile. This means that the principles and values that support the goals fac­ili­tated by agility will them­selves need to evolve. That evolution may be eased if a set of talking points has first been articulated. Where are the issues in service man­age­ment that are par­ticu­larly influenced by agility?

Is this manifesto useful outside of service management?

I won’t pretend to know the answer to this question. That’s up to the practitioners in other domains to decide. My series of articles analyzing the Manifesto for Agile Software Development was not at all meant to be a critique of agility in software development. That domain has its own issues, addressed by its own manifesto. That being said, agility in work in general—and es­pecially in knowledge work—is probably manifested in very similar ways, no matter what the specific domain of the work.

How do the propositions fit together?

Many of the propositions are obviously talking about the same issues, but taken from different perspectives. They are closely related and reinforce each other. I have cross-referenced in the de­tailed analyses the points where these relationships are most per­tinent. Rather than being an orthogonal taxonomy, the propo­si­tions are more like a pentahedron or a pentagonal hosohedron, re­pre­senting five facets of a single whole.

In addition, my particular choice of wording has been strongly influenced by the principles arti­culated in the lean and kanban world. Anyone familiar with David Anderson’s foun­dational principles and core properties of “Kanban” will readily recognize how they have influenced me. But more important than that intellectual debt is the demon­stration of the close fit between kanban and good service manage­ment. In other words, if you agree that agility is a good means for helping to achieve the goals of your services, then you might be asking yourself, “How can we be agile in our day to day work?” Kanban is an excellent way of operating your services to imp­lement your agile approach.

What's next?

I welcome the collaboration of anyone who shares my belief that there is value in articulating and agreeing on such a manifesto. All the propositions can certainly be improved. You may get in touch with me via the form below.

    *Name:

    *Email:

    Your remarks:


    Your details will not be communicated to any third parties without your express permission.

    Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License The article A Manifesto for Service Management Agility—Summary by Robert S. Falkowitz, including all its contents, is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

    Summary
    Manifesto for Service Management Agility—Summary
    Article Name
    Manifesto for Service Management Agility—Summary
    Description
    The Agile Manifesto was originally written for software development. What would a Manifesto for Service Management Agility be?
    Author
    Robert S. Falkowitz
    Publisher Name
    Concentric Circle Consulting
    Publisher Logo
    Concentric Circle Consulting

    Filed Under: Agility, Service Management Tagged With: agile, manifesto, manifesto for software development, rigidity

    Subscribe to our mailing list

    Click here to be the first to learn of our events and publications
    • Email
    • Facebook
    • LinkedIn
    • Phone
    • Twitter
    • xing
    • YouTube

    Reader Interactions

    Comments

    1. Bob GrinsellBob Grinsell says

      22 December 2017 at 17:46

      These have been an enjoyable read, and provide some good ideas for improving how we deliver services and interact with our customers.

      Overall, you could summarize this into “Flexibility over Rigidity,” or “Adaptability over Conformity.”

      Processes are still important, and in many ways critical, to success. But people have to be allowed to respond to a given situation that falls outside the scope of the process definition.

      Reply
      • Robert FalkowitzRobert Falkowitz says

        22 December 2017 at 18:00

        Well, its both, don’t you think?

        Reply

    Trackbacks

    1. How Does Kanban Support Service Management Agility? | Kanbanize Blog says:
      26 February 2018 at 15:21

      […] I have proposed a Manifesto for Service Management Agility, describing what agility in managing services would be. Kanban is well known as a method for agile […]

      Reply

    Leave a Reply Cancel reply

    Your email address will not be published. Required fields are marked *

    This site uses Akismet to reduce spam. Learn how your comment data is processed.

    Primary Sidebar

    Kanban eLearning

    Kanban training online

    Recent Posts

    • Verbs, nouns and kanban board structure
    • The role of the problem manager
    • The Three Indicators

    Tag Cloud

    process metrics lean management agile change management kanban resource liquidity knowledge management flow service manager flow efficiency context switching impact kanban training service request waste rigidity service management tools ITSM Incident Management lean manifesto problem urgency process ITIL bias histogram Cost of Delay priority incident incident management tools value stream process definition manifesto for software development statistical control chart cause knowledge work risk kanban board automation
    • Kanban Software
    • Services
    • Posts
    • Events
    • Publications
    • Subscribe
    • Rights & Duties
    • Personal Data

    © 2014–2023 Concentric Circle Consulting · All Rights Reserved.
    Concentric Circle Consulting Address
    Log in

    Manage Cookie Consent
    We use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
    Functional Always active
    The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
    Preferences
    The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
    Statistics
    The technical storage or access that is used exclusively for statistical purposes. The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
    Marketing
    The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
    Manage options Manage services Manage vendors Read more about these purposes
    View preferences
    {title} {title} {title}