<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>03143ntm a2200373 i 4500</leader>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="8">REF</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2023-06-12</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">FIM .A37 2019 r Thesis</subfield>
    <subfield code="p">T000002390</subfield>
    <subfield code="r">2023-06-12 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2023-06-12</subfield>
    <subfield code="y">THESIS</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">lcc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">6</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2023-06-12</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">CD13360</subfield>
    <subfield code="p">T000002391</subfield>
    <subfield code="r">2023-06-12 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2023-06-12</subfield>
    <subfield code="y">THESIS</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">99536</subfield>
    <subfield code="d">99542</subfield>
  </datafield>
  <controlfield tag="003">MY-KuUP</controlfield>
  <controlfield tag="005">20251125110740.0</controlfield>
  <controlfield tag="006">t||||fr|||| 000 0 </controlfield>
  <controlfield tag="007">ta</controlfield>
  <controlfield tag="008">230612b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">THE0009656 (Local)</subfield>
    <subfield code="q">Hardback</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">UMP</subfield>
    <subfield code="b">eng</subfield>
    <subfield code="c">UMP</subfield>
    <subfield code="e">rda</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">FIM .A37 2019 r Thesis</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Siti Aissah Binti Mad Ali,</subfield>
    <subfield code="e">author.</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Enhancement of software project performance by overcoming waste, volatility and constraints simultaneously /</subfield>
    <subfield code="c">Siti Aissah Binti Mad Ali</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="a">Kuantan, Pahang :</subfield>
    <subfield code="b">UMP,</subfield>
    <subfield code="c">2019</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="4">
    <subfield code="c">&#xA9;2019</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xiii, 142 pages :</subfield>
    <subfield code="b">illustration (some col.) ;</subfield>
    <subfield code="c">30 cm.</subfield>
    <subfield code="e">1 CD-ROM</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="2">rdacontent</subfield>
    <subfield code="a">text</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="2">rdacontent</subfield>
    <subfield code="a">text</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="2">rdamedia</subfield>
    <subfield code="a">unmediated</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="2">rdamedia</subfield>
    <subfield code="a">computer</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="2">rdacarrier</subfield>
    <subfield code="a">volume</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="2">rdacarrier</subfield>
    <subfield code="a">computer disc</subfield>
  </datafield>
  <datafield tag="347" ind1=" " ind2=" ">
    <subfield code="2">rda</subfield>
    <subfield code="a">text file</subfield>
    <subfield code="b">PDF</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Faculty of Industrial Management</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
    <subfield code="a">Thesis (Master of Science) -- Universiti Malaysia Pahang &#x2013; 2019</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Includes bibliographical references</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">There have been many projects and researches conducted to identify software projects&#x2019; failure and success factors. The success factors were always remained as best practices as it favours desired results while the failure factors are always avoided as it yields undesired factors. However, it is least understood that focusing on avoiding a failure factor could actually influence other forms of failure risk(s). In this study, it has been understood through literature review that most of the findings on software projects failure factors have been repetitive for more than two decades. These failure factors commonality was then understood and categorized by bridging few studies and experts&#x2019; opinions based on three well-known theories; Lean, Requirement Volatility and Theory of Constraints. There are nine types of wastes, three types errors that leads to requirement volatility and eight types of constraints in relevance to software projects. Through literature and discussion with 15 experts it was apparent that there could be interdependency and interrelationship amongst these 20 variables. The relationship amongst the variables were studied by employing the DEMATEL methodology. DEMATEL was opted to show the Impact Relation Map which could serve as a good source of reference to help decision makers formulate their decisions pertaining these 20 variables. A Software Project Success Framework was then developed to assist the foundation for planning and prioritizing relevant mitigations and corrective measures about software projects failure factors. Requirement volatility has been emphasized as the main cause of software project failure. It does not only cause direct impact towards software projects failure but also influences other identified factors to affect the sotware project performance adversely.</subfield>
  </datafield>
  <datafield tag="610" ind1="2" ind2="0">
    <subfield code="a">Faculty of Industrial Management</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Universities and colleges</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Thesis</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">lcc</subfield>
    <subfield code="c">THESIS</subfield>
  </datafield>
</record>
