Related Content
Manage Project Problems without Getting Trapped by Catastrophic Thinking It would be short-sighted for any project manager not to consider the potential risks in the project and not to evaluate and continue re-evaluating what can go wrong. But there's a difference between planning for risk and falling victim to catastrophic thinking—focusing on unlikely or irrational worst-case scenarios. |
||
When You Should Get Your Project Sponsor Involved If there are decisions to be made on a project, the project manager may think he's helping by going directly to the customer to get her opinion. But project sponsors represent the organization, and they should be consulted before any significant decisions are made. Do you know when you should get the sponsor involved? |
||
Who’s the Boss? Let Agile Teams Manage Themselves This idea of a team in charge of itself is difficult for many people to accept. Traditional practices condition us to wait for someone to tell us what to do, and managers are accustomed to controlling everyone’s work and knowing everyone’s status. But agile teams can manage themselves—in fact, it's essential to agile. |
||
Build the Right Things and Build Them Fast: Accelerate the Continuous Delivery Pipeline When most people think about continuous delivery, they think of improving the build-test-deploy-operate cycle. They don’t think about how to improve the intake process. Ensuring that quality is built into the application—not tested for after the fact—is the key to achieving accelerated continuous delivery. |
||
7 Harms Done by Keeping Unrealistic Project Goals Project management is about supporting informed decision-making. No one wants to break the news that a project is not on schedule, but a good sponsor would want to know that the original goals are no longer realistic. Reluctance to communicate or unwillingness to hear have some real business consequences. |
||
The Importance of Timing when Implementing Change Too many changes at once can prolong upheaval and delay people's adjustment to the new norm. If you are planning to start a complex project, introduce a new tool, or undertake any other major initiative, and employees are still reeling from other changes, it may be wise to delay the planned change if you can. |
||
Improve Software Project Success by Conducting a Hudson’s Bay Start The Hudson’s Bay Company outfitted fur traders in the 1600s. To avoid problems when camping in freezing conditions, they'd send traders on a short trial expedition before the real one. This idea also can be used to reduce risks when starting a software project that’s complex, expensive, or disaster-prone. |
||
The Problem with Software Measurement and Metrics Many software practices rely on setting target numbers for the team to hit. But when a measure becomes a target, it ceases to be a good measure. People start gaming the system by changing their behavior in such a way to favorably adjust the measure in order to achieve the target. Don't get hung up on metrics. |