Home

The APQC Blog

Where does PCF® fit – Software as a Service?

A string of recent questions about “how to adopt the Process Classification Framework (PCF)®” comes from companies engaged in software development, offering software as a service, and combinations thereof. This blog post is dedicated to you: software developers and high-tech mavens. Really, it’s dedicated to anyone who builds a “virtual” product, then sells “copies” of that product. OR perhaps performs that products for others.

Here’s a representative question:

"I see that the PCF splits out services (section 5). Our company sells two types of services A) of training for our end users (teachers) on our products and B) Software as a Service. In relation to our service, please clarify what 5.2.3 represents (Enable service delivery resources) and would Hierarchy ID 5.3 (e.g. be the actual development and delivery of the service?

The questions are usually very similar and focus on the areas of service development and production and service delivery to clients.

Create high-level value streams to understand scope

Let’s split this out into high-level value streams. These are the high-level flows: 1) developing the software to be sold as a service and establishing it as a product that is sold to clients; and 2) offering support of the product (the software as a service) to clients. Here’s the first, developing the software as a service:

I can hear the collective “but wait, it says ‘physical products!’” now. But trust me, this is where things that you develop to sell to clients are housed in the PCF. If you look at the process groups in the category 4.0 part of the PCF – they closely align to the phases and stages of various software development methodologies. Supply chain planning ensures that you have resources at hand to meet the planned needs. Procurement ensures that you have access to libraries and even contractual development help outside of your 4 walls. The use of the manufacturing category is not that foreign, considering that things like agile take lean manufacturing as their inspiration. Manufacturing is where you build your product, whether it is software or widgets. Just replace stamping machines and conveyor belts with developers and GIT, and you have a solid analogy.

But what about offering support of the product, after it has been developed? In this case, the offering of the software as a service begins again at 1.0 – in terms of establishing the vision and strategy for this product. It is critical to acknowledge however that this assumes that the product already exists. You built it above. Work then moves on to category 2.0, where product development decisions are made. These product development decisions are about the offering of the product as a service, including the various service levels. You may even see some customization in 2.3.3 as you “Prepare for production/service delivery”. 3.0 sees the development of sales and marketing materials and plans, and finally 5.0 consists of things relevant to delivering the service.

The big difference between the first value stream and this one is that we’re replacing the “deliver physical products” category with the “deliver services” category. This category contains process groups that establish governance, manage service delivery resources, and of course actually deliver services to customers; but it depends on something you have already developed and can support. It depends on the underlying products, and those products are developed in a different process flow, like the first one above. The “Deliver Services” process group depends on an existing pattern or offering, and in the absence of such a pattern or offering, will revert back to the basic “understand requirements and solve the problem” approach. The value here is the effort, knowledge, and skills that the service delivery brings with it. You’re selling hours here, not just a specific product.

But enough examples: back to the question at hand. In relation to our service, please clarify what 5.2.3 represents (Enable service delivery resources)

In this case, “5.2.3 enable service delivery resources (12127)” is all about making sure that the people who are doing the implementations of your software as service are successful. It includes training in the underlying product (developed in the first value stream) as well as the overall methodology (developed in the second value stream.) This training happens in 5.0, not anywhere else.

Confirm process alignment with the PCF

The answer to the second question: “Would hierarchy ID 5.3 be the actual development and delivery of the service?” is partially YES. If you look at the processes within this process group, you’ll recognize the delivery of a contracted service to a customer. I would expect that the delivery of the product (the software developed in the first value stream) would happen in 5.3.2.6, where the make/build/buy decision is executed, and the software is implemented/customized/delivered as an ongoing concern to the client. Product development generally occurs in category 2, far from the confines of category 5.

20058

5.3

Deliver service to customer

20059

5.3.1

Initiate service delivery

20060

5.3.1.1

Review contract and agreed terms

20061

5.3.1.2

Understand customer requirements and define refine approach

20062

5.3.1.3

Modify/revise and approve project plan

20063

5.3.1.4

Review customer business objectives

20064

5.3.1.5

Confirm environmental readiness

20065

5.3.1.6

Identify, select, and assign resources

20066

5.3.1.6.1

Establish people objectives

20067

5.3.1.6.2

Establish engagement rules

20068

5.3.1.7

Plan for service delivery

20069

5.3.2

Execute service delivery

20070

5.3.2.1

Analyze environment and customer needs

20071

5.3.2.2

Define solution

20072

5.3.2.3

Validate solution

20073

5.3.2.4

Identify changes

20074

5.3.2.5

Obtain approval to proceed

20075

5.3.2.6

Make build/buy solution

20076

5.3.2.7

Deploy solution

20077

5.3.3

Complete service delivery

20078

5.3.3.1

Conduct service delivery/project review and evaluate success

20079

5.3.3.2

Complete/finalize financial management activities

20080

5.3.3.3

Confirm delivery according to contract terms

20081

5.3.3.4

Release resources

20082

5.3.3.5

Manage service delivery completion

20083

5.3.3.6

Harvest knowledge

20084

5.3.3.7

Archive records and update systems

Here’s an exercise left to the reader: what is the mapping in the PCF for the technology part of the software as a service? How does that align? I’d love to see your answers in the comments.