Unitils update – TestListeners

In a previous post I got some help from Tim Ducheyne to work out a way to use a spring wired DataSource with Unitils.  He mentioned a better way was coming…

Sometime back now they added the support for TestListener which solves this issue.

Unitils – TestListerer API

I don’t work with conventional databases much now, but was intrigued to see this post explaining how to extend unitils and use TestListeners to test ldap.  Neat eh!

Extending Unitils to test LDap.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Culture and Agile Adoption

Its a Punch and Judy Show

Beach Hut - By Martin Harris

More and more I have been thinking about the effect of culture on Agile adoption. Then a friend tweeted this article on Agile Culture by Michael Sahota. Its a real eye opener and one key message is that it might be quicker to fit your process to the culture rather than the other way around.

There is some evidence to suggest that trying to introduce and Agile Development system into a culture that won’t naturally accept it is a recipe for failure.

For me its more complex that this. I am not 100% sure I am anywhere near a solution but these thoughts arise.

Evolution v Revolution and mandate
Without going into the detail which can be found on other posts the cultural fit is probably more important if you can’t change the culture. Most of the time we are somewhat restricted by our mandate. Its rare that someone senior wants this bad enough that they are prepared for the risk of revolutionary change.

If you were about to move in that direction, perhaps you can change the culture to fit. This path is also easier if your scope is small. i.e. if your dealing with a small group of people and not a multinational.

Otherwise perhaps initially selection of technique and Agile process should be culture driven.

The Kanban / Control argument
Its interesting to see Michael point out that Kanban is not Agile. At least by cultural definition. It occurred to me also that successful open source cultures might not be Agile either, they seem to fall into the “Craftsmanship” section.

Yet, were you to take a controlling culture and conduct Kanban with XP practices might it not over a long period of time begin to change. Perhaps towards craftsmanship as an appreciation of quality evolves?

So what now then Agile Coaches and CTO’s?
Well I for one have found the diagrams very useful. Just an awareness of this idea helps bring people to a higher view of what might be going on in their Agile Adoption process and that is no bad thing. Its too easy to get wrapped up in the daily Punch and Judy show forgetting about the bigger picture.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

InfoQ: Chet Hendrickson on the Need for Good Technical Practices

Excellent interview that parallels some of my experiences.

InfoQ: Chet Hendrickson on the Need for Good Technical Practices.

Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)

Update on building .NET

Sometime back now I posted an article on building .NET and dependency management.

I have come to learn that there are several ways. Here are my favorites.

  1. Build your own maven plugin to build .NET projects. Package 3rd party products as zips and put them in maven. Write a plugin that reads solution and project files and calls MSBuild with the appropriate flags.  Advantage, maximum flexibility.  Disadvantage, lots of effort.
  2. Use the existing maven-dotnet-plugin.  Advantage, does a lot for you including various types of test and coverage systems, plus it can run sonar.  Disadvantage, Hard to get it to work on complex silverlight projects. In fact hard full stop.  The docs are not great.
  3. Use NuGet.  Advantages, it has .NET pedigree and Microsoft Backing.  Adoption amongst .net developers is probably an easier sell than a java utility.  Disadvantages, Very early days for the project, as yet unproven.
  4. Finally npanday.  Advantages, nice integration with Visual Studio.  Disadvantages, very hard to get it to work with silverlight.  Impossible in fact as MS have kindly removed the command line baml compile utility.
So in summary.  There are ways to do this now.  There is hope for .NET dependency management!
Digg This
Reddit This
Stumble Now!
Buzz This
Vote on DZone
Share on Facebook
Bookmark this on Delicious
Kick It on DotNetKicks.com
Shout it
Share on LinkedIn
Bookmark this on Technorati
Post on Twitter
Google Buzz (aka. Google Reader)