Advanced Agile – maybe not
Document Actions
From the beginning of this blog (and more recently on my internal company blog), I've spent more time writing down thoughts on more advanced Agile topics such as what to do once a team is semi-successful with an Agile process. However, over the past couple of months, I've encountered a growing number of questions about how to get started with Agile, both from within the company and from outside. This surprised me in some ways because I've been thinking there are fewer books written about advanced, large Agile projects, but converting over to this new process for software development is still a challenge for many. What appears to be missing is the incentive for those to make the change, so here a few ideas to use as ammunition in convincing those in your group to seriously consider the change to an Agile-based process.
- Meeting dates will become the norm.
- Customers will enjoy higher quality and more of the features they really need.
- The engineering team will experience fewer sleepless nights trying to meet unpredictable timeframes.
- The Agile process is a welcomed addition to a software professional's experience portfolio. (I predict having this experience will be resume requirement in 5 or less years.)
- And if that's not enough, try this timeless line: "Come on, try it. All the cool kids are doing it." (i.e. Google, Microsoft, Yahoo, etc…)
_____
tags:
Forgot your password?
New user?
