Thoughts on Non-functional requirement in Agile

In an ideal system the below mentioned non functional characteristics could be imagined:


  • Highly Secure
  • Very High performance 
  • Massive flexible 
  • Extremely Scalable 
  • Easy to use
  • Easy to support
  • Simple to develop and maintain
However this comes with a cost hence a careful up front analysis should be done to make an informed  decision on what architecture to choose for the system.

Suggestion is to involve all the people involved in the delivery in the beginning of the project to think through the application. This would help identify the impact on below mentioned activities:

  • System architecture
  • Project schedule
  • Test strategy
  • Overall Cost
Stories with clear acceptance criteria must be created so that these could be tracked and thinking is evaluated.

Remember to avoid such acceptance criteria :  Response time must be "as fast as possible"  If no further analysis is done on such criteria then there are possibility of adding complex code in the system which may not be required in the first place at all the scenarios!!

Source- Continuous Delivery - Reliable Software Releases Through Build, Test And Deployment Automation.pdf

 
 

Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more