Home Software Engineering IT Services Maturity of an IT development group
07 | 02 | 2012
Notizie flash

A career as a Cobol programmer might not be as sexy as slinging Java code or scripting in Ruby, but if you buckle down and learn hoary old Cobol, you could land one of the safest, most secure jobs in IT.

Analyst reports indicate that Cobol salaries are on the upswing. The language is easy to learn, there's a healthy demand for the skills, and offshore Cobol programmers are in short supply -- plus, the language itself holds the promise of longevity. All that loose talk about mainframes going away has subsided, and companies committed to big iron need Cobol pros to give them love.

(fonte computerworld)

Maturity of an IT development group PDF Print E-mail
Written by Administrator   
Sunday, 06 December 2009 16:38

These are my point of attention to understand what is the "status of art" of a team/IT organization:

  • Project control and Planning
    • How do you do plan, do you follow any methodology?
    • What tools do you use when planning?
    • How do you perform project control?Are you using EVM (Earned Value Methodology)?
    • Are there common plans among team?
    • Does a time tracking system is on site?
    • Are there any formal milestones during the software lifecycle, where a phase is closed and a subsequent is opened?
  • Is there any requirement management tool in place? how do you gather requirements?
  • Development.
    • What is the software lifecycle (both software for internal use and the one sold by our organization)?
    • How you develop? Is it possible to have some examples?
    • Is it possible to have a graphical representation of the sequence/process that is followed when developing a new functionality?
    • What is the average number of person days for a modification?
    • Are our estimations precise? What is our percentage of estimation correctness?
    • What are the environment/IDE you use, when developing?
  • Environments
    • What programming languages are used?
    • On what environment the software is running. Windows, Linux, Unix, z/OS?
    • Do we use virtualization systems?
    • What is the position of the organization to Open Source in term of production and usage of software?
    • How environment are administered?
      • Server
      • Backup
      • Disaster Recovery
      • Tool maintenance
    • Is it possible to have a list of tools?
      • time tracking
      • Versioning
      • Requirement
      • Planning
      • Bug/Issue tracking
  • Test.
    • Is there a dedicated test team?
    • What tool do you use for testing?
    • Do you have any defined test process?
  • Quality.
    • Do you measure quality, in any way?
    • Is it possible to see any KPI on quality?
    • What is the perceived quality level from internal resources and from the clients?
    • Do you have some specific quality procesess as peer review, software inspections?
  • Documentation.
    • What the quality of our documentation?
    • What is the coverage/completeness of the documentation?
    • How old is our documentation (i.e. average age of a document)?
  • Do you have any versioning tool for software and for documents attached to software?
  • What are the change management processes?

( 0 Votes )
Last Updated on Thursday, 02 September 2010 10:21
 
Shinystat
Tag Clouds
  • Italian - Italy
  • English (United Kingdom)
Archivio Articoli
< December 2009 >
Mo Tu We Th Fr Sa Su
  1 2 3 4 5
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 31