|
Automation Test Suites Are Not God! In today’s age of tight deadlines and accelerating delivery cycles of software, test automation is surely favorable for the world of functional testing and critical to the success of big software development companies. But its various benefits have led to unrealistic expectations from managers and organizations. This article highlights the role and use of automation in an agile context and the irreplaceable importance of manual testing.
|
|
|
The Essential Product Owner—Championing Successful Products: An Interview with Ellen Gottesdiener
Video
In this interview, Ellen Gottesdiener talks about her presentation at Agile Development Conference and Better Software Conference West 2014, the importance of having context for requirements, good ways to set value considerations for requirements, and the common mistakes of product owners.
|
|
|
Top Challenges in Testing Requirements
Slideshow
Studies show that at least half of all software defects are rooted in poor, ambiguous, or incomplete requirements. For decades, testing has complained about the lack of solid concrete...
|
Lloyd Roden, Lloyd Roden Consultancy
|
|
Ambiguity Reviews: Building Quality Requirements
Slideshow
Are you frustrated by the false expectation that we can test quality into a product? By the time an application is delivered to testing, our ability to introduce quality principles is...
|
Susan Schanta, Cognizant Technology Solutions
|
|
Testing Lessons Learned from Monty Python
Slideshow
And now for something completely different...
|
Rob Sabourin, AmiBug.com
|
|
Why Classic Software Testing Doesn’t Work Anymore
Slideshow
The classic software testing team is becoming increasingly obsolete. Traditional processes and tools just don’t meet today’s testing challenges. With the introduction of methodologies...
|
Regg Struyk, Polarion Software
|
|
It’s Time for Requirements Craftsmanship Holly Bielawa explains that being a a requirements craftsman means that you need to test your assumptions in real time while developing a product. Then you pivot as needed, change your business model as you learn, and constantly get out of the building and gather data to determine your minimally marketable product.
|
|
|
Using Goals, Objectives, and Assumptions to Model Value (or Not) Kent McDonald writes that identifying objectives and the assumptions underlying them provides you a way to measure whether the result of your project will actually get you closer to what you are trying to accomplish, as well as the impact your various assumptions have on reaching that objective.
|
|
|
Requirements Elicitation—the Social Media Way
Slideshow
Agile methods have proven their ability to improve project success rates. However, when agile methods are applied to complex projects, we need to further explore the area of effective customer involvement. According to the agile philosophy, the users must be part of the development team.
|
Stefano Rizzo, Polarion Software
|
|
Speed Grooming Requirements with SAFe
Slideshow
Want your sprint/iteration planning to take less than fifteen minutes (excluding tasking)? The key is in the story writing we do during backlog grooming. Although the Scaled Agile Framework (SAFe) has little to say about story writing, this "speed grooming" practice makes iteration planning..
|
André Dhondt, Rally Software Development
|