Skip to main content

New Domain Name: Scrum-Breakfast.com

Well, I'd been meaning to do this for a long time, but the painfully long http://scrum-breakfast.blogspot.com is now just www.scrum-breakfast.com (and as soon as the last DNS update takes place, just "scrum-breakfast.com" will work too).

I've also started two sister blogs:
Why do the change now? Well google made me do it.

I discovered that blogger.com/blogspot.com is actually a very nice "poor man's CMS". A couple of nice layouts, easy RSS feads, nice customization. With tag searches, I can create links to groups of articles, like "next scheduled Scrum Courses" or "next Scrum Breakfast". The only disadvantage was kind of long domain names, like "zurich-scrum-breakfast.blogspot.com". Or so I thought.

Yesterday I looked at google analytics and discovered I wasn't getting any referrals from google any more. Huh? Previously, I was getting at least 30 per day. What happened? I tried a search for peter stevens scrum, sprint zero or even scrum blog, queries which usually produced a top 10 placement, and discovered I was no longer in the top 200 results. :-(

It looks like the domain names, layouts and contents of scrum-breakfast blog and the new blogs were too similar, and google decided they looked like SEO spamming sites, sites which pretend to look independent but really only have the purpose of artificially inflating their page ranking. Or perhaps google decided to rank the newer blogs higher, even though they have virtually no content.

So I have not only put everything under one domain (so the relationships will be clearer), but also made the content more unique and minimized linking back and forth between the sites. Hopefully google will realize they've done me wrong and reinstate scrum-breakfast.com to its previous standing.

If anyone has any ideas on how to fix this problem, I'd really appreciate the help! Thanks.

Comments

Popular posts from this blog

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…

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…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …