Archive for June 2012
No post today and probably not on Monday as I’m off to my favorite city of them all! The picture to this post is actually where I got married.
If you can guess where it is leave a comment, tweet, facebook message or else and I will pick from the correct answers. The winner gets a one hour chat with me for IT consulting on whatever issue (no guaranty that I can help though..).
Yesterday I was introduced to Hogan.js the templating library from twitter. It was new to me so I had a look at the documentation and I think I know when I would use it.
And when I would not.
Yesterday I was asked if I miss programming now that I quit being a developer or architect and instead joined the client side and I have to say that for about 5 months straight I haven’t written a single line of code.
Not even for private joys.
After long discussions we managed to reduce our requirements to a minimum. The project was ready to go.
Then I got a phone call.
Our development team is working on multiple titles in parallel and their work includes daily business stuff like small features and bugfixes as well as projects. If a project is a little bigger we try to organize a fixed sub-team for it.
And lock them in a room!
During the last couple of days I installed some more WordPress plugins to see if they would have any positive effect on the traffic. I was mainly focussing on social media integration and cross linking.
Here’s the list of plugins I tested.
There are three things to consider to any given IT project: scope, time and quality. You can only fix two of them and the third one need to be able to scale to allow for the others. You can run out of scope, out of time or end up with dirty code. Your choice. That’s why we want to use agile methodologies like Scrum.
Most of the time quality will be the loser..
Following yesterdays post I had a little discussion with a colleague of mine who is a scrum master and working in a Scrum project himself. In the end we argued about whether it’s ok to change the Scrum process to fit your working situation or whether it should be the other way around.
Needless to say I prefer to bend the process.
In a currently running project we had our first sprint review meeting yesterday. Me as a product owner, the scrum master and the team. We found some good things and some not so good ones.
Then we changed what so far we thought was Scrum.
I blogged about RIM before and I still think that they will either cease to exist or completely change their business to turn things around. In comments on financial magazines I often read similar statements.
The ideas what RIM should do are divided.