Final answer:
To make non-functional requirements visible, a development team should include them in the definition of 'Done' and create specific tasks for them within the backlog.
Step-by-step explanation:
Two good ways for the Development Team to make non-functional requirements visible are:
- Including non-functional requirements in the definition of 'Done' for work items: This ensures that these requirements are considered and checked throughout the development process.
- Creating specific tasks for non-functional requirements within the backlog: By defining tasks related to non-functional requirements, such as scalability or security, it becomes easier for the team to track progress on these important aspects of the product.
Both methods involve early identification and continuous monitoring of non-functional requirements, which can often be overlooked in the rush to develop functional features. By integrating non-functional requirements into the workflow, the development team can ensure that the final product meets all necessary quality standards and user expectations.