Software development is relatively new when compared to plumbing or electricity. We don’t have stand [...]
In Agile, developers, testers and business analysts build a working product through a series of short iterations. At the end of each iteration, the product owner accepts the software as working or not, and the team moves forward to the next iteration. This kind of acceptance is not the same as the User Acceptance Testing (UAT) traditionally done at the end of the development effort (Waterfall) by business users or end users who have the knowledge of the product to check it’s functionality and ensure that it can support them in their daily tasks on the job.UAT is still seen by most as a critical step in assuring quality software and that it meets the needs of end users, however, UAT does not fit neatly into Agile. For those implementing Agile, this often represents a missing link that causes significant pain. In this blog, we discuss how to solve this problem.
Incorporating User Acceptance Testing into AgileListen in to this webinar with Philip Lew and Cheney Ma as they discuss the problems with User Acceptance Testing and how to implement in Agile when it appears there is no time as the sprints roll on. The trick is in your process and development of user stories combined with detailed yes/no acceptance criteria and tests. Also see how it's implemented in Jira with SynapseRT as Cheney gives a demonstration of complete traceability by associated epics with user stories, user stories with acceptance criteria and tests with defects. View this XBOSoft webinar to learn more >
The software industry is still quite young, yet as it matures, we’ve seen many development trends, technologies and tools come and go. As you know, one methodology that has become popular of late is Agile. We all know it as an adjective, we all desire to be agile. Who wants to be slow and clumsy? Those that gathered and put together the Agile Manifesto certainly chose a good name for “it”, whatever “IT” is. That’s the subject of this article, the definition of Agile or what is Agile? Agile is capitalized from here on, because we all know we’re talking about the noun, as a development methodology, rather than the adjective.
Defect Patterns Analysis for Agile and WaterfallThis XBOSoft webinar, “ ” covers differences between Mobile platforms and Desktop platforms. Meet our guest speaker, Michael Mah in this webinar.Whether you're waterfall or agile, this presentation will uncover 3 keys to accelerating schedule by managing defect prevention, detection, and remediation by software teams. Actual Industry Case Studies will reveal how to implement an end-to-end defect strategy that maximizes the likelihood of team's success. Topics covered will include waterfall, Agile, pair programming, test-driven development, and outsourced projects. View this XBOSoft webinar to learn more >
We've given many workshops and webinars on Agile Metrics and how to connect your agile objectives to measure and improve the agile process. In Rex Black's talk on "Stupid Metrics Tricks" in 2016 at the Pacific Northwest Software Quality Conference, he discussed some of the ways people manipulate and use metrics for their own personal gain, how to that, and how to use them in a productive way. The important thing to remember is that when developing your agile objectives, velocity can be one objective but needs to be balanced with others. And we all need to recognize that...
As software engineers and testers, we are so deep into the “Agile” transformation movement, that we often forget that Agile is also an adjective. Habit #7 is understanding that you must always maintain a "long term view" on your goals and efforts to implement Agile effectively.
As software engineers and testers, we are so deep into the “Agile” transformation movement, that we often forget that Agile is also an adjective. Habit #6 is understanding that you must always maintain "focus on the customer" to implement Agile effectively.
As software engineers and testers, we are so deep into this “Agile” transformation movement, but often forget that Agile is also an adjective. Habit #4 is understanding that you must change parts of your "being" to implement Agile effectively.