<?xml version="1.0" encoding="UTF-8" ?>
<modsCollection xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" xmlns:slims="http://slims.web.id" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd">
<mods version="3.3" id="15925">
 <titleInfo>
  <title>The Accidental project manager :</title>
  <subTitle>surviving the transition from techie to manager</subTitle>
 </titleInfo>
 <name type="Personal Name" authority="">
  <namePart>Ensworth, Patricia</namePart>
  <role>
   <roleTerm type="text">Primary Author</roleTerm>
  </role>
 </name>
 <typeOfResource manuscript="no" collection="yes">mixed material</typeOfResource>
 <genre authority="marcgt">bibliography</genre>
 <originInfo>
  <place>
   <placeTerm type="text">New York</placeTerm>
   <publisher>John Wiley &amp; Sons</publisher>
   <dateIssued>2001</dateIssued>
  </place>
 </originInfo>
 <language>
  <languageTerm type="code">en</languageTerm>
  <languageTerm type="text">English</languageTerm>
 </language>
 <physicalDescription>
  <form authority="gmd">Printed Material</form>
  <extent>xviii, 269 p. : figs., index ; 24 cm.</extent>
 </physicalDescription>
 <note>This &quot;cheat sheet&quot; provides you with practical advice and critical information you need to manage successful software projects.To help you successfully manage your projects, Ensworth provides you with all of the forms you'll encounter during your project, when you'll need them, and how to use them.With minimum jargon and maximum common sense, you'll learn about:&#13;
&#13;
The various associates who become members of your team, upon whose skills and efforts you will depend&#13;
The four major phases of a software development project and the project manager’s role within each phase&#13;
Ways in which different organizations vary with regard to the responsibilities of the software quality assurance group&#13;
All the necessary steps for planning and budgeting your software project&#13;
Advice on how to evaluate the software project managers who may report to you and how you can help them do a better job.(bn.com&#13;
&#13;
</note>
 <note type="statement of responsibility"></note>
 <subject authority="">
  <topic>Leadership</topic>
 </subject>
 <subject authority="">
  <topic>Project management</topic>
 </subject>
 <subject authority="">
  <topic>Product Development</topic>
 </subject>
 <subject authority="">
  <topic>Information technology</topic>
 </subject>
 <subject authority="">
  <topic>Managers</topic>
 </subject>
 <subject authority="">
  <topic>Planning</topic>
 </subject>
 <classification>AH/BH/WL</classification>
 <identifier type="isbn">047141011X</identifier>
 <location>
  <physicalLocation>Perpustakaan - Sekolah Tinggi Manajemen PPM Pusat Informasi Manajemen</physicalLocation>
  <shelfLocator>AH/BH/WL Ens</shelfLocator>
  <holdingSimple>
   <copyInformation>
    <numerationAndChronology type="1">31070</numerationAndChronology>
    <sublocation>General (General)</sublocation>
    <shelfLocator>AH/BH/WL Ens</shelfLocator>
   </copyInformation>
  </holdingSimple>
 </location>
 <slims:image>The_accidental_project_manager.jpg.jpg</slims:image>
 <recordInfo>
  <recordIdentifier>15925</recordIdentifier>
  <recordCreationDate encoding="w3cdtf">2002-08-21 00:00:00</recordCreationDate>
  <recordChangeDate encoding="w3cdtf">2020-01-28 12:56:53</recordChangeDate>
  <recordOrigin>machine generated</recordOrigin>
 </recordInfo>
</mods>
</modsCollection>