Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add stakeholder, and possible needs to the context #46

Open
Baasie opened this issue Jun 22, 2023 · 4 comments
Open

Add stakeholder, and possible needs to the context #46

Baasie opened this issue Jun 22, 2023 · 4 comments

Comments

@Baasie
Copy link
Member

Baasie commented Jun 22, 2023

Hello friends!

I want to suggest to add at least a stakeholder field to the canvas. I find it important, also for software architecture, to know who the stakeholders are. These can of course be the users (Specified) that interact with the model, but also departments in the organisation that have certain needs they need to see fulfilled.

For instance, for a cinema, you can model the bounded context called movie screening seat allocation. Who has the stakeholder which is a movie visitor that want to select seats. Then we might also have finance who's needs is it to fully fill the cinema as much as possible. But at some points during corona you also have legal that had certain needs to the context.

Now the more stakeholders on a context can signal that the context might be to big as wel!

Now all can be described right now in the purpose, but I would like to make it explicit in the canvas, including the needs.
Here an example of how it might look like, but first let;s discuss if it is needed!

afbeelding

@Max-Git
Copy link
Member

Max-Git commented Jun 22, 2023

I like the idea and the heuristic "the more stakeholders on a context can signal that the context might be to big as wel!"
But with the example you gave "movie visitor that want to select seats", you might have the same information duplicated in the Inbound Communication section where the collborator would be the visitor (via the App) and the message would be select seats.
I feel like this is a cool idea but we need to turn it in a way that would add value on top of the other sections.
What do you think?

@Baasie
Copy link
Member Author

Baasie commented Jun 23, 2023

Good question, so stakeholders are more than the user alone. And it also depends on how you model the communication.

In this case the 'visitor' user the app, and that app communicates with the BC. So will you put user -> app -> command on it, or just app -> command?

I tbh do not mind the duplication and I believe we can make it more explicit like this.

@Max-Git
Copy link
Member

Max-Git commented Jun 23, 2023

Yeah I don't care about the duplication neither.
Looking at the section description again, I feel like it's more as if you'd take what's inside Customer Segment and Value Proposition from a Business Model Canvas. Am I right? And I think it totally makes sense to have this in a the canvas so that you're making sure you're aligned with the business vision.

@Baasie
Copy link
Member Author

Baasie commented Jun 28, 2023

Can be, domain experts/stakeholders can also be people inside the company. Like the legal department, or payrolling or finance. In this case you might have a business side responsible for filling up the rooms as much as possible. That might be your own team (hopefully) or it might be the venue specialist.

I see it more as the first two things you put on a wardley map. User and their needs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants