Sunday, August 21, 2005

What can cause a product to slip? How do you safeguard against this?

The most common factor in a product slipping is scope creep but it can also occur for a variety of reasons such as lack of resources, which includes information about other products that yours interacts with. This is both the strong suit and the potential weakness of .NET.

For example MS Messenger Service can solve a lot of security issues, when you know how it functions and can test it.

Doing more project planning with dependencies worked in, and resource planning helps.

Letting management know what the limitations are especially when you can not effect needed changes directly from your own level helps safeguard things over time. In this way you are asking for resources before it becomes too late, or making it clear what the results will be if the resources are not available, or if you don't get the information you need on time, raising any issues that can potentially cause product release slipage.

It is important to put this kind of information into written, not just verbal, reports.

No comments: