Great webinar!

Been doing this for a long time. It's a core deliverable of UX designers.

@Boris - I think you're right. This requirements traceability article definitely needs some refreshing. We'll need to find somebody willing to do so.

This looks good

Because we (manufacturers of traceability tools) are criticized in the article, I would like to comment on this: The most recent source in the article is from 2009... it is perhaps a bit outdated. We have actually done something since then ... and continue to work.

Here is a customer statement as proof:

“The elimination of manual effort, especially the manual maintenance of Excel matrices, is a great relief; YAKINDU Traceability helps us to work 70% more efficiently and clearly structured in our projects ... The use of this professional software tool was very well received by the OEMs (and strengthened the relationship of trust)”

Take a look yourself: http://itemis.com/traceability

A nice and very important contribution. We totally agree that Requirements Engineering is indispensable in all – even in agile project settings! In our certification schemes we provide an insight how to elicit, document and manage requirements in agile projects. Our syllabus and handbook is available at no charge and for download from: https://www.ireb.org/de/cpre/re-agile/

Regarding the section about "Requirements Traceability Best Practices":

I'm missing one point: Be benfitial! With well managed traceabiltiy data, it is so easy to provide reports that help both managers and engineers in their daily work. Here's a rough illustration and an emperical prove for this point: https://www.itemis.com/en/yakindu/traceability/documentation/user-guide/benefits_of_requirements_traceability#benefits_of_requirements_traceability

Great article series on requirements! Thank you Dan for your insights.

Once an analyst has chosen the method(s) by which to select which requirements have highest priority, she should turn to her colleagues and other stakeholders for input to ensure that everyone is in agreement regarding the emphases of the project. She should also ensure that they understand and agree on the method(s) by which the requirements will be prioritized.

When it comes to the process of assigning a requirement’s priority, any requirement may be prioritized at any point in its lifecycle, according to BABOK. But regardless of when it is done, before a requirement can be prioritized, an analyst must consider what is most important from a business standpoint. There are a number of possible business considerations , including value, cost, risk, difficulty of implementation, likelihood of success, stakeholder agreement and urgency, each of which is described in more detail below. Often, a combination of these methods is used when considering the business need; rarely is one alone used in a vacuum.