Testers who point out project risks are often perceived as "negative" thinkers. Software test consultant Fiona Charles (an optimist by nature and a pessimist by trade) writes about how a culture of unthinking optimism pervades our organizations and our society, and describes some of its detrimental effects on software projects.
Things change, and when they do, it's best to be ready to change with them. The best plans are doomed to fail if they aren't malleable. In this column, George Schlitz and Giora Morein take a look at the military concept of "Commander's Intent" and how it can apply to non-military project planning.
When you face the discomfort and uncertainty brought about by change, it's tempting to want to do something to deal with the situation. But, acting precipitously could be a big mistake. In this column, Naomi Karten explains why and offers some suggestions of what to do instead.
This short book by Clarke Ching is a "biztech" parable for software developers who want to survive—and then thrive—through the credit crunch. We have republished the book in a four-part series. In part three, when things seem at their very worst, Bob has a "light bulb moment" that just might save the day. Follow the story as our characters fight to keep their jobs by implementing creative business ideas and management skills taken from agile development.
Bob Aiello explains the process to reaching agile comes from more than simply declaring yourself as such. The road to agile is a journal, and one that requires hard work. But once you get there, the benefits can be immense. Making sure everyone on board is dedicated to the cause to reach the goal.
In this interview with Vishwanath Nagaraj, originally published in the Sticky ToolLook eNewsletter, he discusses the concept of distributed agile and some of the tools that help make the idea a reality.
Subject matter experts (SMEs) serve important roles on a project and are especially pivotal during the testing phase. In this week's column, Dion Johnson explores how SMEs positively and negatively affect testing and what you can do to make sure you have the right amount of SMEs on your testing team.
Project time reporting evokes a passionate response from most team members-- the consensus is they hate it. While Payson Hall worries about supporting something so unpopular, he offers benefits of project time reporting and explores some of the common implementation issues that undermine its value.
This short book, written by Clarke Ching, is a "biztech" parable for software developers who want to survive—and then thrive—through a credit crunch. We have republished the book in a four-part series. In part two, Bob, Bill, and Sam discover how a rocky economy can flip project costs and return on investments and how much money could be lost by canning the FBU project. Can they use these projections to save the project and their jobs?
When people begin to get overworked, it's common to fall back on blaming the old chestnut "time management." But the problem may have less to do with how you allocate time to projects than your inability to say no to some of those projects in the first place. In this article, Johanna Rothman takes a look at the difficulty of saying no and offers some suggestions for overcoming it.