Pages

Wednesday, 20 August 2014

5 Things I've learnt being a scrum master

I've been a scrum master now for about 6 months. Having been involved in scrum previously as a product owner, as well as a developer, moving into this role has really opened my eyes to some of the more political and arguably awkward elements of trying to get rid of impediments.

Stay calm when others aren't 


Something that I think is really key about being a scrum master, you have to be thick skinned. You have to not only push back, but when people whine at you and bring office politics into play, it's vital that you remember exactly what the end game is, to meet the sprint goal!  

I should also point out, this doesn't mean ruling with an iron fist, as a scrum master, you still succeed with the team and fail with the team.  You can tell when something isn't working and using an agile methodology shouldn't be a painful process, it should be motivating.

You are neither a manager, nor just a developer

It's quite an interesting position to be in as from my experience, it's not unrealistic to get your hands dirty in some code while being a scrum master.  You have to be strong enough to fend people off from poaching your team members even if they're higher up the food chain to yourself.  You aren't "in charge" of the team, but you do have a responsibility to push back on poachers.

Don't be afraid to say "no"

If your product owner is telling you to put 60 points into a sprint, when you know the velocity you've been hitting for the past 4 sprints has consistently been 40 points, don't be afraid to say "what you're asking is unattainable".  It's much better to be honest early on and push back.  Blindly saying yes, promising to the customer and then having to deal with the consequences later on isn't where anyone wants to be.

Make sure stand ups are to the point

This might be like telling grandma to suck eggs, but it's vital that stand ups really are short, sharp and to the point.  There's nothing worse than listening to a stand up where everyone in the back of their mind is thinking "I wish s/he'd just get to the point!".  This is a situation where you have to stick to your guns and if people get offended, they get offended.  You have to tell the person, "we don't need to know any of the extra detail, we just need to know from a high level; what it is you're going to achieve today, did you achieve what you set out to do yesterday and importantly, do you have any impediments".

Keep things moving

Sometimes things in a sprint can get stale, tasks can get stuck in one condition, you need to keep them moving!  As an example, If there's a task that's been coded for half a day but not released to testing, find out why.  You never know, the CI server might be down, there might be a problem releasing, you need to get it out before it becomes an impediment.  Keeping the task board fresh and a true representation of what's actually happening in your sprint can really boost morale if you know there's only a few tasks left and you're literally "sprinting" to the finish :)

Wednesday, 14 May 2014

Jax-RS custom exception handling

One of the nice things about working with JEE is the components available really are pretty standard.  While using JAX-RS, sometimes you need to control how exceptions get processed and fed back to the user.  If an exception is thrown, by default, you'll get some horrible HTTP 500 internal server exception, exposing the internal failings of your web service.

Consider the following gist, this endpoint would be used to view a user based on the Id.

Now, the implementation of this interface would look something like the following, to do the donkey work of actually retrieving the user.

This looks fine, but consider if the userDao was doing some entity business logic, using Query.getSingleResult and the user with this ID didn't exist?

According to the JEE6 API documentation, you'd receive a NoResultException, which would cause an HTTP 500 error exposing your internal server exception, which is definitely something end users shouldn't see. We need to leverage the exception handling of Jax-RS!

First, we need a dumb exception object, appropriately named, which will be what we'll actually throw, consider the code below..

Next, we need to modify our original code to take into account this exception, I've modified the original UserWebService and associated implementation appropriately below.

This will now throw an appropriate exception when a user cannot be found. However, we still need to create a Handler object to convert this exception into an actual JSON response so we get a nice friendly error message. The class below handles this exception and will convert the error message in the exception into a JSON response. The important annotation you'll see on this class is the @Provider annotation.

You'll notice we create an ErrorMessage object to respond to from the web service. This is just a simple dumb object to hold the details of the actual error that'll be marshalled into JSON.

The final step in mapping our exception handler provider to the web-app is to add the following into our web.xml for our webapp.

Now when we call this REST endpoint with a user ID that doesn't exist (let's say "DAG"), we'll happily receive the following JSON response rather than a stacktrace.

Friday, 17 January 2014

Stripping Java string SQL statements automatically

Do you ever get sick of typing out an SQL statement in Java with all the String syntax?

Then, when the statement doesn't work, you have to copy it back into pure SQL to run it to check it works?

This was a pretty common problem for me, so I made a simple syntax stripper http://idavid.co.uk/sqlstripper/ so I could quickly covert from SQL into a Java string and back again.  Consider the following Java String...

String query = "SELECT * " +
"   FROM USERS u" +

"INNER JOIN CODE cd ON cd.userid = u.id " +
"WHERE u.id in ('1','2') ";

This would parse fine if it was being sent into stmt.executeQuery(query)

But it I wanted to run this on SQL server just to see what it produced, I'd have to manually remove all the syntax etc to make it run and generate the following SQL.

SELECT *
FROM USERS u
INNER JOIN CODE cd ON cd.userid = u.id
WHERE u.id in ('1','2')

This is exactly what my SQL stripper does.  It also gives you the ability to paste in an SQL statement into the right hand textbox and convert it into a nicely formatted Java String, so converting the SQL statement above would give...

"SELECT *"
+ " FROM USERS u"
+ " INNER JOIN CODE cd ON cd.userid = u.id"
+ " WHERE u.id in ('1','2')";