Development Agile Test & Quality Assurance Project Management Requirements
CM & ALM Devops Cloud Mobile People & Teams

By Topic

Requirements

Requirements and Business Analysis Stories
What Is Acceptance Test-Driven Development?

We help define the concept of acceptance test-driven development with the help of an interview between Ken Pugh and Ade Shokoya. As we raise the level of collaboration and shift the relationship between testers and developers, we realize the potential for faster, better products.

Noel Wurst's picture
Noel Wurst
The Product Canvas: A Complementary View

The product canvas, when used with a business model canvas, provides similar benefits to the product owner that the business model canvas provides to the product manager. Scott Sehlhorst examines the product canvas and the business model canvas and how the two tools can be used together.

Scott Sehlhorst's picture
Scott Sehlhorst
Seven Tips for Virtual Requirements Meetings

Increasingly, projects teams are dispersed and may be working not only in different cities but potentially in different countries, continents, and time zones. Adrian Reed offers seven tips to help overcome challenges when facilitating virtual requirements elicitation sessions for a dispersed team.

Adrian Reed's picture
Adrian Reed
Story Roadmaps—Product Vision That Paints a Picture

A product roadmap tells the story of what you’re going to do with your product. It is a manifestation of the vision of what you’re trying to do and why. Scott Sehlhorst explains how best to communicate the product roadmap with your team and the product's stakeholders.

Scott Sehlhorst's picture
Scott Sehlhorst
Project Lessons from the Great Train Robbery

Successful repetition of any business activity can lead to a false sense of security. We often assume that just because something has worked in the past, it will always work in the future. Adrian Reed looks at what we can learn from the Great Train Robbery and how selective perception affects us.

Adrian Reed's picture
Adrian Reed
Why Business Analysts Don't Elicit Requirements

Business analysts don’t gather requirements, but they don’t elicit requirements either. Business analysts have conversations with stakeholders to understand their needs and wants, and that information leads them in the direction of identifying the requirements.

Laura Brandenburg's picture
Laura Brandenburg
The Great PM and BA Debate

The discussion of the relationship between the project manager (PM) and the business analyst (BA) is quite common, and some see a natural career path from senior BA to PM. The BA and PM roles are complementary—and there may be similar shared competencies—but there is a very different focus.

Adrian Reed's picture
Adrian Reed
Get Out There and Learn About Stakeholders' Problems

One of the more often repeated phrases from the lean startup and customer development lexicon is the admonition to "get out of the building" in order to meet and learn about customers. What project teams should take away from this idea is the need to interact with stakeholders to address problems.

Kent J. McDonald's picture
Kent J. McDonald