software-quality.blogspot.com
Software Quality: Handling Late Requirements Weblog
http://software-quality.blogspot.com/2006/03/handling-late-requirements.html
Share, improve, learn, co-operate on topics related to software quality assurance. Friday, March 31, 2006. Many of project issues are related to bad requirements management. One particular. Issue which is hard to tackle is the handling of late requirements. Coping with new requirements after the development has started often leads to problems in the project. Schedule, cost and scope. Of the running project become unknown. Problems, unsufficient time left for testing. Of the development team. Pretty good ...
software-quality.blogspot.com
Software Quality: April 2005 Weblog
http://software-quality.blogspot.com/2005_04_01_archive.html
Share, improve, learn, co-operate on topics related to software quality assurance. Saturday, April 30, 2005. LSD Lean Software Development. A more recent contribution to the agile community is Lean Software Development, with focus on increasing delivery speed. And lowering production cost. Becoming 'lean' is a process of eliminating waste. With the goal of creating value. Two mindsets: (ref. Joel Cutcher-Gershenfeld - ESD.60 Lean/Six Sigma Systems. Posted by Ronny De Winter at Saturday, April 30, 2005.
self-improvement-is-the-answer.com
Goal Setting Software
http://www.self-improvement-is-the-answer.com/goal-setting-software.html
The good news: There is a VAST array of goal setting software on the Internet to download. The bad news: Most of these applications aren't free. And the ones that are free usually aren't that great, meaning they might not install properly or they won't allow you to do much more with them than a common word processing program might. Honesty out of the way, now for the MEATY PART of this brief starter to my main article. And now for the VERY VERY meaty part of this article. Concerning the above list of onl...
software-quality.blogspot.com
Software Quality: Software Distribution Making Weblog
http://software-quality.blogspot.com/2006/01/software-distribution-making.html
Share, improve, learn, co-operate on topics related to software quality assurance. Tuesday, January 31, 2006. An important process in software development is the making of the distribution. Here are some good practices. Make sure tarballs always unpack into a single new directory. Not the current directory! A pointer to the project website. If it has one). Notes on the developer's build environment. And potential portability problems. A roadmap describing important files and subdirectories. Good Developm...
software-quality.blogspot.com
Software Quality: September 2005 Weblog
http://software-quality.blogspot.com/2005_09_01_archive.html
Share, improve, learn, co-operate on topics related to software quality assurance. Friday, September 30, 2005. 5 mistakes from Linux IT Managers. Five common mistakes that Linux IT managers make and tips to avoid the mistakes. Mistake #1: Reactive, not proactive. Have disaster plans in place rather than trying to implement a disaster plan on the fly (hardware failure, natural disaster, compromised systems,.). Plans for the future in terms of capacity planning, upgrades, and support. As a secondary priori...
software-quality.blogspot.com
Software Quality: August 2005 Weblog
http://software-quality.blogspot.com/2005_08_01_archive.html
Share, improve, learn, co-operate on topics related to software quality assurance. Sunday, August 28, 2005. Software Health versus Software Quality. Create thrust and establish a healthy relationship with your customers. Software quality is often measured by the number of bugs remaining in the product, as an instanteneous view on the state of the system (also called external quality. Is important we better talk about software health. When the load changes? When the requirements changes? What does it cost.
software-quality.blogspot.com
Software Quality: November 2005 Weblog
http://software-quality.blogspot.com/2005_11_01_archive.html
Share, improve, learn, co-operate on topics related to software quality assurance. Sunday, November 20, 2005. Six Sigma Terms and Definitions. Former CEO of General Electric, and one of the most succesful corporate leaders ever, used Six Sigma. As major Quality Improvement method. In his book Winning. Six Sigma is not about averages. It is about eliminating variances. From your relationship with the customers. Six Sigma Definitions from the the GE website. Quality Approaches and Models. A vision of quali...
software-quality.blogspot.com
Software Quality: July 2005 Weblog
http://software-quality.blogspot.com/2005_07_01_archive.html
Share, improve, learn, co-operate on topics related to software quality assurance. Saturday, July 09, 2005. Managing Complexity and Uncertainty. Categorizing software development projects according to their complexity and uncertainty, you can adapt your process. By adding practices according. To each project's profile. Projects can be put in a four-quadrant graph similar to the Boston Consulting Group's Boston Matrix. Simple projects with low uncertainty. Simple projects with high uncertainty. Iterations...
software-quality.blogspot.com
Software Quality: December 2005 Weblog
http://software-quality.blogspot.com/2005_12_01_archive.html
Share, improve, learn, co-operate on topics related to software quality assurance. Wednesday, December 28, 2005. Good Development Practices for Open-Source Developers. Don't rely on proprietary code. Languages, or libraries. Open-source developers don't trust code for which they can't review the source. Configuration choices should be made at compile time. People building from sources today expect to be able to type configure; make; make install. Your code before release. For Python projects, the PyCheck...
software-quality.blogspot.com
Software Quality: Good Development Practices for Open-Source Developers Weblog
http://software-quality.blogspot.com/2005/12/good-development-practices-for-open.html
Share, improve, learn, co-operate on topics related to software quality assurance. Wednesday, December 28, 2005. Good Development Practices for Open-Source Developers. Don't rely on proprietary code. Languages, or libraries. Open-source developers don't trust code for which they can't review the source. Configuration choices should be made at compile time. People building from sources today expect to be able to type configure; make; make install. Your code before release. For Python projects, the PyCheck...
SOCIAL ENGAGEMENT