Topic: pm

Project Management
Software Project Management Stories

Your managers want you to estimate features or projects months or even years in advance. But the work changes—or the code changes, or the people on the project change. What you thought might be a reasonable estimate four weeks ago looks wacko when you revisit it in six months. What can you do?

If the project you're managing goes better than planned—you finish ahead of schedule, under budget, or with greater results than expected—you might be inclined to chalk it up to luck and not want to draw attention. But here's an argument for why you should make sure people notice and you get credit.

Project teams have to learn to manage the difficult personalities they encounter on a project. The key is to identify which type of personality you are dealing with, then quickly apply approaches to smooth over the situation. Here are some tips for handling passive aggressive stakeholders' concerns.

Having participated in a number of unsuccessful metrics programs throughout his career, Lee Copeland has identified and distilled four key principles that help prevent the mismeasurement of software. Evaluate how your metrics work against these four principles. Do you need to make any changes?

Large IT projects are challenging. Complexity is hard to estimate well. Big systems are tough to implement. But when you're staring at a fast-approaching deadline and you know your system will not be functional in time to meet it, there are ways of handling the situation that are better than others.

Ineffective project managers take many forms. Sometimes the PM simply lacks the knowledge or training to do what the job calls for. Sometimes he is eager to please, so he gives ambitious timelines or says yes to every client request. But then, some PMs are just bad. Learn to recognize some signs.

In the latest issue of Better Software magazine, there are insightful articles covering a wide range of topics impacting the software delivery process. Feature articles explore the next wave of computing: mobile and wearable intelligent devices and the experiences and challenges they bring.

We keep changing the names of the development processes we use, but we do not fix the fundamental error they all suffer from: the failure to set a date and control the scope of the project—including proper estimation of testing efforts. Customers and IT must work together to truly be successful.

Many people on agile teams have at least one person who is not collocated. Those on collocated teams indicate that more of their projects are successful; those on far-located teams have the highest number of challenged projects. What can you do if you're part of a geographically distributed team?

Some managers don’t realize that they are not their titles. The value they should bring is the "plus": the management, plus their relationship with their peers, the people they manage, and the systems and environment they enable or create. If you're a manager, are you providing servant leadership?