This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these template messages) This article includes a list of general references, but it lacks sufficient corresponding inline citations. Please help to improve this article by introducing more precise citations. (June 2009) (Learn how and when to remove this template message) This biography of a living person needs additional citations for verification. Please help by adding reliable sources. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately from the article and its talk page, especially if potentially libelous.Find sources: "Steve McConnell" – news · newspapers · books · scholar · JSTOR (January 2010) (Learn how and when to remove this template message) (Learn how and when to remove this template message)

Steven C. McConnell is an author of software engineering textbooks such as Code Complete, Rapid Development, and Software Estimation. He is cited as an expert in software engineering and project management.[1][2][3][4][5]

Career

McConnell graduated with a bachelor's degree in philosophy, minoring in computer science,[6] at Whitman College in Walla Walla, Washington, and a master's degree in software engineering from Seattle University. He then pursued a career in the desktop software industry, working at Microsoft, Boeing, the Russell Investment Group and several other Seattle area firms. At Microsoft, McConnell worked on TrueType as part of Windows 3.1. At Boeing, he worked on a Strategic Defense Initiative project.

McConnell published his first book, Code Complete, in 1993.

From 1996 to 1998, he was the editor of the "Best Practices" column in the IEEE Software magazine. From 1998 to 2002, he served as the editor-in-chief of the magazine.[7]

The New York Times has quoted McConnell stating that there are "15 to 50 defects per 1,000 lines of code in delivered software" on average.[8]

References

  1. ^ Michael Krigsman (July 23, 2010). "Top thinkers in project management today". ZDNet. Retrieved 2015-04-13.
  2. ^ Gregory B. Russell (2007). A systems analysis of complex software product development dynamics and methods. DSpace@MIT (Thesis). MIT. hdl:1721.1/42371.
  3. ^ Detlev J. Hoch, ed. (2000). Secrets of Software Success: Management Insights from 100 Software Firms. Harvard Business Press. p. 191. ISBN 1578511054. Retrieved 2015-04-13.
  4. ^ Dwayne Phillips (2004). The Software Project Manager's Handbook: Principles That Work at Work. John Wiley & Sons. p. 472. ISBN 0471674206. Retrieved 2015-04-13.
  5. ^ Stwart Baird (2002). SAMS Tech Yourself Extreme Programming in 24 Hours. SAMS Publishing. p. 406. ISBN 0672324415. Retrieved 2015-04-13.
  6. ^ Steve McConnell; Scott Berkun (2009). "Better Practices: An Interview with Steve McConnell". In Andrew Stellman; Jennifer Greene (eds.). Beautiful Teams: Inspiring and Cautionary Tales from Veteran Team Leaders. O'Reilly Media. p. 205. ISBN 978-0596804923. Retrieved 2015-04-13.
  7. ^ Warren Harrison (2003). "Our 20th Anniversary". IEEE Software. 20 (6): 5–7. doi:10.1109/MS.2003.10026.
  8. ^ Perlroth, Nicole (7 June 2016). "Software as Weaponry in a Computer-Connected World". The New York Times.

External links

Authority control databases
Categories