Cross-functional requirements (CFRs), most commonly referred to as Non-functional Requirements (NFRs), form an integral part of software quality. And testing for them and making them as part of the
Cross-functional requirements (CFRs), most commonly referred to as Non-functional Requirements (NFRs), form an integral part of software quality. And testing for them and making them as part of the team's process is an absolute necessity for any team that promises to deliver high-quality software to their users. Often, the emphasis that is placed on the functional requirements are not equally placed on the cross functional requirements in software delivery teams and by the business stakeholders.
There could be multiple reasons for teams to make this decision but one of the reasons I have seen working on different teams is the lack of awareness on how to approach CFRs testing as they come across really vague, like say testability or maintainability, for example. In this workshop I would like to elaborate why it is essential to consider testing for cross-functional requirements and introduce an approach to continuous testing of all the cross-functional requirements and make it as a part of the process.
I will cover how to uncover different CFRs, including those really vague ones, and therefore aid in continuous testing and building quality into the software. This workshop provides the tools and techniques to introduce and implement CFR’s within your teams or organizations. I will share how to create your own CFR template and I will share the knowledge you need to facilitate your own sessions with your teams.