Computer programming was their passion<\/strong>. Their mastery<\/strong> in computer programming turned later into a profession, fulfilling their need for self-esteem and self-actualisation.<\/p>\n\n\n\n
They were leading the way <\/strong>in the nascent Software industry shaping and inventing a new profession. Just like they will do during the mobile and the web and the Internet revolutions, the cloud revolution, and now the AI revolution.<\/p>\n\n\n\n In the late 90s, they faced a software industry in pain<\/strong> because software development was growing from an individual discipline into a complex team discipline, organisations of the time were not ready for it, therefore too many software development projects were failing.<\/p>\n\n\n\n At that time Agile pioneers thanks to their curiosity<\/strong> were natural innovators, and critical thinkers, with a continuous improvement mindset so they were best placed to search for new and better ways of doing things and keep improving. Their involvement in the 2000s in the new open-source movement made them experienced also in collaboration and co-creation<\/strong>.<\/p>\n\n\n\n Later the software industry knew an exponential growth, as did the popularity of Agile after it crossed the chasm around 2010. This lead to a massive talent shortage. To facilitate the onboarding of new workers the role was unpacked into siloed roles<\/strong> each one taking care only of one aspect.<\/p>\n\n\n\n Basic training and certifications were put in place to make up for the lack of depth and breadth of experience<\/strong> in software development.<\/p>\n\n\n\n Overcomplicated prescriptive scaled frameworks were used to guide novice Agile practitioners<\/strong> with less hands-on experience.<\/p>\n\n\n\n What the new Agile practitioners have in common with the Agile pioneers tho’ is the desire to put people at the centre<\/strong>, teamwork<\/strong>, and the need for psychological safety<\/strong>.<\/p>\n\n\n\n Do these characterisations of the early and late practitioners match your experience? \n\t Many have already explored the trajectory of Agile adoption, the changes in sentiment toward Agile, and the recent challenges.<\/p>\n This is a new look at how the population of Agile practitioners changed over time.<\/p>\n","protected":false},"author":2,"featured_media":3213,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-3209","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-lean-agile"],"_links":{"self":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts\/3209","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/comments?post=3209"}],"version-history":[{"count":13,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts\/3209\/revisions"}],"predecessor-version":[{"id":3229,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/posts\/3209\/revisions\/3229"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/media\/3213"}],"wp:attachment":[{"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/media?parent=3209"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/categories?post=3209"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.smharter.com\/blog\/wp-json\/wp\/v2\/tags?post=3209"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
Supported by their background they were constantly questioning the foundations of what they were doing in order to stand on solid ground to enable the next leap.
Because of their insatiable curiosity, these geeks always put progress over job security<\/strong>, they were rebels and natural change agents.<\/p>\n\n\n\nThe age of exponential growth<\/h2>\n\n\n\n
Market demand and good salaries attracted a new diverse group of people willing to learn the ropes.
Unlike the pioneering geeks and rebels, many of these aspiring Agile practitioners were less inclined to question<\/strong> what they were taught and told to do and to have their beliefs challenged. Many had the legitimate desire and need for job security, which is something which change agents cannot enjoy, but they were not told about this.
Pioneering software developers and Agile pioneers used to do all the work from talking to customers to doing the analysis, design, development, testing and often support while taking care of the whole tech stack.<\/p>\n\n\n\nYour reflections<\/h2>\n\n\n\n
What consequences do you draw from these characterisations?
Get in contact and let me know!<\/p>\n\n\n\n
\n\n\n\n![\"\"](\"https:\/\/www.smharter.com\/blog\/wp-content\/uploads\/nourish.png\")
<\/figure>\n<\/div>\n\n\n\nElevate your Agility.<\/h3>\n\t
\n\tSee how we can help.\n\t
\n\tYou, your team, your organisation.\n\t
\n\t
\t\n\t<\/p>\n\n\t