B.Y.O.D. deteriorates best practices and increases risks!


Today leaders have dealt with some of the key service values that customers and employees have risen up regarding their perspectives of wireless access.

Leaders, caught in between these two stakeholder groups, vacillate between the customer demand for wireless alternatives to gain access to products and services while employees who want wireless access to gain productivity enhancements. In the latter case, to meet employees’ perceptions, organizations defined a mobile policy that outlined entitlements, device selections and preferred supplier rate plans. This plan is generally managed by small disparate internal teams who cull together in an effort to develop best practices. Many strides were made to mature best practices to control this pattern of business activity by standardizing the variable devices, rates and plan choices.

Employees continue to have a strong desire to determine the selection criteria for mobile devices which has led IT to relinquish a B.Y.O.D. program – Bring Your Own Device.

This program has been quickly hailed as part of IT’s value to embark on the “consumerization” of IT. Basically, employees can bring their personal computing devices, predominately smartphones, to the workplace and have the device connected to the corporate network.

Yet, leaders have not evaluated the many risks associated with B.Y.O.D. programs. To create new best practices leaders must assess their current approaches and mitigate the implications to corporate policy, service delivery capabilities and supplier management.

While corporate leaders face challenges in gaining consensus on a mobile policy and a governance model to ensure strategic alignment, they have inadvertently added more complexities that lead to increased risks. Some observations on risks include clarifying:

    • What mobile ownership option will employees be required to subscribe, personal or corporate liability
    • What types of devices will be authorized and who determines who is entitled to gain access to the B.Y.O.D. program
    • What needs to be done to maintain legal and regulatory compliance for retention related functions such as, legal hold notifications, clinical trial data and other types of corporate information
    • What is the security control when a device is lost or stolen and the wipe feature is used to erase personal information

Service delivery organizations may see B.Y.O.D. as a function of a few team members across several functional groups that can be marshaled quickly to execute a mobile deployment. IT leaders should consider how B.Y.O.D. fits into the service portfolio and address the service management of B.Y.O.D. that include:

    • What is the architecture platform to be designed to align the organization’s policy and the it’s expected business outcomes
    • What applications will be required to be customized to enable mobile CRM, ERP or productivity tools
    • What are the mobile OS criteria to determine between iOS or Android
    • What is the investment required to support the wireless infrastructure
    • What is the organizational structure required to support a mobile service delivery model

Sourcing and procurement management leaders need to determine the implications of the service value and the provisioning requirements to manage B.Y.O.D.

    • What is the supplier capability required to provision a reliable service with a level of assurance to meet the geographic, security, availability and compliance need of the organization.
    • What Service Level Agreements can be used to ensure contract management and performance expectations for the offered service.
    • What are the best practices for expense and audit controls of wireless cost management to drive budget transparency. In many cases, wireless expenses outpace traditional voice and data expenses. This expense is usually part of individual departments T&E budgets. These expenses go unnoticed at the aggregate level and are not evaluated as part of the IT cost index.

Lastly, leaders need to determine if the B.Y.O.D. program is too internally focused on the employee needs and does not support the strategic objectives of the organization. 

Leaders should be careful not to tout B.Y.O.D. as an employee productivity enhancement that may provide intangible benefits that is weighed down by new business risks that invariably lead to increased operating efforts.

Related articles

Image Reference : http://www.rainkingonline.com/blog/market-insights/insights-on-byod/

Telecom Expense Management


Ain’t Life Fun!

On the one hand, the massive mergers of voice and data carriers (traditional telecom providers) and wireless providers over the past five years have been a boon to overstressed IT managers trying to make sense of ever-increasing service offerings from suppliers.

On the other, the demand for more and better, faster and cheaper never lets up so telecom expense managers (usually some poor guy down in IT with too few staff and too many performance expectations) means telecom is becoming ever more pervasive throughout businesses of all sizes.

This is a summary of an article that I contributed to that was printed in CIO Update. Follow the title link to the full article

Regards,

Peter

Related articles

If you are considering Cloud Computing or SaaS read this!


Keep Eyes Wide Open When Considering SaaS

Organizations today rely heavily on their IT software to drive the business objectives to meet the needs of the market. There are a number of sophisticated software applications that have grown in demand and complexity to support an organization’s value chain such as Customer Relationship Management (CRM) and, conversely, the back office, Enterprise Resource Planning (ERP). In the traditional model, to meet the needs of the organization the IT department designs software, hosts applications, codified software and manages the operational functions to distribute the internal software packages to customers.

This is a summary of an article that I authored to that was printed in Cloud Computing Journal and reprinted in others. Follow the title link to the full article

Regards,

Peter

Service Management (ITIL) and Project Management – a contrast in execution


This topic is a series of articles that I authored as part of the Program Delivery Effectiveness Group – The source of innovative program delivery techniques by PA Consulting.  That blog has six major areas of focus:

  • Simply Better PMO – John Hall provides invaluable insight on how your PMO can get the basics right, do the important things well, and minimize overhead.
  • Program Management – Alexander Lowry offers insights on strategic program management. His posts address many of the challenges that occur along the program delivery path.
  • Portfolio Delivery – Tim Pare shares research findings on portfolio management based on survey data we have collected and, continue to collect, from program managers around the world in a variety of business sectors.
  • Design Authority – Andre Vargas discusses techniques for ensuring that solutions are designed & built as imagined through the use of discrete Design Authority function.
  • Change Management – Teneka Polite & Precillia Redmond share valuable insights on driving and releasing change to ensure sustainable benefits from change efforts
  • ITIL & Program Management – Peter Tarhanidis provides a unique perspective on program management as it applies to service management (ITIL)

My series is based on the contrast between Project management and ITIL service management and how they can co-exist since one is based on the temporary undertaking delivering a unique goal and the latter is based on a lifecycle approach. Below are the key articles that are linked back to that site for

Service Management (ITIL) and Project Management – a contrast in execution

Today many IT organizations are redefining their approach to delivery and support of IT of their customers. Some of those IT organizations are adopting a customer oriented approach to meet the requirements of flawless execution of the services customers receive. As a result, IT organizations adopt both Service Management (ITIL) and the use of Project […]

ITIL Service Strategy and Project Management – a contrast in execution

The purpose of these updates is to continue to show how these two best practices, ITIL and project management provide synergy to improve effectiveness and drive overall maturity for organizations to meet the needs of the business. In this article I will focus at a high level what service strategy and project management can leverage […]

ITIL Service Design and Project Management – a contrast in execution

The purpose of this series of articles is to continue to show how these two best practices, ITIL and project management provide synergy to improve effectiveness and drive overall maturity for organizations to meet the needs of the business. In this third article I will focus at a high level on how service design and […]

Thank you for any comments or feedback that provides clarity to distinguish good practices in developing both these disciplines.

Regards

Peter

Related articles

  1. The Basics Of ITIL Training (projectqwerty.wordpress.com)
  2. The Keys to IT Demand Management (vaughanmerlyn.com)
  3. What is ITIL Service Portfolio Management? (tomjsmyth.wordpress.com)
  4. ITIL Maturity Assessment Chart (tomjsmyth.wordpress.com)
  5. Delivery and Process (ITIL) – Job Descriptions (freeitjobdescriptions.wordpress.com)
  6. Program and Project Management – Job Descriptions (freeitjobdescriptions.wordpress.com)
  7. How to Develop Next-Gen Project Managers (pcadvisor.co.uk)