Say What?

Why We Need Daily Scrums

2011-04-15T15:48:00.005+08:00

For me a scrum team's goal is to be a self managing team. Not knowing what your teammates are up to is not very helpful in achieving this goal. I know that there are other people that aren't comfortable with meetings. That is one of the reason why a daily scrum is held in less than 15 mins. and usually standing up.

Daily scrums keep you and your teammates up-to-date. Yes, you may easily tell your teammate that you need help. But what about those moments that you end up being blocked because you don't know who could help you. Scrums help mitigate this risk. You'll never know that the least person you thought could help you might actually know the solution.

I prefer having the scrums during the start of the day. Why? Because I don't want my focus to be broken in the middle of the day. And I want to respect the time of my teammates. Respect is key for me.

Given that our projects doesn't have the luxury of being co-located, this daily scrum helps in making the team's connection stronger. They need to be comfortable with each other despite the distance. Its almost an impossible goal but for me, daily scrums could help ease the tension.

At the moment, these are my main reasons as to why we need daily scrums. How about you? Why do you do them?

** Also posted in http://info.exist.com/blogs/bid/47363/Why-We-Need-Daily-Scrums

Indulging Open Source Technologies

2009-08-05T11:01:00.006+08:00

Its been more than a year since I last wrote here. And I must say that since then I have continued to learn new stuff and was really amazed by the technology I've been using.

I am now working for G2iX Philippines and since day 1 has been FULLY exposed to open source technology. I've used and played around with open source tech like Spring, Hibernate, Maven, etc. But I have not fully indulged myself in them.

This company hasn't only used open source technologies but has encouraged their employees to really bring back something to the community. It is through them that I have learned what "committership" is. The place is just full of committers, PMCs, tech evangelists, etc. :)

=============
It is only now that I fully appreciate Maven and started to really care about what my pom.xml contains. Keeping it clean and streamlined. I know that I still haven't fully exhausted the functionality that Maven has to offer but with my current tasks and further working with this company, I hope to learn more.

For the past months, I have dealt with Liferay, Xalan, Rome, Lucene, Spring MVC, and now JMS Remoting. And I hope I could share stuff as I go along. I'll try to post more!

Test Driven Development: A Short Story

2008-07-09T16:09:00.004+08:00

Last Sunday, I scheduled myself to prepare for my next training assignment which is mostly related to Test Driven Development (TDD) and Unit Testing. I know how to do it but teaching it and making the participants appreciate TDD is a whole different thing for me. After browsing through the slides for the nth time, nothing came to me as to how I would attack this topic. Thankfully, Franz is at the office as well. He gave me something to read from The Craftsman. Its just a short story but gave a clear approach on how to teach TDD.

Come Tuesday that week, I was so excited to try out the approach I've learned in the story. I started by explaining the development approach that we will be learning for that day. I asked one student to be the typist and reminded that everybody is expected to share their thoughts on the application.

We used the same problem used in The Craftsman, they are to get the prime factors of a certain number. So we started writing their very first test. The test scenario is called testTwo which checks if the length of the array is correct and the value of the array is indeed 2. Of course their test failed after running it, so I asked them to write the simplest code that would pass the test. After writing down their solution, I was surprised it’s the same solution in the story that I was simulating. So I just continued by asking them to write the next test which would get the prime factors of 3. At this point, they're already making fun of me by saying "Oh we'll be testing the whole day, we'll be writing test for 2-1000!" What made me freak out is that their reactions and solutions are very similar to the story. The main deviation would be the additional/minor information I added during the process such as best practices in testing and seeing it LIVE! I never thought that the story predicted the events in such accurate points.

At the end of the exercise, the participants have completed the events in the story. They enjoyed the interactions that they had during the exercise and were really happy with what they just learned, AND that System.out.println() is not the only testing tool around.

Trying out Google Sites

2008-03-04T17:45:00.004+08:00

I've been playing with Google Sites lately and found it easy to set-up and customize. It is quite similar with the collaboration tools that we use at Orange and Bronze. Some thoughts...

Subscribing to the site/pages in the site. What's great about this is you get notified by the changes that is happening to your project. I'm not sure if the one we are using could be tweaked to do this.
Customized issue tracker. Yes, they do have this. You could easily add, delete and modify components of the issue tracker that you want. You can even add a deadline field which allows you to attach a date to a certain issue. However, you don't have the grouping of issues to milestone deadlines. Human error in giving a deadline past its milestone deadline is quite high. You also can't get reports as to how much of the issues in a particular milestone has been successfully resolved.
Include Google Docs in your site. I liked this feature purely because of my documentation quirks. Since collaborators can edit the same document simultaneously, the changes are reflected in your site. You could also collaborate spreadsheets! Aside from that, you wouldn't have the problem of transferring tables from the wiki to a .doc file. I've tried this before and it was hell. I believe our PM/BA dept. will benefit from this feature.
Uploaded docs are version controlled. Documents uploaded to the site are versioned automatically. What I didn't like is I can't download and upload multiple files. I was looking for a "Download all attachments" function, the one just like in Gmail, but I found none.
Remind your team with the countdown feature. With these feature, it is easy to remind your teammates about an approaching deadline! What's just sad about this is even if the deadline has passed, the countdown is still there (just with a 0 days left notice).
Announce what you want. The announcement page is similar to a collaboration of blogs. You don't need to go anywhere to share what you've done or learned with the project.

These are some of the features that I have checked out. I believe Sites is a good option for online document collaboration. Another colleague of mine have tried this out and wrote down his insights as well, do check it out. :)