Gartner ITxpo

Prepare now for future changes in development teams' makeup

Get ready for big changes in application development teams as we know them. Greater emphasis on the quality of the user interface and frequent updates of mobile applications are just some of the forces driving changes in development team composition, according to James Duggan, vice president for research at Gartner Inc.

In ways, the present moment resembles earlier shifts in IT development paradigms, such as those in the '90s when IT moved from a focus on the mainframe and procedural languages such as American National Stardards Institute (ANSI)

    Requires Free Membership to View

COBOL to a new focus on client-server systems and object-oriented languages such as Java and C#.

In those days, developers had to be re-educated, and the re-education didn't always take. Some highly skilled developers didn't make the jump to object programming and new development team structures.

Big change may be due again. A point at issue, according to Duggan, is that most enterprise application development groups need new talent to effectively work to develop mobile applications or social media. "I don't find a lot of mobile skills in enterprises," he told an audience last month at Gartner's ITxpo in Orlando, Fla.

"There are a lot of new things you are going to have to train for. That is a situation we haven't been in for a decade or more," said Duggan. "We need to push people into new patterns."

Mobile and social applications have expanded the user base and given more influence to selective consumers. That may hinder some developers.

"There are things like user experience that are dramatically new, and we are probably not going to master them," said Duggan. He said enterprises will often have to go outside the company to hire programmers skilled in user interface dynamics and will have to live with the fact that these programmers may leave for other companies after a while. He recommended team managers be sure to address the usability of applications at the design state -- not the build stage.

Changed application life cycles will likely require another round of analysis of legacy apps within organizations. He recommended that IT portfolio managers move aggressively to offload burdensome applicationsand drive out legacy inefficiencies in order to deal with the new types of applications.

Follow us on Twitter at @SearchSOA.

This was first published in November 2012

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Expert Discussion

TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.