I was rebooted this week and that inspired me to write a new blog post in a long time. \u00a0I have been ![](\"https:\/\/upload.wikimedia.org\/wikipedia\/commons\/thumb\/6\/68\/Human-gnome-session-reboot.svg\/2000px-Human-gnome-session-reboot.svg.png\")
itching to write about tech and ideas that I have been learning since joining my latest job (checked my LI profile to see that) but nothing had\u00a0motivated me enough just yet. \u00a0\u00a0My co-workers were also subliminally influencing me on being more active due to their highly active blogging\/social media behavior. \u00a0My current job has presented great opportunities that have really rekindled a passion for tech for me and I always did love working.<\/p>\n
This week things changed. \u00a0I went through a training that I was not keen on. \u00a0So here goes my first post in a long time… (bear with me)<\/p>\n
This week I went through Agile training conducted by none other than Ken Rubin<\/a>\u00a0and to be very honest I was skeptical going into it. \u00a0“Why you ask?” \u00a0Well, I consider myself be an Agile expert. \u00a0I have been executing agile in various ways (as it evolved) for over 10 years and have executed multiple successful agile transformations\/transitions. \u00a0I have a good idea of what works and what doesn’t. \u00a0I recently presented on Leading Agile Transformation at AgileCamp<\/a> in Newark, NJ. \u00a0Yes – I am the only one without a profile pic (doh!). \u00a0I had the privilege of sitting at an executive roundtable on Agile where I got my first exposure to Ken’s Agile views. \u00a0We had very similar views.<\/p>\n After attending 3 days of grueling training on Agile that was conducted at the highest level by Ken, I walked away learning a few key things. \u00a0We learned the basics and I found myself realizing that this was valuable not from an education perspective for me but from a reboot perspective.<\/p>\n Reboot? \u00a0Yes, the same reboot that resets\/restarts a computer or as we now know affectionally with almost every darn super-hero movie – it is stripping a concept down to its core and rebuilding it back up. \u00a0I prefer the latter to describe my experience this past week.<\/p>\n I started to realize that I was allowing my past experiences, which have built up my Agile knowledge and prowess, to create an implicitly biased view of Agile for me. \u00a0I took a few notes but primarily kept focusing on “rebooting\/resetting” my mind. \u00a0My key takeaways:<\/p>\n (Yes I did not give full details\u00a0above as I wouldn’t be able to do it justice the way Ken did)<\/p>\n I walked away with an appreciation that I needed this reboot to ensure I apply Agile properly. \u00a0Not with a bias but taking the framework and rebooting it for the current needs while definitely borrowing from the past. \u00a0I need to start from the foundation (“the base framework”) not from the\u00a0biased version of it from my career so far and then add my applicable experiences or “lego blocks” if you will appropriately. \u00a0Eliminating the bias was important – REBOOTED<\/strong>! \u00a0Excited to apply this going forward.<\/p>\n What did learn new? I did learn about SAFe<\/a> (Scaled Agile Framework) at a detail level (only had known about it at a cursory level) and how in truly agile fashion, companies have taken the base framework as just a guideline. \u00a0Companies have adapted and customized it to their needs. \u00a0The Lego Case Study <\/a>(as pointed out by Ken) is a great example of this.<\/p>\n\n