Happy New Year!! Here are some technology predictions for 2009 that are worth a read for software developers, business analysts and database developers who want to position themselves for success in 2009:
1. Pay attention to Social Media says CapGemini:
“2009 will be the year when use of social networking tools within companies will be the talk of the town. Yes, it has been around for a while but to be honest, nothing much has really happened apart from that Serena Software uses Facebook internally.
So when our global heads of Capgemini Consulting visited Sweden office last week and started talking about the power of social networking only five minutes into the talk I felt that something had changed. For the better. Substantial growth is predicted in web 2.0 for the enterprise within the next five years.”
2. The economy looms large says PCWorld:
“Ultimately, economic conditions will play a huge role in how 2009 pans out for the developer community. When customers aren’t buying, tool vendors don’t innovate — so don’t expect many groundbreaking new technologies to debut this year.
Among enterprise customers, tightening budgets are likely to put the kibosh on many an ambitious new project. But smart companies will realize that process automation is one of the best ways to reduce costs in any business.
Now may actually be the ideal time to revisit old software schemes that got shelved back when staffing budgets were flush. Layoffs and hiring freezes will mean there are fewer developers to go around, however, which could make smart projects infeasible for the time being.”
3. Agile development is a must says Barry Gervin:
“Many of my customers began large-scale re-writes of their key software assets in 2008, many of them against my recommendations. For most of my key customers in 2008 and into 2009 I’m an advocate of providing incremental value in short iterative releases, not major re-writes that take 6+ months to develop.
Even if your application is written in PowerBuilder 6 or Classic ASP, avoid the temptation to rewrite any code that won’t see production for 4 months or longer. We can work towards componentized software by refactoring legacy assets and providing key integration points so that we can release updated modules towards gradual migration.
It is difficult for software teams in this economy to produce big-bang, “boil the ocean”, build cathedral type projects. We simply can’t predict what our project’s funding will be in 4 months from now, or if we’ll be owned by another company, scaled down, out sourced or just plain laid off. That is of course unless you work for the government.
Government spending will continue if not increase in 2009, but still, try to spend our taxpayer money wisely by delivering short incremental software releases. It allows you to build trust with your customers, mark a line in the sand and move onward and upward, and let’s you move quickly in times of fluid business requirements and funding issues.
Incremental, Value-Based software development isn’t easy.
It takes lots of work, creative thinking, and much interop and integration work than one would prefer. It might easily seem like an approach that costs more in the long term, and in some cases you could be right. But if a company has to throw out work in progress after 6-8 months or never sees the value of it because of other changing business conditions, then what have you saved? Probably not your job anyway.”
For more technology predictions for 2009, Bob Stumpel has an impressive compilation of tech predictions from around the web here.