Personas & User stories about blueprint HOT 7 CLOSED

How about using a well defined structure for writing the user stories? I remember Cucumber for Behavior Driven Development. This blog post explains it a bit.

from blueprint.

I'd like to add the Application Owner, its an extension of the cloud-native application developer, this persona would like to try deploying his app and running it, so that he can gather operational experience (which is very different from an integration test) and feed that experience back into the documentation.

Application Owner

• all the info to get the application deployed
• all the docs to pass on to the developers, so that could they can deploy the app
• all the source of info required to run the app

from blueprint.

Let's start with the 2 personas we have in our own team. That would be

• Service Operator
• Service Consumer

"Service" is a placeholder for every ODH and non-ODH component we're running.

from blueprint.

cc @goern with operate-first/apps#108

from blueprint.

bump for more discussion

from blueprint.

I'd add few more personas to consider from top of my head:

• System Integrator
• Platform maintainer (overlaps the Humair's "Users looking to emulate our setup")
• Solution Architect/Technology scout

System integrator

To me this persona signifies somebody who wants to integrate their application into our setup and make it accessible for our users on clusters managed by us. This persons has to be able to obtain the knowledge and understanding into:

• How our setup works in general so they can verify we are genuine and trustworthy.
• what steps he should take to be included - from namespace and user groups creation and creating ArgoCD apps, to how to structure their application manifests to be able to deploy everything they have in their repository, in a single step.
• How to provide us their secrets, what communication channels should be used and where they can see their application status, monitoring and stuff and how they, personally can be alerted on their application misbehavior.

Platform maintainer

I imagine Lars and Ilana to fit in this role. This persona is somebody who can deploy an OCP cluster and wants to get it ready for us, so we can deploy all our applications in there. I'd say this persona has to have access to info about:

• What are the basic needs for us.
• How to grant us the proper access.
• How to deploy our ArgoCD setup in case this is an isolated environment.
• How to attach their cluster to an existing ArgoCD environment in case this new cluster should belong to any existing deployment.

Solution Architect/Technology scout

This persona is quite the opposite to the ones above. This persona should be able to gain trust in our solution so it can be promoted further. This persona should easily obtain:

• All the information on how we do things and why.
• Can easily grant access to an example deployment as an user in any end user role imaginable.
• Should be able to spin up a dev environment without much previous knowledge - in a "single click deployment" way as possible

from blueprint.

I think our bi-weekly meetings and the issues on this repo (labelled accordingly) are where the future discussions are being held, so closing this in favor of those. Re-open if needed.

from blueprint.