Better Software Magazine Articles
 |
Focused Improvement Improving processes takes planning, time, and effort. A formal improvement project that applies the best practices of development to process improvement can help focus your team and effect real and lasting change. |
Karen King
August 1, 2002 |
|
Agile Meetings Does the thought of going to yet another meeting make your head spin? Read about how to increase your team's productivity by making your meetings short, frequent, and focused. |
||
|
Ken Schwaber on Agile Processes Agile processes are founded on an empirical model of process control theory, and they deliver value iteratively and incrementally. Customers and development teams collaborate to wrest the greatest value from advanced technologies and emerging requirements, which practitioners call "value-driven" software development. Here, the developer of the agile process Scrum gives his recommendations for sources on agile processes. |
Ken Schwaber
July 30, 2002 |
|
|
Tinkerable Software In what ways should software be like a house? In a recent issue of STQE magazine, Technical Editor Brian Marick’s musings about the concept of “tinkerable software” generated some interesting discussion about the very nature of software design. This week’s column runs a portion of that piece so that our Sticky-minded readers can sink their thoughts into the concept. |
Brian Marick
July 30, 2002 |
|
|
The Two Faces of Quality Lina Watson questions the conflicting views of quality assurance and describes the distortions that can occur between software process realities and their perceived image in the corporate world. |
Lina Watson
June 26, 2002 |
|
|
A Baker's Dozen of Dirty Words III offers alternatives to thirteen commonly misused terms and phrases, including walkthrough, quality assurance, phase, O-O analysis, maintenance, function, and estimate. |
I II
June 26, 2002 |
|
|
One Size Does Not Fit All For all of the effort we've made in the software field to find the best methodology, the best programming language, the best operating system, the best set of tools, even the best process maturity model—the search for the "best" is often futile. Robert L. Glass urges you to not be confined by a software approach that doesn't match your specific needs. |
Robert L. Glass
June 26, 2002 |
|
 |
Faults of Omission Brian Marick is obsessed with faults of omission in software code, and he thinks you should be too. In this Bug Report, Marick describes coding omissions, design omissions, and requirements omissions, and offers some ways to prevent (or at least test) them. |
Brian Marick
June 26, 2002 |
 |
The Spirit of the Times Brian Marick points to Web resources and email lists that help keep you current with software and computing trends. |
Brian Marick
June 26, 2002 |
|
Learning from Pathfinder's Bumpy Start Steve March discusses problems experienced by the Mars Pathfinder. He imparts the following lessons: 1) design defensively in the face of complexity; 2) design defensively for post-shipment problems; and 3) beware of best cases. |
Steve March
June 26, 2002 |
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.