When a schedule starts to slip, the project manager should be ready to jump in and get things back on track. Here are some strategies the PM can use that do not involve forcing everyone to work 80-hour work weeks.
603 items found
Recent reports prove that there are significant changes in demographics and the marketplace for workers. Plan now to make these new constraints your project’s competitive advantage.
Stop counting test cases and bug reports in development! They aren’t as helpful as you might think, and there is no direct correlation between these counts and delivered value or quality.
Doing more (overtime) on less (schedule) isn't the smart way to develop software. Why? Because the sooner you want it, the later you'll get it. To break the vicious cycle, you need to negotiate your way to a more realistic schedule. Here's what you can do about unrealistic project schedules.
How you represent yourself both online and in print is reflected in the words you use. This means demonstrating the skills and achievements you’ve attained in an accurate manner while also trying to grab the attention of both automated and human-based searching techniques. Are you guilty of 10 overused words to sell yourself?
The estimation game is widely played--and widely misunderstood. Get the kind of estimates that you need by communicating clearly with your client on reasonable timeframes and costs. Once you start playing the game, you run the risk of losing big.
Why do we gave a hard time listening, and what can we do about it? Read on for advice from experts.
Teams will say that they need to learn how to say "no" more often. Actually, they need to learn ways to decline requests in a positive, productive manner. Here are five recommendations for teams to both properly support their stakeholders while also defending their own productivity.
When faced with a burdensome change request, don’t just roll over or flat-out refuse. Instead, use a ‘conditional yes’ to buy time and develop a full picture of the impact. You may make the case to nix the change, but if you still end up implementing it, at least everyone will know what it takes and why it’s important.