requirements management

Conference Presentations

Requirements Engineering: A Practicum
Slideshow

Identifying, documenting, and communicating software requirements are key to all successful IT projects. Common problems in requirements engineering are “How do we discover the real requirements?”, “How do we document requirements?”, and “How do user stories fit into requirements?”

Erik van Veenendaal, Improve IT Services BV
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
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
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
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
Driving Down Requirements Defects: A Tester’s Dream Come True

The industry knows that a majority of software defects have their root cause in poor requirements. So how can testers help improve requirements? Richard Bender asserts that requirements quality significantly improves when testers systematically validate the requirements as they are developed.

Richard Bender, BenderRBT
STARCANADA 2013 Keynote: Testing Lessons from Hockey (The World’s Greatest Sport)
Video

Over the years, Rob Sabourin has drawn important testing lessons from diverse sources including the great detectives, the Simpsons, Hollywood movies, comic book superheroes, and the hospital delivery room. Now Rob scores big with breakaway testing ideas from hockey, Canada’s national sport.

Rob Sabourin, AmiBug.com
The Next Level of Agile: DevOps and Continuous Delivery
Slideshow

Mature agile organizations are introducing continuous delivery as a crucial step to realize their goal of delivering business value rapidly. Andrew Phillips highlights implementation issues about how agile development can fit with enterprise release management policies and governance needs. Andrew outlines proven practices and selection criteria for tools to help you address these issues. Then, he presents a DevOps case study demonstrating the continuous delivery process for building, packaging, deploying, and testing a complex application. Find out about deployment support for server and resource configurations, application binaries, database upgrades and rollbacks, messaging, and enterprise service buses. With the right tools and processes you can develop an open, extensible framework that supports additional services and platforms.

Andrew Phillips, XebiaLabs Inc.
The Right Question for the Right Requirements
Slideshow

How often have you gone down the road of developing software almost to completion only to discover new requirements that require significant design and coding changes at the last minute? Requirements analysis is not just writing down what customers say they want. It's about digging down and discovering what they need. Without real analysis, our requirements often end up as poorly defined lists, anemic mock-ups, and incomplete or inconsistent models. Jack Jones spotlights one simple technique to discover these needs: Ask "why?" When the customer states a requirement, ask "why?" to delve down a level to discover their real problem, need, or opportunity. You may find you need to repeat "why?" a number of times. Join Jack to explore the very real consequences of not comprehending customer needs early in the process, and practice better communications techniques to avoid unnecessary requirements and scope changes.

Jack Jones, KMI

Pages

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!