Related Content
 |
Signs of a Project Headed for Trouble Projects rarely get in trouble suddenly. More often, the descent into trouble is gradual, and the signs are easy to miss—but they are there. If you detect any of these potential signs of possible failure, it would be wise to take steps sooner rather than later to address them and get the project back on track. |
|
 |
Improving Requirements with Preemptive Testing Most product defects are created during requirements definition. To significantly reduce and prevent requirements problems, consider making their management your software testers' responsibility. They can identify requirements defects as they are being developed, as well as work out mitigations for their root causes. |
|
 |
5 Factors That Could Be Making Your Project Estimates Go Wrong Why do our estimates for a project or a testing phase so often turn out wrong? Whatever causes underestimation, we clearly do not learn from experience, as we repeatedly make estimation errors, despite feedback showing previous errors. It’s a chronic problem. What could be driving these errors? Here are five factors. |
|
 |
The World Has Product Ideas—and So Can You From where do organizations—both big and small—get product ideas? Most often, pioneers and revolution makers have ideas that are homegrown, but today the market is such that the world has ideas. Our industry has plenty of patterns, trends, and ideas to work on and augment. |
|
 |
Project Management in Any Industry Software teams in niche industries may think they require a project manager with expertise in their domain. Good project managers can anticipate and address the primary considerations for any project, regardless of industry, but if you encounter a skeptic, here’s a generic template you can use to pitch any project. |
|
 |
Be Careful What You Ask For: Contract Considerations for New Projects In a new project, there are always going to be challenges and delays, and when the end date is looming, you may be tempted to rush through the contracting and procurement process. But that can have dire consequences down the line if roles, responsibilities, and expectations aren't clear. Take the time to communicate. |
|
 |
The Risk of Overemphasizing Risks We are trained to identify and evaluate risks. This prevents teams from making decisions that are unlikely to work, saving time and money and helping the team move forward. However, a risk-avoidance mindset can also stop progress. Successful agile teams see risks as ways of starting a conversation, not stopping it. |
|
 |
Refining Your Scrum Planning Meetings Scrum events are meant to be productive opportunities for collaboration that replace more tedious, wasteful meetings. If you find your planning meetings becoming passive events where no one is asking questions or actively seeking to understand the backlog, the problem might be in the execution or the preparation. |
