<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Momenton - Medium]]></title>
        <description><![CDATA[Momenton - Medium]]></description>
        <link>https://medium.com/momenton?source=rss----29269809ff78---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Momenton - Medium</title>
            <link>https://medium.com/momenton?source=rss----29269809ff78---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:05:04 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/momenton" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Secure Your Containers Now! with Automated Docker Build Pipelines]]></title>
            <link>https://medium.com/momenton/secure-your-containers-now-with-automated-docker-build-pipelines-e869c2a1c671?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/e869c2a1c671</guid>
            <category><![CDATA[containers]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Timothy OBrien]]></dc:creator>
            <pubDate>Thu, 30 Sep 2021 01:02:55 GMT</pubDate>
            <atom:updated>2021-09-30T01:02:55.036Z</atom:updated>
            <content:encoded><![CDATA[<p>Secure container images from the ground up with automated image builds.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5xbXFXmq3E2QJU4H4lP9_w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@lazycreekimages?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Michael Dziedzic</a> on <a href="https://unsplash.com/s/photos/secret?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Container image platforms, like <a href="https://hub.docker.com/">Docker Hub</a>, have made it easier than ever for software developers, cloud-native engineers and DevOps teams to create and share fully bundled images of their applications.</p><p>A recent study of over 200 IT Leaders by <a href="https://www.capitalone.com/tech/cloud/container-adoption-statistics/">CapitalOne</a> shows that 86% wanted to <em>“use containers for more applications”</em> across the enterprise; with their key drivers being compliance and portability.</p><p>Given the rapidly increasing adoption of this paradigm, containers have landed at the heart of many environment’s security profiles. Therefore, ensuring the contents of these containers are free from security vulnerabilities has become a critical exercise for maintaining a secure container infrastructure.</p><p>In this article, we will build a fully automated CI/CD pipeline that produces a Docker image for our application. We’ll focus on a combination of tools and methods that help us to produce a secure image that is both well tested and free from known security vulnerabilities.</p><h3>What will I need?</h3><p>We will use the following components to assemble our secure container image build pipeline:</p><ul><li>A <a href="https://github.com/">GitHub</a> Repository for holding your Dockerfile and pipeline code.</li><li><a href="https://github.com/features/actions">GitHub Actions</a> for building our automated CI/CD workflows.</li><li>A local <a href="https://docker.com/">Docker or Docker Desktop</a> running on your computer. This is optional but useful for testing images as you go.</li><li>Terminal commands for Linux or macOS. If you’re on Windows, I recommend WSL2 with Ubuntu or similar.</li><li><a href="https://www.gnu.org/software/make/">GNU Make</a> we will use a Makefile to execute our pipeline commands.</li></ul><p>We’ll also be using some awesome Open Source tools that are called via GitHub Actions plugins. These include:</p><ul><li><strong>Goss</strong> Quick and Easy server validation <a href="https://github.com/aelsabbahy/goss/">https://github.com/aelsabbahy/goss/</a></li><li><strong>Hadolint</strong> Dockerfile Linter <a href="https://github.com/hadolint/hadolint">https://github.com/hadolint/hadolint</a></li><li><strong>Grype</strong> Vulnerability scanner for container images <a href="https://github.com/anchore/grype">https://github.com/anchore/grype</a></li></ul><h3>What are we making?</h3><p>The following diagram shows the automation workflow we will build in GitHub Actions to produce our secure Docker images:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Td8zAaEMFonj_Gcpys0CzA.png" /><figcaption>Secure Docker Image Build Pipeline</figcaption></figure><h3>Let’s get started!</h3><p>All of the code for this exercise can be viewed below, or downloaded from the following GitHub repository:</p><p><a href="https://github.com/obrientimothya/tutorial-secure-docker-image">https://github.com/obrientimothya/tutorial-secure-docker-image</a></p><h4>Step 1. Dockerfile</h4><p>In this exercise, we will build a docker image that contains some useful Terraform tools, as well as the Goss server validation tool that we will use later for testing.</p><p>Create the following Dockerfile at the root of your repository:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/644543dd126984d3b92ea194f419ceaf/href">https://medium.com/media/644543dd126984d3b92ea194f419ceaf/href</a></iframe><p>As you can see, we are using version Alpine 3.10.6 as our base image, with the Terraform and Goss versions controlled by ARG variables.</p><blockquote>Note that we are including our alpine:3.10.6 image using the sha256 reference method. Image tag values can be overwritten by upstream developers, therefore they do not provide a guarantee that the contents of a version won’t change over time, or be interfered with my a malicious actor.</blockquote><blockquote>A more secure method is to provide a sha256 digest reference. This ensures that the exact same image is pulled every time, regardless of upstream tag changes.</blockquote><h4>Step 2. docker-compose.yaml</h4><p>Create the following ‘docker-compose.yaml’ file in the root of your repository. This will be used to call the Hadolint syntax linter:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd5456caf9f2e9da9036a88b73974065/href">https://medium.com/media/dd5456caf9f2e9da9036a88b73974065/href</a></iframe><h4>Step 3. Hadolint Configuration File</h4><p>In the root folder, create the following ‘.hadolint.yaml’ configuration file to control Hadolint’s parameters:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/92f8c6f366af1fe598164e07c2fe1aef/href">https://medium.com/media/92f8c6f366af1fe598164e07c2fe1aef/href</a></iframe><blockquote>This step forms part of our Secure Configuration. Note that we are only allowing docker to pull from Trusted Registries. For this exercise, we will allow docker to pull images from docker.io and ghcr.io.</blockquote><blockquote>Limiting the registries that docker has access to will prevent accidentally pulling base images from unapproved sources. For instance, if you have an internal docker registry in your environment (such as JFrog Artifactory) you should set the trustedRegistries to allow it only.</blockquote><h4>Step 4. Makefile</h4><p>Our Makefile will be used to execute the commands required by our pipeline.</p><p>The Makefile defines the three stages, ‘Lint’, ‘Build’ and ‘Test’ that we will trigger with GitHub Actions in the next steps.</p><p>Create the following Makefile in the root folder:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/157e41dde181df085bf15997632ec3f6/href">https://medium.com/media/157e41dde181df085bf15997632ec3f6/href</a></iframe><h4>Step 5. Goss Tests</h4><p>Create the folder structure .<strong>/tests/goss.d</strong></p><p>Add the following ‘goss.yaml’ file to the ‘./tests’<strong> </strong>folder:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc6b46059555c3c72e3660215310e79c/href">https://medium.com/media/bc6b46059555c3c72e3660215310e79c/href</a></iframe><p>Add the following file to the ‘./tests/goss.d’ folder:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1234dbc34668897e57f00b698c492318/href">https://medium.com/media/1234dbc34668897e57f00b698c492318/href</a></iframe><blockquote>Review ‘goss_files.yaml’.</blockquote><blockquote>Here, we are running tests to ensure that the binaries inside our image match an expected SHA hash. This security measure ensures that any binaries downloaded during the docker build phase are valid.</blockquote><blockquote>If a malicious actor modifies any of the binaries upstream, these tests will fail and prevent us from incorporating unknown content into our image. <br>Awesome, right!</blockquote><h4>Step 6. GitHub Actions</h4><p>Create the folder structure <strong>.github/workflows</strong> and add the following to ‘.github/workflows/GHA01-pull-request.yml’ :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/3056eb8c0f786742771a573993cd22a9/href">https://medium.com/media/3056eb8c0f786742771a573993cd22a9/href</a></iframe><p>Have a read of the <em>pull-request</em> file. We are defining the ‘Lint’, ‘Build’, ‘Test’, ‘Scan’ and ‘Push’ stages that will happen automatically whenever a developer raises a pull request:</p><ul><li><strong>Lint</strong> — Executes make lint to run the Hadolint linter to check the syntax of our Dockerfile.</li><li><strong>Build</strong> — Builds an image based on our Dockerfile</li><li><strong>Test</strong> — Executes make test to perform the Goss tests we defined above to ensure that the image contains the exact versions of assets we expect.</li><li><strong>Scan</strong> — Performs a Security Scan for any known vulnerabilities that exist in our image. Uses the ‘anchore/scan-action@v2’ GitHub Actions plugin to run the Grype scanner.</li><li><strong>Push</strong> — Publishes a test version of the image to the GitHub Container Registry and adds a comment to our pull-request with the details of the image.</li></ul><p>Now, create the ‘.github/workflows/GHA02-push-main.yml’ :</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/d5c607cf889cb71b565b2656d80930d0/href">https://medium.com/media/d5c607cf889cb71b565b2656d80930d0/href</a></iframe><p>The <em>push-main</em> workflow is automatically triggered when a passing pull-request is merged to the ‘Main’ branch. The workflow here is much the same, except for a further ‘Tag’ step:</p><ul><li><strong>Tag</strong> — Adds a Git Tag to the main branch and creates a new Release for the final secure image.</li></ul><h3>Ready to Run!</h3><p>Let’s get secure!</p><ol><li>In your GitHub repository, raise a Pull Request to trigger GitHub Actions.</li><li>Under the Actions tab, open the job for your pull request, similar to below:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Zr-qHGyXU9ic9BJyRInKeg.png" /><figcaption>pull-request actions with failing scan</figcaption></figure><p>At this point, you will see the overview of our secure build workflow: Build and Lint, Scan and Test, and Push. Also, the page shows us any Annotations (errors) and Artefacts (our built docker image called ‘secureimage’)</p><p>As you can see, our ‘J04-scan’ job is failing. Annotations indicate that our scan discovered security vulnerabilities in our image (Oh, no! Danger! We’d better fix these in the next section!)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1rQ5MUtzBMRhmOHJYzi0ZA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Kelly Sikkema</a> on <a href="https://unsplash.com/s/photos/warning?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Security Reporting</h3><p>In the previous section, we saw that our Scan job had failed. To see more detailed reporting on the exact security vulnerabilities found, GitHub can display the details of the ‘results.sarif’ that we uploaded during the pull-request job:</p><ol><li>In your GitHub repo, open the ‘Security’ tab, then choose ‘Code scanning alerts’</li><li>In the ‘Filters’ input, enter is:open pr:&lt;number&gt; where &lt;number&gt; is the ID number of your Pull Request from the previous section.</li><li>Code Scanning shows the detail of the CVE’s found, per the image below:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xXsx8IkTzx9LYm8P5p9rrw.png" /><figcaption>Code scanning alerts report</figcaption></figure><blockquote>Excellent! At this point we now have a working build pipeline that fails when it detects security vulnerabilities in our packages.</blockquote><blockquote>We also have detailed security reporting that points us to the source of any found vulnerabilities so that we can patch them before they impact our operations.</blockquote><h3>Patching Vulnerabilities</h3><p>The security report showed vulnerabilities in some of the packages in our base Alpine 3.10.6 image. This release of Alpine is quite old, so we should start by trying to upgrade it to a newer release:</p><ol><li>Edit the Dockerfile in your repository.</li><li>Remove the line starting with FROM alpine@sha256abd435...</li><li>Replace it with FROM alpine:3.14 <em>(note: please use the most current Alpine version from </em><a href="https://hub.docker.com/_/alpine?tab=tags&amp;page=1&amp;ordering=last_updated"><em>Docker Hub</em></a><em> as this may change by the time you read this)</em></li><li>Save and Commit, then push to the pull-request with your new Dockerfile to re-run the pipeline:</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2jZreyzHHcQjURO5kcHfVg.png" /><figcaption>passing pull-request pipeline</figcaption></figure><blockquote>Success! The pipeline is now passing and is free from known security vulnerabilities.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I-GCCvaE-InPbnCOfWfo9w.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@mbaumi?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Mika Baumeister</a> on <a href="https://unsplash.com/s/photos/hero?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Some Other Things for you to Explore…</h3><ul><li>Check the comments section of your Pull Request. You’ll notice that GitHub Actions has posted a link to your new docker image so that you can test it in your environment - such as locally via docker or in a Kubernetes configuration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/931/1*5p8kn7NAULF5WLFxjbPUBQ.png" /><figcaption>link to testing image</figcaption></figure><ul><li>Once all your checks pass, you can merge your pull request into the ‘Main’ branch. This will generate a new tagged release of your image, so that you can consider it for use in production:</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/942/1*vk6kUKKK1kDQbDvRiyjHdQ.png" /><figcaption>release generated on merge to Main</figcaption></figure><ul><li>Explore the Hadolint and Goss tools in more detail to understand their value.</li><li>Consider how you might schedule your security scans to ensure your latest code remains secure?</li></ul><h3>Thanks!</h3><p>Security is a critical focus for automated systems. By incorporating security awareness and reporting directly into our container build pipelines, we saw how we could catch and remediate security vulnerabilities as early as possible in the containerisation life-cycle.</p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> or send us a message on <a href="https://www.linkedin.com/company/momenton/mycompany/?viewAsMember=true">LinkedIn</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e869c2a1c671" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/secure-your-containers-now-with-automated-docker-build-pipelines-e869c2a1c671">Secure Your Containers Now! with Automated Docker Build Pipelines</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Kickstarting your First Kubernetes Operator]]></title>
            <link>https://medium.com/momenton/kickstarting-your-first-kubernetes-operator-4252b09f92bc?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/4252b09f92bc</guid>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[kubernetes-operator]]></category>
            <category><![CDATA[workflow]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Ankur Soni]]></dc:creator>
            <pubDate>Mon, 06 Sep 2021 00:48:19 GMT</pubDate>
            <atom:updated>2021-09-06T00:48:18.981Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4uopW-y0YhVjbM3rDT3MBg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@carrier_lost?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Ian Taylor</a> on <a href="https://unsplash.com/s/photos/container?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Kubernetes Operators are a powerful mechanism for extending Kubernetes to perform application-specific functions. Operators can seem like magic, automating tasks that ensure Kubernetes clusters are healthy and optimal. It may seem daunting to start using Operators after all Kubernetes is complex, however, they are worth the effort to understand, use and maybe even create your own.</p><p>Read on to see how Operators can improve your Kubernetes experience and optimise the way you work with your Kubernetes cluster. This article will paint a picture of the importance of Operators, touching on: what they are and when to use them, the existing operator ecosystem both from an implementation and development lens and provide some best practices when building your own Kubernetes Operator.</p><h3><strong>Why use Kubernetes Operators?</strong></h3><p>Operators are useful when there is a need to automate Kubernetes resources on an ongoing basis. This piece of automation, once bundled as a controller code and its custom resource definition forms the Kubernetes operator.</p><blockquote><em>‘Operators make use of custom resources to manage applications and their components. Operators follow Kubernetes principles, notably the control loop.’ [1]</em></blockquote><p>- <a href="https://kubernetes.io/docs/concepts/extend-kubernetes/operator/">Kubernetes.io</a>.</p><p>Operators allow an application to interact with Kubernetes API and whose behaviour is driven by its own specific manifest, namely a custom resource. Figure 1 provides an overview of how operators work from a user modifying a custom resource and the reconciliation loop that drives the operator to keep the desired state in sync with the current state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B_blHGRJ1E2HIqB5" /><figcaption><strong>Figure 1: </strong>Operator Concept <a href="https://blog.container-solutions.com/kubernetes-operators-explained">blog.container-solutions.com</a></figcaption></figure><p>You can use Kubernetes objects such as pods, config maps, and secrets to run your application. For simple applications, this is just fine. But what if you want an overarching management layer that observes these native Kubernetes objects and changes their state based on events? The simplest example of such a need was first expressed by distributed database clusters running natively on Kubernetes:</p><ul><li><a href="https://operatorhub.io/operator/etcd">etcd</a></li><li><a href="https://operatorhub.io/operator/redis-enterprise">Redis</a></li></ul><p>These operators encapsulate the automation code necessary to scale out or scale in a distributed database cluster. This is without intervention to the stateful sets or Kubernetes configurations needed to achieve the same outcome for their desired state.</p><p>A more complex example is that of the <a href="https://operatorhub.io/operator/elastic-cloud-eck">Elasticsearch operator</a>. This operator helps spin up multiple application pods, services and stateful sets that are part of its search, visualisation and logs storage stack — reflecting the power of operators in the Kubernetes world.</p><p>Head to <a href="https://operatorhub.io/">Operator.io</a>, a community hub for sharing operators, across numerous categories such as AI/ML, database, cloud, networking, integration and Openshift.</p><p>Figure 2 and 3 shows an example that I built, describing how to run a machine learning workflow in Kubernetes. This diagram shows a Go-based workflow running on a command line or Kubernetes, with the help of a custom operator for a quick and automated data pipeline for your machine learning projects from the aspects of MLOps.</p><p>Machine learning and similar programs need a workflow engine to orchestrate various steps for processing data, training model and evaluating model in a pipeline. Occassionally, popular CI platforms (like Jenkins) are available to run pipelines but they are more suitable for application centric build and integration pipelines. Then, there are powerful workflow engines like Apache Airflow, Argo workflow etc. that provide the workflow management with many capabilities to get the end result. My motivation to carry out a new workflow engine — Roiergasias is simply to:</p><p>1. Have a very simple declarative workflow that keeps the machine learning engineer always in the driver seat by giving him/her the opportunity to be in complete control of the environment in which the steps are running.<br>2. Reuse the capabilities of Kubernetes operator to be the core driver for the workflow engine thereby making it K-native.</p><p>Besides this, there is a unique selling point for this operator over others i.e. it allows the workflow to split into smaller ones that can run in multiple worker nodes.</p><p>The example given here starts with a bunch of python scripts (one for each stage — process data, train model and evaluate model) along with unprocessed source data preloaded to S3 bucket.<br>With a simple custom resource manifest yaml, instructions to the workflow engine are shown below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cFRukuecZNxzLC9ao1TjUA.png" /><figcaption><strong>Figure 2</strong>: Example of a Custom Resource manifest</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VvKoz4xRLL069SCoQSEjnQ.gif" /><figcaption><strong>Figure 3</strong>: Example of an Operator <a href="https://github.com/ankursoni/kubernetes-operator-roiergasias">https://github.com/ankursoni/kubernetes-operator-roiergasias</a></figcaption></figure><p>Notice the sequence of actions begins:<br>1. Create config map 1 + job 1 for split workflow — “process data” on “node1”.<br>2. Wait for job 1 to complete.<br>3. Create config map 2 + job 2 for split workflow — “train model” on “node2”<br>4. Wait for job 2 to complete.<br>5. Create config map 3 + job 3 for split workflow — “evaluate model” on “node2”.<br>6. Wait for job 3 to complete.</p><p>You may refer to this <a href="https://github.com/ankursoni/kubernetes-operator-roiergasias#run-machine-learning-workflow-in-aws">article</a> for a more detailed explanation.</p><h3><strong>Applying the Operator Framework</strong></h3><p>Not all application stacks require an Operator. The flowchart below provides the decision process to understand whether an application would be candidate for automating using an Operator:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/692/0*EBdugo9yCMIqAWTW" /><figcaption><strong>Figure 4</strong>: Process for determining if you need an Operator</figcaption></figure><p>There are many options to go about building your first operator, namely:</p><ul><li><a href="https://operatorframework.io/">Operator Framework SDK</a></li><li><a href="https://book.kubebuilder.io/">Kubebuilder</a></li><li><a href="https://kudo.dev/">KUDO (Kubernetes Universal Declarative Operator)</a></li><li><a href="https://juju.is/">Charmed Operator Framework</a></li></ul><p>Kubebuilder provides a quick tutorial and easy scaffolding for code generation of various components involved in an operator codebase such as CRD and Controller-API.</p><h3><strong>Momenton’s Best Practices</strong></h3><p>Setting up your first Kubernetes Operator can be a daunting task. From our experience, some of the below considerations and best practices should help you get started. These practices are not exhaustive and things like declarative APIs, leveraging SDKs are all considerations for Operators.</p><p>Firstly, Operators should be specific to a single application. For example, Airflow is normally used with MySQL and Redis. You could develop an operator that automates the features of an application for all three: Airflow, MySQL and Redis. However, it is better to build three operators — one for each application. It gives you the flexibility to swap out MySQL or Redis for another database. Try to break down an operator into its smallest component that still provides value. This promotes separation of concerns, domain isolation and greater flexibility for the operator.</p><p>Secondly, the reconciliation code in the operator should be stateless and only depend on the current state of Kubernetes objects provided by calling the Kubernetes API. Idempotency, meaning “the ability to apply the same operation multiple times without changing the result beyond the first try”, is crucial in the reconciliation code. Hence, the Operator should achieve this by piggy-backing on the native resources’ controllers (like config maps, secrets etc) rather than doing custom resource creations for every need of the application. This will promote maximum reuse and least custom resource management, i.e. reconciliation overhead [2, 3, 4].</p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> or send us a message on <a href="https://www.linkedin.com/company/momenton/mycompany/?viewAsMember=true">LinkedIn</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><h4>References</h4><ul><li>[1]: <a href="https://medium.com/swlh/kubernetes-operator-for-beginners-what-why-how-21b23f0cb9b1">Kubernetes Operator for Beginners</a></li><li>[2]: <a href="https://kubernetes.io/docs/concepts/extend-kubernetes/operator/">Operator pattern Best Practices | Operator SDK</a></li><li>[3]: <a href="https://sdk.operatorframework.io/docs/best-practices/">Best Practices | Operator SDK</a></li><li>[4]: <a href="https://github.com/cncf/tag-app-delivery/blob/eece8f7307f2970f46f100f51932db106db46968/operator-wg/whitepaper/Operator-WhitePaper_v1-0.md">Operator WhitePaper v1.0</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4252b09f92bc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/kickstarting-your-first-kubernetes-operator-4252b09f92bc">Kickstarting your First Kubernetes Operator</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[4 Tips for Better Remote Meetings]]></title>
            <link>https://medium.com/momenton/4-tips-for-better-remote-meetings-1ca1af970d27?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/1ca1af970d27</guid>
            <category><![CDATA[remote]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Rory Dwyer]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 00:53:54 GMT</pubDate>
            <atom:updated>2021-02-15T00:53:54.768Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tWwS_KrTXtmMadzkKiz1Lg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cwmonty?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Chris Montgomery</a> on <a href="https://unsplash.com/@cwmonty?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I’m sure many meeting facilitators and scrum masters out there will agree — the last year has taught us that remote meetings can be a drag, and that it can be a real challenge to have consistent engagement in your calls. Have you ever been the only one with a camera on, staring at your reflection, talking seemingly into the abyss, questioning where it all went wrong?</p><p>Well, I have. So over the last few months, I’ve tried to reflect on this challenge and find ways to improve. There’s still lots to learn, but my team and I have seen improvements in this area. So I wanted to share some of our learnings and I hope that you find them helpful.</p><h3>1 — Be Human</h3><p>When working remotely, we miss out on so much human interaction that we normally get in the workplace. Aside from the research showing how important human interaction is for our health, we are also missing opportunities to connect and grow as a team. These opportunities to get to know each other could be in the form of simple office banter, asking about favourite hobbies over a coffee, or even confiding in a colleague and asking for support. It’s no surprise that these things are more difficult through an instant message, email or call, where there’s limited or no body language to work with.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F26BRuo6sLetdllPAQ%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F26BRuo6sLetdllPAQ%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F26BRuo6sLetdllPAQ%2Fgiphy-downsized-large.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="303" frameborder="0" scrolling="no"><a href="https://medium.com/media/92f678979f0babd05c503520b4b60d2c/href">https://medium.com/media/92f678979f0babd05c503520b4b60d2c/href</a></iframe><p>With this in mind, we need to be mindful we don’t become robots jumping from one meeting or task to the next. Allow for some time in your remote meetings to have more human interactions. How this plays out will differ based on your team’s dynamics and size, so don’t force something that doesn’t fit. Some examples could be:</p><ul><li>Take 5 minutes at the start or end of the call for general chit-chat. This is especially great for meetings on a Monday or Friday where people have exciting weekend plans to talk about.</li><li>If you run daily stand-ups, take turns telling a joke or riddle at the end of each call. Even the cringey dad-jokes will get a chuckle.</li><li>There’s always the pet person in the team. They will be happy to show off their furry loved ones to the team.</li></ul><p>Whatever the approach, try to involve everyone and have fun with it. Fun = engaging. And if some days nobody wants to chat, don’t take it personally.</p><p>Even with this tip in mind, engagement can still be difficult if you’re the only one making an effort. Which leads me to point 2…</p><h3>2 — Get Feedback — and Give Your Own</h3><p>If you’re making an effort to engage and it feels like the rest of the team isn’t, this can lead to frustration and resentment. If this is the case, or if your meetings just aren’t as good as you’d like them to be, it’s great to raise this during the <a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">Scrum Retrospective</a> (or equivalent session in the framework you use). Remember to raise the issue with an open-mind, without directing blame, and be prepared to receive feedback yourself.</p><p>As an example, saying “I feel that our scrum ceremonies aren’t collaborative enough” instead of “You all ignore me in backlog refinement!” will set you up for a more positive conversation. In this way, you’re asking the whole team to collaboratively inspect what is going wrong with the meetings. This may lead to brainstorming ideas that the whole team, including you, could implement. Perhaps you’ll find out that meetings often meander away from the agenda, which leads people to become disconnected. That may prompt you to think about timeboxing and other techniques. Keep a <a href="https://www.brainpickings.org/2014/01/29/carol-dweck-mindset/">growth mindset</a>. Easy.</p><h3>3 — Be Pointed (When Necessary)</h3><p>Often as a facilitator, you’ll find yourself asking an open question to the group. It’s great when someone immediately jumps in with a response to keep the conversation going, but that doesn’t always happen. There are two tactics to try and keep things going in this case.</p><p><strong>First option</strong>: Let the awkward silence roll…</p><p>Okay, long silences can be hard for some of us. But often as facilitators, we try too hard to force the conversation forward. It’s okay to let it breathe, as the audience digests the information and considers a response. As you feel the urge to jump in, hold off a little longer. You might even find that your hastiness is interrupting the flow. Maybe your team has more analytical personality types and they like to take their time before replying.</p><p><strong>Second option</strong>: If the awkward silence technique isn’t working, consider politely prompting someone by name. If the topic is specialised, maybe you’ll want to prompt someone who is the subject matter expert in that area. Otherwise, just randomly pull a name from the list and ask them. Seriously.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3ohhwiunVgYqfVYVEs%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3ohhwiunVgYqfVYVEs%2Fgiphy.gif&amp;image=https%3A%2F%2Fi.giphy.com%2Fmedia%2F3ohhwiunVgYqfVYVEs%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="217" frameborder="0" scrolling="no"><a href="https://medium.com/media/14591e89b4a15fcaca95e4c225704a14/href">https://medium.com/media/14591e89b4a15fcaca95e4c225704a14/href</a></iframe><p>Try not to constantly single out the same people each time, as this could lead to other problems in the team. Your goal is for everyone to be collaborating.</p><h3>4 — Share Facilitation</h3><p>This is one of my personal favourites. What better way to build up engagement than to have different team members facilitate meetings? There are a few great benefits to this; other team members get to cross-skill, the usual facilitator gets to see new ideas from a fresh perspective, and the whole team increases their empathy for some of the challenges faced by a facilitator. I’ve personally found that once someone starts facilitating they become a more engaged audience member later. Empathy is powerful.</p><p>I would usually recommend doing this with a less “daunting” meeting, such as a Retrospective which can be run in <a href="https://www.google.com/search?q=scrum+retro+ideas">so many different ways</a>. In one of my teams right now, we’re taking turns running the Retro and I’m being exposed to many great ideas and tools. It’s also just nice participating from the “audience side” for a change to see what works and what doesn’t.</p><p>There’s so many more techniques and strategies out there, so keep digging. And if you’re really struggling with your remote meetings and want some quick wins on the board, I’d recommend starting with tips 2 &amp; 4!</p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ca1af970d27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/4-tips-for-better-remote-meetings-1ca1af970d27">4 Tips for Better Remote Meetings</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[2020 Reflections]]></title>
            <link>https://medium.com/momenton/2020-reflections-52f02d00f583?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/52f02d00f583</guid>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Adarsh Muraleedharan]]></dc:creator>
            <pubDate>Mon, 15 Feb 2021 00:38:27 GMT</pubDate>
            <atom:updated>2021-02-15T00:38:27.542Z</atom:updated>
            <content:encoded><![CDATA[<h3>How we outperformed in a crisis</h3><figure><img alt="Mountain reflection on a lake" src="https://cdn-images-1.medium.com/max/1024/1*Do9CZwR135PblEL70QMLOQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@paulgilmore_?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Paul Gilmore</a> on <a href="https://unsplash.com/s/photos/reflections?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><h3>Introduction</h3><p>2020 was a hard year for the world. We were faced with challenges like never before; this blog will talk about my experience joining a new organisation and how we as a team overcame the challenges and even surpassed our performance in the pre-covid world.</p><p>In early March 2020, I joined Momenton. I was excited, a new role and a new chapter in my career. However, I had absolutely no idea of what was in store for me or the rest of the world in 2020. When Covid-19 was announced as a global pandemic, there were rumours of a pending lockdown in Melbourne. So we decided to trial the whole team working from home for two days in preparation. Almost immediately after this trial, a state of emergency was declared. The client I was consulting with invoked its Business Continuity Plan, it’s premises were locked down, and we all had to work from home. So here I am, having just joined a new company and haven’t even been in the office for 2 weeks.</p><p>My role at this client is helping two different squads in delivery and ways of working; one was following scrum where the squad had a specific customer segment, a mission and a clear road map. The other squad was in the final stages of a large initiative and had been following the Kanban methodology and were yet to define a roadmap beyond that. I found it hard to do a lot of context switching as the two squads were entirely different from each other. However, both the squads were operating in a co-located model, used a physical board to visualise the work and had a certain rhythm which was disrupted by remote working.</p><p>During the initial stages of remote working, we had acknowledged that there would be a dip in productivity and we started monitoring the throughput, and cycle time more closely. Lack of face-to-face conversation also meant that the team initially found it hard to stay in sync and facilitate a certain discussion that involved brainstorming or drawing board. Overall it was almost as if we were starting as a new team. Unlike in an office environment, we did not have the opportunity to just stand up or walk up to a team mate and clarify something; hence things took a little longer than before. Both the teams were also working on features that were considered ‘covid-appropriate’ as they were expected to enable self-service for customers and reduce calls to the call centre or visits to the branch. This applied additional pressure to deliver these features.</p><p>We moved all our ceremonies, including stand-ups, planning sessions, refinement, retrospective into a major online meeting platform and used Jira to visualise the work and stay in sync. We would then refer to the digital boards via screen share to facilitate the ceremonies and stay focused on the goals. Digital solutions that can be used to scribble and share ideas were identified and socialised.</p><p>We also organised a brown bag for the teams on Remote Working as by then we knew it was to stay for a while. The session covered 3 aspects of remote working, mental, physical and technical wellbeing and the challenges and opportunity this entails. It was important to discuss this as the sudden lifestyle changes, and being isolated could harm your professional and personal life.</p><p>Under mental wellbeing, we discussed how we could protect ourselves from loneliness, stress and anxiety, the importance of allowing time for things you really enjoy doing, making personal connections and staying informed. Physical wellbeing was more about ergonomics, monitoring screen time, getting out and staying physically active. Lastly, we spoke about technical well being and maintaining productivity, the importance of setting up work life boundaries, staying relevant and securing sensitive information from potential threats. We also discussed the opportunities that this brings and how the team can benefit from this.</p><p>We started an informal session every week to come together and use the time for team bonding. We would either play online games, have a trivia or just chat about a topic that the team really enjoys. There are plenty of resources online. Something that we really enjoyed was the Aliens game. In this game, we assume that Aliens have landed, and we have to explain to them what we do in our teams using pictures. This game was very interactive, and it was really fascinating to see how creative some of our team members were, and also the fact that a lot of them had similar ideas or concepts.</p><figure><img alt="series of pictures explaining banking system in layman terms" src="https://cdn-images-1.medium.com/max/480/1*v7hYGVspIbEV5_PX90xTkw.jpeg" /></figure><figure><img alt="series of pictures explaining banking systems in layman terms" src="https://cdn-images-1.medium.com/max/480/1*JuYk8Moc6HLQP_7QW_WE1w.jpeg" /><figcaption>Our superstar engineers explaining what we do with pictures</figcaption></figure><p>During our sprint planning, we also set up a stretch goal for the team to do physical activity everyday. There was no individual goals but only team goals just like our sprints. As long as we achieve that as a team, the goal is met. The idea was to encourage each other and work as a team. This also involved a lot of banter which was important to build a social aspect to the team. The challenge was to avoid inertia and be able to do things differently. Once we did a retro where everyone had to reflect on the last sprint using GIFs, and we thoroughly enjoyed it. These initiatives also helped me personally get to know the teams, and it’s dynamics and fit in quickly and be a crucial part of the team.</p><figure><img alt="simpson holding a magnifying glass" src="https://cdn-images-1.medium.com/max/480/1*JcqCFuZXn0810M7IvW-1_Q.gif" /><figcaption>D’uh</figcaption></figure><p>During the early days of remote working, we also observed a lot of questions and clarifications while the story is In Progress or In Test, which started to impact our cycle time. We also observed that we were not having story kick- offs, resulting in gaps in understanding a story. So we re-emphasised the importance of story kick-off, ensured that it was happening for every user story and was attended by a Developer, Analyst and/or QA. We encouraged the teams to do some background work before meetings/workshops to facilitate decision-making and outcomes. The team was encouraged to demonstrate more autonomy and make quick decisions as opposed to beating a dead horse. In the middle of the sprint, if someone has finished all their stories, we would consider how they can help others in the squad finish their stories rather than adding more stories.</p><figure><img alt="Cycle time report showing average, standard deviation and median" src="https://cdn-images-1.medium.com/max/795/1*yMoCj1usoU1qQba2EaYZnQ.png" /><figcaption>Cycle time report</figcaption></figure><p>When the team reported challenges with the distribution of code reviews, we started using Github metrics that provide the team with more insights into their delivery process. This provides more insights on the feedback process, number of commits, size of the pull requests and time taken to approve and merge.</p><figure><img alt="Graphs explaining code review turnaround time and size of the pull request" src="https://cdn-images-1.medium.com/max/632/1*RR0ToSn5P2FtIPAE7mqnmA.png" /><figcaption>Github Insights</figcaption></figure><p>We also revised our working agreement to make it appropriate for remote working. All this culminated in our team understanding each others strength and started leveraging the same to the team’s benefit. We also organised feature workshops with the delivery partners from other areas of the organisation to make sure everyone is onboard, committed to the feature, understand the expectations from each of them and agree how we work to deliver the features to our customers. This was really critical as cross tribe delivery and alignment had been a bottleneck in the past. We also created powerful metrics and dashboards to measure the progress of the work. As a result, we were able to run Scrum of Scrums more effectively and had complete transparency of the work happening across the different squads helping us identify and address any issues right away.</p><figure><img alt="an example of a working agreement that explains what is encouraged and what is not" src="https://cdn-images-1.medium.com/max/1008/1*squ89DgFvPXH0wJ0pDCyuA.png" /><figcaption>Working agreement</figcaption></figure><p>The team’s throughput started to rise again as we addressed the initial hiccups, embraced the new working model and finally found the rhythm again. We delivered some really great features while working remotely and one of them was delivered in less than 6 weeks from discovery to customer launch. Most importantly we had fun doing this, so much so that as soon as we deliver one feature, we can’t wait to start the next feature at full throttle. And today our throughput is more than what it was before we started working remotely.</p><p>What stands out the most is the people I had the chance to work with. We have some really capable individuals who demonstrate high morale and work ethics. Now that we are working out plans to open offices and what the future working model will look like, I can’t wait to sit down and have a coffee with the people that I have been working remotely with for the past 10 months and meet some of them for the first time.</p><h3>Summary</h3><p>This whole experience has challenged us but has also made us stronger and ready for the future working model. We have also learned to appreciate the positives of both remote working as well as working from the office. As we move forward there will be other challenges but we will face into them as team and come out stronger on the other side.</p><p>Reach out to hello@momenton.com.au to understand how Momenton can help your organisation with new remote ways of working and how we can help you deliver your product faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52f02d00f583" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/2020-reflections-52f02d00f583">2020 Reflections</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Yes, Scrum is Easy to Understand but Difficult to Master]]></title>
            <link>https://medium.com/momenton/yes-scrum-is-easy-to-understand-but-difficult-to-master-5d247c375d6f?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/5d247c375d6f</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[process-improvement]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <dc:creator><![CDATA[Sam Perera]]></dc:creator>
            <pubDate>Thu, 17 Dec 2020 06:34:20 GMT</pubDate>
            <atom:updated>2020-12-17T06:34:20.487Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C3o_-3L2QAoyTMPHLTJBjw.png" /><figcaption>Image Credit — scrum.org</figcaption></figure><h3>Prologue</h3><p><em>From the most recent feedback I was given by the teams I currently work with, I noticed a common theme emerging. Although they did highlight a variety of positive points, the one thing that stood out was how good they felt — how good they felt about being part of that team, the sense of appreciation they felt for the features they have been able to deliver, and how much they enjoyed interacting with me and other team members in doing what they do every day.</em> <em>I have been working as a scrum master for close to four years now. Back in 2017, I started to wear the scrum master ‘hat’ while continuing with the business analyst role I held at the time. That gave me the first glimpse of being a servant leader whose responsibility was to protect the team from any distractions so that they could focus on the outcomes they had committed to. With the experience I gathered during the first two years, I was successful in securing a full-time position as a scrum master. I still remember how tense my interactions with the team members were when I first started working with them. It seemed almost impossible to get my message across to them about the different aspects of the scrum framework and the value of having various ceremonies. During meetings, they wouldn’t make eye contact with me, they wouldn’t respond to my questions, and, whenever they did, it would be a very short ‘yes’ or ‘no’ — at times, I even suspected I was invisible. To make matters worse, whenever I sought feedback on my contribution to the team, it fell on deaf ears almost every time. And when someone got me into a room to provide some kind of feedback, it was about something I had done to offend someone or something I did to push the envelope too hard, too fast.</em> <em>In short, the contrast between the feedback I received then and the feedback I receive now could not be any starker.</em> <em>The interesting self-observation, however, is that my intention to help my team, do the right thing by each team member, and ensure we have a healthy environment in which to deliver successful outcomes has not changed since those early days. So, what is different now? What has changed in me that enabled me to make such a positive impact on my teams? What has changed the way my team members perceive me during my interactions with them?</em></p><p><em>These are the questions I have been mulling, searching for answers, during the last few weeks. All of a sudden, early this week, I had an epiphany while I was strolling through </em>The Scrum Guide<em>¹ and stumbled across a statement on page 3 . . .</em></p><h3>The Golden Statement</h3><blockquote><em>‘Scrum is lightweight, simple to understand, difficult to master’</em></blockquote><p>This is the statement that so eloquently captures the reasons why so many scrum masters find it challenging to strike a spark and create the required connection with their teams when they first start working, in spite all the noble objectives they set upon themselves and their teams.</p><p>Let’s dissect the three parts of the above statement and take a deeper look at each of them.</p><h4>1. Lightweight</h4><p>The entire <em>Scrum Guide¹</em> (including the cover and table of contents) contains just 19 A4 pages. That literally makes it lightweight. The theory of scrum is derived from empirical process control theory that consists of transparency, inspection, and adoption. Empiricism states that knowledge comes from what has been tested and validated and using that knowledge to make more informed decisions in the future.</p><p>Scrum employs an incremental process through which work is completed iteratively, with continuous planning, building, and reviewing, prompting adjustments with each iteration. This process aims to improve and optimise predictability while controlling and reducing risks associated with the delivery of outcomes.</p><h4>2. Easy to Understand</h4><p>If you read through <em>The Scrum Guide¹</em>, you will notice that the crux of the whole framework is formulated using three ‘roles’, four ‘ceremonies’, and three ‘artefacts’ that stand around the scrum team. The rules that bind them together explain the interactions between these three entities to create an empirical process.</p><p>This makes the scrum framework one of the easiest frameworks to read, remember, and understand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sBiihtYAPsyHSCchOVBaEw.png" /><figcaption>Scrum in a Diagram</figcaption></figure><p>As scrum is a framework that is simply described and easily grasped, in my opinion, these positive attributes lead most of us to believe that we have ‘mastered’ scrum once we understand the text literally and manage to successfully answer the questions in the certification exam.</p><p>This misplaced belief leads most of us to conclude that ‘<em>I am a great scrum master’</em>, and we jump out in excitement, waving the scrum values as flashy words, enforcing the scrum rules to a tee, hanging onto to various half-baked workflow measurements, and continuously judging our fellow team members on their scrum knowledge.</p><p>Becoming a great scrum master takes a whole lot more than simply understanding what is written in <em>The Scrum Guide¹</em>. It takes a tremendous amount of experimentation with and learning from, different approaches, failures, and self-reflection over a long period of time. It requires you to interact with many different individuals, challenges, organisational structures, and perhaps even product domains. It requires you to develop empathy towards your team members and the circumstances in which they operate. It requires a deeper understanding of the values defined in <em>The Scrum Guide¹</em> to encourage your teams to join you on the journey to deliver, reflect, and continuously improve. This is not because you advocate for them but because they are genuinely inspired and motivated by what you share and can see the benefits for themselves.</p><p>This is what makes scrum difficult to master.</p><h4>3. Difficult to Master</h4><p>Let’s take a look at the dictionary definition<em>²</em> of the word ‘<em>master’</em>:</p><p><em>adjective:</em> having or showing very great skill or proficiency;</p><p><em>verb:</em> acquire complete knowledge or skill in (a subject, technique, or art).</p><p>Considering the above definitions, we can arrive at a more descriptive definition of a scrum master:</p><blockquote><em>An individual who has acquired in-depth knowledge of the scrum framework and has a deep understanding of its values.</em></blockquote><p>In general, our personal values define the choices (both words and actions) we make when we are presented with a challenge or problem to solve. It is practically impossible to learn and prepare in advance for every challenge or situation that life might throw at us. The same goes for what is explained in <em>The Scrum Guide¹</em> — it does not explain how a scrum master is supposed to approach teams with all the possible characteristics, operate in all the possible circumstances and develop all the possible kinds of products. Instead, it provides a set of values.</p><p>The scrum values provide the moral compass from which a scrum master can draw guidance and respond to situations in a manner that demonstrates the value of doing something in a particular way. This is what differentiates a person who will be able to clearly explain the fundamentals of the framework and inspire people to see the value of adapting the framework to their ways of working from a person who merely knows scrum.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/850/1*9AnVDPdLaqi_Q7XrfUyEZw.png" /></figure><p>Just as important as the scrum master promoting these values and expecting the team to practise them, it is also important that the scrum master is led by these values to bring the team together to do what they do best while feeling their best.</p><p>This allows the scrum master to be part of the journey within the team and helps that person obtain the buy-in, rather than simply being an adviser who is there to tell the team what they should and should not do.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*-6zTx3Gnr0U8deXESmxhQQ.png" /></figure><p><strong>Open Mind:</strong> Every team is different. Embrace each of them with an open mind. You might not necessarily be able to successfully solve a problem in the same way as you have in the past. Since you will end up with a brand-new team every time a new team member joins, or an existing team member leaves, reminding yourself to be open to suggestion and innovative ways to tackle challenges is a great way to master your scrum.</p><p><strong>Open Intentions:</strong> Always share the ‘why’ with your team. The most critical factor in the success of any change or improvement you may suggest is the buy-in from your team. And what better way to get that than by explaining the reasons for doing it? Being upfront about the reasons and the envisaged benefits will trigger conversations among the team and will allow you (as scrum master) and the team members to further fine-tune the proposed approach so that everyone feels they are part of it when it is implemented.</p><p><strong>Open Metrics:</strong> Measurements are a key part of any high-performing team. This is how the team can constantly evaluate if they are on the right path and if the changes they have put in place are delivering the intended outcomes or not. The best way to keep your team motivated and energised on an initiative they agreed upon is to define measurements collaboratively and make them clearly visible and easily understood. Review these measurements regularly with the team and continue the dialogue on how they could be tweaked to better assess the results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/410/1*C3P-AZzk37fNdTURVxt92A.png" /></figure><p><strong>Focus on Team Members:</strong> A team is made up of individuals, and every individual is different. The character of the team is an amalgamation of the characteristics of these individual team members. As much as focusing on the sprint goal and the backlog, the scrum master must focus on the individuals and the circumstances each of them is in. Understanding their cultural backgrounds, their personal and professional journey thus far, and their individual aspirations and goals for the future will allow you to be a lot more effective in guiding the whole team towards maintaining a healthy and productive dynamic.</p><p><strong>Focus on Product Owner:</strong> I have always felt that a happy product owner leads to a happy team. The fact that the product owner and the teamwork extremely closely in a scrum team calls for healthy and open interaction between the two parties in order to cultivate a supportive environment. By understanding the circumstances, challenges, and situations the product owner faces from his/her stakeholders, sponsors, and other influential people across the organisation, while supporting him/her on those issues will most probably create a ‘paying it forward’ culture within the team. This will reduce the friction between the product owner and the development team, which is felt from time to time.</p><p><strong>Focus on the Challenges:</strong> One of the most valuable contributions a great scrum master can make is to have a clear focus on the challenges and blockers thrown at the team every now and then. By focusing on them and working with relevant stakeholders to have them removed will naturally enable the team to focus on the sprint backlog and the sprint goal.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/415/1*NkbGqGrr-pnrjc2YYbqYNQ.png" /></figure><p><strong>Respect Current Achievements:</strong> As scrum masters, we often tend to engage our ‘advice-giving monster’ and straightaway jump into stating what the team must do. However, this often leads to a lack of cooperation from team members and even resistance at times. Respect the team for what they have achieved thus far and what they’re doing right now. Explore more and more in order to understand the reasons for what they are doing, rather than switching into adversarial mode simply because you have concluded that they have no idea what they’re doing.</p><p><strong>Respect Individuals:</strong> Each person in the team brings a unique personality and set of skills into the team. When you effectively tap into those, it can be invaluable to the way the team comes together to have fun, while delivering awesome outcomes for the organisation. When you see an individual behaving in a manner that’s not conducive to a healthy team, reach out and have a respectful conversation to explore and work with him/her on an action plan aimed at overcoming the situation.</p><p><strong>Respect the Status Quo:</strong> Sometimes situations are much more complicated than they seem on the surface. This is very important if you are working with a team that’s part of a large organisation. The processes they are part of, the systems they use, and the reporting lines across the organisation could be complicated, marred with historical incidents, internal politics, individuals with hidden agendas, and egos. Be aware of the history of the organisation and its traditional methodologies before you go jumping in and slapping <em>The Scrum Guide¹</em> in their faces. Instead, reach out to the teams outside of your own, and build close relationships in order to understand their side of the story and to work together on a set of actions that will bring small but effective improvements that would benefit all.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/406/1*Tu4nmpDePOJjcDBaGnRugQ.png" /></figure><p><strong>Courage to Have Tough Conversations:</strong> Life as a scrum master at work could be full of challenges. Dealing with difficult individuals, tools, and applications that are not fit for purpose, test environments that are not reliable and complete, lack of response from depending teams, and absence of clarity on priorities are just a few. A great scrum master needs to have the courage to take on these challenges and find the best way forward to overcome them by having tough conversations with individuals and teams. Trying to hide away from these challenges or pretending that they don’t exist will only exacerbate the situation. Approach these conversations with respect, and have an open mind about the outcomes you might end up agreeing upon.</p><p><strong>Courage to Protect the Team:</strong> One of the best ways a scrum master can be effective and earn the trust of the team is by genuinely protecting them from unwarranted distractions. This will allow the team members to feel that they don’t have to constantly bat away requests that land on their desk, that they don’t have to wrangle between conflicting priorities, and that they don’t constantly have to switch context. The team will feel that their scrum master genuinely values the importance of meeting the sprint goal and respecting team members to get on with what they have committed to.</p><p><strong>Courage to be Accountable:</strong> As scrum masters, we preach to our team members about taking accountability for their actions. The best way to get them on board with that is for you to lead by example. Don’t limit your engagement to being a coach or mentor who will leave the ultimate delivery and the productivity goals entirely up to the team. That will only widen the distance between your team and you. Develop empathy towards your team and truly believe that you are one of them. Take ownership of the outcomes and have a genuine stake in them.</p><p><strong>Courage to get to the Next Level:</strong> This is where I feel that a scrum master plays the role of a parent. Parents are always eager to get their children to fare better in their lives. They want their children to achieve greater goals as they grow. A great scrum master will always explore the personal growth of individual team members and utilise that growth towards the greater good of the team and the outcomes it delivers.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/414/1*6-uPunSgP8ajKy65tGj1Tg.png" /></figure><p><strong>Commitment to the Team:</strong> As much as scrum masters aim to make the team part of their journey, they need to be part of the team’s journey. This commitment will allow team members to build trust and feel comfortable. More importantly, it will allow team members to be open and authentic when it comes to discussing their emotions and the challenges they face. It will make the process of identifying effective steps to overcome them easy and practical.</p><p><strong>Commitment to Continuous Improvements:</strong> A scrum master must commit to the improvements that the team agrees upon. You should support the team in every way possible by being their voice across the organisation in order to resolve the challenges they face. This is particularly important in relation to improvements that require wider tribe or organisational assistance in order to be successful. The action items that come out of a ‘retro’ need to be properly planned and followed through with the same level of attention as any other item on the product backlog. This is extremely important in keeping your team motivated to continuously improve what they do and how they feel about it.</p><p>When our development teams have to wrestle with development tools, test frameworks, requirement gathering techniques, and deployment tools and environments, we, the scrum masters, need to look after the people who are part of those development teams. We have to deal with people with different attitudes, cultural backgrounds, upbringings, and who have different values and principals in their own lives. We need to constantly adapt to individuals with different personalities and traits, cooperate with them to make them feel their best, and empower them to do their best. We have to deal with aspects that cannot be programmed, refactored, debugged, or redeployed.</p><p>The only way we can give ourselves the best chance to succeed, and thereby help our teams to succeed, is to continue with the journey of deepening our understanding of the values defined in <em>The Scrum Guide¹</em>.</p><h3>Epilogue</h3><p><em>As for me, my feedback wasn’t without areas that require improvement. I’m nowhere near perfect. As with most aspects of our lives, being a great scrum master is not a destination, rather it is a journey.</em> <em>I will continue to reflect on every piece of feedback I have received, together with my own reflections on how I operate today and continue to make small but effective changes to become an even better scrum master tomorrow.</em></p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><h4>References</h4><p><strong><em>¹ </em></strong>— <a href="https://www.scrumguides.org/scrum-guide-2017.html"><em>The Scrum Guide</em></a><em>, </em>November 2017 edition was referred to at the time of writing this article. An updated version of <a href="https://www.scrumguides.org/scrum-guide.html"><em>The Scrum Guide</em></a> has since been published in November 2020.</p><p><strong><em>²</em></strong> — Definition of the word ‘<em>master</em>’ was referred to on <em>Google</em> where the actual definition is provided by <a href="https://languages.oup.com/google-dictionary-en/"><em>Oxford Languages</em></a><em>.</em></p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/yes-scrum-easy-understand-difficult-master-sam-perera-he-him-/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5d247c375d6f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/yes-scrum-is-easy-to-understand-but-difficult-to-master-5d247c375d6f">Yes, Scrum is Easy to Understand but Difficult to Master</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Jira vs. GitHub Issue Tracking]]></title>
            <link>https://medium.com/momenton/jira-vs-github-issue-tracking-4cdf3bdd1437?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/4cdf3bdd1437</guid>
            <dc:creator><![CDATA[Rory Dwyer]]></dc:creator>
            <pubDate>Tue, 06 Oct 2020 01:22:42 GMT</pubDate>
            <atom:updated>2020-10-06T01:22:42.650Z</atom:updated>
            <content:encoded><![CDATA[<h3>Jira vs GitHub Issue Tracking</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4CeBMq8rS0U1Ud4twlcq2A.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@headwayio?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Headway</a> on <a href="https://unsplash.com/s/photos/github?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I recently joined an established software development team in a large enterprise who exclusively used GitHub for issue tracking. From a developers perspective, it made sense. GitHub becomes your one-stop shop for tracking, version control and source code management. <br>If it ain’t broke, why fix it?</p><p>The Product Owner and I talked about backlog visibility and found this was one of the major challenges with the current setup. As the team maintains a number of services spread across multiple GitHub repositories, there was no single board to view and refine a combined backlog. Another challenge was that there were no estimations or story points, with more of a gut-feel approach on what could be completed in any given sprint.</p><p>After a few <a href="https://www.scrum.org/resources/what-is-a-sprint-retrospective">retros</a>, we noticed some common themes occurring. So we decided to do an agile baseline health-check to further validate where we could improve. We individually scored our team on various agile fundamentals then had a big retro to review the results. Some of the common themes we struggled with were, in part, directly related to those limitations in our issue tracking mentioned earlier. Clarity on the product vision and backlog management was an issue, which a single backlog view could improve. Sustainable pace was an issue, which estimations and understanding our velocity could help with. The quality of user stories was also an opportunity for us to grow, which would require discipline — but perhaps the right tool could accelerate the process!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*wNIJ3yEngod3DLlV.jpg" /><figcaption>We projected our agile health to improve by at least 40 stonks with the right issue tracking tool</figcaption></figure><p>For the record, our target areas could be tackled in lots of ways! But for this article, we’ll focus on <strong>issue tracking and the backlog</strong>.</p><h3>Backlog</h3><p>Out of the box, Github’s <a href="https://docs.github.com/en/github/managing-your-work-on-github/about-project-boards">project board</a> is essentially a kanban that can be setup quickly and easily. It has some automation available around tickets being moved between status columns which is handy, but it’s not really a backlog view. For a more traditional backlog, you could potentially view each repository’s issue list separately, but that wasn’t feasible for us with 15–20 repositories — imagine backlog refinement! 😱<br>The only way to combine all of them (in out of the box GitHub) is to use a project board.</p><p>Aside from not really being a traditional backlog offering, a limitation of the project board is that it is not suited to larger projects and teams with a higher number of issues. In those environments, you may not want to use automation to add all new issues to the board, or it will get cluttered quickly and lose clarity. Therefore, you’ll be adding cards manually using the Add Cards pane. This offers no drop-down menus or auto-fills for simplified searching, so if you’re running a lot of repositories and issues this becomes a bit daunting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtWEPULpkjW_eR1zHYdcuA.png" /><figcaption>Easy to setup, but has it’s limits</figcaption></figure><p>Another limitation of GitHub’s project boards is that a maximum of twenty-five repositories can be linked to one board. For most teams this isn’t a problem. However, it’s worth considering how your team and product might grow over time when making a choice.</p><p>Whilst I’m sure there are many ways to customise your GitHub, our team wanted a light-touch setup. Those who have worked in large enterprises will know the challenges in customising your operational tooling, with approvals and dependencies likely to slow down any significant change.</p><p>At least it’s super easy to get rolling with.</p><p>Alternatively, Jira <em>could </em>take slightly longer for that initial setup but may offer more value overall.</p><p>We decided to go with Jira for a few reasons, one of them being the backlog view. We added <a href="https://support.atlassian.com/jira-software-cloud/docs/configure-quick-filters/">quick filters</a> to allow the PO to switch between the combined backlog view of all issues or to view issues only for a particular service. While at the same time, developers could bookmark the Jira board with the quick filter(s) for their current workstream already selected — saving them from the noise of unrelated issues.</p><p>The backlog view in Jira allows us to drag and drop issues between sprints and backlog easily. We can drag priority tickets to the top of the backlog to visualise and plan how the next sprints will look, ensuring our refinement ceremonies are more meaningful.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*286NCRkVFROVoEvp" /><figcaption>Clean and crisp backlog</figcaption></figure><h3>Issue Fields</h3><p>Our team had identified two key problems relating to the contents of issues — a lack of estimations and user story quality being a little “lacking”. In GitHub, there’s no built-in field to capture effort. How could we plan for a sprint if we couldn’t quantify the required work in some way? Well, Jira not only had a built-in field to capture story points but also shows this against each issue in the backlog. It also displays totals above the active sprint of story points to do, in progress and done. Use of story points can be enhanced with some add-ons for burndown and velocity charts, which in our case were already available in our Jira environment. Within 3–4 sprints, we started getting some consistency and understanding the velocity we could achieve in each sprint on average. This has brought more confidence to our sprint planning and helps improve toward a sustainable pace for the team.</p><p>On the second problem of user story quality; as touched on earlier this would require discipline from the team, but could also be helped with by the right tool. By simply enabling the Acceptance Criteria field in our Stories in Jira and making it mandatory, we were reminding ourselves to meet some minimum requirements on all of our Stories. This was a basic example of prompting the user, but plenty of Jira’s built-in fields could be used to guide users in the right direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/813/0*3oq6RzLYb2HH1mpf" /><figcaption>Great job, me!</figcaption></figure><p>Another benefit with issue content was using Epics to group Story issue types. Where previously in GitHub, we were trying to loosely group related tasks using combinations of labels or milestones, the Epic issue type allowed us to create a high level parent issue with some information around the overall goal of that feature or enhancement. This is far superior to a GitHub label, for example, as it allows information such as acceptance criteria or a business-level user story, to be held at the top level Epic — as well as allowing the Epic itself to transition through a workflow.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/0*ziREJ5n6HrX1tN8D" /><figcaption>Epics are awesome. And epic!</figcaption></figure><h3>Migrating from GitHub to Jira</h3><p>Having decided as a team to give Jira a try, we started migrating GitHub tickets to Jira in increments. Fortunately, we were able to use GitHub’s API for this instead of writing out hundreds of issues manually. We used the list-repository-issues call (<a href="https://developer.github.com/v3/issues/#list-repository-issues">API docs</a> / <a href="https://developer.github.com/enterprise/2.21/v3/issues/#list-repository-issues">enterprise API docs</a>) to extract all open issues in a particular repository, then used an open source tool to convert JSON to CSV, then tidied up the CSV into a format we could <a href="https://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html">import into Jira</a>.</p><p>A limitation is that the issue comments don’t come back in that API response; instead you’ll need to make a second API call for each issue to another endpoint for comments. As our comments were low volume and not worth the extra effort, we simplified the approach and instead made the CSV template a <em>tiny </em>bit fancy by concatenating the original GitHub issue link into the new Jira description to be imported. That way if anyone wanted to check the original link for comments it was right there in each Jira ticket.</p><h3>Summary</h3><p>When would GitHub work best for issue tracking? In my opinion, it could work in smaller development or support teams who only need a simple kanban setup and have a lower volume of issues. Perhaps it could also work for high-performing, well-established development teams with other methods and tools for estimations, reporting, backlog refinement and visualisation!</p><p>When would Jira work best for issue tracking? From my experience, when directly comparing to GitHub, Jira gets the chocolates in most categories. Especially in large enterprises where transparency and reporting are fundamental. Yes, it can take longer for initial setup depending on your requirements, such as for more complex workflows. However, if you need a lightweight setup there are built-in workflows.</p><p>One downside is that you need some customisation to link Jira issues directly to GitHub pull requests, which developers may bemoan when comparing to GitHub.</p><p>Hopefully this information helps as you consider the needs of your team. Good luck!</p><p><em>I have no affiliation with Jira or GitHub. I’m just a nerd for organisation.</em></p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation and how we can help mature delivery of your products.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4cdf3bdd1437" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/jira-vs-github-issue-tracking-4cdf3bdd1437">Jira vs. GitHub Issue Tracking</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote delivery — the importance of keeping the culture alive]]></title>
            <link>https://medium.com/momenton/remote-delivery-the-importance-of-keeping-the-culture-alive-26ceeb2acd2b?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/26ceeb2acd2b</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[David Rizkalla]]></dc:creator>
            <pubDate>Tue, 11 Aug 2020 04:45:13 GMT</pubDate>
            <atom:updated>2020-08-11T07:59:50.002Z</atom:updated>
            <content:encoded><![CDATA[<h3>Remote delivery — the importance of keeping the culture alive</h3><h3>Introduction</h3><p>Our year at Momenton started full of promise. In February, we partnered with a government agency to modernise its architecture. The ask was to build and quickly deliver a complex process orchestrator that would scale and be fast. Here we had an excellent opportunity to showcase our technical skills — Kubernetes, event-driven architectures and API gateways — and our ability to deliver high-quality software within a short time frame. Just one month later, the spectre of Covid-19 loomed. We knew this was going to force businesses into a remote working model. To get ahead of this and to be prepared, we trialled remote working before restrictions were enforced. As a team, we were set up for success, armed with an elite skill set, ready to overcome the challenges of a global pandemic, forcing us to work remotely. What we discovered was that even the best processes and tools could falter without strong human connections.</p><h3>Remote working begins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/1*LTClELt1ouTHHxeNFJ9BBQ.png" /><figcaption>March- The Pandemic starts to hit Australia and all businesses begin preparing for remote working</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*5y8fM1lVdWRhHoRjwOxUIQ.jpeg" /></figure><p>First, we worked on a 2-day rotation. Half the team worked from home and on Fridays we all came together in the office.</p><p>The following week, everyone worked remotely from Monday to Wednesday and came into the office on Thursday and Friday. We were able to perform our ceremonies via Slack video calls. We stayed in contact throughout the day using Slack chat and email. We were able to visualise our work using tools such as Jira and GitLab.</p><p>Finally, remote working became the norm; for our safety, we all worked from home 5-days a week. Thankfully we were prepared, or so we thought…our workflow, tools and processes were solid and built for a remote working environment. Our code repositories were web-based and remote access was not restricted. However, our team morale started to decline. The way we were communicating with one another became laced with an air of frustration and hostility. Individuals started to take feedback on code reviews personally and team collaboration was breaking down. This was evident in Story Refinement sessions and Retrospectives. As a result, our performance and sprint goals were negatively affected. These were issues which our team did not have before the pandemic. Nothing had changed with our processes and tools; we still performed all of our ceremonies and could access our work all the same.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kuz2XDS9FNtrtek32VwIig.png" /></figure><p>So what was causing this drop in team performance and morale? Well on top of the pressure of delivering an end product amidst a toilet paper buying frenzy, hands dryer than the Sahara caused by the excessive use of hand sanitiser and the daunting prospects of home schooling; working remotely was affecting our team culture. We were losing our identity, the bond we had developed over time through human interaction. We only ever communicated during work-related ceremonies, Slack chat and email. Even code reviews and questions on stories were done via the comments section of GitLab and Jira. Comments were being misinterpreted as demanding or condescending when written compared to verbal conversations. We were missing ‘face to face’ interactions.</p><h3>The new ‘face to face’</h3><p>Before lock-down and remote working, casual social interactions with colleagues occurred regularly such as, going for a coffee together or Friday night drinks. The importance and value of this time was taken for granted. These casual moments brought us closer together as colleagues and friends. Accepting and taking on feedback from colleagues is always easier when there is a mutual sense of respect.</p><p>In order to deal with this breakdown, we implemented a few principles to improve communication across the team. We came to an agreement that code review and Jira comment queries were to be followed up by a verbal conversation. If feedback was added to a code review, this would be followed up by a video call to the developer. Here feedback could be elaborated on. The same applied for Jira comments, rather than just tagging a person in a comment. These conversations helped in bringing a sense of understanding and respect back into the team.</p><p>To reinvigorate this lost work culture, we all decided to dial into stand-ups with coffees in hand, making them less formal and more in line with the friendly vibe that we had lost. We also started having Zoom catch-ups on Wednesdays and Fridays. We ended our workday at 4:30 pm, grabbed a drink, changed our virtual background to something fun and had a laugh. That’s all it was about; we didn’t discuss work or the sprint. In fact, we introduced a rule, you bring up work, you get kicked from the Zoom party!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yly2uz32k9PtvvXVca1nZQ.png" /></figure><p>These simple changes had almost immediate effects, our team was much happier. Individuals began to accept feedback from one another more willingly and produced better code. Overall, our team was back to its high-performing self, successfully and remotely, we delivered a fully functioning Complex Process Orchestrator within 16 weeks.</p><h3>Conclusion</h3><p>Whilst having a framework to set guide-rails for Agile teams is important (something we will talk about in a subsequent post) what is just, if not more important is maintaining team culture and morale especially when working with remote &amp; distributed teams.</p><p>We went into a remote working setting with the right setup and tools to get the job done, but that wasn’t enough. We needed to maintain our face-to-face conversations and values to keep our performance alive. Simple techniques you can use to give feedback is video chats such as Slack or Zoom as opposed to commenting on stories or code reviews. Along with some scheduled break out time to have a virtual drink together was a major key to our successful delivery of the project.</p><p>Look after your team’s happiness, and they’ll look after the required task at hand. Don’t underestimate the importance of human connection and the impact it can have in the workplace; especially during this time.</p><p>Reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how <a href="https://momenton.com.au/">Momenton</a> can help your organisation with new remote ways of working and how we can help you deliver your product faster.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26ceeb2acd2b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/remote-delivery-the-importance-of-keeping-the-culture-alive-26ceeb2acd2b">Remote delivery — the importance of keeping the culture alive</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cost management to get the best out of your cloud infrastructure (Part 2)]]></title>
            <link>https://medium.com/momenton/cost-management-to-get-the-best-out-of-your-cloud-infrastructure-51b501e470af?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/51b501e470af</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[cloud]]></category>
            <category><![CDATA[cost]]></category>
            <category><![CDATA[multi-cloud-management]]></category>
            <dc:creator><![CDATA[Melchi Salins]]></dc:creator>
            <pubDate>Mon, 27 Jul 2020 00:22:16 GMT</pubDate>
            <atom:updated>2020-09-22T02:30:14.422Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NHaw_1MQOdrOJ6H1" /><figcaption>Photo by <a href="https://unsplash.com/@jarispics?utm_source=medium&amp;utm_medium=referral">Jari Hytönen</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>This is the second in a multi-part series aimed at identifying how organisations can manage and optimise costs to get the best of their cloud infrastructure. At <a href="https://momenton.com.au/">Momenton</a> we place a strong focus on leveraging cloud whilst also seeking to optimise cost management. I will be looking on the compute aspect of cloud in this blog.</p><p>About five years ago, Public Cloud services were not well understood. Large enterprises debated if migration to the cloud would meet their security requirements, paralyzed with the fear of the unknown. We have since come a long way — Digital Transformation is now synonymous with migration to the cloud. The benefits of on-demand infrastructure and elasticity have made engineers more productive and businesses happier with the promise of improved time-to-market.</p><p><em>Note: A key assumption being made in this write up is that your organisation has a considerable portion of applications that are stateless and can be subjected to horizontal scaling to make the most of cloud infrastructure. We will address optimising cost other workloads in another blog in this series.</em></p><h4>Elasticity — The Double Edged Sword</h4><p>Public Cloud is a double-edged sword, especially when it comes to on-demand infrastructure and elasticity. Although spinning up resources and scaling out horizontally takes little effort, gracefully shutting down and draining connections to the same resources needs a more foresight and engineering rigour. If this is not done right, you could be racking up a hefty bill.</p><p>The pay as you go model of public cloud is not as straightforward either. Several services have a complex billing model where data retrieval is charged at a different rate than data storage of the same service, <a href="https://aws.amazon.com/xray/pricing/">AWS X-Ray</a> is a good example one such a service. When X-Ray is used with other services such as AWS API Gateway and Lambda in a single solution, forecasting the spend gets a more complex.</p><p>Momenton is a proponent of <strong>Kubernetes</strong> and has helped several organisations adopt this container orchestration system. I will try and highlight the reasons why you may want to do the same.</p><h4>Focusing on compute as a starting point</h4><p>At Momenton we have the privilege of working with several clients large and small who operate in domains varying from Finance, Utility to Gaming. We see the nuances of how their teams grow and adopt different technologies on their road to cloud adoption. However, irrespective of their domain there are always similarities in the way they utilise resources.</p><p>From our experience, we see that compute is generally the largest cloud cost. For example, the following figure shows the usage costs by service for four companies across different domains. We can see that compute is the biggest component of cost, with it contributing to 40% to 70% of the cost.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SBAmTvfGQMKNn7Yj1gAFzA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TZnhUHlbAShhodU9Ed1i8Q.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MVlml1LKQxJS8n0gPruDWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kBAvQBAaueZQRrzfvJrr7w.png" /><figcaption>Cloud Service usage cost for different business domains</figcaption></figure><h4>Understanding Cost to Usage Ratio</h4><p>Public Cloud Vendors do a good job of breaking down usage by line item and show the trends of the billing cost. What they do not do, is a good job of highlighting the actual usage of service. For example in the EC2 line item from the images — all we see is how much we pay, not how much of that service is being used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m8xdQo52mpKS12ZFpEZL4w.png" /><figcaption>Monthly service cost trends</figcaption></figure><p>You need to dig deeper to get a better understanding of utilization. Cloud Watch on AWS and Stack Driver on GCP do a pretty good job at this.</p><h4>Leveraging the right data for informed insights</h4><p>What you cannot measure you cannot optimize, and measuring the right metrics is even more important. To explore inefficiencies in compute utilization we can start with collecting CPU and RAM metrics. Cloudwatch allows easy plotting of CPU usage metrics.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jMlg7cYUtB0jyt0WgjuFaA.png" /><figcaption>Average CPU utilisation</figcaption></figure><p><strong>Averages are misleading</strong> — When you look at data points on a very large scale, averages water down spiked sustained CPU usage. The above graph shows the average CPU utilization is about 7%. When you look at the P95 &amp; P99 of the same data you see a slightly different picture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zu6NO_SGREziKkQ1ZUBGOA.png" /><figcaption>P95 of CPU utilisation</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZlySFU8y5WtEgrjgSo-V-Q.png" /><figcaption>P99 of CPU Utilisation</figcaption></figure><p><strong>Use percentiles instead</strong> — In the above two images you can see the CPU utilisation is around 16% and 22% respectively for the 95 and 99 percentile measurement, which is significantly higher than the average measurement. These two measurements paint a more accurate picture of the CPU load profile and the compute capacity you need to configure. It’s generally a good idea to have your elasticity desired state configure to P95, Average to Min &amp; P99 configured to Max.</p><p>The same metrics can be plotted for RAM as well — Most cloud service providers don’t let you do this out of the box due to limitations in the hypervisor but Momenton has you covered. To enable memory metric collect checkout this repo 💻 <a href="https://github.com/momenton/aws-memory-monitor">https://github.com/momenton/aws-memory-monitor</a></p><h4>Always on Elastic Infrastructure is the future</h4><p>It is a common practice to see organizations turn off their non-production infrastructure at nights or over the weekends. But with more organisations choosing to have geographically distributed teams working in different timezones, turning off infrastructure is not always feasible.</p><p>Also, it is important to ask yourself how many times you have walked into work on a Monday morning to discover that not all your infrastructure has booted as expected. Teams that move fast tend and update their infrastructure-as-code often and may encounter issues more frequently. Broken infrastructure reduces productivity drastically so this is another reason to leverage elasticity instead of turning off infrastructure. In our experience at Momenton, we’ve discovered more often than not the productivity loss from infrastructure issues outweigh the cost gain of turning off the infrastructure over the weekend.</p><p>An organisation that takes the approach of leaving their infrastructure always-on will enable their teams to work in multiple time-zones and flexible work hours. Kubernetes allows for clusters to scale from hundreds of nodes to just a couple without any manual intervention. Resource allocation can also be changed for all the containers in a matter of seconds with just a call to its API.</p><h4>Understanding the power of Kubernetes Bin Packing</h4><p>Once you have understood the compute requirement of your workload, you will need a platform that will allow for the optimisations of the use of your servers. This is where Kubernetes &amp; its Bin Packing feature comes in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/567/1*_T_vTcwW3BBEQqzEDMgSQA.png" /></figure><p>Bin Packing works just like the game Tetris. Consider each of the pieces in the game to be application workloads. Kubernetes takes these containers workloads and places them on the same server for maximum utilisation of the resources. The security, resource utilization and isolation of these containers is also managed by Kubernetes but this is a topic for another blog post.</p><p>Kubernetes allows you to think of compute resources (CPU &amp; RAM) as a pool instead of different servers. This paradigm of approach allows to look at the entire compute requirement across the organisation and hand off the divvying of these resources to Kubernetes.</p><h4>Summary</h4><p>In these uncertain times, most organisations are looking to optimise their spend where ever they can. Momenton has developed a number of tools to allow for easy visualization of metrics that can be turned into actionable insights. Optimising compute utilization is just the start, please reach out to <a href="/service/mailto:hello@momenton.com.au">hello@momenton.com.au</a> to understand how<a href="https://momenton.com.au/"> Momenton</a> can help your organization with this and more.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=51b501e470af" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/cost-management-to-get-the-best-out-of-your-cloud-infrastructure-51b501e470af">Cost management to get the best out of your cloud infrastructure (Part 2)</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[RETROspective — The Most Important Agile Ceremony]]></title>
            <link>https://medium.com/momenton/retrospective-the-most-important-agile-ceremony-c34fa848fe68?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/c34fa848fe68</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[retrospectives]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Sam Perera]]></dc:creator>
            <pubDate>Tue, 26 May 2020 06:43:17 GMT</pubDate>
            <atom:updated>2020-05-26T06:43:16.998Z</atom:updated>
            <content:encoded><![CDATA[<h3>RETROspective — The Most Important Agile Ceremony</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*dawdx1hyMylGxl56DAOd5w.png" /></figure><p>If you ask me what my favourite Agile ceremony is, the answer will be the Sprint Retrospective (or the <em>Retro,</em> as we affectionately call it), without a doubt. It’s not because I get to wear a crazy hair wig, put fancy eyewear on or conduct cool and fun team activities that involve asking my team members wacky questions. These contributing factors may make <em>Retro</em> the most fun Agile ceremony, but more importantly, it’s my favourite because of the platform it provides to pause what we are doing, reflect on our past and learn to improve things in the future.</p><h3>An Effective Retro</h3><p>An effective <em>Retro</em> allows team members to embrace each other with a fun-filled activity, take an objective look at the way they worked in the immediate past and come up with a small but effective set of actions to keep improving.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qOiJKAbTvDumLkFVOHSDSw.png" /><figcaption>An effective Retro conducted regularly will continuously improve the quality of work.</figcaption></figure><p>Let’s take a closer look at the benefits of an effective <em>Retro</em>.</p><h4>It provides a reality check</h4><p>The <em>Retro</em> allows everyone in the team to pause and take a reality check of the objectives and key results (OKRs) set upon them and how each team member is aligned with it. It allows the team to identify any drifts away from the original goal and make adjustments before they become more complicated and expensive to rectify.</p><h4>It sets a natural starting point</h4><p>If you have been tasked with transforming the manner a team works into modern and Agile ways of working, re-energising a team, taking on a new project or program after completing another in the past, or a team has undergone significant changes in terms of skill, members, or direction, conducting a <em>Retro</em> creates a logical and natural starting point. The sensation the ‘pause’ creates gives everyone the feeling that we all ought to reflect and agree on the best ways to move forward rather than linger in the past.</p><h4>It’s about people</h4><p>It’s the only Agile ceremony that puts the focus back on people and how they interact with each other. The other ceremonies focus on the product or the service that the team is tasked to deliver. It is people who create the product or the service and getting it right with people is the foundation of getting the product or the service right.</p><h4>It treats everyone equally</h4><p>The <em>Retro</em> does not take the positions of the team members into consideration. Therefore, it doesn’t include a chain of command for discussions. Everyone is treated equally and placed on the same level playing field, offering a platform to highlight what is and isn’t good. The purpose of the <em>Retro</em> is to encourage everyone to:</p><ul><li>acknowledge and build upon the things that worked and helped the team,</li><li>appreciate the wins (big or small) and the collaboration between team members who looked after each other,</li><li>focus on improving or pivoting from practices that prevented the team from achieving their goals,</li><li>formulate a united front to focus on the challenges presented by external parties or factors.</li></ul><p>On the other hand, a poorly formulated and conducted <em>Retro</em> can be more damaging to the team than not having one at all. It can tarnish the trust between team members, create fear, create a command-and-control structure and lead to a situation where points of improvement raised during the ceremony fall on deaf ears, without any serious desire to rectify and improve.</p><p>So, what makes a <em>Retro</em> effective?</p><h4>Create a safe space</h4><p>Creating a safe space for everyone in the team to walk into and express their views is at the heart of making the <em>Retro</em> a positive and result-oriented activity. The team is not there to focus on any individual or individuals but on the events that occurred and the challenges they faced.</p><p>The <em>Prime Directive for Retrospectives</em> according to Norm Kerth, clearly articulates the basis for establishing a safe space for the <em>Retro</em>.</p><blockquote><em>‘Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand.’</em></blockquote><p>This ties in with the overall fabric of creating a safe culture across the entire ways your team works. It does so by not only removing the fear of retribution for getting something wrong but also by continuing to encourage the team to be creative and innovative in order to improve in the future.</p><h4>Get the whole team involved</h4><p>All of the team members must take part in the <em>Retro</em> for it to be complete and effective. This will create a holistic viewpoint of the events that occurred so that they are not viewed from the potentially narrow perspectives of individuals. The more comprehensive the information presented about each <em>Retro</em> point, the more applicable and effective the responses will be.</p><p>If your team comprises of members who are geographically distributed, it is important for all team members to be invited, regardless of their location, and for it to be held on a day and at a time that is convenient for everyone. It is also important for remote participants to be given an equal opportunity to speak up and for them to be actively engaged throughout the <em>Retro</em>.</p><h4>Conduct regular Retros</h4><p>When <em>Retros</em> are conducted regularly (usually on the last day of every sprint), the opportunity to raise points of discussion while the memories are fresh is provided:</p><ul><li>events that occurred,</li><li>challenges your team faced,</li><li>great things that team members achieved and,</li><li>products and services your team delivered.</li></ul><p>This way, the chances of something important falling through the cracks of memory is reduced, as well as losing details critical for proper scrutiny. This also allows the team to agree on actions that can be put in place to address these points incrementally.</p><h4>Come prepared</h4><p>A typical sprint can last from two weeks to a month, which is not a short time to retain a vivid memory of all the events, challenges and great moments that happened. Therefore, encourage your team to keep making notes of moments that felt good or bad in detail throughout the sprint so the <em>Retro</em> has an impact.</p><p>Coming to the <em>Retro</em> well prepared not only improves the quality of the points raised and enriches the discussions but also saves your team time when listing the points. This leads to more relaxed and articulated discussions of each point, providing the opportunity to arrive at a more structured response to each point raised.</p><h4>Lose your en(title)ments</h4><p>The titles we hold define the duties and responsibilities we carry out day-to-day. However, they also represent organisational hierarchy, authority and seniority. Forget your titles and entitlements during the <em>Retro</em>. This enables all team members to feel equally safe and confident as well as to be open and honest, increasing the value of what’s being raised and discussed.</p><p>Agree on a social contract to practice humility and empathy, look at each other from the other person’s viewpoint and ask open-ended questions to allow the other person to be more expressive about what they’ve highlighted at the first place. Don’t attempt to advise or solve problems for the team, even if you’re in a more authoritative position, but encourage the team to collectively arrive at a response. Arriving at actions and responses as a team increases the chances of these being followed through until the desired outcomes are achieved.</p><p>Even as the coach, delivery lead or scrum master, you’re not there to solve the problem. You are there to facilitate the session, encourage active participation and steer the session in the right direction to achieve the best results. Your mission is to use your specialised training and knowledge to guide the team towards the objective.</p><h4>Focus on small improvements</h4><p>It is crucial to agree on actions, changes or improvements that could be easily implemented by your team and these should be implemented during the next couple of sprints if possible. Avoid discussing systematic changes that would most likely require a project with a wider scope. Nominate a representative within your team to bubble up the types of points at a more relevant meeting within your department/tribe.</p><p>The actions your team arrive at have a better chance of succeeding if they are seamless enough to be incorporated into usual day-to-day activities and small enough to keep the additional attention and effort required by your team members to implement them at a minimum.</p><blockquote><em>The objective shouldn’t be to drain the entire lake to catch fish. It should be to identify how to hold the fishing rod better, to use a more suitable type fishing rod and bate and to find the best time to go fishing in order to catch fish easily and more frequently with minimum effort and time.</em></blockquote><p>Small and incremental tweaks are the most effective way to showcase the improvements your team continuously undergoes to your stakeholders and make your team feel that the <em>Retro</em> has a positive impact on the way they work.</p><h4>Follow up on actions agreed</h4><p>This is one of the most important factors in upholding the trust your team has in the <em>Retro</em>. It becomes untenable to keep asking your team to come back and make an effort to raise their points if the actions they previously agreed on are not followed through. Ensure that the actions are visible to the team and that the owner of each action provides ongoing updates on the progress until it has been completed.</p><blockquote><em>A Retro without the desire to implement actions is just a winging session.</em></blockquote><h4>Make it fun</h4><p>Last but not least, make sure the <em>Retro</em> is fun. Remember my opening paragraph on Retrospectives? It’s about coming together as a team to discuss how you work together. Ensure that you include a fun-filled team activity at the start of or during the <em>Retro</em> to keep everyone energised and engaged. It is also important to create a warm and welcoming environment where everyone feels relaxed, safe and able to be their true selves.</p><blockquote><em>Retro is about people, and people love having fun!</em></blockquote><p>Team activities can be organised in a way that they either convey a deeper, more serious message with a lighter touch or as an opportunity for team members to get to know each other better so that they learn to interact with each other more effectively during work.</p><h3>Summary</h3><p>A well-structured and conducted <em>Retro</em> is what lays as well as strengthens the foundation for a healthy team.</p><p>It allows team members to form stronger bonds by enabling conversations outside the typical day-to-day framework. It shifts the focus away from the product or service they create to the method they employ to create it by facilitating conversations on ‘ways of work’ instead of ‘work’. It provides all team members with an opportunity to let go of their official titles, simply be human and talk about good things, bad things and, more importantly, what they could do about the bad things. The <em>Retro</em> makes everyone in the team get up from their chairs and move around to have a bit of fun!</p><p>Go ahead… get your next <em>Retro</em> organised and plan to have loads of fun!</p><p>Thank you for reading this article.</p><p>If you’re interested in finding out more about how well-structured <em>Retros</em> are run to continuously improve the way your teams work, please hit us up at <a href="https://momenton.com.au/">https://momenton.com.au/</a></p><h3>Further Referring Material</h3><p><em>* A list of different types of formats that could be used to create excitement and variety in each Retro — * Follow the link below if you’re interested in conducting Retros involving remote teams, either by design or as a result of lock-down measurements in place due to COVID-19 pandemic. — * Below are some questions each team member could ask on their own to instigate Retro points. </em><strong><em>Product Owner</em></strong> <a href="https://scrum-master-toolbox.org/2020/03/blog/facilitating-remote-retrospectives-for-recently-distributed-teams/"><em>https://scrum-master-toolbox.org/2020/03/blog/facilitating-remote-retrospectives-for-recently-distributed-teams/</em></a> <strong><em>Developer</em></strong> <a href="http://www.agileuprising.com/2017/01/01/10-retrospectives/"><em>http://www.agileuprising.com/2017/01/01/10-retrospectives/</em></a><strong><em>Tester</em></strong> <strong><em>|Analyst</em></strong> <a href="https://www.atlassian.com/blog/jira-software/5-fun-sprint-retrospective-ideas-templates"><em>https://www.atlassian.com/blog/jira-software/5-fun-sprint-retrospective-ideas-templates</em></a><strong><em>Scrum Master / Delivery Lead</em></strong> <strong><em>|</em></strong><a href="https://funretro.io/retrospective-ideas"><em>https://funretro.io/retrospective-ideas</em></a></p><ul><li><em>What can we do to support my team to focus on the business problem I want them to solve?</em></li><li><em>How can we ensure that my team is not distracted and does not end up spending time and effort on anything that is not going to be valuable to our customers?</em></li><li><em>How can I work with the business stakeholders so I could be upfront and proactive about the need to deliver a particular feature, upcoming work and priorities?</em></li><li><em>How can I make my team’s work in progress transparent and visible to business stakeholders?</em></li><li><em>How can I make my pull requests small and build systems free of issues?</em></li><li><em>How can I work with my Journey Expert, Tester and Product Owner to make them understand the challenges I face with technology and how it impacts the solution?</em></li><li><em>How can I work with Testers more closely so they are prepared to test my story effectively and efficiently?</em></li><li><em>How can I work with my fellow developers so they are aware of what I’m doing and the potential blockers I might face?</em></li><li><em>How can I balance the expectation between delivery of new features and Tech-Debt?</em></li><li><em>How can I get clear details on test requirements, delivery scope and underlying services that need to be involved while testing a story?</em></li><li><em>How can I make myself heard more during effort estimates and commitment dates?</em></li><li><em>How can I juggle stories that move forward that have been completed by around the same time?</em></li><li><em>What support do I need from my team to make up the lost time due to test environments being down?</em></li><li><em>How can I make sure that test data has been provided by respective parties on time and in its entirety?</em></li><li><em>How can I work with other team members to understand the business requirement and map that to the best possible solution offering?</em></li><li><em>How can collaborate with other teams to explore how they have solved similar problems in the past?</em></li><li><em>How do I find the time to document everything effectively and share them with my team?</em></li><li><em>What’s the support I need from my team to juggle a hundred different things I need to complete during a Sprint?</em></li><li><em>How can I get my team to slice the work so they are small and independent but valuable on their own when completed?</em></li><li><em>How can we protect the team from distractions?</em></li><li><em>How can the team manage unplanned work?</em></li><li><em>How can the team get better at collaboration and knowledge sharing?</em></li><li><em>How can we empower each team member to be their best and feel safe to be open and honest about the challenges they face?</em></li><li><em>How can we rally around the Product Owner to enable the business value in the shortest time span and with the required quality?</em></li></ul><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/retrospective-most-important-agile-ceremony-sam-perera-he-him-/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c34fa848fe68" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/retrospective-the-most-important-agile-ceremony-c34fa848fe68">RETROspective — The Most Important Agile Ceremony</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Remote working — How to make it work for everyone?]]></title>
            <link>https://medium.com/momenton/remote-working-how-to-make-it-work-for-everyone-4341d93a2ff2?source=rss----29269809ff78---4</link>
            <guid isPermaLink="false">https://medium.com/p/4341d93a2ff2</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[ways-of-working]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[work-from-home]]></category>
            <dc:creator><![CDATA[Sam Perera]]></dc:creator>
            <pubDate>Thu, 26 Mar 2020 03:04:18 GMT</pubDate>
            <atom:updated>2020-03-26T03:04:18.782Z</atom:updated>
            <content:encoded><![CDATA[<h3>Remote working — How to make it work for everyone?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/1*WbgKRIfRigYG2Or6vDf6pg.jpeg" /><figcaption>Image Credit — runningremote.com</figcaption></figure><h3>COVER NOTE</h3><p>I have been working on this article since early February without a set date to publish it. At that time my intention was to create broader awareness of the remote working arrangements adopted by most tech companies or departments over the past decade and to encourage a wider audience to consider adopting such practices in their own working environments.</p><p>I (and most of us for that matter) never thought that remote working would so rapidly become a critical aspect to businesses continuity, but the global <a href="https://en.wikipedia.org/wiki/Coronavirus_disease_2019">COVID-19</a> pandemic that has unfolded before our eyes has made it so. Most organisations are scrambling to find the answers that I attempt to share in this article. The kicker, however, is that a process that would ordinarily have taken weeks-if not months-to properly design, implement and fine-tune must now be executed in a matter of days.</p><h3>INTRODUCTION</h3><p>In this day and age, where the notion of the work-life balance is gradually evolving into work-life integration, remote working has become a crucial discussion point both during the initial hiring process and during ongoing employment arrangements. Despite this, members of our society hold a variety of opinions and draw a variety of conclusions about this sometimes-contentious topic. Some people embrace it as the holy grail of flexible working while other people dismiss it as one of the most abused aspects of employment-both from an employer and employee viewpoint.</p><p>Whether we like it or not, this practice is only heading north with more and more organisations and industries offering the opportunity to work remotely. Not only does this offer make jobs attractive to their potential and current employees but it also allows companies to utilise their existing office space and resources more effectively and efficiently.</p><p>As a father of two kids, I have benefited from the flexibility of remote working, although it has not been without challenges. This article is an attempt to elaborate on three key areas that we should consider when implementing remote working: objectives and philosophy, culture and mindset, and technology. We should carefully consider these concepts before embarking on a remote working journey as individuals, teams and organisations. This consideration will give our remote working practices a better chance of success and ensure that both employers and employees get the value they expect.</p><h3>OBJECTIVE AND PHILOSOPHY</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*Q4RDoeF3_W3XZVMdw-NwdQ.jpeg" /></figure><p>Objective and philosophy refer to the ideas at the heart of the initiative. An organisation must delve into its values, principles, vision and mission statements to establish reasons for allowing its employees the freedom to work remotely without constant supervision from their managers or leaders.</p><p><strong>The ‘Why’</strong> — Organisations should clearly define and articulate the objectives for extending their employees the flexible option to work remotely. Without measurable objectives, it will be challenging to establish a justification for remote working and to monitor the strategy’s effect on the organisation’s ways of working. It will also be challenging to identify any adjustments the process needs or, at worst, to make an informed decision to scrap it altogether.</p><p>Some examples of such measurable objectives could be a reduction in the number of sick leave days that employees submit, an increase in productivity over a given time period compared, an increase in the employees’ happiness index or savings from the reduced cost of utilities, cleaning and general maintenance of office buildings.</p><p><strong>Intent </strong>— This is where the mindset of an organisation’s leaders is put into the test. They must have a genuine intent to make remote working work, and not just treat it as another ‘cool’ thing that the organisation can offer to employees that would eventually be seen as a ‘fad’. The most important factor in the success of remote working will be the leaderships’ willingness to give the strategy their effort, guidance, open mindset and attention to any practical issues that arise.</p><p><strong>Teams </strong>— Consider trialling the process with one or two teams at the start. Smaller and more cohesive teams make great candidates as they will most likely reduce the number of early challenges you will face during the trial. This strategy will allow the organisation to learn fast and implement necessary changes to keep the trial on the right path until you can bring more complex and challenging teams on board.</p><p><strong>Days </strong>— Another decision an organisation’s leaders must make is for how many days they will allow their employees to work remotely. A good number to start with is one. This way the leaders can identify any practical issues without experiencing major disruptions to business continuity, operations and productivity levels.</p><p><strong>Security</strong> — It is important to ensure that the organisation’s security policies are revised and updated to ensure that they work as smoothly in a remote working environment as they do at office premises. This is especially relevant in the case of accessing software applications and resources like files and documents.</p><p>Organisations should engage the right employees early on in the conversation. This will reduce the practical issues their workforce might struggle with while working remotely. It will also reduce the resistance from staff whose job involves security, which is important because resistance might have an adverse impact on the overall success of the initiative.</p><p><strong>Feedback </strong>— Leaders should take time to listen to feedback from employees and provide them with ample opportunities to voice their concerns and suggestions throughout every stage of the remote working initiative. They should then reflect on this feedback and formulate an action plan with the aim of genuinely learning and improving. The action plan should be transparent and available across the organisation, and after its release leaders should continue to seek advice and assistance from relevant individuals and departments to solve any challenges reported.</p><p><strong>Courage </strong>— Decision-makers should be bold and test innovative approaches that specifically address the unique needs of the organisation and its business model. Leaders should create a safe and reassuring environment throughout their organisations so that individuals can suggest ideas and, where feasible, take the initiative to action those ideas.</p><h3>CULTURE AND MINDSET</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*q3ZmswhUVfjuMxUA5KOiVg.png" /></figure><p>Culture and mindset set the tone for the policies and procedures associated with remote working. It is important to acknowledge that people are at the heart of every process and we all need to play our part for remote working to be successful.</p><p><strong>We’re all different </strong>— It is important to be mindful of the different cultural backgrounds that team members come from and the effect these backgrounds might have on how they operate. This could be particularly important while having meetings where some team members might not feel comfortable asking questions over remote channels even when they require clarification on certain points (see the ‘Inclusive Meetings’ subsection for further details).</p><p><strong>Give and take </strong>— When it comes to organising activities and requiring your employees’ and colleagues’ participation, it is good to have an open mind and a willingness to be flexible. People organising such activities should take account of the time zone of each team member and ensure that no one person is inconvenienced all the time by rotating the Happy-Hour around different time zones.</p><p><strong>Open communication </strong>— Exploring innovative ways to gather feedback from team members, allowing them to express themselves and their opinion during working hours, would be beneficial. This goes back to the cultural factor that was discussed above. Using a variety of methods will increase the chance of team members with different traits being equally heard and will increase participation throughout the day and-more importantly-during key decision-making periods.</p><p><strong>Be transparent </strong>— Colleagues should make their remote working schedule visible to all the related teams they work with. One of the best ways to achieve this is to add remote working days to your existing leave or holiday calendar. They can also bring those days up in their daily or weekly huddles and as part of sprint planning activities (if you organise your teamwork into sprints). They can also set reminders using the team’s instant messenger software to send out alerts in the morning so the whole team is aware of their working arrangements.</p><p><strong>Plan your day </strong>— It is important that people working from home ensure they have a sufficient amount of work to fill their day and keep them productive. If a workplace provides a limited bandwidth to allow employees to access the office network over the internet, they should make local copies of documents they plan to work on remotely. They should also make short notes about activities they need to complete during the day so you don’t miss anything important or end up not completing the work they initially intended to.</p><p><em>It is important that nobody makes any secret plans not to work as this would mean that the rest of the team will have to bear the brunt of their lack of contribution in the short term. This will have an adverse impact on the success of the remote working practice as a whole in the long term.</em></p><p><strong>Make your work visible </strong>— Team members should constantly share their progress of your work during the day. They should keep updating the status of their work items in the work management tool with corresponding comments. They can type in a short message of the progress made and give a heads-up about any assistance they might need from their teammates and any upcoming meetings or chats they might want to have before they can progress further.</p><p>For example @here team, I have raised a pull request on story APP-12656 and waiting on Winston to review it, or @Silvia, I have tested the story APP-25676 and updated my test results under the comments section, could you please have a look?</p><p><strong>Inclusive meetings </strong>— It might not be possible to make meeting-free days for everyone who is working remotely. It would therefore be more practical to agree on how to best organise, prepare and effectively conduct meetings that include remote participants. Some strategies include:</p><ol><li>Providing context: Share the meeting agenda upfront and include all relevant background information, clearly defined meeting objectives, desired outcomes, any relevant preparation work and prior notes from any related meetings.</li><li>Setting clear phases: If you’re the facilitator of the meeting, make sure that the phases of the meeting are laid out clearly and are accessible so that people participating remotely can easily follow the meeting and make an impactful contribution.</li><li>Letting them see the meeting room: Ensure the remote participants can see the meeting room in the office and hear what’s being discussed clearly.</li><li>Looking for visual clues: Before the meeting, agree on visual clues that remote workers can use to grab the attention of other team members and keep looking out for them so everyone in the meeting gets an opportunity to speak up. Team members who usually feel reserved and shy about speaking up tend to become even more silent while participating remotely. Ask open-ended questions to encourage them to express their views.</li><li>Preventing distractions: Call out off-topic conversations that might distract the participants during the meeting. It is also important to allow only one conversation at a time to reduce unnecessary noise within the room and to allow remote participants to follow each conversation properly.</li><li>Using illustrations: Use visual illustrations and drawings whenever possible to provide better clarity on the matter that is being explained or discussed.</li><li>Let others see you: If you’re a remote participant, letting others see you is probably the most effective way to make your presence felt amongst other participants and to increase the chances of making an effective contribution during the meeting. Enabling video during a meeting must be the norm rather than the exception.</li><li>Share your surroundings: As a remote participant share a bit about your surroundings when the time is right. For example, kids and/or pets at home, an artwork, a photo hung on the wall appearing in the background or something interesting about your garden if you have chosen to sit outdoors would be a great icebreaker and probably enable others to connect with you on a deeper level.</li><li>Post-meeting updates: Share notes, action items and photos of the whiteboard with people working remotely immediately after the meeting to ensure they could take in the meeting in the same level of detail as the people who were at the office.</li><li>Equal opportunities: Involve people taking part remotely in the actual decision-making process and not just as passive listeners. Ask questions actively both during the meeting and as part of any follow-up conversations before the final decision is made. Ensure that any decisions are communicated to team members within the office and those working remotely at the same time as much as practically possible.</li></ol><h3>TECHNOLOGY</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/536/1*GIYOpJA6HHEW7e6LRriN_Q.png" /></figure><p>Finally, both employers and employees need to consider carefully their technological requirements and what tools they require to be effective while working remotely.</p><p><strong>Connectivity </strong>— Organisations should invest in a robust and reliable internet connection as it is the number one technical reason most remote working arrangements fall through the cracks. A connection that is reliable and fast will provide an uninterrupted pathway and facilitate the exchange of data between the employees’ remote locations and the office building whether it is during a video conference, presentation or simply in order to access a file that is stored in the office network.</p><p><strong>Software </strong>— Software is equally important for providing an efficient and effective working environment for all. Video conferencing, file sharing, Virtual Private Network (VPN), up-to-date virus scanning, and productivity applications that support collaboration amongst team members are pivotal to this. It is also important to consider how bespoke software that has been purpose-built for an organisation’s needs (such as customised ERP packages) will behave when accessed remotely. The expectation should be that such a software package would continue to offer the same level of functionality remotely without compromising the organisation’s cybersecurity.</p><p><strong>Training </strong>— Employees should be provided with sufficient up-front and ongoing training on any equipment and additional software to be used during remote working. People who are constantly struggling to initiate a video conference, share a screen during a presentation or hear what a remote caller is saying will often conclude that remote working is disastrous when in fact it is the knowledge about how to use the technology that needs improving.</p><p><strong>Access </strong>— Working with security decision-makers and operational teams to arrange simple and transparent login mechanisms can prevent users from having to jump through complicated user authentication and validation processes. One great approach is to implement a ‘single sign-on’ system to allow remote users to access all required organisational resources with the same user ID and password. Two-factor authentication can provide enhanced security.</p><h3>SUMMARY</h3><p>These three aspects, when considered carefully and implemented properly with the right intentions, will most definitely make remote working work for your organisation. They will increase levels of employee engagement, lead to a workforce that is much more agile, responsive and self-organising. This will lead to a business with a more robust operating model and a <a href="https://en.wikipedia.org/wiki/Business_continuity_planning">Business Continuity Plan</a> (BCP) built into its DNA.</p><p>Remote working is here to stay. Let us all do it right and get the most out of it.</p><p>Thanks for your time reading through this article. I hope you stay healthy and safe during these challenging times!</p><p><em>Originally published at </em><a href="https://www.linkedin.com/pulse/remote-working-how-make-work-sam-perera-he-him-/"><em>https://www.linkedin.com</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4341d93a2ff2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/momenton/remote-working-how-to-make-it-work-for-everyone-4341d93a2ff2">Remote working — How to make it work for everyone?</a> was originally published in <a href="https://medium.com/momenton">Momenton</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>