|
Tests and Requirements: Like Ham and Eggs, Sugar and Spice, Lucy and Desi
Slideshow
The practice of agile software development requires a clear understanding of business needs. Misunderstanding requirements causes waste, slipped schedules, and mistrust within the organization. Developers implement their perceived interpretation of requirements; testers test against...
|
Ken Pugh, Net Objectives
|
|
Are your developers aware of automated testability requirements? Sometimes automation projects either fail or are made far more difficult because developers don't adopt automated testability as a design requirement. Are your developers aware of these?
|
|
|
How to Implement CM and Traceability in a Practical Way Software development can often be a very complex endeavor, so it is no wonder that important details can sometimes get lost in the process. Here, Bob Aiello discusses how to implement configuration management (CM) and traceability in a practical and realistic way.
|
|
|
Leverage Social Media for Requirements Gathering: An Interview with Stefano Rizzo
Podcast
Stefano Rizzo introduces the idea of using social media to encourage customers to get involved in the requirements gathering process. Learn how by introducing something that your customers are already contributing towards, you can capture the mood behind their true wants and needs.
|
|
|
What CM Professionals Need to Know about Business Requirements While we know the technology, some configuration management (CM) experts don’t always have a strong enough business focus, which can be a real problem. Read on if you would like to understand what CM professionals need to know about business requirements and how CM can directly impact the business itself.
|
|
|
An Agile Approach to Thinking Up Front about Requirements Thinking about interacting with the customer at the start of the project? Who would argue against that? Well, it depends on what you call it. It also depends on whether you then do it without the benefit of the rest of the project team. Here, Ulrika Park helps us see what an agile approach to thinking about the requirements might look like.
|
|
|
Find Requirements Defects to Build Better Software
Slideshow
Requirements defects are often the source of the majority of all software defects. Discovering and correcting a defect during testing is typically twenty-five times more expensive than correcting it during the requirements definition phase. Identifying and removing defects early in the...
|
John Terzakis, Intel
|
|
Find Requirements Defects to Build Better Software
Slideshow
Requirements defects are often the source of the majority of all software defects. Discovering and correcting a defect during testing is typically twenty-five times more expensive than correcting it during the requirements definition phase. Identifying and removing defects early in the...
|
John Terzakis, Intel
|
|
An Interview with Dean Leffingwell: ADC-BSW 2013 Interview Series
Video
Committed to covering the latest trends and approaches for anyone investigating or implementing agile development practices, processes, technologies, and leadership principles, Agile Development & Better Software Conference West offers their 2013 interview series.
|
Dean Leffingwell, Leffingwell LLC
|
|
Agile Requirements Is Not an Oxymoron
Slideshow
Misconceptions abound about the way requirements fit—or don’t fit—into agile projects. Is “agile requirements” an oxymoron—two contradictory terms joined together? How is it possible for requirements to be agile? Do agile projects even need requirements? In reality, requirements are...
|
Paul Reed, EBG Consulting
|