I assign, for my Software Engineering class, fine articles written by other people in the industry. These news letters and reports often do not have a stable URL, so I asked permission to make (unmodified and fully attributed) copies that I could use for this class:

• Kessler: Why Projects Fail
• Brooks: No Silver Bullet
• Spolsky: 12 steps to better code
• Schaefer: Diablo Postmortem
• Boehm: Spiral Development
• Wiegers: Requirements Traps
• Wiegers: Prioritizing Requirements
• Sisson: User Characterization
• Wiegers: Developing Use cases
• Wells: User Story Cards
• Rakitin: What is Quality?
• Spolsky: Five Worlds
• Rakitin: What is Software Quality Assurance?
• Boehm: S/W Defect Reduction
• Wieger: Peer Reviews
• Gabler: Game Prototyping
• SEI: S/W Architecture
• Garlan: S/W Architecture (ch 1-2)
• Foote: Big Ball of Mud (digest)
• Wieger: Inspections
• Wieger: 7 Deadly Sins
• usability.net: User Centered Design
• Talin: U/I Design Principles
• Bay: Designing Games that Don't Suck
• Nielsen: Web U/Is are different from GUIs
• Object Mentor: Packaging Granularity
• Spolsky: What are specs?
• Garlan: S/W Architecture (ch 3)
• Kampe: Common Algorithmic Patterns
• Cornett: Code Coverage
• Kampe: S/W HA
• Bug Life-Cycle
• SWE Metrics
• Black: writing a bug report
• Fowler: Continuous Integration
• Williams: Pair Programming
• Rosenberg: Problems w/Pair Programming
• Global Software Development
• Peters: S/W Project Estimation
• Wiegers: Risk Assessment & Management
• Scrum backlog grooming
• Wiegers: Successful Project Management
• Spolsky: Stealth Process-Improvement