[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-353508-105":53,"doc-detail-353508-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","idealsm-a-users-guide-for-software-process-improvement","IDEALSM - A User’s Guide for Software Process Improvement","","Handbook CMU/SEI-96-HB-001 introduces IDEALSM as a structured guide for software process improvement. It presents a phased approach covering initiating, diagnosing, establishing, acting, and leveraging, with specific activities such as building an SPI proposal, assessing organizational climate, conducting baselines, developing and piloting solutions, managing training and support, and revising the organizational approach. Copyright, warranty disclaimers, and distribution/permission terms govern internal and derivative use.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":46,"@type":70,"position":76},"https://docshare.wps.com/template/paper-templates/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/idealsm-a-users-guide-for-software-process-improvement/353508/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/idealsm-a-users-guide-for-software-process-improvement/353508.png","ImageObject",442,249,{"name":88,"@type":89},"Pentious","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-16","2026-09-22",true,{"@type":98,"interactionType":99,"userInteractionCount":76},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"IDEALSM在软件过程改进中主要覆盖哪些阶段？","Question",{"text":108,"@type":109},"文件以阶段化流程组织内容，包括Initiating、Diagnosing、Establishing、Acting和Leveraging阶段，并在每个阶段给出对应活动。","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"在Initiating阶段需要完成哪些关键工作？",{"text":113,"@type":109},"Initiating阶段包括Getting Started、识别业务需求与改进驱动、构建SPI提案、争取支持与审批、建立SPI基础设施、评估组织气候，并定义SPI的一般目标与指导原则，最终启动项目。",{"name":115,"@type":106,"acceptedAnswer":116},"Diagnosing阶段如何形成改进所需的依据？",{"text":117,"@type":109},"Diagnosing阶段要求确定所需的baseline并规划获取，随后开展baseline并呈现发现，再进一步形成最终发现与建议报告，并向组织沟通结果。","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},353508,1791672296,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":45,"category_name":46,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":76,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":141},1374404730887,"https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8","Handbook  \nCMU/SEI-96-HB-001  \nIDEALSM: A User’s Guide for Software Process Improvement  \nBob McFeeley  \nFebruary 1996  \nHandbook  \nCMU/SEI-96-HB-001  \nFebruary 1996  \nIDEALSM: A User’s Guide for Software Process Improvement  \nBob McFeeley Industry Sector  \nUnlimited distribution subject to the copyright.  \nSoftware Engineering Institute  \nCarnegie Mellon University Pittsburgh, Pennsylvania 15213  \nThis report was prepared for the  \nSEI Joint Program Office HQ ESC/AXS  \n5 Eglin Street  \nHanscom AFB, MA 01731-2116  \nThe ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange.  \nFOR THE COMMANDER  \n(signature on file)  \nThomas R. Miller, Lt Col, USAF SEI Joint Program Office  \nThis work is sponsored by the U.S. Department of Defense.  \nCopyright © 1996 by Carnegie Mellon University.  \nPermission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works.  \nRequests for permission to reproduce this document or to prepare derivative works of this document for external and commercial use should be addressed to the SEI Licensing Agent.  \nNO WARRANTY  \nTHIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTIBILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.  \nThis work was created in the performance of Federal Government Contract Number F19628-95-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The Government of the United States has a royalty-free government-purpose license to use, duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so, for government purposes pursuant to the copyright license under the clause at 52.227-7013.  \nThis document is available through Research Access, Inc., 800 Vinial Street, Pittsburgh, PA 15212.  \nPhone: 1-800-685-6510. FAX: (412) 321-2994. RAI also maintains a World Wide Web home page. The URL is  \n[http://www.rai.com](http://www.rai.com)  \nCopies of this document are available through the National Technical Information Service (NTIS) . For information on ordering, please contact NTIS directly: National Technical Information Service, U.S. Department of  \nCommerce, Springfield, VA 22161. Phone: (703) 487-4600.  \nThis document is also available through the Defense Technical Information Center (DTIC). DTIC provides access to and transfer of scientific and technical information for DoD personnel, DoD contractors and potential contractors, and other U.S. Government agency personnel and their contractors. To obtain a copy, please contact DTIC directly: Defense Technical Information Center / 8725 John J. Kingman Road / Suite 0944 / Ft. Belvoir, VA  \n22060-6218. Phone: (703) 767-8222 or 1-800 225-3842.]  \nUse of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder.  \nContents  \nAbout This Guide vii  \nIntroduction 1  \n1.0 The Initiating Phase 11  \n1.1 Getting Started 19  \n1.2 Identify Business Needs and Drivers for Improvement 21  \n1.3 Build a Software Process Improvement (SPI) Proposal 23  \n1.4 Educate and Build Support 26  \n1.5 Obtain Approval for SPI Proposal and Initial Resources 28  \n1.6 Establish Software Process Improvement Infrastructure 30  \n1.7 Assess the Climate for SPI 47  \n1.8 Define General SPI Goals 49  \n1.9 Define the Guiding Principles ofthe ","cbCailPRf1iwvLJJ","https://ap.wps.com/l/cbCailPRf1iwvLJJ","pdf",501175,236,"English","# About This Guide\n## Introduction\n## The Initiating Phase\n## Getting Started\n## Identify Business Needs and Drivers for Improvement\n## Build a Software Process Improvement (SPI) Proposal\n## Educate and Build Support\n## Obtain Approval for SPI Proposal and Initial Resources\n## Establish Software Process Improvement Infrastructure\n## Assess the Climate for SPI\n## Define General SPI Goals\n## Define the Guiding Principles of the SPI Program\n## Launch the Program\n## The Diagnosing Phase\n## Determine What Baseline(s) Are Needed\n## Plan for the Baseline(s)\n## Conduct Baseline(s)\n## Present Findings\n## Develop Final Findings and Recommendations Report\n## Communicate Findings and Recommendations to Organization\n## The Establishing Phase\n## Select and Get Training in a Strategic Planning Process\n## Review Organization’s Vision\n## Review Organization’s Business Plan\n## Determine Key Business Issues\n## Review Past Improvement Efforts","[{\"question\":\"IDEALSM在软件过程改进中主要覆盖哪些阶段？\",\"answer\":\"文件以阶段化流程组织内容，包括Initiating、Diagnosing、Establishing、Acting和Leveraging阶段，并在每个阶段给出对应活动。\"},{\"question\":\"在Initiating阶段需要完成哪些关键工作？\",\"answer\":\"Initiating阶段包括Getting Started、识别业务需求与改进驱动、构建SPI提案、争取支持与审批、建立SPI基础设施、评估组织气候，并定义SPI的一般目标与指导原则，最终启动项目。\"},{\"question\":\"Diagnosing阶段如何形成改进所需的依据？\",\"answer\":\"Diagnosing阶段要求确定所需的baseline并规划获取，随后开展baseline并呈现发现，再进一步形成最终发现与建议报告，并向组织沟通结果。\"}]","IDEALSM - A User’s Guide for Software Process Improvement | PDF",1790105853,83]