View in EDS PDF Full Text

Why Big Software Projects Fail: The 12 Key Questions.

Saved in:
Bibliographic Details
Title: Why Big Software Projects Fail: The 12 Key Questions. (cover story)
Authors: Humphrey, Watts S.1
Source: Journal of the Quality Assurance Institute. Oct2005, Vol. 19 Issue 4, p30-35. 6p.
Subjects: Software configuration management, Software engineering management, Software productivity measurement, Computer software development, Software architecture, Computer programming management, Management information systems, Capability maturity model, Software maintenance, Education
Abstract: The article discusses the twelve key questions and reasons why large software projects fail. The questions that are discussed in the article are related to software project management, the kind of management system to be use in the project, manager and developer communication, project planning, management system changes and management of team performance. The article also discusses the Capability Maturity Model (CMM) which is a method used for planning software projects and the autocratic style of management which is considered as ineffective for software projects. Another reason why most software projects fail is that the managers do not know enough about the work to make detailed plans.
Database: Engineering Source
FullText Links:
  – Type: pdflink
Text:
  Availability: 0
Header DbId: egs
DbLabel: Engineering Source
An: 20007797
AccessLevel: 6
PubType: Academic Journal
PubTypeId: academicJournal
PreciseRelevancyScore: 0
IllustrationInfo
Items – Name: Title
  Label: Title
  Group: Ti
  Data: Why Big Software Projects Fail: The 12 Key Questions. (cover story)
– Name: Author
  Label: Authors
  Group: Au
  Data: <searchLink fieldCode="AR" term="%22Humphrey%2C+Watts+S%2E%22">Humphrey, Watts S.</searchLink><relatesTo>1</relatesTo>
– Name: TitleSource
  Label: Source
  Group: Src
  Data: <searchLink fieldCode="JN" term="%22Journal+of+the+Quality+Assurance+Institute%22">Journal of the Quality Assurance Institute</searchLink>. Oct2005, Vol. 19 Issue 4, p30-35. 6p.
– Name: Subject
  Label: Subjects
  Group: Su
  Data: <searchLink fieldCode="DE" term="%22Software+configuration+management%22">Software configuration management</searchLink><br /><searchLink fieldCode="DE" term="%22Software+engineering+management%22">Software engineering management</searchLink><br /><searchLink fieldCode="DE" term="%22Software+productivity+measurement%22">Software productivity measurement</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+software+development%22">Computer software development</searchLink><br /><searchLink fieldCode="DE" term="%22Software+architecture%22">Software architecture</searchLink><br /><searchLink fieldCode="DE" term="%22Computer+programming+management%22">Computer programming management</searchLink><br /><searchLink fieldCode="DE" term="%22Management+information+systems%22">Management information systems</searchLink><br /><searchLink fieldCode="DE" term="%22Capability+maturity+model%22">Capability maturity model</searchLink><br /><searchLink fieldCode="DE" term="%22Software+maintenance%22">Software maintenance</searchLink><br /><searchLink fieldCode="DE" term="%22Education%22">Education</searchLink>
– Name: Abstract
  Label: Abstract
  Group: Ab
  Data: The article discusses the twelve key questions and reasons why large software projects fail. The questions that are discussed in the article are related to software project management, the kind of management system to be use in the project, manager and developer communication, project planning, management system changes and management of team performance. The article also discusses the Capability Maturity Model (CMM) which is a method used for planning software projects and the autocratic style of management which is considered as ineffective for software projects. Another reason why most software projects fail is that the managers do not know enough about the work to make detailed plans.
PLink https://search.ebscohost.com/login.aspx?direct=true&site=eds-live&db=egs&AN=20007797
RecordInfo BibRecord:
  BibEntity:
    Languages:
      – Code: eng
        Text: English
    PhysicalDescription:
      Pagination:
        PageCount: 6
        StartPage: 30
    Subjects:
      – SubjectFull: Software configuration management
        Type: general
      – SubjectFull: Software engineering management
        Type: general
      – SubjectFull: Software productivity measurement
        Type: general
      – SubjectFull: Computer software development
        Type: general
      – SubjectFull: Software architecture
        Type: general
      – SubjectFull: Computer programming management
        Type: general
      – SubjectFull: Management information systems
        Type: general
      – SubjectFull: Capability maturity model
        Type: general
      – SubjectFull: Software maintenance
        Type: general
      – SubjectFull: Education
        Type: general
    Titles:
      – TitleFull: Why Big Software Projects Fail: The 12 Key Questions.
        Type: main
  BibRelationships:
    HasContributorRelationships:
      – PersonEntity:
          Name:
            NameFull: Humphrey, Watts S.
    IsPartOfRelationships:
      – BibEntity:
          Dates:
            – D: 01
              M: 10
              Text: Oct2005
              Type: published
              Y: 2005
          Identifiers:
            – Type: issn-print
              Value: 10643761
          Numbering:
            – Type: volume
              Value: 19
            – Type: issue
              Value: 4
          Titles:
            – TitleFull: Journal of the Quality Assurance Institute
              Type: main
ResultId 1