Being Cellfish

Stuff I wished I've found in some blog (and sometimes did)

Browse by Tags

Tagged Content List
  • Blog Post: My worst stand-up(s)

    Reading this story about the worst daily scrum ever made me think about my own experience. An both actually reminds me of what happened in the linked story. Read more here .
  • Blog Post: Estimating projects

    Several years ago I told a story about a project that proved that estimation was a waste of time once the work was split up in small enough chunks. Not necessarily equal size of chunks but manageable size chunks. But sometimes you need to do estimations because somebody wants to know the cost of some...
  • Blog Post: The green February revolution

    I read this great article " the February Revolution " listing four things that tend to happen when great results are achieved. The thing that interested me the most was how similar at least three of the items were to how a successful military unit operates. People know why they are doing their...
  • Blog Post: Cost of meetings

    This was recently sent to me and anybody who has worked at Microsoft knows that a lot of teams (if not all) have a lot of meetings and do a lot of communication over email. The essence of the article linked is that people who's work mainly consists of meetings need to understand that people who contribute...
  • Blog Post: How Spotify Works

    While I wish I could write a long article on how Spotify works technically this is not what I want to tell you about today. Nor will I tell you how I would build Spotify if I had to, but that would be an interesting blog post. But today I want to tell you about a great article describing how Spotify...
  • Blog Post: Lean processes explained with LEGO

    I read this interesting article that illustrated the difference between processes optimized for flow efficiency versus resource efficiency. Maybe not obvious in that article why flow is cheaper (or same) cost as resource optimized but if we assume customer satisfaction is a great asset I think it is...
  • Blog Post: One way to make management understand development

    I spent the weekend catching up on my RSS feeds and read this interesting story on how to explain why two developers pair programming would only produce a hundred lines of code in a single day. Brilliant idea to use business plans to explain what development really is about.
  • Blog Post: Ten Commandments of Egoless Programming

    I recently saw this post with ten tips on how to be a better developer . It made me think of the Viking Laws again. The Viking Laws covers a few more aspects than the Ten Commandments which essentially just tell you to be a good person and point out a few different aspects of being a good person. So...
  • Blog Post: Drunken estimation

    As I've pointed out before , estimation is usually a waste of time in my opinion. The time can be spent on other things that are more productive and lead to better understanding of velocity. Well, I'm almost prepared to start being an advocate for estimation again... Drunken estimation to be precise...
  • Blog Post: Alt.Net Seattle Conference 2011

    I spent half of last week at the Alt.Net Seattle Conference 2011. It started with two days of workshops and ended with two days of open spaces. For me personally the four hour workshops did not work well. There was a good intention to let us get lots of hands on experience but in practice a lot of the...
  • Blog Post: Boy scout retrospectives

    In our last retrospective we tried a new way of gathering things that were good and things to improve. Apparently this is something the boy scouts use and it's referred to as SSC ; Start, Stop, Continue . I think this was a brilliant way of capturing what is important in the retrospective; to gather...
  • Blog Post: @"Tired of Scrum"

    I got a comment here that deserved more than just a comment response. It is an interesting comment and I wish I could sit down with whoever wrote that and discuss that comment. But I guess that will never happen so here it goes. First of all I feel sorry for whoever made that comment and everybody else...
  • Blog Post: Planning poker for your Windows Phone 7

    Since I'm still waiting for my windows phone 7 I have not tried the planning poker application (you need to be signed in to see it) that is available but from what I've seen it's good idea. Keeps people from using their phones for email and surfing during the planning poker session which something I...
  • Blog Post: Why have iterations?

    Almost two months ago Michael Feathers wrote a thing on zero length iterations . The post is very similar to the one that inspired me to write this but he also brings up an important point; the intention of iterations is to force a decision, force the team to make trade-offs and keep moving towards a...
  • Blog Post: What to do when one user story is complete and all other user stories are on track

    There was recently a discussion on an internal distribution list that caught my eye. The initial question was; when should you add more to a sprint instead of ending early ? At first glance I think it is safe to assume that while the person asking the question claimed to be doing scrum he had missed...
  • Blog Post: Viking laws

    After reading this which jokingly tells us that the Viking laws will replace the agile manifesto I started to think about manifestos and "agile". The agile manifesto well describes how you need a change in your mindset to become agile. And some try to refine it even further . But the Viking laws are...
  • Blog Post: Can the daily scrum be a waste of time?

    Sometimes a team come to the conclusion that the daily scrum (a.k.a. the daily stand-up) is a waste of time. I think the most common reason for this is that the team is not having an effective informative meeting. I've seen a lot of daily scrums turn in to a status report where everybody tries to justify...
  • Blog Post: Beware of Parkinson's law

    Parkinson's law , if you have not heard it before, states that Work expands so as to fill the time available for its completion. That means that if you estimate a task to take one day to complete it will take one day to complete. This is a potential problem with using hours as estimates for your tasks...
  • Blog Post: Scrum or Kanban?

    One interesting thing I've heard over the last years ( and again the other day ) is that a lot of teams that have implemented Scrum and have become very successful with Scrum often end up with a feeling that iterations are unnecessary. Some teams take the leap away from Scrum and starts working in a...
  • Blog Post: Definition of a failed sprint

    Recently there was a discussion on an internal mailing list about when a sprint was was considered a failure. Specifically the question was asked if seven out of nine user stories completed meant that it was a failure. Naturally that should be considered a failure! NOT ! As far as I'm concerned there...
  • Blog Post: Improving meetings with ROTI

    There are two things people seam to love at Microsoft; Meetings and email. The latter needs a quick mentioning; there is definitely a culture at Microsoft where a lot of people tend to send email rather than walk a few meters to somebody else's office and actually talk to them. Enough about that. Meetings...
  • Blog Post: Should a professional developer always use TDD?

    The answer is no - a professional developer should always use BDD. No seriously. I read this today and didn't hesitate a second to steal the topic since I there are two discussions around TDD I love; the discussion with people who struggle to write good code and the discussion with people who write...
  • Blog Post: Why do TDD when it slows you down?

    In my experience a lot of teams that wants to start using test driven development did not write a lot of unit tests before they started to use TDD. And even if they did they often experience a feeling of getting "slowed down". So why do teams bother to do this? Well I don't think you're slowing down...
  • Blog Post: Working in war teams is great

    One thing that came up in the retrospectives as a good thing a few times in my previous team was working in war teams . So what is a war team ? To us it meant that whenever we ran into some kind of problem, a difficult bug, a big design challenge or similar we format war teams . Sometimes the war team...
  • Blog Post: On Toyota's recent recall of cars

    So the company who gave us lean is recalling a lot of cars because of break problems. I don't think it is something spectacular there. Sometimes these things happen and you do what you have to do. But there is another dimension of this I just cannot resist to mention... Apparently it is a software problem...
Page 1 of 4 (82 items) 1234