Setting Requirements Priorities |
||||||||||||||||||||||||||||||||||||
|
|
Home > Articles >
Every software development project is bound by some constraints, and more often than not, those constraints include time. In today's competitive market, there is a definite first-mover advantage, and the first company to release its product has by far the best chance of becoming the market leader.
As a result, you must have some tools in your software development process that help you proactively deal with such time constraints. You, as a project manager, must be able to determine ahead of time which features must make it in the product for the customer to accept it, and which can be delivered in the next release. If your development schedule is aggressive, you're inevitably going to cut some features. The question is, are you cutting features that will cost you a sale?
Must-Have versus Nice-To-HaveCustomers are not always reasonable when asked to prioritize requirements, and generally speaking, they'll qualify everything as a must-have. Please login/register to read the entire article.
sponsored announcements and special offers
Learn how IT can better guide its strategic investments and operational resource allocation throughout the service lifecycle. With Service Portfolio Management, IT investments and resources are translated into things the business cares about – services. Download the white paper Service Portfolio Management: Manage IT For Business Value.
Don't re-invent the wheel! Why divert resources to developing business intelligence and analytics functionality when partnering results in improved productivity and more innovation? Check out this IDC white paper from SAP to see why partnering with an established BI vendor presents a compelling economic case.
Register Today and Save 15%!
Register now for a webinar on March 23rd: Looking for a Project and Portfolio Mgmt software?
|
| ||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||