Last September 2 and 3, I was privileged to have been sent to an Agile Training at Sofitel. I met a lot of good people wanting to implement some change by promoting transparency and successful product iterations.

Scrum is not a new thing for me, but it was well worth it to strengthen what I already know and try to get some help from the scrum masters there too on some problematic situations I’ve encountered. It was fun, and I got to share some of my experiences too. Gained some friends in the process and enjoyed myself during the training. Found below is a photo of Franchere Chan, myself, and Allan Tan.

Yukka Lindstrom and Emerson Mills were really good trainors and weren’t boring too! Emerson’s endless stream of stories to share helped in understanding what scrum practice would be and what it can’t be for a team, a project or a process.

Overdid myself again!

Attendees of the Certified Scrum Master training course range from software developers, programmers, and project managers of the IT industry’s leading companies who are looking to gain a deeper understanding of Scrum. According to attendees, many of their clients are either already using the methodology or are interested in using it with the goal of increasing productivity. The last training course was attended by such companies as Ideyatech, SQME Professional, ProV International, HP NexUS, and Macquarie. By far, Scrum seems to be getting good results, as Maricris Nonato of DevEx attests. “I think it’s working well for us,” she claims. “The turnaround of every sprint cycle is good. By far I haven’t had a failed sprint yet. And our stakeholders are happy. You know the transparency thing that scrum promotes is very helpful for them. Scrum is really working out for us.”

Read more here: http://codelean.com/en/News/10-09-27/Scrum_Practices_Gain_Popularity_in_the_Philippines.aspx

Visit Codelean to find out more about Scrummaster Training.

I think this is by far the best, though vague and ambiguous poetry I’ve ever seen and I loved it!

It puts the technical context of programming in a development cycle into lay context. I stumbled upon this lovely piece of work, through CodingHorror’s article entitled: Version 1 Sucks, But Ship It Anyway

As we know,
There are known knowns.
There are things we know we know.
We also know
There are known unknowns.
That is to say
We know there are some things
We do not know.
But there are also unknown unknowns,
The ones we don’t know
We don’t know.

Makes me want to keep in mind that knowledge in programming is quite volatile as it comes to real world problems to be solved, and that no accurate solution is definite across a period of time. The unknown is really a part of the process.