Agile Velocity is an extremely simple method for measuring the rate at which scrum teams consistently deliver business value. In other words – How much product backlog effort a team can handle in one sprint? It’s the rate at which a team delivers stories from the product backlog, i.e. sum of estimates of delivered (i.e., accepted) features per iteration. It can be measured in story points, days, ideal days, or hours that the Scrum team delivers – all of which are considered acceptable.
This is one of the most common questions discussed among the Agile Community – What happens with the undone User Story of Current Sprint? Why does this happen? How should you deal with the undone user story? What should become of such stories? What should be done with the product backlog item itself? Should be it split or should it be carried into the next sprint? Should the team receive any velocity “credit” for completing a portion of the story? And how do you prevent it from happening again? This article addresses all of these questions.
Agile software testing is the requirement of a modern software development team. Choosing agile testing tools is not an option anymore, it’s a necessity. If you want the end product to be effective, speedy and sustainable simultaneously, you must go with a tool which provides agile testing solutions under a feasible budget.
People. Individuals. Employees. Team Members. Testers. Employees are the backbone to success of any enterprise. Attitude & Skills are the two main ingredients to make or break an enterprise. In my 7+ years of IT career I have come across variety of professionals. With special affinity towards Software Testing Technology, let’s just talk about the types of Software Testers. Yeah! You should not be surprised to know that we do have different category of Software Testers? Seriously!
Today most of the organizations are moving or have already moved to agile development and testing. Or at least they think so. Sprints and daily stand-ups are common. Everybody is talking about Scrum & minimum viable product. We are tracking the team velocity & burndown. We have cut down on the documentation & invested in working software. Everyone is focused on customer satisfaction by accepting change. But wait a minute! This is too-happy a picture to be true.
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read Continuing on our Interview questions series, let’s see some more interesting FAQs related to Domain, Software requirements, Agile Kanban, Career in Testing, SMAC Testing, Automation and Selenium Webdriver.
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read ? Continuing on our Testing Interview questions series, let’s see some more interesting FAQs…
User stories and Use cases are both used to document the requirements. They both capture features of the system. They’re both used by the development team to construct the best solution. They can be used to organize and categorize requirements. And they can be used as references during testing to ensure that the requirements have been met. While user stories and use cases are similar, they also differ in substantial ways. The difference can be challenging to understand and explain, especially if your team is making a transition from a Waterfall software development environment to Agile and Scrum. Each serves a distinct purpose, and they both have their place on a well-run software project. We will try and cover User story vs Use case in this article…
There is no such statement as ‘I am now prepared for the interview‘. When facing a Testing interview no matter how many interview questions and answers you have gone through – there is always more to read ? Continuing on our Interview questions series, let’s see some more interesting FAQs…
Software Testing Levels, Test Data, Waterfall methodology, Agile Scrum, HTML Elements, Selenium Automation, WebDriver, Test Data Management, Scrum methodology
The mobile application ecosystem is very dynamic. OEMs are launching new devices and new customization, and new OS versions are delivered every now and then. This is the constant challenge that most enterprises face. As the new versions of devices and operating systems create capabilities to expand your application, it’s imperative to test your app quickly over an ever expanding variety of devices so your newer versions are as spotless as ever. To achieve this, innovative techniques like Cloud based Testing for Mobile applications are required to be implemented to ensure optimal performance and user experience regardless of the type of his handset, operating system, geographical location and network service provider. Cloud based Testing for Mobile applications offers Web-based access to a large pool of real handsets and devices connected to live networks spread globally, providing enterprises with end-to-end control for manual and automated testing practices.
Transitioning to Agile? Or looking for ways to improve your current agile practice? These 12 Agile Manifesto Principles are a set of guiding concepts.
Many Software development methodologies evolved over the years, but why do you think Agile development stuck? What made it so popular? Yeah, the Foundation! The Agile Manifesto was written in February of 2001 by seventeen independent-minded software practitioners. The Manifesto defines four Agile values and twelve principles which forms the foundation of the agile movement.
“The art of life is a constant readjustment to our surroundings” – being Agile! Let’s see why Agile Methodology is not just an approach, it’s an attitude.
Looking for Software Testing Interview questions? Let us start with basics…What’s the difference between a defect & a failure? What Test methodology did you follow? Which all methods did you use? You have worked at which all Test levels? How did you organize different Test cycles? Involved in what all Testing types? What about the Test artifacts – did you prepare any? Which technique did you use for Test Design or execution? Confused with these fundamental Software Testing Interview questions?