Personas

[balhar-jakub]

At the moment we miss unified language when talking about the people using Zowe. This means that often when explaining who is specific feature for or what is the problem we need to explain a lot about the actual person.

The goal is to create accessible repository of the key people that are involved with Zowe. From the decision makers that must agree with putting Zowe on the system to the individual contributors installing, configuring and using the Zowe.

We already started the effort for the education work. The initial state is available below.

What we have ready at the moment

Personas

Administrator

zOS (System Programmer)

Senior

Operates applications on zOS platform for many years or decades. Knows the environment and the application running there inside out. Most of the TN3270 commands could recite in the middle of the sleep. He favorit tool for any work is TN3270 and doesn’t feel any need to change it. Also quite often like the status quo and don't want to change it.

Junior

Is new to the operation of the application on zOS platform. Rarely knows how things work and have to always search for the answers, often unsuccessfully due to lack of available zOS resources. Doesn’t want to bother senior ones too often and prefer ro find the answers self-service. Doesn’t feel happy with TN3270 environments and want to use more modern tooling. Also wants to automate repeating tasks and would like to use modern tools he was hearing about.

Windows / Mac OS X

Is responsible for installing, updating and patching applications available to the people on their machine. This could include the virtual machine. Creates the default installation image and in case of virtual environments, creates the baseline image.

The person is heavily concerned with security and believes that people should have access limited as much as possible.

SRE

zOS

Junior. Unless we consider SysProgs in this role, this field is too young in zOS world.

Hybrid

SRE is responsible for helping engineers with the day to day operations of their services. Building the tools to deploy, operate and observer the applications within the environments within which they are deployed. Also helps with setting up standards across the enterprise for the operable applications. In the day to day work SRE depends heavily on APIs and CLI tools to consume them. SRE also uses usually more lightweight IDEs such as VS Code.

Application Developer

zOS

Senior

Has experience mainly with languages such as HLASM, C, Metal C, COBOL and maybe a bit of Java. Has been developing applications for zOS for many years or decades. Feel comfortable within the TN3270. Rarely uses modern IDEs

Junior

Has experience mainly with languages like Python, Java, .NET, Go, JavaScript. Doesn’t have any experience with TN3270 and doesn’t want to learn the tool. Depends on modern IDEs such as VS Code and Intellij for daily work.

Hybrid

Has experience with some of the languages available on the market. Is used to the deployment in the distributed environment and is familiar with the DevOps principles and usually adheres to them. Depends on modern IDEs such as VS Code and Intellij for daily work. Usually operates the solutions it built.