TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPassBlogs

Better Software Magazine


Subscriptions

In This Issue >>

StickyNotes >>

Upcoming Events

Back Issues & Reprints >>

Advertise >>

About Us >>

Contact Us


Better Software Home > Back Issues and Reprints > List Back Issues
Back Issues






 2009
November/December
63• Managing Your Analysis Debt
• Countdown to Agility
• Constructing the Quality Story
• Prepare to Succeed
• Outside the Strike Zone
September/October
63• Software Longevity Testing
• The Whos and Wheres of Stakeholder Requirements
• Scrumdamentalism
• Food for Thought
• It Takes a Village
• IDEs and Build Scripts
July/August
63• Software to Go
• Testing the Contract Metaphor
• That’s No Reason to Automate!
• Feel the Burn
• Adapting Inspections to the Twenty-first Century
• Predicting the Past
• Three Kinds of Measurement and Two Ways to Use
• How Agile Practices Reduce Requirements Risks
May/June
63• Issues about Metrics about Bugs
• What to Expect When You’re Automating Testing
• Scrum
• GUT Instinct
• Virtual Realities
April
63• Understanding Software Performance Testing
• Navigating Conflict
• The Trouble with Derivation
• Learning from Experience
• What’s It Mean?
March
63• Lean Portfolio Management
• Taming the Headless Beast
• Building a Foundation for Structured Requirements
January/February
63• Risk-Based Testing in Action
• The TSA and Software Quality
• A Path to Readable Code
• The Kanban Primer
• Building a Foundation for Structured Requirements





 2008
December
63• What's a Manager to Do?
• Six Thinking Hats for Testers
• The Key to Good Interviewing
• The Abolition of Ignorance
• Don't Fear the Repartee
• Train Wreck Spotting
• Lessons Learned in Close Quarters Combat
November
63• Getting Agile With User-Centered Design
• Google Web Toolkit
• Simple Summaries Of Complex Projects
October
63• The One-Hour Regression Test
• Google Web Toolkit
• A Gram of Prevention
September
63• So, You’ve Got a Problem…
• It's in the Way That You Use It
• Keys to Top-Notch Estimates
• A Culture of Trust
• Is 'Agile' Distracting You?
• From Here to Acceptance Test-Driven Development
July-August
63• How to Fail with Agile
• Two Cheers for Ambiguity
• Programming with GUTs
• Give Your Defects Some Static
June
63• The Myth of Risk Management
• Agile Model-Driven Development
• A 'D' in Programming
May
63• It’s a Bug!
• What’s the Deal with Investigators?
• Out of the Rut
• The Chivalrous Team Member
• Let’s Talk Agile
April
63• Incremental and Iterative Development
• Software Quality and the Prisoner's Dilemma
• A 'D' in Programming
• Developers…Start Your Engines
• Where Do I Go From Here?
March
63• Mind The Gap
• Breaking Ground on SOA
January-February
63• Inside SOA
• Designing Reusable Software
• Some Assembly Required
• New and Improved
• The Hawthorne Effect




 2007
December
63• Man and Machine
• Tools for Our Time
• Let Your Values be Your Guide
• A Story About User Stories and Test-Driven Development
November
63• The Measure Of A Management System
• Behind The Scenes
• A Story About User Stories And Test-Driven Development
• 3. . .2 . .1 . .Liftoff!
October
63• Pairwise Testing
• McLuhan forTesters
• Four Tips forTechnique Seeking
• What's on Your Dashboard?
• Transform Your Software
September
63• Users We Don’t Like
• Ready, Aim, Release
• Navigating the Installation
• Skills For Software Smokejumpers

August
63• Your Mom Doesn’t Work Here
• Kicking Off the Slow Software Movement
• Go with the Flow
• Getting Your Hands Dirty
• Games Stakeholders Play
• Extreme Programming Is People!
• Small Releases Big Returns
July
63• The Plight of the Servant Leader
• Test Design with Risk in Mind
• Drawing Out the Facts
• Putting Policy in Its Place
• Quality: It’s All in the Values
June
63• To Track Or Not To Track
• Hurry Up and Wait
• Do You Work in IT?
• An Arsenal of Answers
• Jack be Agile, Jack be Lean
May
63• The QA Catchall
• Testing Around the World
April
63• The Right Stuff
• PMBOK to Agile
• Know What's At Stake
• Rising Above the 7 Percent Rule
March
63• Beat The Odds
• The Ins and Outs of Integration Testing
• Solve the Real Problem
February
63• The Case of the Missing Fingerprint
• Principle-Driven Development
• Big, Complex, and Tested? Just Say “When”
• The Power of Three
• A Box of a Different Color
January
63• From Primitive to Prominent: The Past, Present, and Future of Automated Code Analysis




 2006
December
63• Believing Is Seeing
• Changing The Hand You're Dealt: Better Designs Through Problem Redefinition
• Marine Corps Maxims: Principles for Building Strong Test Teams
• Is There an Assessment in the House? Diagnosing Test Process Ailments in House
• Happy Are the Software Engineers
November
63• Simple Ain't Easy
• Speaking Truth to Power: How To Break Bad News To Those Who Can Crush You
• Get in the Game: Agile Lessons From Video Game Developers
• X Marks the Test Case: Using Mind Maps for Software Design
• A Look at VMware
• William Robert Elmendorf: In Memoriam
October
63• Risky Business
• Master of Your Domain
• Ba and the Art of Development Environments
• The More Things Change... Revisiting a Software Engineering Culture
• The $60 Web-Testing Toolbox
• What's Happening at StickyMinds.com?
September
63• Blink...or You'll Miss It
• Code Improvement
• QA All-Stars
• Test to Impress
July/August
63• The Many Layers of Ajax
• The Factors of Function Testing
• Bridging the Gap
• Proving Our Worth
• A Look at FinalBuilder
June
63• The Declaration of Interdependence
• Old School Meets New Wave
• A Look at QuickBuild
• Static Electricity
May
63• Debunking Myths of Agile Development
• The Truth About Exploratory Testing
• What Lies Beneath
• Developers Who Test

April
63• Refactoring: Small Steps Guaranteed to Help You Clean Up Your Code
• Project Roundup
• From Primitive To Prominent
March
63• A New Strategy
• Taking Our Act on the Road
• Behavior Modification
• A Look at Command Line Utilities
• Tester PI: Performance Investigator
• Help Wanted
February
63• A Critical Line of Defense
• Living by Principles, Not by Plans
• Breaking with Tradition
• Maintaining Your Course
• Patterns without Purpose
January
63• Are We There Yet?
• Bulking Up
• Code with Character




 2005
Annual Tools Guide
63• Getting Your Hands Dirty
• In Search of Defect Tracking Systems
• Fear of Automation
November/December
63• The Good, the Bad, and the Agile Customer
• A Look at Canoo WebTest
• Brushing Up On Functional Test Effectiveness
• Model Driven Architecture
• Metrics Motivation
October
63• Do-It-Yourself
• A Crash Course in Scripting
• Strangling Legacy Code
• A Look at Selenium
September
63• If the Shoe Doesn't Fit
• Three You Should Read
• Putting a Face on Customer Needs
• A Look at PerlClip
• Bring Your Requirements Discussions Down to Earth
• What Goes Up Must Come Down
July/August
63• The Cream of the Crop
• Technically Speaking: The Dark Side of Multitasking
• From the Front Line: Bridging the Gap Between Disciplines
• I Don't Want a Bug Report
• Tool Look: A Look at Subversion 1.2
• The Whole is the Sum of Its Parts
May/June
63• High Performance Testing
• Crossing the Line
• LIghts, Camera, Automate Software Builds and Deployments
• Remaining Relevant
April
63• Watir Works
• It Takes Two to Tango
• Why Agile Projects Do Not Thrash
• Injecting Testability
• Visual Studio
March
63• Creative License
• Form Fitting
• Open Source Disk Imaging with Frisbee: An Interview
February
63• Double Duty
• Testing with an Accent
• The Proper Care and Feeding of Programmers
• Combined Strengths
• Honeybees, Blimps, and Lava Lamps
• The Peculiar Nature of Requirements
January
63• It is All in How You Slice It
• A Look at Worksoft Certify
• Good Tool. Bad Application.
• Testing Without a Map




 2004
Year-Long
63• Are You Ready for the Test Automation Game?
• Decisions, Decisions
• Right Tool. Right Job. Right Time.
November/December
63• A Formula for Successful Peer Reviews
• Alter Your Requirements Process
October
63• Case Your Own Joint
• Warning: Security Storm Brewing
September
63• Continuous Integration
• Is Your Haystack Missing a Needle
• Passing the Baton
July/August
63• Traditional--with a Twist
• Lightweight Development. Heavyweight QA.
• Safety-Critical. XP Rules.
• Unjust Deserts
May/June
63• Just Use It
• Fooling Around with XP
• A Look at IntilliJ IDEA 3
• The Liars Contest
April
63• Domain-Centric Programming
• Behind the Screens
• Remote Control
March
63• (Not So) Trivial Pursuits
• A Perfect FIT
• Make What"s Counted Count
• Want Better Software? Just Ask.
February
63• Saving a Sinking Project
• In Other Words
• No Documentation? No Problem!
• My Mentor: The Internet
• Soap Opera Testing
January
63• No More Second-Class Testers!
• Pair Testing
• An Elephant in the Room
• Promises and Prescriptions




 2003
November / December
63• Inside the Mind of an Exploratory Tester
• What’s Different about Agile Management?
• Logical Capture/Replay
• Let SQA Be Your Guide
• Go With the Bug Flow
September/October
63• Cem Kaner on Scenario Testing
• Congratulations! You"re a Manager. Now What?
• Every Crash, Everywhere
• You Don"t Say
• Make It Personal
July/August
63• Orchestrating Integration Testing
• The Marriage of Estimation and Negotiation
• Eliminating Automation Overhead
• Once Upon a Design
• Leveraging Inspections
May/June
63• Troubleshooting Risk-Based Testing
• The Product Champion
• Visual Requirements
• Are You Ready?
• A Small Matter of Metrics
March/April
63• Security Bugs--Exposed
• Ready, Aim…Hire
• Action Figures
• Knowing the Odds
• Show and Tell
January/February
63• Site Unseen: Testing Web Services
• The Productivity Factor
• Deconstructing GUI Test Automation
• A Calculated Gamble
• Metrics That Matter




 2002
November/December
63• Testing Merged Databases
• Making Virtual Teams a Reality
• Wall-to-Wall Tools
• Test Estimation
• QA Consciousness Raising
September/October
63• A Picture"s Worth a Thousand Words
• Delivering Unwelcome News to Developers
• Bypassing the GUI
• Project Archaeology
• A Measured Response
July/August
63• Mission Made Possible
• Focused Improvement
• Preparing to Choose a CM Tool
• Adopting XP
• A Blueprint for Success
May/June
63• Targeted Fault Insertion
• Agile Meetings
• Bug Tracking Basics
• Go Configure!
• Forecasting Software Defects
March/April
63• Telling It Like It Is
• Karl Wiegers on Humanizing Peer Reviews
• A Lesson in Scripting
• Use Cases, Ten Years Later
• Release Criteria: Is This Software Done?
January/Febuary
63• Learning to Love Unit Testing
• Project Planning: It"s in the Cards
• Managing the End Game
• Meaningful Metrics




 2001
November/December
63• The Test Matrix
• The Human Side of Process Improvement
• Are You Ready for the Test Automation Game?
• James Bach on Explaining Testing to Them
• Getting the Most from Outsourcing
September/October
63• Usability Testing
• Distributed Teams
• Orthogonally Speaking
• Escaping the Clutches of Zombie Projects
• How Good Is this Software?
July/August
63• eXtreme Rules of the Road
• Untangling Communication
• Tracking Down a Defect Management Tool
• Building a Project-Oriented Culture
• Web Page Response Time 101
May/June
63• Adventures in Automated Testing
• At Your Service
• Trade Secrets from a Web Testing Expert
• Requirements When the Field Isn"t Green
• Meaningful Metrics
March/April
63• Web Load Test Planning
• A Recipe for Success
• Bringing Your Test Data to Life
• Collaborate for Quality
• Look Before You Test
January/February
63• Behind Closed Doors
• Managing in Mayberry
• Mining Gold from Server Logs
• Immunizing Against Predictable Project Failure
• When Assessments are Relative




 2000
November/December
63• Session-Based Test Management
• The Quality Barometer
• Risky Beginnings
• Juggling Concurrent Releases
• Measuring Process Improvement
September/October
63• Step-by-Step Test Design
• Perspectives from a Test Manager
• Intelligent Test Automation
• The Ritual of Retrospectives
• Organize Your Problem Tracking System
July/August
63• Software Installation Testing
• Retiring Lifecycle Dinosaurs
• Automating Requirements Traceability
• Keys to Setting Achievable Goals
• Managing the Communication Storm Front
May/June
63• Testing Web-based Applications
• Calculating the Value of Testing
• Build It or Buy It?
• Avoiding Scalability Shock
• Designing Useful Metrics
March/April
63• Effective Test Status Reporting
• The Influential Test Manager
• In Search of Defect Tracking Systems
• Case Study: Selling the CMM
• Cem Kaner on Rethinking Software Metrics
January/February
63• Looking Under the Hood
• Testers and Developers Think Differently
• Using Monkey Test Tools
• Karl Wiegers Describes 10 Requirements Traps to Avoid
• Bayesian Belief Nets




 1999
November/December
63• James Bach on Risk-Based Testing
• Outsourcing
• Getting Automated Testing Under Control
• Modeling Organizational Change
• Estimating Time, Effort, and Cost
September/October
63• The Top 13 Mistakes in Load Testing Web Applications
• Lessons in Test Automation
• Lo-FI GUI Design
• Building Productivity Through Measurement
July/August
63• Test Design
• Integrating Software Suites
• Matching ISO 9000 Registration to Your Organization
• Managing Your ERP Project
• Customer Satisfaction Measurement
May/June
63• On-track Requirements
• Quality Meets the CEO
• Making the Right Choice (GUI tools)
• Anticipating Human Error
• Configuration Management
• Software Measurement Programs
March/April
63• Testing E-commerce
• Packaged-Software Indigestion
• Heuristic Test Oracles
• Testing in the Dark
• Extreme Testing
• Tracking Severity (Issue Tracking Systems)
January/February
63• It"s January 1, 2000… What Have You Overlooked?
• Weinberg on The Essential Team
• Evaluating Tools
• User-Driven Design
• Reporting Systems: Tracking the Details
• Finding the Signal in the Noise

Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2010 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback