InfoQ

News

Predictions: The Changing World of IT Work

Posted by Deborah Hartmann on Feb 17, 2007 11:08 AM

Community
Agile
Topics
Careers ,
Agile in the Enterprise
Tags
Planning ,
Remuneration and Incentives ,
Self-organizing Team ,
Outsourcing ,
Diversity in Teams ,
Performance Evaluation ,
Offshoring
We’re working in a world of constant change.  In his recent Datamation article, James Maguire noted the difficult challenge of staying employed in an environment in which the rules are continually rewritten.  Looking for a forecast to help workers plan ahead, Maquire spoke with Gartner analyst Diane Morello, author of a study looks at the tech workplace through 2010, The IT Professional Outlook: Where Will We Go From Here?  The article presented 5 predictions for those thinking about career directions as they look toward 2010.

1) 60% of people affiliated with the IT organization will assume business-facing roles.
This is a shift from about 30% today. The IT worker who’s strictly focused on technology is going to be a rarer bird.  “In many of the companies that we talk to, there’s a clear demand from the business that the IT organization become more business savvy.”  Paradoxically, the same report says that “there’s also kind of a subversive demand within IT organizations that businesses become more IT savvy.”

2) 30% of top technology performers will migrate to IT vendors and IT service providers.
Currently, the overwhelming majority of IT workers work for companies that *use* technology, but this is going to change.  IT pros who don’t want to delve into business should look to IT service providers to find more technical jobs.

3) IT organizations in mid- and large-sized companies will become at least 30% smaller.
Outsourcing and automation will shrink IT departments. The impact could be enormous.

4) 10% to 15% of IT professionals will drop out.
Staying employed in turbulent waters can wear down even the most resilient soul.  Some give up and change careers - and a larger proportion of these will be women, a trend already in evidence.

5) 70% of leading-edge companies will seek and develop “versatilists” while de-emphasizing specialists.
A versatilist is a staffer with enough multi-faceted expertise – across business, technology and inter-personal skills – to handle several areas of responsibility at once.  In Agile software, another term for this is the generalizing specialist.

Related Sponsor

VersionOne is recognized by Agile practitioners as the leader in Agile project management tools. Companies such as Adobe, BBC, CNN, Dow, HP, IBM, Sony and 3M have turned to VersionOne to help deliver greater value to their customers.
Old guard vs new guard by Vic Cekvenich Posted Feb 18, 2007 5:30 PM
Re: Old guard vs new guard by Alexandre Poitras Posted Feb 19, 2007 2:39 AM
Re: Old guard vs new guard by Deborah Hartmann Posted Feb 21, 2007 3:23 PM
  1. Back to top

    Old guard vs new guard

    Feb 18, 2007 5:30 PM by Vic Cekvenich

    Old guard, brick and morta companies will shrink by more then 15%, and during shrinking they would offshore to accelerate the shrinking. New guard companies, ex: google, win market share growth via IT. In the past every time there was gloom about replacment, there was another company to hire and then some. I know in San Francisco, there is a shortage of software engineers. To test this, please put your resume on Dice and say you live in the area, and see how many people call you. .V

  2. Back to top

    Re: Old guard vs new guard

    Feb 19, 2007 2:39 AM by Alexandre Poitras

    I know in San Francisco, there is a shortage of software engineers. To test this, please put your resume on Dice and say you live in the area, and see how many people call you. .V
    Same in Montréal.

  3. Back to top

    Re: Old guard vs new guard

    Feb 21, 2007 3:23 PM by Deborah Hartmann

    Interesting, I wonder if this mainly a big-US-city effect then? I know from personal experience that Montreal, though large, tends to have different hiring trends than the US and sometimes Toronto. And a recent trip to Portland suggests to me that there are more of the newer, leaner organizations out there (not "old guard" as Vic suggests). Perhaps the predictions in the article don't apply across the board. I do think I'm seeing the effect mentioned in Toronto.

Educational Content

Bindings, Platforms, and Innovation

This presentation focuses on the Internet and separating myth from fact, history from the future, and the mundane from the imaginative. Bob Frankston presents a vision of what could and should be.

Orchestrating Long Running Activities with JBoss / JBPM

This article explores the use of JBoss and jBPM to implement design solutions that effectively address the issue of orchestrating long running activities.

Neo4j - The Benefits of Graph Databases

This presentation covers the use of graph databases as an optimal solution for data that is difficult to fit in static tables, rapidly evolving data or data that has a lot of optional attributes.

Realistic about Risk: Software development with Real Options

This session introduces Real Options and shows how it can help in running your project. Real Options is a decision-making process that can be used to manage risk.

Communication Flexibility Using Bindings

This article discusses the use of bindings on services and references (including the instance of non-configured bindings) as the means to implement SCA communications in a Web and SOA environment.

Writing DSLs in Groovy

After a short introduction to DSLs, Scott Davis plays with the keyboard showing how to approach the creation of a DSL by typing working snippets of Groovy code that get executed.

Scaling Agile with C/ALM (Collaborative Application Lifecycle Management)

IBM Rational and InfoQ present, Scaling Agile with C/ALM, an eBook showing organizations how to become “finely tuned software delivery machines” by enabling team integration and scaling.

Concurrent Programming with Microsoft F#

Amanda Laucher presents a real life enterprise application written in F#. She shows actual code snippets, explaining design decisions and suggesting how to use some of the F# constructs.