Tag Archives: SCRUM
Testing Early, Testing Often for Greater Success in Agile SCRUM
In my experiences, I have found two different approaches taken towards testing in Agile SCRUM: Testers creating test plans while interacting with BAs, as like in waterfall model, in the beginning of each sprint, and executing those tests once the development is done. In this model, testers and developers still managed to survive successfully in their own islands/worlds and things used to move. However, there is not much interaction and collaboration between developers and testers during development phase. There are chances of usual conflicts that happens in the world of development and testing. Testers creating test plans with help of BAs, collaborating on test cases, related with user stories, with …
How to Address Application Security in Agile Scrum Teams?
One of the concerns that takes the back burner while setting up the agile SCRUM teams is application security. One other area that gets similar behavior like security is performance which shall be addressed in later articles. However, performance gets addressed quickly as it is key quality characteristic and gets noticed by end users very quickly. In the traditional waterfall based development model, security gets fair attention as the non functional requirements related with security gets captured in the initial stages and the team gets composed of at least one security officer/specialist/architect to take care of security requirements. However, having a security specialist/officer in each SCRUM team is not feasible …
A Centralized R&D Team – Key to Highly Performing Agile Scrum Teams
If you have an Agile SCRUM based development center that consists of multiple SCRUM teams to working on different features and functionality of one or more product, you always have the concerns in relation with highly performing teams in terms of usage of relevant and latest technologies from time-to-time. One of the key challenges in front of SCRUM teams is to make sure that they are using most appropriate technologies at all point of time. This can be achieved in multiple different manners. Some of them are following: Set aside stories for research & development of new tools & frameworks to be done in each sprints. Stories of such kind, …
Agile Design Documents with WebSequenceDiagram Tool
Earlier, I wrote a blog on how to write a winner design document when working in Agile Scrum methodology. The blog has been based on my experience while working with distributed SCRUM manner. Disbelief in Design Documentation for Agile SCRUM I have come across various sections of people who did not believe in design document at all when working in SCRUM manner. Their argument has been that SCRUM is all about encouraging technical discussions through different manners such as white-boarding etc and, adopting design documentation just kills the overall objective. I agree to some extent given the entire team is working at one place and could do quick discussions including …
I found it very helpful. However the differences are not too understandable for me