Skip to content

77 Sure Fire Ways to Kill a Software Project

Spend $50 to get a free movie!

ISBN-10: 0595126103

ISBN-13: 9780595126101

Edition: N/A

Authors: Daniel Ferry, Noelle Frances Ferry

List price: $9.95
Blue ribbon 30 day, 100% satisfaction guarantee!
Out of stock
what's this?
Rush Rewards U
Members Receive:
Carrot Coin icon
XP icon
You have reached 400 XP and carrot coins. That is the daily max!

Customers also bought

Book details

List price: $9.95
Publisher: iUniverse, Incorporated
Publication date: 8/28/2000
Binding: Paperback
Pages: 108
Size: 5.75" wide x 9.25" long x 0.50" tall
Weight: 0.484
Language: English

Why We Wrote This Book
Who Should Read This Book
A Note about Gender
Introduction--So You Want to Kill a Software Project...
Unhealthy Project Startups
Bid on Projects Requiring Unrealistic Schedules
Buy a Failing Contract to Enter a New Arena
Make Sure Your Facility Fee is Minimal
Propose a Low Skill Mix
Award the Proposal Team Important Management Slots
Staff from outside the Company
Screen Candidates Mercilessly
Pull SLOC Estimates from the Air
Stretch Those Hardware Dollars
Apply the Waterfall Model
Development Mayhem
Give Your Client That Warm, Fuzzy Feeling
Leave Requirements Gaps and Discrepancies
Begin Design While Requirements Are Fluid
Pick a Fashionable Design Methodology
Generate Useless Design Products
Keep the User Interface Design Ambiguous
Require Abundant Attendance at Inspections
Make Developers Fight for Every Purchase
Get Technically Involved
Design Reusable Units by Committee
Don't Bother with COTS Software
Make Unit Designs Resemble Code
Give Spice to the Design with Asynchronous Processes
Create Lots of Clever New Types
Encourage Designers to Use Complicated Data Structures
Advocate the Use of Side Effects
Establish Exhaustive Naming Conventions
Concentrate on Cosmetics, Not Functionality, at Inspections
Plan Each Build at the Last Minute
Declare System Administration a Part-Time Job
Modify Common Code Frequently
Require Developers to Employ Reusable Software
Forego Prototyping
Don't Plan for Large-Scale Debugging
Make It Fast
Require Exhausting Unit Testing
Dictate Rigorous Verification of Unit Test Results
Don't Plan for Integration Testing
Assign the Wrong Person to Do Integration Testing
Perform Big Bang Testing
Give Everyone Beepers
Let Your Team Make Changes on the Fly
Management Tricks to Guarantee Your Project Will Be Late and Overbudget
Let System Engineering Slip Milestones
Welcome Creeping Requirements, Especially During Coding
Do Lots of Presentations
Make Everyone Stop Development to Update Documentation
Schedule as Many Meetings as Possible
Require Formal Intermediate Deliveries
Punish Teams Meeting Their Schedule
Change the Development Environment
Promise the Client Anything
Don't Worry the Client by Presenting the True Status
Keep Subsystem Leads Busy Writing Reports
Don't Use Technical Editors or Word Processing Experts
Assume the Lowest Common Denominator
Require Developers to Meet Inspection Metrics
Require Formal Inspections for All Code Changes
Jump on the Process Improvement Bandwagon
Create Lots of TQM Groups
Hire a TQM Expert from outside the Company
Morale Busters
Manage from a Distance
Let the Client Call the Shots
Delegate Responsibility, Not Authority
Establish a One-Way Professional Atmosphere
Disregard Developers' Ideas for Improving Productivity
Institute Shift Work
Claim Low Productivity Results from Idle Developers
Require Overtime Work without Compensation
Ask Overburdened Developers to Work Proposals
Hire Temp Programmers
Supply Minimum Training and Conference Opportunities
Give Everyone the Same Bonus
Give Humiliating Performance Reviews
Get Rid of Developers over 40
Refer to People as "Units"
Tie Promotions to Involvement in Process Improvement
Keep the Stockholders Happy
List of Acronyms