Elevator Pitch
Nonfunctional Requirements define system attributes failing to meet any of them can result in system and applications that fail to satisfy critical business objectives and goals. This session is about modelling and sizing critical NFRs for complex distributed applications and systems on cloud.
Description
Nonfunctional Requirements -NFRs define system attributes such as security, reliability, performance, maintainability, scalability, and usability. They serve as constraints or restrictions on the design of the system across the different backlogs. Non-functional requirements are just as critical as functional Epics, Capabilities, Features, and Stories. They ensure the usability and effectiveness of the entire system. Failing to meet any one of them can result in systems that fail to satisfy internal business, user, or market needs, or that do not fulfill mandatory requirements imposed by regulatory or standards agencies. Non-compliance to NFRs can also cause significant issues such as privacy, security, safety, to name a few. NFRs are persistent qualities and constraints that, unlike functional requirements, are typically revisited as part of the Definition of Done (DoD) for each Iteration, Program Increment (PI), or release. NFRs influence all backlogs: Team, Program, Solution, and Portfolio. Proper definition and implementation of NFRs is critical. Over-specify them, and the solution may be too costly to be viable; under-specify or underachieve them, and the system will be inadequate for its intended use. An adaptive and incremental approach to exploring, defining, and implementing NFRs is a vital skill for Agile teams. This session is about modelling and sizing critical NFRs for large distributed systems on cloud.