{"id":391,"date":"2024-04-22T10:44:14","date_gmt":"2024-04-22T09:44:14","guid":{"rendered":"http:\/\/localhost:8082\/?p=391"},"modified":"2024-04-29T10:46:13","modified_gmt":"2024-04-29T09:46:13","slug":"being-agile-not-certified-agile","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2024\/04\/22\/being-agile-not-certified-agile\/","title":{"rendered":"Being agile, not certified Agile"},"content":{"rendered":"\n
I’ve never done any formal agile training, and I don’t intend to start now.<\/p>\n\n\n\n
The truth is, agile training just wasn’t around when I started out in the 2000’s. Instead, I worked in a development team that embraced Extreme Programming<\/a> by following the rules and practising the values, and later on, I used to literally carry around a printed copy of the Scrum Guide<\/a> and spend my spare time reading Jeff Sutherland’s Scrum Papers<\/a>. Lots of experimentation happened along the way, not all successful. But it was a thoroughly exciting time.<\/p>\n\n\n\n Fast forward to 2019, and I actually wrote a blog post about the day I removed agile from my CV<\/a>; however, that was largely a reactionary statement to the blossoming certification mill ie. the proliferation of one or two-day bootcamps with a trivial multiple-choice exam to become a ‘certified’ Scrum Master or Product Owner. Setting aside that market perversion, the benefits of agile are still very clear to me, and alive and well in my \u2764\ufe0f today.<\/p>\n\n\n\n