The Latest
|
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. |
||
|
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. |
||
|
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. |
||
|
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. |
||
|
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
April 23, 2002 |
|
|
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
March 26, 2002 |
|
|
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
March 21, 2002 |
|
|
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
March 20, 2002 |
|
 |
Build and Deployment Process for Web Applications[article] This paper describes practices that have led to a sound and reliable build and deployment process at Hewlett-Packard. Two teams of engineers, later joined by a third, responsible for developing e-service components to build a Web application, chose to use open source development tools/utilities in the "Evolutionary Software Development Lifecycle" environment. |
Bhushan Gupta
March 14, 2002 |
|
Extreme Programming Considered Harmful for Reliable Software Development[article] This paper presents data collected on extreme programming (XP) and how this method relates to traditional software engineering practices. The author presents reasons—albeit no scientific proofs—why extreme programming may be harmful to a reliable software development project. The paper also discusses why Extreme Programming fails to provide answers to significant questions that contemporary software development methods have to answer. The Extreme Programming hype, and its variant in the "Agile Methods" packaging, currently dominates the software development scene and should be investigated and evaluated before assuming it is the best method for a particular project. This paper is an attempt to contribute to the discussion. |
Gerold Keefer
February 19, 2002 |
|
|
What Does Success Look Like?[article] How do you know when software is ready to release? This article discusses one piece of knowing when the software is ready to release—knowing what a successful release would look like. |
Pages
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.