Software the Agile Way....

Issue - While the concept of User story is now quite old but still there are still cases where we see the stories are incomplete and not having enough details which would make team feel confident. Possible Cause of the Issue - Reason for such issue could be due to the culture change. With Agile culture, documents are converted into discussions and Product/business feel that details are not required for documented as this is already discussed in the team meeting. And this will remain in either emails or with some people with whom it was discussed.  Another reason is that it takes time to understand and clarify the requirements queries coming from team by the product/business who are not exactly the user rather some documenting people whose job is to write stories. Tips to handle such issues  - To handle issues with culture, I would advise to listen to team and collaborate with team. It is very much important to understand what team wants. Documenting details would ...

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 comple...

How should the software perform when the network is slow? How should the software perform when the network has 5% packet loss? How about 10% or 30%? If the software requires a persistent connection, what needs to happen when the user steps into an elevator, or when the device goes to sleep, or when the application is interrupted by a phone call? The standard screen resolution for smartphones is 320x300 pixels, but tablets are larger and next-generation mobile devices can support HD screens. What should the user see in all that extra white space? We integrate with Facebook, Twitter or Google login. What do we do when that service is down, and how can we test it? Source- http://searchsoftwarequality.techtarget.com/tip/Mobile-application-requirements-Same-process-new-challenges