5

You seem to have already answered your own question: Scenario: - There are two external user types - sellers and buyers. From this, I infer that you have other roles that are considered internal (e.g. exhibition host, application admin, ...). You inherently listed buyer/seller as "the external user types", because that is what separates them from the ...


5

The statements that you claim should be true in Scrum aren't necessarily true in Scrum, according to the Scrum Guide. It is not true, according to Scrum, that you should be estimating user stories in story points. The Scrum Guide mentions neither user stories nor story points. In Scrum, you have a Product Backlog that contains Product Backlog Items, and one ...


3

How you split the story depends on the sizing of the story. I see two possible options. The first option, and where I would start, would be to write your story in a way that encompasses both user types. An example could be "As a potential exhibition attendee, I want to view the event details of upcoming exhibitions so that I can attend the exhibition." I ...


2

The roadblock you're running into is there by design, and you're running into it for the correct reasons. User stories are things the user cares about. That's why it's written from the point of view of the user. If you can't express your task as a user concern, then it likely isn't a user concern, which is likely the case here. As far as the user can see, ...


2

"Scrum Framework only describes what needs to be done, but does not enforce how it needs to be done." "User Stories are a great technique for capturing functional requirements in a ‘good enough for now’-manner that leaves room for further conversation. But Scrum doesn’t prescribe nor require them. Other techniques are fine, as long as they help promote three ...


1

The official Scrum answer is "Estimate complexity not time and use Story Points" However, on a practical note I would say estimation is not something you want to get hung up on. There are a couple of main objectives scrum is trying to achieve which impact estimation. You can measure progress towards the story in terms of completed tasks. This means that ...


1

Distinct specifications of changes and additions to the product, are called Product Backlog Items (PBIs), that together form the Product Backlog. Each PBI describes something that the Developers can develop and deliver to add value to relevant stakeholders when Done (see Definition of Done). The most common stakeholder is the market, or its representative — ...


Only top voted, non community-wiki answers of a minimum length are eligible