{"id":341,"date":"2018-07-26T04:36:49","date_gmt":"2018-07-26T04:36:49","guid":{"rendered":"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/?post_type=chapter&#038;p=341"},"modified":"2018-08-08T06:21:40","modified_gmt":"2018-08-08T06:21:40","slug":"personal-software-process","status":"publish","type":"chapter","link":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/chapter\/personal-software-process\/","title":{"rendered":"Personal Software Process"},"content":{"raw":"<div>\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\"><strong>PERSONAL SOFTWARE PROCESS<\/strong><\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\">Personal software process is a software development process by the developers to help themselves improve their performance and efficiency by following a personal disciplined framework that facilitates to plan, design, manage and measure their work.<\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\"><strong>LEARNING OBJECTIVES\u00a0<\/strong><\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\">\u2022\u00a0To consistently improve the performance, engineers must use well-defined and measured processes.<\/p>\r\n<p style=\"text-align: justify\">\u2022 To produce quality products, engineers must feel personally responsible for the quality.<\/p>\r\n<p style=\"text-align: justify\">\u2022 It costs less to find and fix defects earlier in a process than later.<\/p>\r\n<p style=\"text-align: justify\">\u2022 The right way is always the fastest and cheapest way to do a job.<\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\"><strong>Better Programmer\u00a0<\/strong><\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\">Better programmer can be achieved by,<\/p>\r\n\r\n<ul>\r\n \t<li style=\"text-align: justify\"><strong>More training<\/strong>\r\n<ul>\r\n \t<li style=\"text-align: justify\">Know how to use tools.<\/li>\r\n \t<li style=\"text-align: justify\">Have seen some problems before.<\/li>\r\n \t<li style=\"text-align: justify\">Know how things fit together.<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li style=\"text-align: justify\"><strong>Familiar with language<\/strong>\r\n<ul>\r\n \t<li style=\"text-align: justify\">Object, semaphore, recursion, etc..<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li style=\"text-align: justify\"><strong>Better process<\/strong><\/li>\r\n<\/ul>\r\n&nbsp;\r\n\r\n<strong>Examples of Better Processes\u00b7\u00a0<\/strong>\r\n<ul>\r\n \t<li><strong>Incremental coding<\/strong>\r\n<ul>\r\n \t<li style=\"text-align: justify\">Code a little, test a little<\/li>\r\n \t<li style=\"text-align: justify\">Compare to writing <em>entire <\/em>program and testing<\/li>\r\n<\/ul>\r\n<\/li>\r\n \t<li style=\"text-align: justify\"><strong>Error prevention versus debugging<\/strong>\r\n<ul>\r\n \t<li style=\"text-align: justify\">Cheaper and easier to prevent than to find bugs<\/li>\r\n<\/ul>\r\n<\/li>\r\n<\/ul>\r\n<\/div>\r\n&nbsp;\r\n<p style=\"text-align: justify\"><strong><span style=\"text-align: initial;font-size: 1em\">Point of Processes\u00a0<\/span><\/strong><\/p>\r\n\r\n<div style=\"text-align: justify\">\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\">The point of processes is to learn from mistakes so that we never make the same mistake twice. It incorporates best practices as something works better than another. \u00a0A process executes routine standard tasks, when once the task is done it right once and then it is reused. Another major point of having processes is predictability<strong>.<\/strong><\/p>\r\n&nbsp;\r\n\r\n<strong>PERSONAL SOFTWARE PROCESS\u00a0<\/strong>\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\">Personal software process is a software development process by the developers to help themselves improve their performance and efficiency by following a personal disciplined framework that facilitates to plan, design, manage and measures their work. PSP helps you to manage your work &amp; assess\/build your talents\/skills. It helps to plan better. And track your performance precisely. It measures the quality of your software products. It provides a framework for determining why you make errors and how you find them, to determine the quality of your reviews and the types of errors you make.<\/p>\r\n&nbsp;\r\n\r\n<strong>REASONS FOR A PROJECT FAILURE\u00a0<\/strong>\r\n\r\n&nbsp;\r\n\r\nLarge and small software projects fail for four reasons.\r\n<ul>\r\n \t<li style=\"text-align: justify\"><strong>Project commitments are often unrealistic. <\/strong>The larger the project, the less influence we have. If we don\u2019t have anything to say, nobody will listen and hence project fails when the project commitments are unrealistic.<\/li>\r\n \t<li style=\"text-align: justify\"><strong style=\"font-size: 1em\">Larger projects are harder to control. <\/strong><span style=\"font-size: 1em\">Today, few developers have personal plans, without a plan, you cannot know job status. If you don\u2019t know where you are, management can\u2019t understand job status. If management doesn\u2019t understand job status, they can\u2019t manage projects.<\/span><\/li>\r\n \t<li style=\"text-align: justify\"><strong style=\"font-size: 1em\">Quality problems get worse with project size. <\/strong><span style=\"font-size: 1em\">In software systems, if any part has quality problems, the system will have quality problems. If the developers do not manage quality, their teams cannot manage quality. When unmanaged, quality will always be poor.<\/span><\/li>\r\n \t<li style=\"text-align: justify\"><strong style=\"font-size: 1em;text-align: initial\">To be effective, teams need leadership and coaching. <\/strong><span style=\"font-size: 1em;text-align: initial\">Leaders build team motivation and commitment. Coaching develops team cohesion. Cohesive, motivated, and committed teams do the best work.<\/span><\/li>\r\n<\/ul>\r\n<\/div>\r\n<div style=\"text-align: justify\">\r\n\r\n&nbsp;\r\n\r\n<strong>The Need for Changes\u00a0<\/strong>\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\">Many lives and businesses now depend on software. We now need larger, more complex, and safer software systems on predictable schedules. Without different software practices, this will not happen. The Team Software Process (TSP) addresses this need. The PSP provides the knowledge and skill that developers need to work on TSP teams.<\/p>\r\n&nbsp;\r\n\r\n<strong>PERSONAL SOFTWARE PROCESS (PSP)\u00a0<\/strong>\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\">Personal software process provides application of CMM principles to individuals. It was developed by Watts Humphrey of the Software Engineering Institute (SEI) in the early 1990s with extensive supporting materials such as books, courses, forms, exercises. It is validated by data from numerous projects such as:<\/p>\r\n&nbsp;\r\n\r\n\u25e6 58% reduction in defects\/KLOC (development)\r\n\r\n\u25e6 72% reduction in defects\/KLOC (testing)\r\n\r\n\u25e6 21% improvement in productivity\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\">Personal software process is complemented by Team Software Process (TSP) which comprises of strict waterfall plus process monitoring and improvement.<\/p>\r\n\r\n<\/div>\r\n<img class=\"aligncenter wp-image-347 \" src=\"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP.png\" alt=\"\" width=\"535\" height=\"347\" \/>\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\"><span style=\"text-align: initial;font-size: 1em\">The PSP is a personal process for developing software or for doing any other defined activity. The PSP includes defined steps, forms and standards. It provides a measurement and analysis framework for characterizing and managing your personal work. It is also a defined procedure that helps you to improve your personal performance.<\/span><\/p>\r\n\r\n<div style=\"text-align: justify\">\r\n\r\n&nbsp;\r\n\r\n<strong>PSP and CMM\u00a0<\/strong>\r\n\r\n&nbsp;\r\n\r\nCMM is top-down - management oriented and PSP is bottom-up - engineer oriented.\r\n\r\n&nbsp;\r\n\r\n<img class=\"aligncenter wp-image-346\" src=\"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2.png\" alt=\"\" width=\"543\" height=\"384\" \/>\r\n\r\n<strong>Overview of PSP\u00a0<\/strong>\r\n\r\n&nbsp;\r\n<p style=\"text-align: justify\">PSP is a disciplined personal framework for developing software and comprises of metrics, forms, and scripts. It produces low-defect products on schedule and within planned costs and manages quality, analyzes results and improves process.<\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\">The overall approach involves experienced programmers to inject one defect per 7-10 lines of code. People tend to make the same mistakes repeatedly. To improve the organization's performance; record data on defects, review data, make process changes to eliminate causes and spend more up-front time (design and detection activities).<\/p>\r\n\r\n<\/div>\r\n&nbsp;\r\n<p style=\"text-align: justify\"><strong><span style=\"text-align: initial;font-size: 1em\">PSP Process Flow\u00a0<\/span><\/strong><\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\">The PSP process flow involves acquiring the scripts which helps in planning the project and building the project with respect to the lines of code. The project is implemented and tested for shortcomings. The key feature in the process flow is to keep track of all the activities done by keeping a log of everything. The project summary report is generated which depicts all the data of the project and process executed.<\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\"><img class=\"aligncenter size-full wp-image-345\" src=\"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3.png\" alt=\"\" width=\"607\" height=\"318\" \/><\/p>\r\n<p style=\"text-align: justify\"><strong style=\"text-align: justify;font-size: 1em\">Management Support<\/strong><\/p>\r\n&nbsp;\r\n<p style=\"text-align: justify\">The initial TSP objective is to convince management to let your team be self-directed. Self- directed teams do the best work. A self-directed team<\/p>\r\n\r\n<ul>\r\n \t<li>sets its own goals<\/li>\r\n \t<li>establishes its own roles<\/li>\r\n \t<li>decides on its own development strategy<\/li>\r\n \t<li>defines its own processes<\/li>\r\n \t<li>develops its own plans<\/li>\r\n \t<li style=\"text-align: justify\">measures, manages, and controls its own work<\/li>\r\n<\/ul>\r\n&nbsp;\r\n\r\n<strong>Web Links<\/strong>\r\n<ul>\r\n \t<li>www.sei.cmu.edu\/tsp\/<\/li>\r\n \t<li>resources.sei.cmu.edu\/library\/asset-view.cfm?assetid=5287<\/li>\r\n \t<li>cs.mty.itesm.mx\/profesores\/pverdines\/TCS\/p3\/PSP-TSP.pdf<\/li>\r\n<\/ul>\r\n&nbsp;\r\n\r\n<strong>Supporting &amp; Reference Materials<\/strong>\r\n<ul>\r\n \t<li>Roger S. Pressman, \u201cSoftware Engineering: A Practitioner\u2019s Approach\u201d, Fifth Edition, McGraw Hill, 2001.<\/li>\r\n \t<li>Pankaj Jalote, \u201cAn Integrated Approach to Software Engineering\u201d, Second Edition, Narosa Publications, 2005.<\/li>\r\n \t<li>Ian Sommerville, \u201cSoftware Engineering\u201d, Sixth Edition, Addison Wesley, 2000.<\/li>\r\n \t<li>Watt.S.Humpherey, \u201cIntroduction to the Personal Software Process\u201d, Pearson Education India, First Edition, 2002.<\/li>\r\n<\/ul>","rendered":"<div>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><strong>PERSONAL SOFTWARE PROCESS<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">Personal software process is a software development process by the developers to help themselves improve their performance and efficiency by following a personal disciplined framework that facilitates to plan, design, manage and measure their work.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><strong>LEARNING OBJECTIVES\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">\u2022\u00a0To consistently improve the performance, engineers must use well-defined and measured processes.<\/p>\n<p style=\"text-align: justify\">\u2022 To produce quality products, engineers must feel personally responsible for the quality.<\/p>\n<p style=\"text-align: justify\">\u2022 It costs less to find and fix defects earlier in a process than later.<\/p>\n<p style=\"text-align: justify\">\u2022 The right way is always the fastest and cheapest way to do a job.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><strong>Better Programmer\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">Better programmer can be achieved by,<\/p>\n<ul>\n<li style=\"text-align: justify\"><strong>More training<\/strong>\n<ul>\n<li style=\"text-align: justify\">Know how to use tools.<\/li>\n<li style=\"text-align: justify\">Have seen some problems before.<\/li>\n<li style=\"text-align: justify\">Know how things fit together.<\/li>\n<\/ul>\n<\/li>\n<li style=\"text-align: justify\"><strong>Familiar with language<\/strong>\n<ul>\n<li style=\"text-align: justify\">Object, semaphore, recursion, etc..<\/li>\n<\/ul>\n<\/li>\n<li style=\"text-align: justify\"><strong>Better process<\/strong><\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Examples of Better Processes\u00b7\u00a0<\/strong><\/p>\n<ul>\n<li><strong>Incremental coding<\/strong>\n<ul>\n<li style=\"text-align: justify\">Code a little, test a little<\/li>\n<li style=\"text-align: justify\">Compare to writing <em>entire <\/em>program and testing<\/li>\n<\/ul>\n<\/li>\n<li style=\"text-align: justify\"><strong>Error prevention versus debugging<\/strong>\n<ul>\n<li style=\"text-align: justify\">Cheaper and easier to prevent than to find bugs<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/div>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><strong><span style=\"text-align: initial;font-size: 1em\">Point of Processes\u00a0<\/span><\/strong><\/p>\n<div style=\"text-align: justify\">\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">The point of processes is to learn from mistakes so that we never make the same mistake twice. It incorporates best practices as something works better than another. \u00a0A process executes routine standard tasks, when once the task is done it right once and then it is reused. Another major point of having processes is predictability<strong>.<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p><strong>PERSONAL SOFTWARE PROCESS\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">Personal software process is a software development process by the developers to help themselves improve their performance and efficiency by following a personal disciplined framework that facilitates to plan, design, manage and measures their work. PSP helps you to manage your work &amp; assess\/build your talents\/skills. It helps to plan better. And track your performance precisely. It measures the quality of your software products. It provides a framework for determining why you make errors and how you find them, to determine the quality of your reviews and the types of errors you make.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>REASONS FOR A PROJECT FAILURE\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p>Large and small software projects fail for four reasons.<\/p>\n<ul>\n<li style=\"text-align: justify\"><strong>Project commitments are often unrealistic. <\/strong>The larger the project, the less influence we have. If we don\u2019t have anything to say, nobody will listen and hence project fails when the project commitments are unrealistic.<\/li>\n<li style=\"text-align: justify\"><strong style=\"font-size: 1em\">Larger projects are harder to control. <\/strong><span style=\"font-size: 1em\">Today, few developers have personal plans, without a plan, you cannot know job status. If you don\u2019t know where you are, management can\u2019t understand job status. If management doesn\u2019t understand job status, they can\u2019t manage projects.<\/span><\/li>\n<li style=\"text-align: justify\"><strong style=\"font-size: 1em\">Quality problems get worse with project size. <\/strong><span style=\"font-size: 1em\">In software systems, if any part has quality problems, the system will have quality problems. If the developers do not manage quality, their teams cannot manage quality. When unmanaged, quality will always be poor.<\/span><\/li>\n<li style=\"text-align: justify\"><strong style=\"font-size: 1em;text-align: initial\">To be effective, teams need leadership and coaching. <\/strong><span style=\"font-size: 1em;text-align: initial\">Leaders build team motivation and commitment. Coaching develops team cohesion. Cohesive, motivated, and committed teams do the best work.<\/span><\/li>\n<\/ul>\n<\/div>\n<div style=\"text-align: justify\">\n<p>&nbsp;<\/p>\n<p><strong>The Need for Changes\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">Many lives and businesses now depend on software. We now need larger, more complex, and safer software systems on predictable schedules. Without different software practices, this will not happen. The Team Software Process (TSP) addresses this need. The PSP provides the knowledge and skill that developers need to work on TSP teams.<\/p>\n<p>&nbsp;<\/p>\n<p><strong>PERSONAL SOFTWARE PROCESS (PSP)\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">Personal software process provides application of CMM principles to individuals. It was developed by Watts Humphrey of the Software Engineering Institute (SEI) in the early 1990s with extensive supporting materials such as books, courses, forms, exercises. It is validated by data from numerous projects such as:<\/p>\n<p>&nbsp;<\/p>\n<p>\u25e6 58% reduction in defects\/KLOC (development)<\/p>\n<p>\u25e6 72% reduction in defects\/KLOC (testing)<\/p>\n<p>\u25e6 21% improvement in productivity<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">Personal software process is complemented by Team Software Process (TSP) which comprises of strict waterfall plus process monitoring and improvement.<\/p>\n<\/div>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-347\" src=\"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP.png\" alt=\"\" width=\"535\" height=\"347\" srcset=\"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP.png 626w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP-300x195.png 300w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP-65x42.png 65w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP-225x146.png 225w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP-350x227.png 350w\" sizes=\"auto, (max-width: 535px) 100vw, 535px\" \/><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><span style=\"text-align: initial;font-size: 1em\">The PSP is a personal process for developing software or for doing any other defined activity. The PSP includes defined steps, forms and standards. It provides a measurement and analysis framework for characterizing and managing your personal work. It is also a defined procedure that helps you to improve your personal performance.<\/span><\/p>\n<div style=\"text-align: justify\">\n<p>&nbsp;<\/p>\n<p><strong>PSP and CMM\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p>CMM is top-down &#8211; management oriented and PSP is bottom-up &#8211; engineer oriented.<\/p>\n<p>&nbsp;<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter wp-image-346\" src=\"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2.png\" alt=\"\" width=\"543\" height=\"384\" srcset=\"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2.png 833w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2-300x212.png 300w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2-768x543.png 768w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2-65x46.png 65w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2-225x159.png 225w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP2-350x247.png 350w\" sizes=\"auto, (max-width: 543px) 100vw, 543px\" \/><\/p>\n<p><strong>Overview of PSP\u00a0<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">PSP is a disciplined personal framework for developing software and comprises of metrics, forms, and scripts. It produces low-defect products on schedule and within planned costs and manages quality, analyzes results and improves process.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">The overall approach involves experienced programmers to inject one defect per 7-10 lines of code. People tend to make the same mistakes repeatedly. To improve the organization&#8217;s performance; record data on defects, review data, make process changes to eliminate causes and spend more up-front time (design and detection activities).<\/p>\n<\/div>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><strong><span style=\"text-align: initial;font-size: 1em\">PSP Process Flow\u00a0<\/span><\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">The PSP process flow involves acquiring the scripts which helps in planning the project and building the project with respect to the lines of code. The project is implemented and tested for shortcomings. The key feature in the process flow is to keep track of all the activities done by keeping a log of everything. The project summary report is generated which depicts all the data of the project and process executed.<\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-345\" src=\"http:\/\/csp8.epgpbooks.inflibnet.ac.in\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3.png\" alt=\"\" width=\"607\" height=\"318\" srcset=\"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3.png 607w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3-300x157.png 300w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3-65x34.png 65w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3-225x118.png 225w, https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-content\/uploads\/sites\/53\/2018\/07\/PSP3-350x183.png 350w\" sizes=\"auto, (max-width: 607px) 100vw, 607px\" \/><\/p>\n<p style=\"text-align: justify\"><strong style=\"text-align: justify;font-size: 1em\">Management Support<\/strong><\/p>\n<p>&nbsp;<\/p>\n<p style=\"text-align: justify\">The initial TSP objective is to convince management to let your team be self-directed. Self- directed teams do the best work. A self-directed team<\/p>\n<ul>\n<li>sets its own goals<\/li>\n<li>establishes its own roles<\/li>\n<li>decides on its own development strategy<\/li>\n<li>defines its own processes<\/li>\n<li>develops its own plans<\/li>\n<li style=\"text-align: justify\">measures, manages, and controls its own work<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Web Links<\/strong><\/p>\n<ul>\n<li>www.sei.cmu.edu\/tsp\/<\/li>\n<li>resources.sei.cmu.edu\/library\/asset-view.cfm?assetid=5287<\/li>\n<li>cs.mty.itesm.mx\/profesores\/pverdines\/TCS\/p3\/PSP-TSP.pdf<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<p><strong>Supporting &amp; Reference Materials<\/strong><\/p>\n<ul>\n<li>Roger S. Pressman, \u201cSoftware Engineering: A Practitioner\u2019s Approach\u201d, Fifth Edition, McGraw Hill, 2001.<\/li>\n<li>Pankaj Jalote, \u201cAn Integrated Approach to Software Engineering\u201d, Second Edition, Narosa Publications, 2005.<\/li>\n<li>Ian Sommerville, \u201cSoftware Engineering\u201d, Sixth Edition, Addison Wesley, 2000.<\/li>\n<li>Watt.S.Humpherey, \u201cIntroduction to the Personal Software Process\u201d, Pearson Education India, First Edition, 2002.<\/li>\n<\/ul>\n","protected":false},"author":4,"menu_order":35,"template":"","meta":{"pb_show_title":"on","pb_short_title":"","pb_subtitle":"","pb_authors":["dr-r-baskaran"],"pb_section_license":""},"chapter-type":[],"contributor":[58],"license":[],"class_list":["post-341","chapter","type-chapter","status-publish","hentry","contributor-dr-r-baskaran"],"part":3,"_links":{"self":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/chapters\/341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/chapters"}],"about":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/wp\/v2\/types\/chapter"}],"author":[{"embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/wp\/v2\/users\/4"}],"version-history":[{"count":5,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/chapters\/341\/revisions"}],"predecessor-version":[{"id":423,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/chapters\/341\/revisions\/423"}],"part":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/parts\/3"}],"metadata":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/chapters\/341\/metadata\/"}],"wp:attachment":[{"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/wp\/v2\/media?parent=341"}],"wp:term":[{"taxonomy":"chapter-type","embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/pressbooks\/v2\/chapter-type?post=341"},{"taxonomy":"contributor","embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/wp\/v2\/contributor?post=341"},{"taxonomy":"license","embeddable":true,"href":"https:\/\/ebooks.inflibnet.ac.in\/csp8\/wp-json\/wp\/v2\/license?post=341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}