Overcoming challenges of NFR implementation in Agile

Non-functional requirement (NFR) is key for any application or product implementation but it gets mostly ignored because of functional requirement precedence. Not realizing the importance of NFR at the early stage of agile phase leads to incorrect architecture design which cant scale to customer needs. In agile, it is important to include NFR in product backlog and prioritize in every sprint planning. Agile being an incremental development throws set of challenges on identifying NFR, prioritization and implementation in an efficient way. In this session, I would share my experience in successfully implementing NFR in large scale product implementation following agile model.

 
 

Outline/Structure of the Talk

1. Introduction to Non-functional requirements (NFR) - 2mins

2. Challenges faced in agile model w.r.t NFR - 5mins

3. Recommendations to implement NFR efficiently in agile (including recent project experiences) - 10mins

4. Q&A - 3mins

Learning Outcome

Participants would understand the importance of NFR in any project which are generally ignored but that can cost a lot in the later stage. Those who face challenges in successfully implementing the NFR can get an insight into some of the best practices to make it work in an cost effective manner.

Target Audience

Architects, Development managers, Scrum masters, Test managers, Performance and secuity testers

Prerequisites for Attendees

Brief understanding agile scrum delivery model and non-functional requirements/engineering like performance and security aspect of product or application.

schedule Submitted 2 years ago

Public Feedback


    • Rajkumar Jaganathan
      keyboard_arrow_down

      Rajkumar Jaganathan / Arun Vutukuru - Rapid Test Automation in Agile World

      45 Mins
      Talk
      Advanced

      In Agile world change is expected at any time and it is very essential for the automation team to align the automation framework suitable for the changes. Mainly when the product development is configurable, it is very essential to build automation engine to generate automated scripts rapidly. I had experienced such a challenge from product stakeholders and overcome it by applying innovative design thinking through our automation engine.

      When the team is new to agile and incorporating design innovation to automation with agility is very challenging.

      Our product is a configurable product which can be customized to any customer with minimal code changes. Our Testing Team had taken the Stakeholder’s challenge of Automating the product Configuration and successfully implemented POC on configuration automation. Ability to generate object repository from DB had been achieved and this will give the advantage of automation script development even before UI development. POC on Automation engine which can generate Selenium code snippet based on the entity specification is also achieved. This leads to possibility of Automation engine which can be used for any customer.

      As you participate, you learn the challenges of rapid automation in agile world, how we overcame the challenges of design innovation with our automation framework, and improved the stakeholder confident.

    • Rajashankari
      keyboard_arrow_down

      Rajashankari / Bidhu - Business Agility in Micro Service world

      45 Mins
      Case Study
      Beginner

      Having applications build in micro service architecture along with evolving scope changes in agile world drives us to plan a better test strategy rather than the conventional approaches. There by focusing on the test pyramid and targeting towards integration testing, component testing and contract testing much early and effective in the software life cycle. To accommodate the changing agile scope and requirements and to achieve continuous integration, test scripts are maintained in the same project structure. Along with unit tests that gets executed during every build and qualifies the change made there by having an effective testing builtin with the project. These tests are created and maintained service wise that gets tested independently on every build.

    • Bidhu
      keyboard_arrow_down

      Bidhu / Rajashankari - Scale your Test Execution to Appraise Continuous Testing in Continuous Delivery

      20 Mins
      Demonstration
      Advanced

      The tag line to inject quality into our software is making sure we can get fast feedback on the impact of changes. generally extensive use was made of manual inspection of code changes and manual testing (testers following documentation describing the steps required to test the various functions of the system) in order to demonstrate the correctness of the system.But it can be a time Consuming Process to comply.

      1. Regression Test Cases (UI/Services/API) takes long time to execute and relatively Expense.
      2. Mistakes occur on RepetitiveTask.
      3. Conducting tests during development yields more precise results rather than in a controlled lab environment.