Seasoned Technologist and Serial Entrepreneur | AI Strategist | Seed Investor | CTO | Championing Growth in AI-Enabled Startups
Agile software projects, where teams that include business users and engineers iteratively work on features, recently have developed a 3X higher failure rate. But are teams really using the intended agile methodology? The core problem with the usage of agile today is that it has become an excuse to avoid focus and change plans on a semi-regular basis, because generally agile projects define priorities on anywhere from weekly to monthly timelines. But, the original precepts of agile are based on engaging the user in the design and decision-making process, not just a scheduling mechanism. While that is still partly true, most projects just run off an infinite list of things the team would like to do that may or may not have a broader correlation and vision. And that's where agile tends to fail: when teams abandon a strategic project vision for the sake of pursuing a shiny new feature because the scheduling mechanism of agile allows it. So instead of allowing agile to be a built-in distraction mechanism, use it as intended: a heartbeat to ensure ongoing alignment on the strategic project vision. https://buff.ly/3Rqb9L8
Great point David, totally agree. It’s very easy for a team to “agile” themselves in circles while they burn all their time and budget. You still need to have a plan
Founder at Data Bakery – Custom Software Solutions
4w💯 - An interpretation of this statistic from another angle is that Agile encourages building without a focus on design and architecture. Could you imagine building a custom home (one of the best analogs for a custom software project) with a "we'll figure out the details as we go" approach?