Testing
Articles
Know Your Customers: They Can Help You Write Better User Stories Too many user stories begin, "As a user …" Who is your user? Or, more accurately, who are they? Improving your understanding of the types of customers who use your software lets you see multiple products where previously, there was only one—and identifying dedicated products will help you prioritize and accelerate delivery. |
||
User Story Heuristics: Understanding Agile Requirements Agile emphasizes just-in-time requirements rather than upfront preparation. The requirements person—be it the product owner, business analyst, product manager, or someone else—embodies the understanding of what is needed, and the user story represents the work that needs doing. This article details what user stories are (and what they are not). |
||
ADC West 2015 Keynote: Lean UX: Turn User Experience Design Inside Out When developing products, features, and enhancements, you have to have your customers’ best interests at heart. “We’re not just creating software,” speaker Jeff Patton said. “We’re changing the world.” You need to better understand the people you’re building things for, and the only way to do that is to spend more time with them. |
||
Accelerating the Adoption of Technical Practices Agile teams are supposed to take responsibility for how they work and how they learn. But what if you need to jump-start that learning? Agile transformation is about making this happen rather than waiting for it to happen. You need to get your team to learn the technical side of agile, and soon. Here are some effective approaches. |
||
The Three Amigos Strategy of Developing User Stories Developing software correctly is a detail-oriented business. George Dinwiddie writes on how using the Three Amigos strategy can help you develop great user stories. Remember, the goal is to have the work done just in time for planning and development. It should be complete enough to avoid stoppages to build more understanding, but not so far in advance that the details get stale. |
||
Designing Scenarios for Agile Stories The needs to improve the time to market of a quality product and adapt to a changing business environment are driving organizations to adopt agile practices in order to be competitive in the marketplace. However, a project team is bound to face difficulties if it is not trained on the fundamentals of agile. Read on to learn how to design scenarios for agile stories using a structured framework. |
||
Transition to Agile: Large Technical Debt, Small Project When you transition to agile and you have a reasonably size codebase, chances are quite good that you’ve been working on the product for a while. You certainly have legacy ways of thinking about the code and the tests. Now learn how to work yourself out of the technical debt you have accumulated. |
||
Arming Advertisers versus Users: Social Media Platforms at Odds` Twitter and App.net both made headlines recently by taking completely different approaches to reach the same goal: dominance in the world of social media. |
||
From One Expert to Another: Markus Gärtner Markus Gärtner is a tester and the author of ATDD by Example. In this interview with Zeger van Hese, Markus talks about his new book, the software craftsmanship movement, and “Beyond Testing,” a workshop he’ll be delivering later this year. |
||
True Performance: Moving Beyond Basic Load Testing Basic load testing is valuable, but it's important to move past simplistic efforts. Here are some ways to gain more accurate metrics from your load tests. |
Jim Holmes
June 18, 2012 |
Pages
Recommended Web Seminars
Mar 28 | The Testing Practices Fueling High-Performing Software Teams |
On Demand | Building Confidence in Your Automation |
On Demand | Leveraging Open Source Tools for DevSecOps |
On Demand | Five Reasons Why Agile Isn't Working |
On Demand | Building a Stellar Team |