<?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[Stories by matt ward on Medium]]></title>
        <description><![CDATA[Stories by matt ward on Medium]]></description>
        <link>https://medium.com/@mattyjward_19401?source=rss-4018937f569a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*M5QKPT9mw5hjn5dw.jpg</url>
            <title>Stories by matt ward on Medium</title>
            <link>https://medium.com/@mattyjward_19401?source=rss-4018937f569a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 11:43:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mattyjward_19401/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Segregation of Duties in a Cloud Native world]]></title>
            <link>https://medium.com/@mattyjward_19401/segregation-of-duties-in-a-cloud-native-world-8a7a001fc16c?source=rss-4018937f569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a7a001fc16c</guid>
            <category><![CDATA[risk]]></category>
            <category><![CDATA[cloud-native]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <category><![CDATA[segregation-of-duties]]></category>
            <category><![CDATA[devops]]></category>
            <dc:creator><![CDATA[matt ward]]></dc:creator>
            <pubDate>Sun, 28 Apr 2019 11:14:17 GMT</pubDate>
            <atom:updated>2019-04-28T11:14:17.741Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m3edoBlgWsnF0Dp2f8059A.png" /></figure><h4>What is Segregation of Duties?</h4><p>“Production access” is a phrase that sends chills down a lot of peoples’ spines.</p><p>Segregation of Duties (SoD) is an internal control that you will find in highly-regulated industries such as banking. It aims to address a couple of risks that arise when someone is accessing or changing production, namely <strong>errors</strong>, and <strong>fraud</strong>.</p><p>It is usually enacted by requiring more than one person to be involved in making a change from development to production, though it often plays out as having more than one team.</p><p><strong>The Good<br></strong>To its credit, traditional SoD does make you go through a formal change management process. If another person is to successfully do a deployment, then clear instructions need to be written down, reviewed, and agreed upon.</p><p>Also, the fundamental SoD practice of not allowing developers to have direct server access does make it harder for someone to do something blatantly dodgy.</p><p><strong>The Bad<br></strong>Unfortunately we are not great at either writing clear instructions, nor are we great at following them. Deployments performed by someone outside the team often introduce errors.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*GUvdFsxAmqCsbxhGNPpKqA.jpeg" /><figcaption>cakewrecks.com</figcaption></figure><p>Further, between code repositories, build systems, and artefact repositories, there are many opportunities for a fiendish developer to sneak something past a deployment engineer without needing direct server access themselves.</p><p><strong>The Ugly<br></strong>Incidents! This is when the change management process often seems to go out the window. Hectic midnight chats with a team of developers desperately throwing suggestions at the deployment engineer - conscious of their SLA’s, their MTTR!</p><p>Then there is collusion. What happens when your developer and deployment engineer team up to commit fraud? Traditional SoD seems to give up at this point and say ‘too hard!’.</p><h4>Segregation of Duties in a Cloud Native world</h4><p>As we have been building our Cloud Native Platform, we have been asking ourselves how we can best solve this problem for our consumers.</p><p>We believe the answer is to provide a build and deployment pipeline to platform consumers that has been configured to allow teams to deliver, but restricts them from modifying the pipeline itself.</p><p>Automated deployments are now commonplace, but a secured, controlled deployment pipeline takes things to the next level.</p><p>Once code hits <em>master</em>, an immutable release candidate is created. It can be pushed all the way to production, or perished (say if tests fail), but it cannot be changed.</p><blockquote>‘How can we shift left Segregation of Duties as far as possible?’</blockquote><p>Given this pipeline, a requirement for an approved pull request on any change to <em>master</em> would satisfy the requirement for SoD.</p><p>Further, as we move to cloud native, and to PaaS/serverless worlds, the concept of direct server access is ceasing to exist. Resource access in the cloud portal is somewhat analogous, but the surface area of what can be changed is infinitely less.</p><p>Moving resource configuration into code, and into the same pipeline as described above, covers SoD for changes to the entire ‘server’, not just the application.</p><p>And collusion? The reduced surface area enables automated configuration and compliance monitoring to become possible, which could alert immediately upon the detection of any anomalies.</p><p>Exciting!</p><p><strong>Some thoughts on audit logs</strong></p><p>You will often hear that the presence of an audit log removes the need for a control to be in place. Post incident, audit logs can help identify what happened, who did it, and are vital in helping quickly remedy the situation.</p><p>From a customer perspective, this may be too late.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a7a001fc16c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Processes and Tools over Individuals and Interactions]]></title>
            <link>https://medium.com/@mattyjward_19401/processes-and-tools-over-individuals-and-interactions-2436044f7b45?source=rss-4018937f569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2436044f7b45</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[continuous-delivery]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[matt ward]]></dc:creator>
            <pubDate>Thu, 07 Mar 2019 09:40:13 GMT</pubDate>
            <atom:updated>2019-03-07T09:40:13.524Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Gcn_g9hL4gqtU2aI" /><figcaption>Photo by <a href="https://unsplash.com/@mr_sherez?utm_source=medium&amp;utm_medium=referral">Adam Sherez</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I like to tell myself that I live the Agile Manifesto. I often quote the four key values, I will bring them up when interviewing a candidate as a starting point for a discussion. I’m sure at some point I have printed them out and stuck them on a wall.</p><p>And then today…. I read them, and my brain flinched. Individuals and Interactions over Processes and Tools? Hmmmm…. Huh?</p><p>The product I am currently working on is aiming to codify a bunch of our organisation’s processes into some easy-to-use tools. Interactions are slow, often painful, and nearly always unpredictable. We don’t want individuals to have to have the same interactions over and over again. Do we?</p><p>It was like my brain had flipped to seeing the other half of an optical illusion. I could no longer remember the interpretation in which individuals and interactions was the preferred way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/194/1*v9nAhJtmLa3wgLH-BEYTmw.jpeg" /><figcaption>young woman or old woman?</figcaption></figure><p>I have spent some time this evening googling this, trying to get a feel for what this value means to other people.</p><p>Some people seem to interpret it as being about working closely with customers. But there is a whole other core value that addresses this — customer collaboration over contract negotiation.</p><p>The twelve supporting principles are often invoked, and looking at them there are some clues</p><blockquote>Business people and developers must work together daily throughout the project.</blockquote><p>and</p><blockquote>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</blockquote><p>suggest that the value concerns the relationship between ‘the business’ and ‘IT’.</p><p>I believe this relationship probably has shifted from Processes and Tools to Individuals and Interactions over the last twenty years, and for the better. Companies travelling through an Agile Transformation often aim to remove the distinction between business people and developers altogether.</p><p>Then there is</p><blockquote>Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.</blockquote><p>I think the key word there is <strong>trust</strong>. Empowerment over micro-management? That could be an interpretation.</p><p>I can see an angle for using it as an argument for self-organising teams, and the unlocking of individual, team, and organisational benefits which that brings.</p><blockquote>The best architectures, requirements, and designs emerge from self-organising teams.</blockquote><p>But then the dichotomy seems off. Individuals and Interactions over Roles and Responsibilities, maybe?</p><p>I have no doubt that this value was imperative when the Manifesto was written, but I wonder if it has not aged as well as the rest.</p><p>Fundamentally, we want to automate our software delivery. Continuous Delivery is a process, and DevOps is the tools. The greater the number of interactions we need to have with other individuals, the slower we go.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2436044f7b45" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ten Weeks a Product Owner]]></title>
            <link>https://medium.com/@mattyjward_19401/ten-weeks-a-product-owner-16e3ce3118e2?source=rss-4018937f569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/16e3ce3118e2</guid>
            <category><![CDATA[technical-leadership]]></category>
            <category><![CDATA[change]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[matt ward]]></dc:creator>
            <pubDate>Mon, 07 Jan 2019 13:42:55 GMT</pubDate>
            <atom:updated>2019-01-07T13:42:55.793Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5n8tevsZPhFAnWnJTzO3lA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/IUY_3DvM__w?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Matt Duncan</a> on <a href="https://unsplash.com/search/photos/roadmap?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>I recently moved from a Technical Lead role to a Product Owner role just ten weeks before heading off for a decent chunk of paternity leave. I thought I would share a few of the things I learnt…</p><p><strong>o — The other side of the fence</strong></p><p>This is the first time in my career that I have been involved with systems where I am not familiar with the codebase. As Product Owner I was making suggestions, asking questions, and was left trying to decipher the looks on the developers’ faces.</p><p>Was what I was saying ridiculous? Would it require a whole rewrite? Was it a clever change that they felt bad for not having implemented? (unlikely!) Had they had a big discussion about this and my question was resurfacing that?</p><p>Who knows!! I’m sure as a developer I would have been on the other side of this so many times, wearing an equally mysterious expression. When the pendulum swings back and I am developing again, I vow to take the time to explain!</p><p><strong>o — We are one, but we are many</strong></p><p>I found there was a large overlap between the things that frustrated me as a Technical Lead and the things that frustrated me as a Product Owner, but that they frustrated me in different ways.</p><p>The near-impossible push to establish continuous delivery in a company that is used to delivering projects — as a Tech Lead this frustrated me because my releases got bigger, and bigger releases are riskier! As a Product Owner this frustrated me because we weren’t getting things into our customers’ hands.</p><p>The weeks lost in hand-offs to other teams for tasks that we weren’t allowed to own — as a Tech Lead this frustrated me because hand-offs meant pausing work, increasing work in play, longer-lived branches or feature toggles, context switching… just bad stuff. As a Product Owner this frustrated me because hand-offs are a black hole, only completing (maybe?) at some unknown point in the future.</p><p><strong>o —Stuck between a roadmap and a hard plan</strong></p><p>Give my team a goal and we will make progress towards it. I’m a big fan of a ‘Now, Next, Later’ Roadmap, no dates, but a clear indication of where we are going. However as Product Owner I was expected to give a pretty clear indication of exactly how far we would progress during the quarter.</p><p>Part of me is amazed that in 2018 people were still asking for detailed delivery plans for software products, another part of me can understand that you need some indication of what you will deliver and when. What was I to do?</p><blockquote>“Look everyone, Matt made a Gantt chart”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*u6tOOx3iqExYo9VsS3yd5Q.jpeg" /></figure><p><strong>o — Let structure set you free</strong></p><p>My role as a Tech Lead was pretty vague, I’d been at the company for a while, I had moved from team to team. Things stick to you, you’re hesitant to let go of other things. I felt like I was in a lot of meetings I didn’t need to be in.</p><p>Moving to a new role gave me a chance to clean the slate. With my team we defined my role, and then I handed over (nearly) everything else to the other Tech Leads — I would still be around, I just wouldn’t be the go-to person.</p><p>Suddenly my days were much more cohesive, it was great! I guess I could have done this exercise at anytime… maybe next time when I feel like I’m in a lot of meetings that I don’t need to be in!</p><p><strong>o — Brains!</strong></p><p>As a self-described ‘constant learner’ I spend a fair bit of <em>my</em> time learning new technologies, but I would often find that after a long day spent coding, the required brainpower to check out the latest javascript framework after work just wasn’t there.</p><p>This completely changed after moving to the Product Owner role, now the techie part of my brain needed scratching, the learner part of my brain was as keen as ever, and as a result I feel I’m now growing technically <strong>more</strong> than when I was in my technical role!</p><p>And there it is, hurray for trying new things :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=16e3ce3118e2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DDD Perth Diversity & Inclusion 2018 Update]]></title>
            <link>https://medium.com/ddd-perth/ddd-perth-diversity-inclusion-2018-update-8ed9af094ff1?source=rss-4018937f569a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ed9af094ff1</guid>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[software]]></category>
            <category><![CDATA[inclusion]]></category>
            <category><![CDATA[diversity]]></category>
            <category><![CDATA[dddperth-official]]></category>
            <dc:creator><![CDATA[matt ward]]></dc:creator>
            <pubDate>Thu, 28 Jun 2018 04:37:38 GMT</pubDate>
            <atom:updated>2018-06-28T04:37:38.930Z</atom:updated>
            <content:encoded><![CDATA[<p>The organising committee are proud of what DDD Perth <a href="https://blog.dddperth.com/our-journey-towards-diversity-1d9796475f24">achieved last year</a>, but as we came together to organise this year’s conference we didn’t want to rest on our laurels, we wanted to go further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZJx7Ktis_oBacgyA7MGKAA.jpeg" /><figcaption>Our awesome 2017 speakers!</figcaption></figure><p><strong>Branding</strong></p><p>We started by reviewing our content, our branding, the message that we were sending out to the world.</p><p>A conference’s Code of Conduct is its official statement on what it represents, so the committee initiated a full review of ours, looking at what other conferences were doing and talking about what is really important for us. Please read what we <a href="https://dddperth.com/code-of-conduct">came up with</a>, it really sets the tone for the conference.</p><p>We asked <a href="https://twitter.com/stringy">Julie Grundy</a> (thanks Julie!) for an accessibility review of our website, and have been working, along with some much-appreciated volunteers, to address all the recommendations. The <a href="https://github.com/dddwa/dddperth-website/issues">remaining issues</a> are all listed on our GitHub repo so please, get involved!</p><p>And finally we thought about our name. We believe the name DDD initially came from Steve Ballmer’s infamous ‘Developers! Developers! Developers!’ chant, but we wanted DDD Perth to be for the whole software community. Luckily, DDD Melbourne had already engaged <a href="https://twitter.com/mattbirman">Matt Birman</a> to redo their logo so we piggy backed off that, stopped talking about developers so much, and now if anyone asks what DDD stands for, we say Developers! Designers! Data Scientists! (DevOps? Data Architects? Distributed Testers?)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*f1DU0ZCLKYaH194n5zuOIQ.png" /><figcaption>Our logo for this year’s conference!</figcaption></figure><p><strong>Community</strong></p><p>Next we thought about community, we are very much a community-focused event, and we wanted to see what new groups we could reach out to this year.</p><p>We decided that we wanted to focus on juniors this year, either in a speaking or attending capacity. We emailed academics, poked student groups on Facebook, and encouraged every junior that we knew to submit!</p><p>We reached out to the Autism Academy of Software Quality Assurance, offering tickets to its members to come along on the day, as well as mentoring for anyone interested in speaking.</p><p>And we’re thrilled to announce that one of our keynote speakers this year will be Mark Leopold from <a href="https://www.beyondblue.org.au/">beyondblue</a>, who will be speaking on ‘Better mental health in the workplace’.</p><p><strong>On the day</strong></p><p>Lastly we thought about the day itself, a conference can be hard to get to if you have kids, or intimidating if you are attending for the first time, don’t know many people, or identity as a part of a minority group.</p><p>We are thrilled to be providing subsidised childcare at this year’s conference. You can purchase an extra childcare ticket when you purchase your ticket, and your child will be cared for and provided with fun activities for the duration of the conference. You will just have to provide them with some food!</p><p>Last year we had one talk live-signed, and this year we are hoping to build on that by providing live captioning for all of our talks.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F4S2tT8tqc-w%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D4S2tT8tqc-w&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F4S2tT8tqc-w%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/758a4138e6a7a6651515f6ffccc8a750/href">https://medium.com/media/758a4138e6a7a6651515f6ffccc8a750/href</a></iframe><p>Finally we thought about assumptions that we may have been making about our attendees. This year when you purchase a ticket you will be able to indicate your preferred pronoun, as well as whether or not you are comfortable being photographed.</p><p>We hope that all these initiatives will lead to a more enjoyable, inclusive, and memorable day. If $50 is too much for you then please grab one of our free <a href="https://dddperth.com/faq">financial assistance</a> tickets. We hope to see you there!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ed9af094ff1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ddd-perth/ddd-perth-diversity-inclusion-2018-update-8ed9af094ff1">DDD Perth Diversity &amp; Inclusion 2018 Update</a> was originally published in <a href="https://medium.com/ddd-perth">DDD Perth</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>