The Latest

The Ritual of Retrospectives: Your First Best Tool for a Learning Organization[presentation]

You've just finished your software release. You have signed off, and it's been shipped. You're done, right? No!

Norm Kerth, Elite Systems
Program Management vs. Project Management[presentation]

When a company has multiple products that are related in some way, management may choose to group those projects together under a Program Manager.

Dulcey Branch, Texas Utilities
Enterprise-Wide Change and Configuration Management[presentation]

Multi-tier applications are increasingly strategic for many organizations, but manually coordinating the movement of disparate components-developed and deployed on multiple platforms through the software development lifecycle-can be tedious a

Melissa Borza, Computer Associates International Inc.
When Your Developers Don't Work for You-How I Managed A Band of "Hackers"[presentation]

The future of the development world lies with a bunch of skilled programmers living wherever they want, taking whichever projects they like, naming their price, and disappearing once the project is over.

Lee Fischman, Galorath, Inc.
The Impact of Team/Personal Software Processes[presentation]

Several years ago, the Naval Oceanographic Office initiated its process improvement effort with Team Software Process (TSP) and Personal Software Process (PSP) as its foundation.

Edward Battle, Naval Oceanographic Office
A New Approach for Estimating in e-Business Development[presentation]

In order to control the costs and schedules of new eBusiness development projects, a revolution in estimation and the software lifecycle must take place.

David Duncan, Cambridge Technology Partners
Buffers and Risk: Critical Chain Project Management[presentation]

Critical Chain Project Management uses statistical process control to more clearly define the relationships between tasks and the project end date by using buffers to represent process variation in project tasks.

Robert Muller, Cytokinetics, Inc.
Software Configuration Management[magazine]

Pat Wegerson recommends software configuration management resources AntiPatterns and Patterns in Software Configuration Management and the online CM Yellow Pages.

Pat Wegerson
Manage the Risks and the Process[article]

Including a testing/QA component early in a software project necessarily prolongs the schedule, right? Not so, according to Ross Collard. In this, the third of a three-part series, Collard explains how to anticipate risks and to aggressively manage the process to prevent disaster.

Ross Collard
Can You Predict Danger?[article]

Testers are in a position to see danger coming. Speaking up early about risks that others may not see can save a project. In this article Yogita Sahoo looks at the problem of NOT speaking up, and discusses the unique position of the test team in preventing failures.

Yogita Sahoo
Manage and Strengthen Testing[article]

Including a testing/QA component on a software project necessarily prolongs the schedule, right? Not so, according to Ross Collard. In this, the first of a three-part series, Collard explains how speed and quality assurance don't have to contradict each other. Read his examples of how testing can actually help reduce the time to market.

Ross Collard
Tinkerable Software[article]

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
Driving Forces for Success[article]

Uncertainty and risk weigh in the decision to outsource, or not to outsource. In this article, Jay Boyle provides useful information and tips for knowing when to outsource and making the right decision when selecting an outsource vendor.

Jay Boyle
Bug Counts vs. Test Coverage[article]

Occasionally, we encounter projects where bug counts simply aren't as high as we expect. Perhaps the product under test is in its second or third release cycle, or maybe the development team invested an inordinate amount of time in unit testing. Whatever the reason, low bug counts can be a cause of concern because they can indicate that pieces of functionality (which potentially contain bugs) are being missed. When low bug counts are encountered, management may begin to wonder about the quality of testing. This article covers techniques for dealing with low bug counts, and methods for reassuring management that coverage is being achieved.

Andrew Lance
Failure Is Not an Option[article]

This paper discusses the factors involved in determining the cost of a 24x7 e-commerce or internal Web site going offline for any length of time. After determining these costs, and showing a real-life example calculation, the paper then goes into several ways to minimize this risk via hardware architecture, software architecture, and stress testing.

Ed Bryce

Pages

CMCrossroads is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.