The Value Play: Prioritizing for Maximum Impact
Once we've analyzed the initial requirements, the next crucial step is prioritization. Everyone has their own method, and it often varies based on the business area. For me, especially since I focus on building sales tools for customers, I typically weigh requirements based on potential volume, revenue, cost efficiency, and rate-of-return. This helps me value them effectively and prioritize accordingly. If I have requirements with similar characteristics, like developing an in-app selling platform versus a sales-web for Bancassurance customers, I group them into a single "Epic" (e.g., "Sales-flow for Bancas"). Then, I prioritize the "user stories" within that Epic and subsequently prioritize Epic against Epic. This structured approach clearly outlines our next steps and easily accommodates new requirements that pop up, ensuring we always know what's coming next.