If you answered “yes,” then you might be interested in learning more about one of the hottest project management topics in discussion over the past few years: technology teams that have tight turn around requirements will often move away from the traditional “waterfall” software development approach to an “agile” approach. Tweet This Agile & Waterfall Methodologies is a great overview of the two.
A few years ago, our development team got bit by the “agile” bug and have gone all-in, using this methodology to quickly iterate our product set and the results have been impressive. We’ve been able to quickly iterate on some major products that have lead to some major wins for our technology team including including recently being named by the CIO 100 Award for our Phoenix project.
Along those lines, our Head of Technology, Aaron Stibel, recently sat down with staff from The Enterprisers Project where he answered questions on how our organization has benefited from going “agile” for our technology development. The kinds of questions he was asked included:
- The shift from traditional waterfall software development to agile seems to be in full force. Are you noticing it in your travels?
- You’ve been using DevOps in your organization to drive faster delivery for at least a year. What has it been like to live through that transition?
- How do you look at measuring the other impacts of a DevOps group and Agile development?
And while we’re a bit biased, we think most business owners looking to get more value out of their development team will find value in his insights.