Comments for bbv Blog

Comment on Prism vs. Caliburn.Micro by Carl Cubillas

Carl Cubillas — Fri, 21 Sep 2012 10:03:13 +0000

Great post! I’m looking into different MVVM frameworks out there such as Caliburn.Micro, PRISM and ReactiveUI. I’m relatively new to WPF and I’m currently using MVVMLight at the moment. Thanks for posting some of their distinctions.

Comment on The Chance that 42 is the Meaning of Life by Katia

Katia — Mon, 16 Jan 2012 14:14:35 +0000

a. 42 is not to be set as equal “Meaning of Live”. It’s just the answer to a very unprecisly formulated question (aka “meaning of Live, THE UNIVERS AND EVERYTHING”). I am not able to follow your reflections above, but I think it’s an educated guess to postulate, that chances, that the answer to that question is 42 is even smaller.
b. “it’s not impossible. It’s just very improbable”.
c.

Comment on The next 2 steps on bbv’s Agile journey by Urs Enzler

Urs Enzler — Wed, 28 Dec 2011 16:33:53 +0000

Hi Thomas

Personally, I’d like to have dedicated Scrum Masters. But this is very hard to sell to customers: “what? two project leaders? (PO and SM)”

But we’re working on that.

Cheers
Urs

Comment on The next 2 steps on bbv’s Agile journey by Thomas Weingartner

Thomas Weingartner — Fri, 09 Dec 2011 01:38:34 +0000

Cool article about the journey, which I was part of it in the beginning, and all the learning you went through. Especially interesting was the disconnect between developer and tester, which I also encountered.

The part where I stumbled upon was the ScrumMaster where you mentioned “The daily work is dominated by normal developer stuff.”. During the SM training with Mike Cohn that topic also came up whether a ScrumMaster should be developer as well, or just ScrumMaster and additionally to what you already pointed out, helps the Product Owner doing his job.

We discussed advantages and disadvantages of dedicated roles vs. split roles. Bottom line of the discussion was, that a ScrumMaster doing developer work as well gets into conflicts all the time and the other developers could be confused whether he speaks as the ScrumMaster or as developer. The recommendation was to have a dedicated ScrumMaster, which can support multiple teams and takes the time to advocate Scrum outside the team. You might consider this as well.

Cheers for now
Thomas

Comment on Caliburn.Micro – Introduction by Marco Amendola

Marco Amendola — Thu, 08 Sep 2011 21:44:59 +0000

Actually, my contribution has been very lacking lately, but I hope to come back very soon.
Looking forward to read your upcoming post about CM

Comment on 16 ideas about what a Scrum Master can do to improve team performance by Jayne Hamilton

Jayne Hamilton — Thu, 18 Aug 2011 22:09:09 +0000

This is an interesting article. My client in Rotterdam, Gemeente Rotterdam IOO, has used many of your points during scrum sprints. The software and team spirit there is really good. Spreading knowledge among the scrum team by moving developers outside of their main skills area, is very important as are code reviews and knowledge transfer sessions.

Comment on 16 ideas about what a Scrum Master can do to improve team performance by Kronenberg Philipp

Kronenberg Philipp — Wed, 15 Jun 2011 12:30:57 +0000

A crispy contribution! I would suggest that this article is enhanced by 84 further points and distributed as a printed booklet.

Comment on 16 ideas about what a Scrum Master can do to improve team performance by Peter Rey

Peter Rey — Tue, 14 Jun 2011 12:31:39 +0000

a good “bag of tricks”.
As a scrum team member, scrum master & product owner during the last few years, I can confirm that your ideas do work!

Comment on Law of Demeter and Testability by Lukas Weibel

Lukas Weibel — Tue, 19 Apr 2011 16:55:02 +0000

Well, actually all depending classes of the testee in the LoD conform test methods are mocked. Room as well as Window are mocked with Mockito (sorry, I omitted the static imports). You are right, it would be better to have interfaces like EnergySavable. But here I agree with Uncle Bob to take the first bullet (introduce abstraction when needed).

Comment on Law of Demeter and Testability by M

Tue, 12 Apr 2011 07:40:56 +0000

The isInEnergySavingModeLoD() method in class House relies only on the method isInEnergySavingMode() of class Room. That’s a nice design and really easier to test.
However, in my opinion, when unit-testing the House class you shouldn’t consider implementations of other classes.
So in this case you shouldn’t consider the algorithm inside of Room.isInEnergySavingMode(). Currently the algorithm depends on windows, but in future it additionally may depend on the temperature, balcony doors…
Instead you could mock the Room class (possible with Mockito) with different behaviours for Room.isInEnergySavingMode(). In this case you are only testing the House class and its direct dependencies.