We have moved away from Facebook and Google+ logins. To access your account please use the forgot password link to generate a new password. Alternatively, you can also use LinkedIn to login if your LinkedIn email id matches with your Facebook or Google+ account.
Prioritization is one of the major concepts of agile practices and a very essential topic for PMI-ACP exam preparation towards achieving an agile certification. Prioritization in literary terms means the decision of arranging things in order of their importance. Prioritization in agile is the act of deciding in what order the agile team will work on the requirements in a project. Understanding prioritization is essential for all projects but it becomes specifically critical in agile as an agile project is time-boxed with fixed set of resources which requires prioritization in order to accommodate the time and budget constraints. Further prioritization process helps the agile team to consider the bare minimum features necessary to create customer value. In order to process agile prioritization, it is essential to understand the factors that a product owner needs to consider before determining the priorities. Below are few of the most important factors.
In between that, here is a sample video that takes you through introduction MoSCoW prioritation method:
Agile Prioritization Factors:
The financial value of the requirements is a major factor to be considered in prioritizing requirements. The value could be expressed as new revenue, incremental revenue or as operational efficiency.
The cost of developing the requirements is another essential factor to be considered by the product owner. Value and cost together indicate the RoI for the requirements.
The next factor to be considered in prioritization is the amount and significance of knowledge and capabilities that the team will gain while working on the requirements.
Understanding the level of risks involved in introducing the new features is very essential in the process of prioritization.
Popular Prioritization Techniques:
MoSCoW Agile Prioritization Technique
MoSCoW prioritization – popularized by the DSDM methodology.
Kano model – introduced by Prof. Noriaki Kano
The relative weighting method – by Karl Wiegers
MoSCoW Prioritization in Agile: In the DSDM methodology the priorities are expressed as per the MoSCoW model:
Must – The must requirements is given the top most priority
Should – Next priority is given to the requirements that are high desirable, though not mandatory
Could – The next priority is given to the requirement that are nice to have
Wont – And the final consideration is given to the requirements which will not work in the process at that point of time.
Kano Model of Prioritization in Agile:
Kano Model of Prioritization[/caption] Kano model of prioritization was propagated by Professor Noriaki Kano. This prioritization technique involves three levels that includes considering customer satisfaction from disappointment to not happy to immediate happiness to getting delighted. Two important factors that create an impact on the satisfaction level during this prioritization are the existence of features and the degree of implementation. The level of satisfaction is achieved along with full implementation. Some features lead to basic level of satisfaction while other creates more – the higher the implementation, the greater the level of satisfaction.
Relative Weighting Prioritization Technique: Relative weighing scheme is a simple model where prioritization is done based upon all the factors mentioned above. The major factors considered in relative weighing prioritization technique are:
The value of a feature and the negative impact that might be caused by the absence of the feature
Based on expert judgment made by the product owner and supported by the agile team in ranking the score of features in following way (a score board from 1 to 9 is usually used)
Benefit from having the feature
Penalty for not having the feature
Cost of producing the feature
Risk incurred in producing the feature
The priority and rank is then determined by dividing the value score as below:
In relative weighting prioritization if the results come out in numerical value it becomes easier for the product owner to arrive at a faster prioritizing decision. Using all these three techniques, a product owner performs the prioritization exercise towards achieving customer satisfaction and customer value. The whole process of prioritization in agile is followed in order to create customer value which is possible with innovation, focused execution and lean delivery. To know more about agile prioritization and agile practices, you can join Simplilearn’s PMI-ACP online training course. You can also attend PMI-ACP agile certification training courses in your city to enhance your PMI-ACP exam prep towards achieving your goal of an agile certification. Know the upcoming dates for agile certification training courses in your city.
Chandana is working as a Senior Content Writer in Simplilearn.com and handles variety of creative writing jobs. She has done M.A. in English Literature from Gauhati University. A PRINCE2 Foundation certified, she has a unique and refreshing style of writing which can engross the readers to devour each sentence of her write-ups.
Leave your details and Our training consultant will get back to you
Disclaimer: "PMI®", "PMBOK®", "PMP®", "PMI-RMP®", "CAPM®" and "PMI-ACP®" are registered marks of the Project Management Institute, Inc.
The Swirl logoTM is a trade mark of AXELOS Limited.
ITIL® is a registered trade mark of AXELOS Limited.
PRINCE2® is a Registered Trade Mark of AXELOS Limited.
MSP® is a Registered Trade Mark of AXELOS Limited
Certified ScrumMaster® (CSM) and Certified Scrum Trainer® (CST) are registered trade marks of SCRUM ALLIANCE®
Professional Scrum Master is a registered trademark of Scrum.org
The APMG-International Finance for Non-Financial Managers and Swirl Device logo is a trade mark of The APM Group Limited.
The Open Group®, TOGAF® are trademarks of The Open Group.
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis.
CBAP® is a registered certification mark owned by International Institute of Business Analysis. Certified Business Analysis Professional, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
COBIT® is a trademark of ISACA® registered in the United States and other countries.
CISA® is a Registered Trade Mark of the Information Systems Audit and Control Association (ISACA) and the IT Governance Institute.
CISSP® is a registered mark of The International Information Systems Security Certification Consortium ((ISC)2).
CISCO®, CCNA®, and CCNP® are trademarks of Cisco and registered trademarks in the United States and certain other countries.