Skip to main content

Swisscom - On the Road to Good Profits?

Good profits are the result of value that you generate for your customer. Bad profits are value that you extract from your customer.

Long contract durations, automatic rollovers, and cancellation windows (pay an exorbitant fee if you cancel too early, prolong for a year if you cancel too late) are classic examples of bad profits.  Bad products are seductive, because they seem like easy money. But nothing encourages your customers to leave like being shaken down for bad profits. Nothing inhibits your ability to move into a new market like bad profits in your home market. In short, nothing is long-term more dangerous to your profitability than a culture of raking in bad profits.

According to numerous reports, [Six: SCMN] announced that they are eliminating an important source of bad profits - the year-to-year automatic rollover for cell phone contracts. From now on, they have a 60 day notice period once the initial contract length has expired. (And yes, I think it is fair that if they sponsor your telephone, then you should stay with them for a certain period).

Is this move just a tactic, or does it represent a deeper change? Time will tell. We'll have chance at an inside look at how Swisscom thinks when Urs Geiser comes to the Scrum Breakfast in Zürich to talk about the creation of Vivo Casa, Swisscom's Digital TV offering.

What should Swisscom do next? The should take an inventory of their good profits and bad profits. Their good profits should be an example and foundation for the future. And the bad profits? Roaming fees, and especially international data roaming fees, would be high on my list of bad profits. Anything which smells of bad profits should be transformed if possible or simply eliminated.

A good start Swisscom! Weiter so...






Comments

Popular posts from this blog

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Explaining Story Points to Management

During the February Scrum Breakfast in Zurich, the question arised, "How do I explain Story Points to Management?" A good question, and in all honesty, developers can be an even more critical audience than managers.

Traditional estimates attempt to answer the question, "how long will it take to develop X?" I could ask you a similar question, "How long does it take to get the nearest train station?

The answer, measured in time, depends on two things, the distance and the speed. Depending on whether I plan to go by car, by foot, by bicycle or (my personal favorite for short distances) trottinette, the answer can vary dramatically. So it is with software development. The productivity of a developer can vary dramatically, both as a function of innate ability and whether the task at hand plays to his strong points, so the time to produce a piece of software can vary dramatically. But the complexity of the problem doesn't depend on the person solving it, just …