2013: A Retrospective

I really like the Scrum retrospective format that I used last year so I decided to use it again this year ๐Ÿ™‚ One of the things that I really like about Scrum is the focus on continuous improvement. The retrospective is one the easiest way to allow me to focus on the things I accomplished last year and also think about the changes I want to do for the following year.

Year in Summaryย 

Here are the things that stuck out to me when I think about 2013.

  • I wrote more in 2013. Writing is one of those hard ones as it doesn’t come naturally to me. However, I find that writing helps me with my thought organization and also helps me re-focus. There have been a number of changes in terms of my writing last year – for one, I am starting to split up my writing on 3 separate blogs instead of just thekunit.com. The breakdown of my blogs are as following:
    • thekunit.com – my personal thoughts and experience on my various interest such as technology, gadgets and personal leadership
    • firsttiger.com – thoughts and experience when it comes to helping start ups and other technology organizations.
    • redfireant.com – my experience on building products
    • kelvinkang.com – my lifestream that summarizes my various activities on the internet
  • I had hoped to give back more by sharing more of my experiences. While I haven’t shared as much as I feel as I should have, I feel that what I have started to do last year is a start. My blogs on firsttiger.com were written primarily to share the things I learned while working at WordJack. I also started to also create summaries and blogs on more tactical things such as common git commands that I often forget and Ubuntu tasks that I find myself using often.
  • I have definitely written more code in the last 12 months that I have had in the previous 8 years before that. It’s been something that I’ve been itching to do and I have to say that I really enjoy it. Even though I’m not expected to code for my job, I have often found that being current in technology is critical to be a technology leader given how quickly technology is evolving. I have started to really enjoy the BDD style of testing especially using Cucumber. It’s a fantastic way to prove product correctness.

Keep Doing

  • Keep writing more code
    I’d like to take it up a notch this year and start putting some of my code into a production environment. If not for my day-to-day work, then definitely with my learning group as a way of validating the work I’ve been doing.
  • Keep writing more blogs
    I’d like to step it up so that I’m writing and publishing a blog every two weeks.

Stop Doing

  • Being so busy that I’m not productive
    It’s a bit ironic but I found myself being so busy at times that I wasn’t productive. I was spreading myself too thin and focusing on everything but resulted in getting very few things accomplished.

Start Doing

  • Getting out more
    One of my my favourite things to say is that “it’s hard to innovate in a shoebox.”ย I need to expand my horizons more and touch base with at least one other person who is in a start up every month. The goal is to continue to learn and ensure that I’m doing the right thing by having a network of people that I can continue to learn from.
  • Plan more, work less, accomplish more
    Benjamin Franklin once said –ย โ€œIf you fail to plan, you are planning to fail!โ€ In order to accomplish more, I need to fight my knee jerk reaction of wanting to do everything but really focus on what’s both urgent and important.

Happy 2014, Everyone!