He needs to bring in various stakeholders into the process and get their agreement on the priority of requirements. Prioritization of requirements cannot be done by the BA alone based on his understanding of the project scope. Whose responsibility is it to prioritize? Hence, prioritization is an important activity that defines what goes into the product and what does not. But, in reality there are only so many requirements that can be developed because of various constraints such as time, resources, etc. Most customers will put their foot down and demand that all their requirements be implemented and the do-it all developers would be willing to provide the customer with any feature he desires. Prioritizing requirements is fraught with challenges – prioritization of requirements requires a good combination of both analytical and social skills.
Stability - It refers to the likelihood of the requirement remaining static.There has to be mention of what time the requirement will expire or also if the requirement is seasonal. Time Sensitivity - Everything comes with an expiry date.As such, a requirement will require the completion of another requirement for its implementation. Dependencies - It is the relationship between requirements.This can be due to various reasons ranging from difficulty in understanding the requirement to implementing the requirement. Risk - It is the probability that the requirement might not deliver the expected value.A resource can refer to finance, man-power or even technology. Cost - It is the effort and resources that are required to implement a requirement.It can refer to the loss in regulatory penalties, poor customer satisfaction or usability of the product. Penalty - It is the consequence of not implementing a requirement.The benefit derived can refer to functionality, quality or strategic / business goals. Benefit - It is the advantage that the business accrues as a result of the requirement implementation.BABOK 3.0 suggests 8 factors that influence the prioritization of requirements. Prioritization means “ Order of importance”. The customer is not wrong on his part the BA needs to understand the needs of the business to prioritize the requirements. But during requirements elicitation the customer provides the Business Analyst (BA) with all the requirements that he feels will make his work easier. Most customers on their part have a reasonable idea of what they need and what they want. There are several constraints such as limited resources, budgetary constraints, time crunch, feasibility, etc., which brings in the need to prioritize requirements. Neither are all requirements equal nor do the implementation teams have resources to implement all the documented requirements.
RELEASE PRIORITY MATRIX SOFTWARE
Large software systems have a few hundred to thousands of requirements.
0 kommentar(er)
