A storyboard that shows the process of a small dev team getting started with Monarch v0.3.0.
Joe manages a small team of developers of which he and Sally are the senior developers and are often responsible for turning the product owner’s requirements into a design and implementation. Fred and Jeff - also team members - are junior developers, supporting the products and directly interfacing with their users for support.
Joe wants to increase the cycle time of the products his team supports and has heard about Monarch from fellow coworkers. He decides to head on over to the Monarch Service Portal to see what all the hype is about. Intrigued with how this may help Joe reach his goal, he decides to give it a spin. Joe logs into the portal using his NIH credentials but is notified that his account is not yet activated. Following the instructions, Joe contacts Monarch support requesting that his account be activated.
Joe is provided an activation key that will enable his account as a standard Monarch User granting him access to define teams and products, deploy supporting infrastructure resources, access and utilize Monarch tooling such as Artifactory and GoCD, and much more!
'NIAID Training Services Products'
Welcome to Monarch!
Joe starts by creating a new team on the portal; his team supports a set of training services that are used in an HR capacity so he creates his first team ‘NIAID Training Services’. Joe’s team already has two groups in AD organizing his team members; one with him and Sally and another with Fred and Jeff. If Joe didn’t already have these two groups he would need to first have them created. These groups could also be specifically for Monarch utilization and named accordingly’.
'NIAID Training Services'
From here, Joe – and Sally once she has also created an account on the portal and been added to the team as an owner – can create products on their team that represent the products the Training Services team currently supports and/or are currently developing.
The products on the team will organize the infrastructure resources that support that product and provide access to services around these resources. As members of the team, both Fred and Jeff can interact with these resources and services and have operational control over things such as running CI/CD pipelines in GoCD, or pulling images built in CI pipelines from Artifactory.