Team service management

Last updated

Team service management (TSM) is an open-source management framework that uses and integrates existing management methods and techniques to help teams deliver ever improving services. TSM is designed to be used by any and all teams within an enterprise including (but not limited to) sales, production, administration, IT, finance and management teams.

Contents

Over 60% of organisations across the world covering private and public sector organisations are now service-based. [1] Physical product enterprises can have the majority of their teams involved in performing service activities, mostly the provision of internal services to other teams, referred to as internal customers, with the minority of teams involved in the control of physical products and materials. For those enterprises whose purpose is to provide physical products, the competitive differentiator is frequently around the way they deliver services, around and in addition to the products.

Today we live in a ‘service world’ and so we need to have routine ways of delivering and developing services and deploy them by and to teams throughout an enterprise.[ citation needed ]

Use

Team service management pulls together and integrates a number of established management methods and techniques in an open source framework for any team to use without reference to consultants. It is intended to complement process centric frameworks notably ITIL and ITSM where management disciplines and the associated processes are defined, but the people and team working aspects are not fully considered.

Components

TSM integrates the following methods and techniques:

Action-centered leadership, from John Adair – to make sure teams work well together, ACL ensures 3 dimensions: the team, the task and the individual are in balance and effective. TSM turns 'Task' into service and adds management and leadership to the model, and renames it team dynamics. [2]

Team lifecycle from Bruce Tuckman – to assess and improve the maturity of teams. TSM uses the forming, storming, norming, performing maturity phases model to help teams maximise their effectiveness. [3] It uses the 'S or bell curve' model (used to define product and technology lifecycles) [4] to illustrate the team lifecycle phases and the illustrate discontinuity when you reengineer teams in the same way there is discontinuity when you move from one technology to the next generation.

Behaviour/attitude/culture/traits to address teams and individuals barriers to change. TSM looks at the people change management addressing the people barriers to effective team and individual working and the provision of services. It helps individuals and teams change their behaviour and attitude, and where possible their culture and traits.

Business service management, a development on the ITIL framework – to help teams focus on and manage the services they deliver. TSM helps teams define the services they provide, their service activities, the service performance objectives, service issues, the capabilities needed to deliver the team services, and identify service and capability improvements.

EFQM, the European Forum for Quality Management – to ensure that team result and team enablers objectives and capabilities are effective and in unison. TSM defines 4 result domains of customer results, finance results, regulatory results and service results, and then ensures the 5 enabler domains are supportive of the getting the results the team needs. The TSM enabler capabilities that are: people, process and technology, along with knowledge and suppliers. [5]

Balanced scorecard, Kaplan and Norton's strategic planning method – to manage team strategy, objectives, performance and improvement initiatives. TSM uses the standard balanced scorecard to set top down objectives for each team and creates a team strategy for operating and improving the team with planned initiatives. TSM extends the four standard balanced scorecard perspectives to the nine of EFQM: It extends the two result domains of customer and finance to four by adding service results and regulatory results; and extends the two enabler domains of people and process to the five by adding technology, knowledge and suppliers.

Personal performance and development plans (PDPs) to ensure that individual performance and Improvement are an integral part of the team's performance and improvement. TSM ensures that individual's performance and development plans are linked to the team's balanced scorecard. So individuals are allocated their share of responsibility for achieving the team's result and enabler objectives, and are allocated their share of ownership of the team's Improvement Initiatives.

The PDCA cycle PDCA Cycle.svg
The PDCA cycle

Deming’s Plan–do–check–act (PDCA) to ensure team and individuals improvement is incremental and continual. TSM takes the Improvement Initiatives and breaks them into bite sized chunks so that they can be delivered incrementally over a short period of time. The chunks or increments are subject to the PDCA cycle where the increment is first planned, then done, then checked, and then finally but most importantly the lessons learned the results achieved assessed so that the next increment the next/ subsequent PDCA cycles can be planned or re-planned to move most effectively to achieving the overall outcome for the Initiative.

Performance management to ensure that all the activities of each team are transparent and linked to the services delivered and the improvements needed. TSM ensures that work and performance of the team is recognised, recorded and analysed and acted upon. It ensures that resource use, and service effectiveness are both recorded and that issues encountered in undertaking the work of the team are recorded and acted upon feeding in more improvement initiatives into the appropriate point of the TSM framework.

See also

Service management
International Organization for Standardization
Microsoft Operations Framework
Social group
The Five Dysfunctions of a Team
Service economy

Related Research Articles

A balanced scorecard is a strategy performance management tool – a well-structured report used to keep track of the execution of activities by staff and to monitor the consequences arising from these actions.

<span class="mw-page-title-main">Dynamic systems development method</span>

Dynamic systems development method (DSDM) is an agile project delivery framework, initially used as a software development method. First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method. In later versions the DSDM Agile Project Framework was revised and became a generic approach to project management and solution delivery rather than being focused specifically on software development and code creation and could be used for non-IT projects. The DSDM Agile Project Framework covers a wide range of activities across the whole project lifecycle and includes strong foundations and governance, which set it apart from some other Agile methods. The DSDM Agile Project Framework is an iterative and incremental approach that embraces principles of Agile development, including continuous user/customer involvement.

Information technology (IT)governance is a subset discipline of corporate governance, focused on information technology (IT) and its performance and risk management. The interest in IT governance is due to the ongoing need within organizations to focus value creation efforts on an organization's strategic objectives and to better manage the performance of those responsible for creating this value in the best interest of all stakeholders. It has evolved from The Principles of Scientific Management, Total Quality Management and ISO 9001 Quality management system.

<span class="mw-page-title-main">Performance indicator</span> Measurement that evaluates the success of an organization

A performance indicator or key performance indicator (KPI) is a type of performance measurement. KPIs evaluate the success of an organization or of a particular activity in which it engages. KPIs provide a focus for strategic and operational improvement, create an analytical basis for decision making and help focus attention on what matters most.

Quality management ensures that an organization, product or service consistently functions well. It has four main components: quality planning, quality assurance, quality control and quality improvement. Quality management is focused not only on product and service quality, but also on the means to achieve it. Quality management, therefore, uses quality assurance and control of processes as well as products to achieve more consistent quality. Quality control is also part of quality management. What a customer wants and is willing to pay for it, determines quality. It is a written or unwritten commitment to a known or unknown consumer in the market. Quality can be defined as how well the product performs its intended function.

Microsoft Operations Framework (MOF) 4.0 is a series of guides aimed at helping information technology (IT) professionals establish and implement reliable, cost-effective services.

A federal enterprise architecture framework (FEAF) is the U.S. reference enterprise architecture of a federal government. It provides a common approach for the integration of strategic, business and technology management as part of organization design and performance improvement.

Project portfolio management (PPM) is the centralized management of the processes, methods, and technologies used by project managers and project management offices (PMOs) to analyze and collectively manage current or proposed projects based on numerous key characteristics. The objectives of PPM are to determine the optimal resource mix for delivery and to schedule activities to best achieve an organization’s operational and financial goals, while honouring constraints imposed by customers, strategic objectives, or external real-world factors. Standards for Portfolio Management include Project Management Institute's framework for project portfolio management, Management of Portfolios by Office of Government Commerce and the PfM² Portfolio Management Methodology by the PM² Foundation.

Supplier relationship management (SRM) is the systematic, enterprise-wide assessment of suppliers' strengths, performance and capabilities with respect to overall business strategy, determination of what activities to engage in with different suppliers, and planning and execution of all interactions with suppliers, in a coordinated fashion across the relationship life cycle, to maximize the value realized through those interactions. The focus of supplier relationship management is the development of two-way, mutually beneficial relationships with strategic supply partners to deliver greater levels of innovation and competitive advantage than could be achieved by operating independently or through a traditional, transactional purchasing arrangement. Underpinning disciplines which support effective SRM include supplier information management, compliance, risk management and performance management.

Capacity management's goal is to ensure that information technology resources are sufficient to meet upcoming business requirements cost-effectively. One common interpretation of capacity management is described in the ITIL framework. ITIL version 3 views capacity management as comprising three sub-processes: business capacity management, service capacity management, and component capacity management.

IT portfolio management is the application of systematic management to the investments, projects and activities of enterprise Information Technology (IT) departments. Examples of IT portfolios would be planned initiatives, projects, and ongoing IT services. The promise of IT portfolio management is the quantification of previously informal IT efforts, enabling measurement and objective evaluation of investment scenarios.

Data governance is a term used on both a macro and a micro level. The former is a political concept and forms part of international relations and Internet governance; the latter is a data management concept and forms part of corporate data governance.

Virtual machine lifecycle management is the class of management that looks at the life cycle of a virtual machine from the viewpoint of the application vs one focused on roles within an organization. A number of major software vendors, including Microsoft and Novell, have begun to release software products aiming at simplifying the administration of larger virtual machine deployments.

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

<span class="mw-page-title-main">Enterprise Architecture Assessment Framework</span>

The Enterprise Architecture Assessment Framework (EAAF) was created by the US Federal government Office of Management and Budget (OMB) to allow federal agencies to assess and report their enterprise architecture activity and maturity, and advance the use of enterprise architecture in the federal government.

Lean IT is the extension of lean manufacturing and lean services principles to the development and management of information technology (IT) products and services. Its central concern, applied in the context of IT, is the elimination of waste, where waste is work that adds no value to a product or service.

Objectives and key results is a goal-setting framework used by individuals, teams, and organizations to define measurable goals and track their outcomes. The development of OKR is generally attributed to Andrew Grove who introduced the approach to Intel in the 1970s.

Disciplined agile delivery (DAD) is the software development portion of the Disciplined Agile Toolkit. DAD enables teams to make simplified process decisions around incremental and iterative solution delivery. DAD builds on the many practices espoused by advocates of agile software development, including scrum, agile modeling, lean software development, and others.

The Service Design Package (SDP) contains the core documentation of a service and is attached to its entry in the ITIL Service Portfolio.

The Information Technology Infrastructure Library (ITIL) is a set of practices and a framework for IT activities such as IT service management (ITSM) and IT asset management (ITAM) that focus on aligning IT services with the needs of the business.

References

  1. ↑ The World Factbook Archived March 26, 2014, at the Wayback Machine
  2. ↑ action centered leadership, (john adair's action-centred leadership model)
  3. ↑ infed.org | Bruce W. Tuckman – forming, storming norming and performing in groups
  4. ↑ Product Life Cycle
  5. ↑ "Proveandimprove". www.proveandimprove.org. Archived from the original on October 16, 2009.
  6. ↑ "Taking the First Step with PDCA". 2 February 2009. Retrieved 17 March 2011.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.