Monday, May 11, 2009
Integration
If you work in the IT-industry "Integration" is one of those buzzwords you just can't avoid running into. Intregration can however be found in nature as well. Look at this tree just outside my office which takes this aspect to a whole different level :) And yes, it is one tree with two different flowers. It's somekind of gardener-trick. Pretty cool ey?
Saturday, May 9, 2009
Certified Scrum Master
Earlier this week I attended a Scrum Master course in order to become a so called "Certified Scrum Master". During 2 days in a workshop like manner we got the opportunity to discuss software development from different points of view and also do some hands-on exercises.
In reality, the principles of Scrum are very easy. You have the Product Owner, who's responsibility is to create and manage the Product Backlog. The Product Backlog is a prioritized list of all functions which are wanted in the product. This is a living document and changes as work progresses.
Next we have the The Scrum Master who's responsible for guiding and protecting the team, i.e a technical project leader of some sort (although it's not correct to use this term).
The Scrum team consists of +/- 7 people preferably with different skills such as programmer, tester etc.
The Scrum framework itself centers around a Sprint. A Sprint is a repetitive cycle, ~30 days, in which the team does its work. It starts with Sprint Planning in which the team chooses and estimates the amount of work which is to be done in the Sprint. During the Sprint the Scrum Master holds Daily Scrum meetings with the team and asks 3 simple questions:
1) What have you done since yesterday?
2) What will you do today?
3) What is hindering you?
During the Sprint no one is allowed to disturb the team and come with additional work requests.
The Sprint ends with a Sprint Review in which the product increment is demoed and discussed. This is followed by a Sprint Retrospective which functions as a lessons-learned session.
This all sounds very simple. Is Scrum some magical "fix-it-all" method then? Well no. However, Scrum adheres from the only certain thing about software engineering: That we do not know what the product will look like in the end. So if the "target" is moving then it is appropriate to adjust your work accordingly along the way. This is a very different approach from the more traditional Waterfall model in which development is looked at as iterative, but straight-forward phases such as planning, design, coding, testing and integration.
The more realistic view on how software development works in reality is the main reason why I believe Scrum may be a good choice. Continual adaptation to the current circumstances as well as the opportunity to vent all potential problems. This is the aim of the Daily Scrums. Any problems and hinders needs to be brought to the Scrum Master for him/her to fix.
Although I now have a new title to use on my CV and more knowledge about Scrum it will take actual experience before I can say much more about it. Scrum may not be appropriate in all organizations and projects, but I intend to give it a try in my current work and see where it will take me. I'm looking forward to it!
In reality, the principles of Scrum are very easy. You have the Product Owner, who's responsibility is to create and manage the Product Backlog. The Product Backlog is a prioritized list of all functions which are wanted in the product. This is a living document and changes as work progresses.
Next we have the The Scrum Master who's responsible for guiding and protecting the team, i.e a technical project leader of some sort (although it's not correct to use this term).
The Scrum team consists of +/- 7 people preferably with different skills such as programmer, tester etc.
The Scrum framework itself centers around a Sprint. A Sprint is a repetitive cycle, ~30 days, in which the team does its work. It starts with Sprint Planning in which the team chooses and estimates the amount of work which is to be done in the Sprint. During the Sprint the Scrum Master holds Daily Scrum meetings with the team and asks 3 simple questions:
1) What have you done since yesterday?
2) What will you do today?
3) What is hindering you?
During the Sprint no one is allowed to disturb the team and come with additional work requests.
The Sprint ends with a Sprint Review in which the product increment is demoed and discussed. This is followed by a Sprint Retrospective which functions as a lessons-learned session.
This all sounds very simple. Is Scrum some magical "fix-it-all" method then? Well no. However, Scrum adheres from the only certain thing about software engineering: That we do not know what the product will look like in the end. So if the "target" is moving then it is appropriate to adjust your work accordingly along the way. This is a very different approach from the more traditional Waterfall model in which development is looked at as iterative, but straight-forward phases such as planning, design, coding, testing and integration.
The more realistic view on how software development works in reality is the main reason why I believe Scrum may be a good choice. Continual adaptation to the current circumstances as well as the opportunity to vent all potential problems. This is the aim of the Daily Scrums. Any problems and hinders needs to be brought to the Scrum Master for him/her to fix.
Although I now have a new title to use on my CV and more knowledge about Scrum it will take actual experience before I can say much more about it. Scrum may not be appropriate in all organizations and projects, but I intend to give it a try in my current work and see where it will take me. I'm looking forward to it!
Monday, May 4, 2009
Web 2.0 in 5 minutes
Since I've entered the world of blogging and social media I have begun to read more about its impact on the way we live our lives online. This video shows in an easy and fun way what it's all about.
Web 2.0 in 5 minutes by Michael Wesch
Web 2.0 in 5 minutes by Michael Wesch
Sunday, May 3, 2009
Evaluation framework for Open Source CMS
The above title is the subject of the master thesis which I am writing currently. In little more than a month I will need to present a complete paper for judging. Since I am working fulltime during weekdays it leaves evenings and weekends for this fun activity. Tired? Yes. Interesting? Yes. It was when I came in contact with Drupal last year which I began to see the potential of CMS's. Now I am also looking at Joomla and Wordpress and trying to learn as much as I can. By drawing on the experiences of others and the theories of CMS and usability I hope to come up with a framework which can be used when choosing between different Open Source Web-based CMS's.
Studying requires a lot of books
Studying requires a lot of books Saturday, May 2, 2009
IBM on Jeopardy
IBM have created a computer which is going to compete in the television show "Jeopardy". Talk about artificial intelligence! The "IBM contestant" will have to obey the same rules as its human competitors i.e respond with a question, no internet connection or other kinds of aid. In addition it will need to be able to pick up on verbal speech variations such as irony, jokes etc. I am really looking forward to seeing this thing in action!
http://www.nytimes.com/2009/04/27/technology/27jeopardy.html
http://www.nytimes.com/2009/04/27/technology/27jeopardy.html
Subscribe to:
Posts (Atom)
Posts
