Process Improvement

101 Items

1.	Economics of Software Quality: An Interview with Capers Jones, Part 2 of 2 (Podcast Transcript) By Rex Black, Capers Jones Jan 17, 2012 Rex Black and Capers Jones continue discussing Capers Jones' book The Economics of Software Quality. Watch this podcast to learn some surprising and motivating facts about software quality and how to improve it.
2.	Economics of Software Quality: An Interview with Capers Jones, Part 1 of 2 (Podcast Transcript) By Rex Black, Capers Jones Jan 16, 2012 In this two-part interview, Rex Black talks with Capers Jones about his book The Economics of Software Quality, in which leading software quality experts Jones and Olivier Bonsignour show how to measure the economic impact of quality and how to use this data to deliver exceptional business value.
3.	The End of Projects: Moving Toward Evidence-Based Software Investment By Aaron Erickson Nov 24, 2011 Is it possible that the software industry could succeed with a model that's not based around designing, funding, and fulfilling individual projects - and then starting all over again? Aaron Erickson, author of The Nomadic Developer, is confident enough of the possibility that he's even given it a name: evidence-based software investment. Tune in for the nickel tour.
4.	Killing Quality, Squelching Success By Larry L. Constantine Aug 22, 2011 Software engineering pioneer Larry Constantine warns designers and developers about the risks of being too good at what they do and cautions managers to mind the organizational factors that can help kill the best products.
5.	Defining Software Quality and Economic Value By Capers Jones, Olivier Bonsignour Aug 15, 2011 This introduction to The Economics of Software Quality covers how to define software quality and economic value.
6.	Painless Process Improvement By Matthew Heusser Jun 22, 2011 If you'd rather bang your head against a wall than go to another pre-planning meeting about the documentation review step of the software process improvement plan, Matt Heusser has a couple of suggestions for saving your brain.
7.	The Clean Coder: Saying Yes By Robert C. Martin May 31, 2011 Professionals are not required to say yes to everything that is asked of them. However, they should work hard to find creative ways to make “yes” possible. When professionals say yes, they use the language of commitment so that there is no doubt about what they’ve promised.
8.	Introduction to CMMI for Development: Guidelines for Process Integration and Product Improvement, 3rd Edition By Mary Beth Chrissis, Mike Konrad, Sandra Shrum Mar 23, 2011 This chapter introduces CMMI for Development (CMMI-DEV), which consists of best practices that address development activities applied to products and services. It addresses practices that cover the product's lifecycle from conception through delivery and maintenance. The emphasis is on the work necessary to build and maintain the total product.
9.	Introduction to CMMI for Services: Guidelines for Superior Service, 2nd Edition By Eileen Forrester, Brandon L. Buteau, Sandra Shrum Mar 22, 2011 Many service organizations accept common problems as "normal" and they don't try to address them or eliminate them. What about your organization? Are you settling for less? Developing and improving mature service practices is a key contributor to improved performance, customer satisfaction, and profitability. The CMMI for Services (CMMI-SVC) model is designed to begin meeting that need.
10.	Introduction to CMMI for Acquisition: Guidelines for Improving the Acquisition of Products and Services By Brian Gallagher, Mike Phillips, Karen Richter, Sandra Shrum Mar 21, 2011 This chapter introduces CMMI for Acquisition (CMMI-ACQ), which enables organizations to avoid or eliminate barriers in the acquisition process through practices and terminology that transcend the interests of individual departments or groups.
11.	Culture Clash: Getting On Board with IT Governance By Jeff Papows Oct 5, 2010 How do we as a development community abandon some of the widely misunderstood perceptions about IT governance and make it a proactive, not reactive, part of the development process?
12.	Glitch: The Hidden Impact of Faulty Software -- Converging Forces By Jeff Papows Sep 13, 2010 Jeff Papows explains that if we continue to allow these technology glitches to fester in our infrastructures, a technology Armageddon could be just around the corner.
13.	Lean Integration for Health Care: Healthy Data for the Future By John G. Schmidt Aug 10, 2010 John G. Schmidt, coauthor of Lean Integration: An Integration Factory Approach to Business Agility, believes that health care in the U.S. will inevitably slide into adopting lean principles. But why should we wait for this desirable state? He explains the current issues that make lean crucial and the obstacles that we need to overcome in getting lean.
14.	Bringing Process Maturity to Agile Organizations—Part I By Paul E. McMahon Aug 9, 2010 Paul E. McMahon discusses five popular myths about processes in Agile organizations, common challenges faced initiating a CMMI process improvement effort within an Agile organization, successful techniques to guide a small growing Agile organization to CMMI level 3 while maintaining an Agile culture, answers to common questions related to developing Agile processes, and practical techniques to structure an organizational repository supporting agility and CMMI compliancy.
15.	Using Metrics to Find Out if Your Code Base Will Stand the Test of Time By Aaron Erickson Feb 18, 2010 Aaron Erickson covers metrics you can use to determine whether your code base will stand the test of time or be a significant source of ongoing cost.
16.	Introduction to CMMI for Services By Eileen C. Forrester, Brandon L. Buteau, Sandy Shrum Nov 19, 2009 Do you need CMMI? If you have problems such as plans that are made but not necessarily followed; inconsistent expectations and service levels; a crisis atmosphere amidst over-commitments and overruns; and unhappy customers, you should read this chapter to see if CMMI is right for your service business.
17.	Quality Last: Why We Make Poor Software By Aaron Erickson Oct 14, 2009 Aaron Erickson discusses why your Statement of Work probably guarantees low software quality.
18.	Don't "Enron" Your Software Project By Aaron Erickson Oct 10, 2009 Aaron Erickson begins a new series on technical finance with a discussion of how technical debt, technical 'off-balance sheet entities,' and technical fraud undermine return on investment.
19.	Robert C. Martin's Clean Code Tip #12: Eliminate Boolean Arguments By Robert C. Martin Aug 25, 2009 We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this twelfth tip in the series, the crew learns that Boolean arguments loudly declare that the function does more than one thing. They are confusing and should be eliminated.
20.	Robert C. Martin's Clean Code Tip of the Week #11: Output Arguments are Counterintuitive By Robert C. Martin Jul 28, 2009 We join "The Craftsman," Robert C. Martin's series on an interstellar spacecraft where programmers hone their coding skills. In this eleventh tip in the series, the crew learns that if your function must change the state of something, have it change the state of the object it is called on.

< Prev 1 2 3 4 5 Next >