Yes, the big idea was that short story titles on cards would help us plan and facilitate lots of conversations between the people who could build software and the people who understood the problems that needed to be solved with it. But, sadly, it takes more than a couple of people to get a finished piece of software out the door.
On a typical team you’ll find project managers, product managers, business analysts, testers, user experience designers, technical writers, and some other roles I’m probably forgetting. They’re all looking at the same cards, but the conversations they have are going to be different because they’ve all got different concerns to look after.
If I’m a product manager or product owner, and I’m responsible for the success of this product, then I have to know a little more about my target market. I need to form some hypothesis about how many people will buy or use this product, or how it’s going to affect the profitability of my company. I’ll want to talk about those things.
If I’m a business analyst, I might be diving into a lot of details, so I need to understand what’s going on in the user interface, and the business rules in the system that are behind the user interface.
If I’m a tester, I need to think about where the software is likely to fail. I need to have some conversations to help ...