Revision as of 14:39, 6 June 2017 edit Aaron S. Kurland (talk \| contribs) 57 edits m →PSP structure: cleaned up parenthetical statement for development. ← Previous edit		Revision as of 18:36, 25 June 2017 edit undo PrimeBOT (talk \| contribs) Bots 2,129,981 edits m Replace magic links with templates per local RfC - BRFA Next edit →
Line 143: * [http://www.amazon.com/Delivering-Successful-Projects-TSP-Sigma/dp/1420061437 Delivering Successful Projects with TSP(SM) and Six Sigma: A Practical Guide to Implementing Team Software Process], Mukesh Jain, 2008. "Delivering Successful Projects With Challenges of New Teams" by Mukesh Jain (http://www.sei.cmu.edu/tspsymposium/2009/2006/deliver.pdf), September 2006. Software Engineering: A Practitioner's Approach 7th Edition. Roger S Pressman. McGraw-Hill Higher Education. 2009. {{ISBN \|0-07-337597-7}}, {{ISBN \|978-0-07-337597-7}}, pages 57–58. * [http://www.sei.cmu.edu/library/abstracts/reports/09sr018.cfm "The Personal Software Process (PSP) Body of Knowledge"] article from the [[Software Engineering Institute]] at [[Carnegie Mellon]]. * [http://www.methodsandtools.com/archive/archive.php?id=60 "Personal Quality Management with the Personal Software Process"] article.

Personal software process: Difference between revisions