{"id":1527,"date":"2009-02-02T14:04:39","date_gmt":"2009-02-02T19:04:39","guid":{"rendered":"http:\/\/dougmcclure.net\/blog\/?p=1527"},"modified":"2009-02-02T14:04:39","modified_gmt":"2009-02-02T19:04:39","slug":"realizing-a-bsm-solution-implementation-perspective","status":"publish","type":"post","link":"https:\/\/dougmcclure.net\/blog\/2009\/02\/realizing-a-bsm-solution-implementation-perspective\/","title":{"rendered":"Realizing A BSM Solution: Implementation Perspective"},"content":{"rendered":"

Realizing a BSM solution is a complex task and has a lot of challenges involved which are not just technology related but also related to process, organization, cultural and expectations.\u00a0Lack of standardization of the process for implementing BSM is a major factor resulting in failures and unmet expectations. Most companies planning\/currently trying to implement BSM have enough tools to implement the solution. But the vendors trying to sell there solutions do not realize that with no standard tools for designing BSM views, the challenge is in a totally different dimension.<\/em><\/p>\n

In this article, my focus is on principles\/implementation guidelines for realizing a BSM solution leveraging the existing tools which are accepted by the organization. Following are few \u2018Mantras\u2019 that if practiced with discipline, provide successful, accurate and adaptable BSM solution that more than a handful of executives can look forward to. (After all BSM is not just about executives, it\u2019s also for a line manager and the engineer who \u2018makes things happen\u2019 on the ground).\u00a0So without further ado here are the principles\/implementation guidelines:<\/span><\/p>\n

    \n
  1. \u00a0<\/span><\/span><\/span>Know Your Business Drivers<\/strong><\/span><\/li>\n<\/ol>\n

    Before knowing the underlying Business drivers, you are not going to get anywhere. When documenting what is to be done (requirement analysis), try to know the underlying motives for the solution? <\/span><\/p>\n

      \n
    • Is the sponsor\/s looking at using it as a Governance solution for enterprise\/line of business which does not have tangible assets (Like applications) to manage?<\/li>\n
    • Is the sponsor\/s looking for this solution primarily for SLA or regulatory reasons?<\/span><\/li>\n
    • Is the sponsor\/s looking for this solution to analyze the resource utilization and strategic growth planning?<\/span><\/span><\/li>\n
    • Is the sponsor\/s looking for reducing failures, restoration times, problem isolation ?<\/span><\/span><\/li>\n<\/ul>\n

      Know your Business Drivers and document them with priorities<\/em>, this will allow you to gain authority on what value proposition needs to be created for verifying the success.\u00a0Most often the client stakeholders of BSM expect some working solution as soon as possible. Set the expectations!!\u00a0<\/span><\/p>\n

      \u00a0\u00a0 \u00a0 \u00a02. \u00a0\u00a0<\/strong><\/span><\/span><\/span>Know the end goal before starting implementation<\/strong><\/span><\/p>\n

      I am a big believer of Agile Business sustenance theory (only those who are swift to adapt sustain, rest die!!), but WE should not\u00a0panic to deliver working solution increment in first 6-10 weeks (depending on the size of the solution).\u00a0 <\/span>Ensure all crucial aspects like Drivers, Value, Stakeholder Categories, Stakeholder concerns, Quality requirements, Commonality\/variability factors and <\/em>\u00a0<\/em><\/span>Business\/Service\/Engineering views are documented well enough for you to feel comfortable on what needs to be done.<\/em><\/span><\/p>\n

      (Important Tip<\/em>: Use SEI standard documentation templates for documenting your solution, this will ensure complete coverage of information required. Yes it is exhaustive, but necessary. )<\/span><\/p>\n

      \u00a0\u00a0 \u00a0 \u00a03. \u00a0<\/strong><\/span><\/span><\/span>Use mind mapping technique to build view design <\/strong><\/span><\/p>\n

      Not many simple, easy to use tools exist for view designing for a BSM solution. In past I have seen\u00a0\u00a0consultants from\u00a0the \u2018big 4\u2019 companies struggling\u00a0with views\u00a0(or what they called\u00a0\u00a0designing) on office tools while customers were speeding along on their talk and thoughts. This makes me wonder, Why do the BSM vendors completely ignore BSM design tools even with no major offerings in market space?<\/span><\/p>\n

      I have experienced that mind maps really works for designing BSM views as they are easily available and synchronize very well the business thoughts\/flow. What is even more appealing about mind maps is that they very often need no refinement before your view is complete after a meeting\/discussion with stakeholders. Benefit of using mind maps are instant feedback, increased speed and velocity. (Doing this will make design and development very agile)<\/span><\/p>\n

      \u00a0\u00a0 \u00a0 \u00a04. \u00a0 Ubiquitous language<\/strong><\/span><\/p>\n

      If you are not aware of Domain driven design concepts and you are into BSM, you are ignorant of a very powerful technique to bump up effectiveness in solving the business problem.<\/em> Forming a common set of terminologies based on domain will get you through the design phase with accuracy, precision and facilitate a disciplined approach. Form a set of common domain language and use it. This really helps, especially brings precision to your Key Business\/Quality\/Performance indicators.\u00a0<\/span><\/p>\n

      \u00a0\u00a0 \u00a05. \u00a0Start small and simple, BIG BANG DOESN\u2019T WORK<\/strong><\/span><\/p>\n

      Take a meaningful Business driver, analyze and discover resources (infrastructure, network, applications) and show value in an end-to-end scenario, this will draw interest, attention and more resources to accomplish further\u00a0value. It will also provide an opportunity to get immediate feedback and agility.<\/span><\/p>\n

      \u00a0\u00a0 6. \u00a0<\/strong><\/span><\/span><\/span>Leverage existing application (this might get me shot!!)<\/strong><\/span><\/p>\n

      My principle is that if you have a culture of using tools from a vendor, stick to them unless they do not meet expectations. BSM is not about redefining tool set!!<\/span><\/p>\n

      \u00a0\u00a0 \u00a0 7. \u00a0<\/strong><\/span><\/span><\/span>Tiered approach is better than professing \u2018Enterprise\u2019 Approach<\/strong><\/span><\/p>\n

      Don\u2019t fall in the \u2018Alignment Trap\u2019, although standardization is important, don\u2019t pressurize teams to use the same fancy dashboard which are recommended by enterprise groups, instead try to leverage what they already have and fill the gap of information they need for what is important to them to expand and retain their business value.\u00a0<\/span><\/p>\n

      \u00a0\u00a0 \u00a08. \u00a0\u00a0<\/strong><\/span><\/span><\/span>Don\u2019t forget to check on traceability<\/strong><\/span><\/p>\n

      Tracing to-and-fro from the solution to Business objectives is an important exercise that should be practiced periodically; make sure you have set aside an hour every fortnight for this. It is very easy to get side-tracked with information from multiple silos (often time single silo can also be enough to loose focus).<\/span><\/p>\n

      \u00a0\u00a0 \u00a0 9. \u00a0\u00a0<\/strong><\/span><\/span><\/span>And finally, \u201cOrganizational Value\u201d cannot be achieved off the shelf<\/strong><\/span><\/p>\n

      There is nothing like \u20188 hours to BSM\u2019. Don\u2019t entertain phony sales presentations and save your customers some money, ensure you and BSM stakeholders focus on value and not tools. WE should not forget the fact that BSM is not only about building a solution, it is also about ensuring quality, ease of access, aggregation of right level of information and\u00a0encapsulation (information hiding) based on stakeholders.<\/span><\/p>\n

      This post provides a brief insight into each of the principles that i have experienced to be successful while ‘working on the ground’; if you would want to know more on this or provide your feedback, please leave a comment or get in touch!! In the next post, I will share insights on attributes of a successful BSM implementation.<\/p>\n","protected":false},"excerpt":{"rendered":"

      Realizing a BSM solution is a complex task and has a lot of challenges involved which are not just technology related but also related to process, organization, cultural and expectations.\u00a0Lack of standardization of the process for implementing BSM is a major factor resulting in failures and unmet expectations. Most companies planning\/currently trying to implement BSM […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[116,704,76,709,424,24,61,460,1,92],"tags":[735,989,731,730,939,215,555,733,728,732,729,264],"class_list":{"0":"post-1527","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-bsm","7":"category-bsm-lite","8":"category-bsm-solution-analysis","9":"category-bsm-strategy-bsm","10":"category-guest-authors","11":"category-service-assurance","12":"category-service-monitoring","13":"category-service-quality-management","14":"category-uncategorized","15":"category-value","16":"tag-agile-bsm","17":"tag-bsm","18":"tag-bsm-principles","19":"tag-bsm-step-by-step","20":"tag-dashboard","21":"tag-dashboards","22":"tag-dependency","23":"tag-domain-driven-bsm","24":"tag-implement-bsm","25":"tag-mindmaping-bsm","26":"tag-realizing-bsm","27":"tag-sla"},"_links":{"self":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/1527","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/comments?post=1527"}],"version-history":[{"count":53,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/1527\/revisions"}],"predecessor-version":[{"id":1589,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/posts\/1527\/revisions\/1589"}],"wp:attachment":[{"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/media?parent=1527"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/categories?post=1527"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dougmcclure.net\/blog\/wp-json\/wp\/v2\/tags?post=1527"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}