Comments for Melle Koning Blog

Comment on Going agile with scrum: The taskboard by admin

admin — Sun, 13 Nov 2011 08:26:04 +0000

Hi Ray, thanks for your comment! Yes we do have the same problem because our stakeholders are usually off-site and not part of the scrum. Please be aware that they do not need to follow the tasks on a too detailed level! The use of the taskboard has made a lot of things clear to us, especially about the in-between small stories, fixes and small incidents that developers are busy with. All related to the flat communication within the organisation. That is, stakeholders / product owners use e-mail to directly communicate with developers. Developers want to please stakeholders and fix things ‘below radar level’. Mainly this is about notifying a difference between small incidents that can interrupt planned iterations on one side and wanting to focus the developmentteam on new user stories on the other side; we are now thinking about setting up a different flow of communication for incidents. It is great to see that starting out with a visible taskboard has led to this: the realisation at management level that the flow of information in the organisation really needs a change so that developers can concentrate on their work Instead of stakeholders following a detailed taskboard of developers; what they really want is regular status update of when their features will be delivered. Hm, I will definately post a new blog to explain in more detail what I mean…

Greetings, Melle

Comment on Going agile with scrum: The taskboard by Ray

Ray — Wed, 09 Nov 2011 18:45:40 +0000

Great job! We also moved from Kanban to Scrum and do the usual things to track our day to day progress. We are having a real challenge in communicating during our daily stand ups with off site stakeholders. We do use Pivotal Tracker to share the stories, but there is nothing out there to easily follow tasks when not in the room. Any ideas?

Comment on Going agile with scrum: The taskboard by Joost Landgraf

Joost Landgraf — Thu, 13 Oct 2011 06:56:28 +0000

The only \”issue\” I see on the board there is still too much in development. focus more on less stories, otherwise you still get the big waterfall-concept.

Comment on Going agile with scrum: The taskboard by Joost Landgraf

Joost Landgraf — Thu, 13 Oct 2011 06:54:47 +0000

Kudos on doing scrum.

I have been doing it for quite a while now and it’s great

Comment on The Agile estimation sheet by Bas

Bas — Mon, 02 May 2011 03:43:49 +0000

Hoi Melle, Leuk voorbeeldje. Wij gebruiken hier JIRA voor het bijhouden van de ‘original estimates’ en ‘remaining work’. Dit geeft je ook een ‘burn-down chart’ en andere handige extratjes.

Het is niet gratis, maar het lijkt hier wel het geld waard.

Groeten,
Bas

Comment on Upgrade to NHibernate 3.0 and FluentNHibernate 1.2.0 by admin

admin — Sat, 05 Feb 2011 08:30:20 +0000

Hi David,

Thanks for your reply, the fault must have creeped in because I removed some try.. catch blocks for readability. Good that you found how to use this little piece of code

Cheers,
Melle

Comment on Upgrade to NHibernate 3.0 and FluentNHibernate 1.2.0 by David

David — Tue, 01 Feb 2011 22:48:10 +0000

Hi,

Thanks for the tip! However, the second code block is not syntactically correct, the foreach block has to be wrapped with curly brackets. In other words you can’t write m => foreach(..) { .. }. It has to be m => { foreach(..) {..} }

Regards,
David

Comment on Unit testing coverage with PartCover and ReportGenerator by Daniel

Daniel — Sun, 02 May 2010 11:14:06 +0000

I solved the problem by using the NRefactory library. Details are described in this post: http://www.palmmedia.de/Blog/2010/5/2/partcover-coverage-of-unexecuted-methods-part-2

Comment on Project references in DDD by admin

admin — Sun, 14 Mar 2010 08:21:40 +0000

Hi Jamie,

I’ve done the colour and styling manually; I’ve changed the styling to “component” instead of “ellipse” and the colouring was also changed for the different kind of projects. Although, now that you mention it, it would be possible to do extra analysis in the projectloading code by determining the colour based on the references the project has. In our case, all the services projects have a relation to the NHibernate.dll so those projects would be the repository/services while the others will be the Plain domain projects.

Also, within GVEDIT I have changed a few settings before generating the picture like the “ratio” flag; that way the layout of the projects in the picture is not too flat. Thanks for putting the project on github!

Cheers, Melle

Comment on Project references in DDD by Jamie Penney

Jamie Penney — Sun, 14 Mar 2010 07:41:38 +0000

Hi Melle,

Thanks for the mention. I’ve updated that project and put it up on GitHub at http://github.com/jamiepenney/VS-Dependency-Viewer I’m glad someone has a use for these little projects I create. I might do a little more work to make it easier to do the colouring you’ve done in your blog post – did you add this manually to the .dot file or did you do some analysis in the project loading code?

Cheers, Jamie