Project ≠ Product ≠ Business ≠ Company

9. Februar 2020
Kategorien
Newsletter abonnieren

Project ≠ Product ≠ Business ≠ Company

Last few weeks I had a number of heated discussions around these terms. People get confused and make wrong decisions because of this.

This is my take on it.

A project is a temporary endeavor undertaken to create a unique product, service or result. It is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources.

And a project is unique in that it is not a routine job, but a specific set of jobs designed to accomplish a singular goal. So a project team often includes people who don’t usually work together – sometimes from different organizations and across multiple geographies.

Where each project is unique, doing projects is something that is recurring. Most organizations spend a lot of time and money on projects.

That is why investing in project management capabilities gives you usually a high ROI.

A product is something that you can build and sell, directly or indirectly. It is the «thing» (though it can be a service) that you could make money from via a business. By itself, though, it won’t make money.

Typically the first version of a new product or service is the result of a project. The second version is usually not.

A business is a set of people, processes, and tools that have been structured around a product or service to enable it to make money.

Ideally, a business is profitable, but it may not be.

Ideally, a business doesn’t depend on any specific person being a part of it (including the founders), but it may rely on some exceptional people.

You can’t run a business solely with projects. You need day-to-day operations.

A company is an organization of people that is designed to run one or more businesses successfully and to create new businesses to respond to opportunities in the marketplace.

This must be, ultimately, independent of any specific employee, since companies, unlike products and businesses, are (or should be) built to last for decades.

A business is worth much more than the product that it sells.

A company is worth much more than the business that keeps it alive.

This is one good rationale for why some startups (e.g. WeWork, Facebook, Twitter), operating in environments where it’s easy to raise money, have bypassed the «build a business» step to go straight to building a company.

The danger with that is that if you don’t first build a business, you might end up building a company that’s incapable of building new businesses – and that’s not worth a whole lot.

In a nutshell: Project ≠ Product ≠ Business ≠ Company

Tags

Das könnte Sie auch interessieren

Scaling Agile: SAFe

2. November 2015

This is the fourth of six articles on approaches that try to help to scale Agile. For the introduction to this series please read the first article Scaling Agile: Nexus Framework. The second article is about Disciplined Agile Delivery (DAD) and the third about Large Scale Scrum (LeSS). This article will present the Scaled Agile

Weiterlesen

Scaling Agile: LeSS

29. Oktober 2015

This is the third of six articles on approaches that try to help scaling Agile. For the introduction to this series please read the first article Scaling Agile: Nexus Framework. The second article is about Disciplined Agile Delivery (DAD). This article will present Large Scale Scrum, or LeSS. The creators of LeSS, Bas Vodde and

Weiterlesen

Product Backlog Stories …

26. Oktober 2015

Last few weeks I had a few experiences around Product Backlog Items and user stories that made me write this article. Let’s start with a simple observation: many teams I have worked with and people I have met still have the notion that every Product Backlog Item should be in the form of a user

Weiterlesen

Scaling Agile: DAD

21. Oktober 2015

This is the second of six articles on approaches that try to help scaling Agile. For the introduction to this series please read the first article Scaling Agile: Nexus Framework. This article will present Disciplined Agile Delivery, or DAD. Contrary to for example Nexus or LeSS, DAD is not Scrum, it wants to be far

Weiterlesen

Scaling Agile: Nexus Framework

19. Oktober 2015

This is the first of six articles on approaches that try to help to scale Agile. One of the most popular Agile methods is Scrum. Scrum is a very simple framework that describes an one iteration, one increment, one team product development effort. The framework leaves the more complex application of Scrum to the user.

Weiterlesen

Estimating with Wideband Delphi and Monte Carlo Simulation

18. Oktober 2015

During the LeSS training in Berlin last week with Craig Larman he mentioned the best estimating method he knows for any big software project. Wideband Delphi with Monte Carlo Simulation. I agree with him on this one hundred percent. This article will explain what Wideband Delphi and Monte Carlo Simulation is (Part 1 & 2),

Weiterlesen

Budgeting a Scrum Project

11. August 2015

A few weeks ago, I took the training for «Agile Estimating and Planning» with Mike Cohn on FrontRowAgile.com. The training was very good and I think it’s an excellent start for all estimation and planning-related questions. But even after this training, it is still unclear for many on how to make the leap from estimations

Weiterlesen

Scrum Project Success Metrics

30. Juli 2015

Last week I was reading „The 2015 State of Scrum Report“ from Scrum Alliance. In February 2015, Scrum Alliance surveyed almost 5000 people about their use of Scrum. The survey respondents make up a diverse group, representing 108 countries and 14 industries. They reflect a range of functional areas, including IT software development, product development,

Weiterlesen
Previous