<?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 Rumman Amin on Medium]]></title>
        <description><![CDATA[Stories by Rumman Amin on Medium]]></description>
        <link>https://medium.com/@rumman?source=rss-85499a3dbf3c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*n-K7iq9-7TWjcC886yPiOw.jpeg</url>
            <title>Stories by Rumman Amin on Medium</title>
            <link>https://medium.com/@rumman?source=rss-85499a3dbf3c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 10:30:24 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rumman/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[January ’22 — Important lessons learnt]]></title>
            <link>https://rumman.medium.com/january-22-important-lessons-learnt-75bc12c9f7ca?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/75bc12c9f7ca</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[transformation]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Fri, 12 Aug 2022 08:32:11 GMT</pubDate>
            <atom:updated>2022-08-12T08:58:38.423Z</atom:updated>
            <content:encoded><![CDATA[<h3>January ’22 — Important lessons learnt</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qTjWoHk1tFtkn7C4" /></figure><p>Sharing some outputs from a retro session this week with the Delivery community of practice [When I say this week, I wrote this in January but forgot to press publish until August 🤯]:</p><p>1. We experienced difficulty adopting OKRs as the mechanism of identifying, tracking and measuring success. The ‘why’ was unclear. KRs included external dependencies that the team did not have control over 🚩<br> <br>2. Hedge educated bets vs upfront planning — An architectural roadmap will help identify opportunities + leverage potential value. Determine criteria to build for reuse vs build product-specific functionality.</p><p>3. Introduce <em>lightweight </em>governance. Multiple layers of steering groups are time consuming and the enemy of delivering anything at pace. Give teams the autonomy to make decisions, communicate outwards and work in the open — but also give them the clear escalation routes so they can get help when needed.</p><p>4. Be clear about strategic priorities and how initiatives link to this + move organisation forward. The absence of this makes prioritisation and motivation difficult 🚩</p><p>5. Benefits definition and realisation. These should be co-owned by business stakeholders and service teams. Work collaboratively rather, regular feedback loops, bi-directional, empowered.</p><p>6. Give yourself extra time to navigate a difficult recruitment environment and complex procurement processes. Also, supplier/contract management is key — How can we foster a positive relationship with suppliers but also make sure we are getting quality and value for money</p><p>7. Think long-term. Life beyond ‘done’. What does ongoing support and continuous improvement of product/service look like? Impact on operational/business teams? Does this include decommissioning? What is the total life cost?</p><p>​</p><p>​</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=75bc12c9f7ca" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[December ’21 — How can we deliver leaner Programmes?]]></title>
            <link>https://rumman.medium.com/december-21-how-can-we-deliver-leaner-programmes-d06a3d48a285?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d06a3d48a285</guid>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Sun, 12 Dec 2021 04:50:15 GMT</pubDate>
            <atom:updated>2022-01-19T12:21:48.193Z</atom:updated>
            <content:encoded><![CDATA[<h3>December ’21 — Can we deliver leaner Programmes in Gov?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_Rpw1E_5acjrKMtD" /></figure><p>I went for a walk along the Embankment on Friday to clear my head from a long, and at times, frustrating week. The cold fresh air does absolute wonders for the mind, and made even better with some hot churros.</p><p>So what’s been frustrating me recently? Well as a delivery person (and it doesn’t matter at what level) we’re hard-wired towards certain things like protecting teams, planning change, removing blockers, providing clarity in/out, maintaining delivery momentum, navigating org processes etc — And over the last few weeks, It’s become increasingly clear the environment we’re operating in doesn’t quite have the stability and mechanisms in place to deliver change without the need for total control.</p><p>The challenge with large government programmes is by their very nature, they are almost the opposite (maybe even an anti-pattern) of what we consider good Agile delivery practices — but as a vehicle for complex change, they are pretty much the default in most government organisations.</p><p>And maybe this belongs in a longer post or better confined to the safety net of our community of practice, but I’ve noticed two things:</p><ol><li>There is a correlation between the size of change taken on and the Agile maturity of the organisation.</li><li>Environments of trust, autonomy and psychological safety are not the default <em>(Although you can influence your immediate surroundings).</em></li></ol><p>What this means is instead of starting small, lightweight governance and working in the open; you experience months of scope definition, forensic financial forecasting and painfully heavy reporting.</p><p>I’m curious to understand what this is down to. Could it be the way funding is allocated? How our organisations operate in silos? Should we even be attempting ‘large’ programmes of change?</p><p>This reinforces the point, you cannot simply do technical/digital change in isolation. The cultural/org change must happen alongside it to really unlock those long-term benefits for your organisation.</p><blockquote>“[People] and interactions over processes and tools.”</blockquote><p><strong>Update:</strong> There was a great <a href="https://twitter.com/rumantweets/status/1469962731801436164">thread about this on Twitter</a>, I’ve pulled out my favourite tweet that sums it up perfectly:</p><h3>himal on Twitter: &quot;People. Teams. Tools. Room. Pizza. Figuratively speaking. Leave them to it. So hard for many orgs to do. Let people get on with things / Twitter&quot;</h3><p>People. Teams. Tools. Room. Pizza. Figuratively speaking. Leave them to it. So hard for many orgs to do. Let people get on with things</p><h4>Workshop</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1003/1*z3YRILakkSWdXIhnpEvLVg.png" /><figcaption>Workshop output — 2x2 Value/Effort Grid</figcaption></figure><p>Coincidently, one real win for us over the last month has been to conclude one of our early transformation programmes for Cloud Hosting.</p><p>We often ask teams to be flexible, but governance should also be flexible. Value for them (and their users) isn’t usually an assurance gate or date.</p><p>As we neared the end of these programmes, we took a step back to understand:</p><ol><li>Have we delivered the highest priority?</li><li>Are we clear on the next priority? and our long-term objectives?</li><li>Is ‘x’ a priority or a nice to have?</li></ol><p>For us, our primary users here were developers and our delivery teams, who would be using the Cloud Platform to build, host, run and support services. I thought we had achieved our goals and met our users needs, so it was the right time to wind things down — but it was important to get the service owner, team and key stakeholders together to discuss this.</p><p>It’d been a while since I’ve facilitated a workshop but there’s nothing like an old fashioned 2x2 value/effort grid. In this session, we determined:</p><ol><li>We have enabled teams to host and run new services in the cloud.</li><li>Migrating things out of the Data Centre is important (will take time to plan/mobilise)</li><li>Maturing new cloud service further with additional features is a nice to have but not essential (See 1.)</li><li>We need to get better at prioritisation given that bottom right (don’t do) corner was blank.</li></ol><p>Anyway! Have a nice break folks and enjoy the snow while it lasts. 😀</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*yjQc_B8JECmTFEE5" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d06a3d48a285" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[November ’21 — Understanding sunk cost]]></title>
            <link>https://rumman.medium.com/november-204fbec9cfd?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/204fbec9cfd</guid>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Sat, 20 Nov 2021 03:50:54 GMT</pubDate>
            <atom:updated>2021-12-04T12:47:09.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vwMzTrMI--WZdJuS" /><figcaption>Recently visited the Homes England Liverpool office</figcaption></figure><p>I’ve previously written about our <a href="https://rumman.medium.com/digital-transformation-in-government-d2521ecb36c2">Digital Transformation journey</a> and the various techniques that worked well. Something I want to do more of is talk about some of the challenges we’re coming up against.</p><h4>Sunk Cost Fallacy</h4><p><em>[Noun. The phenomenon whereby a person is reluctant to abandon a strategy or course of action because they have invested heavily in it, even when it is clear that abandonment would be more beneficial.]</em></p><p>I’ve been thinking about this a lot over the last few weeks and it came up as recently as yesterday. We were discussing a project that has been in progress for some time, and we tried to take a step back to understand what the overarching priorities are for that area as a whole — and if this particular project, is still helping us achieve or get closer to those goals.</p><p>At what point do we draw a line under a project or initiative? Have we achieved everything we set out to? Has our thinking or our priorities changed? Are we still meeting our users’ needs? Are we still delivering value? And depending on some of the answers, Have we come to a natural conclusion?</p><p>This sort of honest reflection is important, particularly if a project has drifted. We’ve all been involved in projects that have pushed on, even when the right thing to do would have been to stop. Maybe that’s human nature, to see things through to the end, particularly if you’ve invested a lot of time, money and effort towards it.</p><p>Introduce regular feedback loops, rather than waiting for ‘gates’ and create an environment of <a href="https://hbr.org/2017/08/high-performing-teams-need-psychological-safety-heres-how-to-create-it">psychological safety</a> where teams can speak openly with ideas or raise concerns without dreading stakeholders.</p><p>A final point about value. There is absolutely value in doing an experiment and then coming to a conclusion that this discovery or alpha or project x should stop based on research or feedback — In fact, you’ll be saving time and money.</p><p><strong>We should normalise stopping.</strong></p><h4>Some tips I always go back to:</h4><ol><li>Be clear on why you’re doing the work</li><li>Understand what problems you’re trying to solve</li><li>Start small and iterate</li><li>Regular feedback loops</li></ol><h3>November focus</h3><p>Main focus for me over the last month has been trying to mobilise the four technology programmes within our Transformation portfolio. These build on the great work done over the last 12 months building the foundational Cloud and Data platforms.</p><p>Since then the portfolio has grown to 4 programmes covering:</p><ol><li>Technology (Cloud, Legacy, Sharepoint, Apply for funding)</li><li>Corporate (Foundational processes i.e. procurement, Document Mngt, Workforce planning and Risk Mngt)</li><li>Data Transformation (BI, MI, Governance, Data Platform, Strategy)</li><li>Rapid solutions (Low code. Operating within guardrails to deliver at pace)</li></ol><p>We’re all familiar with the snails pace and red tape getting approvals for large programmes can be. Oh and a high number of Powerpoint presentations!</p><p>Oh and I also took a week off. Which was great. ☀️</p><figure><img alt="Dubai" src="https://cdn-images-1.medium.com/max/1024/1*d2rTdeyVqX08TbaXsLfA6g@2x.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=204fbec9cfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote: 23 July 21]]></title>
            <link>https://rumman.medium.com/weeknote-23-july-21-d3ab3d858a08?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3ab3d858a08</guid>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[government]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Sun, 25 Jul 2021 02:08:52 GMT</pubDate>
            <atom:updated>2021-07-25T11:16:34.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*UTBYakCMXS1ZTbDI" /></figure><p>I jumped out of bed yesterday, forgot to eat anything and rushed to my first HIIT spinning class in 15 months. It was going ok but 30 mins in, just after the most intense part of the class, I wasn’t feeling great. I stopped and sat down…next thing I know, I’m surrounded by paramedics. So ye, an eventful Saturday! S/O to the staff at the gym and the ambulance/hospital folk ❤️</p><h4>Eid Mubarak 🧕🏽🕋</h4><p>On Tuesday I celebrated Eid Al-Adha. This was the first post-Covid restrictions and it was nice to have that feeling of a community again, as people gathered in the park for the special Eid prayers. Plus food. Lots of food!</p><h4>DM Training Paths</h4><p>I previously wrote about how we put a lot of thinking and energy behind how we can support the delivery community to become more familiar with Agile delivery, multi-disciplinary teams and new roles through coaching and training. Some of the initiatives we have done so far:</p><ol><li>Agile Coach (Drop-in sessions, 121s, mentoring teams and individuals)</li><li>Coaching syllabus (Multiple Lunch ’n’ Learns covering various delivery topics like Agile ways of working, GDS phases, UCD roles, Scrum etc)</li><li>Pluralsight (Curated playlists for delivery managers at each level)</li><li>Digital playbook (Documented body of knowledge covering ways of working, policies, processes)</li></ol><p><strong>Formal Training</strong></p><p>For more formal training, last year we signed people up to the <a href="https://www.gov.uk/guidance/digital-and-agile-foundation-course-description"><strong>Digital and agile foundation course</strong></a><strong> </strong>run by <a href="https://www.gov.uk/government/collections/gds-academy-course-descriptions">GDS Academy</a>. As people developed, we needed to establish a more structured formal training path. Last week we highlighted the courses below to support DMs from Associate level right through to Lead.</p><ol><li>Certified Scrum Master</li><li>ICAgile Project And Delivery Management</li><li>ICAgile Coaching</li><li>Lean Agile Leadership</li></ol><h4>Rapid Application Development (RAD)</h4><p>In my <a href="https://rumman.medium.com/weeknote-9-july-2021-d3b2e53eed20"><strong>last weeknote</strong></a>, I spoke about Shadow IT and how one symptom of it was in fact the very delivery processes that we have implemented i.e. A Portfolio/Digital Front Door and the Discovery/Alpha/Beta/Live. I’m absolutely a firm believer and advocate of these processes, but there is something about delivering at pace (or lack of) that is putting off our colleagues in the business — which leads to Shadow IT.</p><p>To overcome this, our SLT are looking at bringing in a sort of RAD team. I know they won’t mind me saying that I <strong>don’t </strong>think this alone will be enough, simply adding more people won’t solve this problem. Once their backlog is full…they’ll be another bottleneck. I also worry if stakeholders see this as a quick way of getting a solution, our service teams and formal delivery routes may not longer be appealing.</p><p>What we really need is to introduce an alternative way to quickly way up options, triage and test hypotheses before making any significant and expensive commitments. The answer is of course long-term cultural change but in this environment, we have to be flexible.</p><p>Maybe design sprints is the answer or something like deploying low code solutions in certain use cases? Maybe the answer is a hybrid model, with lean assurance and clear architectural guardrails support flexible delivery where needed.</p><h4>Next week</h4><ol><li>2 x Discovery KOs in Employee engagement and a new funding imitative</li><li>Meeting our new CDTO</li><li>Open source model for common components</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3ab3d858a08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote: 9 July 2021]]></title>
            <link>https://rumman.medium.com/weeknote-9-july-2021-d3b2e53eed20?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d3b2e53eed20</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[weeknotes]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Sat, 10 Jul 2021 01:21:08 GMT</pubDate>
            <atom:updated>2021-07-10T01:46:44.803Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YljPYCZYKu0R9BZu" /></figure><p>I took a much-needed break last week. I received one of those emails from HR asking everyone to check their holiday allowance and turns out I still had 90% of my annual leave remaining — So I promptly booked 3 days off.</p><h4><strong>Football</strong></h4><p>Let’s just get the football out of the way. Absolute pandemonium ensued when Harry Kane scored the other night, I couldn’t believe it, England were actually on their way to a major final.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*kzbvJ3ZNz70e-GfRaFqo-A.jpeg" /></figure><p>My earliest memories of international football were from World Cup ’98. I was so mesmerised by Ronaldo’s boots, I ran home from primary school, grabbed my piggy bank and rushed to this football shop in Bethnal Green — Sadly for me, my jar of copper coins only had enough to buy a pair of shin pads. Mind you, I still have them!</p><p>Since 1998 we’ve had some highly talented squads. Unfortunately, through a mixture of bad performances and misfortune, we have massively underachieved. This time it feels different, and not just on the pitch where players are finally replicating the form they show throughout the season; but also off it.</p><p>A special shout out to Gareth Southgate, who has been an inspirational leader — before the tournament he wrote a <a href="https://www.theplayerstribune.com/posts/dear-england-gareth-southgate-euros-soccer">powerful letter</a>, here’s a couple of nice quotes that demonstrate the qualities of his team as well as himself:</p><blockquote><em>It’s their duty to continue to interact with the public on matters such as equality, inclusivity and racial injustice, while using the power of their voices to help put debates on the table, raise awareness and educate.</em>​​​​​​​</blockquote><blockquote><em>It’s about how we conduct ourselves on and off the pitch, how we bring people together, how we inspire and unite, how we create memories that last beyond the 90 minutes. That last beyond the summer. That last forever.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0d_Jw6hMSMz4bTya" /></figure><h4><strong>Shadow IT</strong></h4><p>Our CDTO wrote a blog earlier this week, talking about the challenges of shadow IT — which is something that has become more prevalent over the last 18 months as digital tools became more accessible and more integral to our working practices.</p><p>How do we define shadow IT? Well IMO it’s usually one of these things:</p><ol><li>Online or downloadable software i.e. Something like Miro? <em>(Although, where would we be without it now?!)</em></li><li>OTS digital solutions i.e. Buying a new performance management system</li><li>Commission of services i.e. X department commissions a third party to build a website</li></ol><p>This is a difficult topic. There is usually a minefield of implications around security, data, architecture, support and legal. It’s not easy, there is certainly no one size fits all and each one of the 3 points above has its own challenges.</p><p>I think it’s important to find a middle ground on these sorts of things. Have clear policies on tools and digital procurement but also be flexible where possible so people can operate within safe guardrails. Introduce feedback loops and signpost clear routes to delivery so colleagues know who to talk to. Raise awareness of digital teams, so they are represented upstream across the organisation.</p><p>Every procurement gone wrong or third party software that’s now worryingly become business critical is a learning opportunity.</p><p>We need to work collaboratively with colleagues across the business to identify ways to use the existing skills and tools we have at our disposal, without the need to start projects or procure new systems.</p><p>We also need to introduce a way of running small experiments i.e. less than 2 sprints, not a 6–8 week disco/alpha, flexible procurement rules, with clear business benefits, which will satisfy architectural principles — So we can quickly test hypotheses and determine what the options are before making any significant commitments.</p><h4>Next week</h4><ol><li>A discovery on a new funding imitative and what we’re trying to learn</li><li>Supporting colleagues through periods of significant change</li><li>Meeting our new CDTO &amp; Transformation Director</li><li>Outcomes from a x-gov workshop on digital front doors (invites open)</li></ol><p>I think that is everything! Please have a lovely weekend and let’s all hope Monday is declared a bank holiday 😉</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d3b2e53eed20" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote: 25 June 21]]></title>
            <link>https://rumman.medium.com/weeknote-25-june-21-6d30e5b6cc19?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/6d30e5b6cc19</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Fri, 25 Jun 2021 15:01:56 GMT</pubDate>
            <atom:updated>2021-06-26T01:06:35.900Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8jbCe2g33sYgpL3s" /></figure><p>Recently, I have been able to put some of the ‘project’ things on hold and spent more time with some of my direct reports. With objectives high on the agenda this month, I used this time to discuss how they could stretch themselves over the coming year.</p><p>I’ve been proud to see how this group has developed over the last 12 months. A large number of them had different roles/titles a year ago, in that time they’ve all navigated a sea of change in our department, utilised learning and development opportunities and haven’t been afraid to go outside their comfort zone. Through this, they’ve gained so much confidence and self-belief, which has propelled them to another level. It goes to show how important capability building and investing in people is.</p><p>On another note, I was impressed yet again by the shadow leadership team — A group of junior colleagues, who work collaboratively with SLT. They ran an interactive session on the new comms charter, to understand what information people wanted to be updated on and how. I loved how they used the anonymous voting feature on Teams to gather this feedback.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ukJ6wEGt_WvHS1Fo-KgAgQ.png" /></figure><h4>Delivery Away Day</h4><p>On Tuesday, the delivery team came together for our virtual away day. On Tuesday, the delivery team came together for our virtual away day. Everyone from Delivery and Product Managers to Business Analysts and Developers (as well as others). Our team is based right around the country from London to Leeds and up in Newcastle. It was great to look back at last year and talk about what’s to come.</p><p>One area I think deserves special mention is the work Nikki has done on spend controls. We often talk about solving problems, meeting user needs, delivering value. And sometimes that’s enough to get people on board but sometimes you need a stick to drive prioritisation and decision making.</p><p>David Durant and James Hunt joined us from Hackney Council to talk about some of the great delivery they’ve done and the challenges they have overcome. I was particularly moved by how they overcame a debilitating cyber-attack and used it as a catalyst to sort of start afresh.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W5IZ3IwL0Xc_Z-rOYN9oIA.png" /></figure><h4>Privilege</h4><p>I’ve been thinking about this <a href="https://cate-mclaurin.medium.com/the-helpful-conceit-of-design-thinking-70c4556e1efd">great article by Cate Mclaurin</a>. Cate writes about design thinking and the privileges that are required to successfully challenge and be disruptive.</p><p>This form of privilege exists across Government departments. Sometimes there are degrees of empowerment, particularly when there is common acceptance that there is a need for change, but in my experience, you can apply this to all forms of disruption to established practices.</p><p>The privilege to speak the truth or challenge senior leaders. The privilege to try new things. The privilege to make mistakes without consequences. The privilege to go into unknown territory.</p><h4>Forms workshop</h4><p>Last week I joined a brilliant workshop ran by Cathy Dutton, bringing together folk from across government to talk about forms.</p><p>Even in my relatively short time here at Homes England, we’ve had multiple projects that have required PDF forms or surveys or applications of some kind.</p><p>We’ve been thinking about how we can create a repeatable component or pattern for this or at least make it easier to build forms that meet standards by using something like the <a href="https://moj-online.service.justice.gov.uk/">form builder by MoJ</a>.</p><p>There were some great questions posed by people. Two resonated with me:</p><ol><li>Do we need forms at all? <em>(Forms are a means to and end)</em></li><li>How does affordability impact the decision to invest in the time and people to build good forms?</li></ol><p>With my delivery hat on, I’ve been thinking about the second question in particular.</p><p>In central government, it’s probably easier to get investment for a full multi-disciplinary team to really look at the end-to-end journey, complete a discovery and build something that meets user needs. But is this applicable or even appropriate for everyone?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6d30e5b6cc19" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote: 18 June 21]]></title>
            <link>https://rumman.medium.com/weeknote-18-june-21-31160941981e?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/31160941981e</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Fri, 18 Jun 2021 06:32:15 GMT</pubDate>
            <atom:updated>2021-06-18T08:32:04.267Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3owypkSIpM8xw6p7W0%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fequipedefrance-allezlesbleues-frustre-3owypkSIpM8xw6p7W0&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExZTk1MDlhZTM0ZTU1N2E2OWVhMTcwOTRhMjViM2E3MTNkNmM4NzRkYiZlcD12MV9pbnRlcm5hbF9naWZzX2dpZklkJmN0PWc%2F3owypkSIpM8xw6p7W0%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/92414806b90a2626ad02db3414cf7202/href">https://medium.com/media/92414806b90a2626ad02db3414cf7202/href</a></iframe><p>It’s been one of those weeks where the weekend can’t come soon enough. I’ve been feeling quite frustrated, demotivated and somewhat absent-minded. I’ve been unable to focus in meetings and it’s taken me ages to complete tasks. I’ve been increasingly doubting myself in situations where previously I’d be confident and assured.</p><p>It could be due to challenges at work, where a lot is going on and I feel like I’m at a bit of a crossroads. We’ve achieved a lot as a team in a short space of time, so I guess there was bound to be a natural drop off and some turbulence.</p><p>It could also just be a result of working from home for 15 straight months. I’ve got into a bad habit of working when I should be switching off and then I jump straight back on my desk first thing in the morning, so my brain isn’t getting any downtime.</p><p>I don’t think it’s been fair on my colleagues so I apologise if I’ve seemed distracted or haven’t been as helpful as I usually am — or at least try to be!</p><p>I don’t know. I’m sure I will snap out of it on Monday. I’m seeing family and friends this weekend which will be a much needed distraction 🙂</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N3f-NAT19fpcz5yW3A86dQ.png" /><figcaption>Good time to remember this poster.</figcaption></figure><h4>T shaped people</h4><p>Once a fortnight, our heads of professions meet to discuss new portfolio requests, unpick dependencies, swarm on challenges and discuss how we can get better at one thing or another.</p><p>This week we discussed how we can support people in our teams be more “<a href="https://jchyip.medium.com/why-t-shaped-people-e8706198e437">T shaped</a>”.</p><p>In a multi-disciplinary team, each person brings their unique expertise to play specific roles. However, teams can sometimes encounter bottlenecks, particularly when work transitions from one person to another e.g. analysis to build.</p><p>There are opportunities for people to become a “generalised specialist” i.e. someone who can contribute to adjacent activities, as well as their primary role; through knowledge transfers, training and pairing. The idea is, self-organising teams with <a href="https://jchyip.medium.com/why-t-shaped-people-e8706198e437">T shaped people</a> can increase overall team capacity and help with personal development.</p><p>In our case, it wasn’t so straightforward. With limited Business Analysts, our Product Managers would usually be best placed to do some of the added wrangling and systems thinking — but due to long-term challenges like single points of failure, lack of docs and silos; developers (with their specialist knowledge of these heritage systems) were going above and beyond, when really they just want the space to focus on building things.</p><p>We’re taking a multi-pronged approach to tackle this <em>(recruitment, service teams, common components, cloud/data platforms, modernising legacy + training, pairing and docs)</em>, but it will take time. I’m just proud knowing we have brilliant people who really care!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BqyzQ4KPY-FbA5Ny" /><figcaption>The Cloud</figcaption></figure><h4>Sustainable delivery</h4><p>At the <a href="https://week.digileaders.com/">Digital Leaders</a> conference this week, I managed to catch a talk by Charlotte Walsh on <a href="https://week.digileaders.com/talks/heres-how-digital-transformation-will-create-a-more-sustainable-world-and-this-is-why-you-should-care/"><em>How digital transformation will create a more sustainable world</em></a>. It was a real eye opener for me.</p><p>Other than recent headlines about how much energy <a href="https://www.bbc.co.uk/news/technology-56012952">Bitcoin consumes,</a> tech isn’t usually what comes to mind when we talk about sustainability — certainly not compared to something like the Airline industry.</p><p>It’s certainly something I’ll be thinking about as we work on our Delivery Strategy.</p><h3>Rumman Amin on Twitter: &quot;Eye opening by @detoxLDN at @DigiLeaders. What can we do to raise awareness of carbon footprint of Internet &amp; digital services? Lot of invisible waste that isn&#39;t surfaced vs things like #CryptoHow are local/central gov depts prioritising sustainable procurement/delivery/design? pic.twitter.com/WWLX6Doadm / Twitter&quot;</h3><p>Eye opening by @detoxLDN at @DigiLeaders. What can we do to raise awareness of carbon footprint of Internet &amp; digital services? Lot of invisible waste that isn&#39;t surfaced vs things like #CryptoHow are local/central gov depts prioritising sustainable procurement/delivery/design? pic.twitter.com/WWLX6Doadm</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=31160941981e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote: 11 June 21]]></title>
            <link>https://rumman.medium.com/weeknote-11-june-21-beddc7214e69?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/beddc7214e69</guid>
            <category><![CDATA[government]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Fri, 11 Jun 2021 07:04:41 GMT</pubDate>
            <atom:updated>2021-06-11T07:23:15.272Z</atom:updated>
            <content:encoded><![CDATA[<p>Work is starting to pick up again this week following a relatively quiet <a href="https://rumman.medium.com/weeknote-4-june-21-713e4e9935f4">one last week.</a> My areas of focus were succession planning, team check-ins and more x-gov conversations with colleagues from DfE and Defra.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qSJlGz_qy0LKli3B" /></figure><h4>Highlights</h4><p>One important update I forgot to mention last week was that I got my first COVID vaccination! Massive shout out to the NHS staff at King George Hospital for running such a smooth operation 💙</p><blockquote>Please visit the <a href="https://www.nhs.uk/conditions/coronavirus-covid-19/coronavirus-vaccination/book-coronavirus-vaccination/">NHS website</a> if you haven’t already and book your jab.</blockquote><p>Another highlight was going on an actual date night in central London after an absolute eternity. The food was great and it felt nice to walk around Soho, Covent Garden and Bond St as they start to wind up again.</p><p>A shout out to Helen Pringle and Wayne Atkinson from Digital Support. I was having an absolute nightmare with my laptop and it was getting quite stressful. They were kind enough to send me a new one at short notice 🙏</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TwO8fx2k4PPQrcjknUa33g.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l82r2B9nEgb4Y8Gfj798ew.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*toERlWy_YQnhkFarQJOvjw.jpeg" /></figure><h4>Succession planning</h4><p>Over the last 12 months, we’ve been working hard to establish our foundational cloud and data platforms, and build key reusable components. We’ve built specialist multi-disciplinary teams with partners like <a href="https://www.bjss.com/">BJSS</a>, as well as through the contingent market to deliver these projects.</p><p>With these projects now progressing well, I’ve been working with the teams to start looking at life post-delivery. Some of the things we’re thinking about:</p><ol><li>Have we achieved our MVP?</li><li>What are future development ideas?</li><li>Do we have a clear and trusted onboarding process?</li><li>What support model are we adopting?</li><li>What is the Governance process?</li><li>What is the cost of ownership?</li></ol><h4>New colleague</h4><p>I met with Craig, our new interim Head of Software; to give him some insight into current challenges and opportunities in the developer community, before he joins us later this month. Amongst other things, we spoke about supporting people’s development, establishing DevOps and SRE principles, championing initiatives like coding in the open and empowering the community to play an active role in modernising our technology services.</p><h4>Team check-ins</h4><p>This week, I met with all our delivery and project teams to see how they were getting on. Recently, we’ve introduced <a href="https://engineering.atspotify.com/2014/09/16/squad-health-check-model/">Team Health Checks</a>, as a way to surface patterns across teams and help us focus on areas of concern.</p><p>One pattern that was starting to emerge across teams is around <em>autonomy —influencing what the team works on. </em>To support teams, we introduced a Heads of Professions forum, which positions us further upstream in conversations and manage complex dependencies.</p><p>One of the areas I&#39;m most proud about is our gradual transition from a centralised <em>product support team</em> to a <a href="https://rumman.medium.com/digital-transformation-in-government-d2521ecb36c2">service team model</a>. Rob and the team have been doing an <strong>incredible </strong>job to support our entire estate of systems, but this just wasn’t a sustainable way of working.</p><blockquote><a href="https://rumman.medium.com/digital-transformation-in-government-d2521ecb36c2">Service teams</a> promote local prioritisation and decision making. Shifting the focus away from one-off projects and isolated bug fixes, to a regular discussion between the team and stakeholders to define long-term goals that bring the most value to users.</blockquote><h4>Conversations</h4><p>On Monday I met with <a href="https://twitter.com/markdalgarno">Mark</a> from Defra and then later in the week, with <a href="https://twitter.com/KatiePether1">Katie</a> and Ben from DfE. It was great to hear about how they’ve approached the concept of a front door and portfolio process in their organisations; and how they’re working with stakeholders to embed these processes. Having gone through a <a href="https://rumman.medium.com/digital-transformation-in-government-d2521ecb36c2">similar journey</a>, I was really happy to share some insight and lessons that I’ve learnt.</p><p>One theme that has repeated itself again and again, is despite all the (justified) emphasis and excitement around Agile, Digital Transformation, User Centred Design, etc; at the heart of all this change is still about people. How do you communicate and influence people. <strong>How do you bring people on a journey?</strong></p><h4>Favourite meetings</h4><p>Since the start of lockdown, like everyone else, I’ve experienced stress and fatigue due to the overwhelming number of <a href="https://medium.com/enrique-dans/no-please-not-another-video-call-53145f9784bc">meetings</a>. However, there is one meeting that I look forward to every week…the Delivery Leadership team meeting.</p><h3>Rumman Amin on Twitter: &quot;Highlight of my week is our delivery team meeting. We give our fist of 5s, talk in a safe space, unfiltered and often get sidetracked with discussions about chocolate and music from bygone eras ❤️ Occasionally convos about work break out@MossMo55 @homesvictoria @ricyeboah + 3 pic.twitter.com/rShsbGAYJ2 / Twitter&quot;</h3><p>Highlight of my week is our delivery team meeting. We give our fist of 5s, talk in a safe space, unfiltered and often get sidetracked with discussions about chocolate and music from bygone eras ❤️ Occasionally convos about work break out@MossMo55 @homesvictoria @ricyeboah + 3 pic.twitter.com/rShsbGAYJ2</p><p>Hosted by our AD of Delivery, <a href="https://twitter.com/MossMo55">Sarah Slack</a>; we take turns sharing our <a href="https://agilefaq.wordpress.com/2007/10/21/what-is-fist-of-five/">fist of 5</a> ratings and talk about how things have gone over the week. It’s unfiltered and raw and a genuine safe space. We hone in on challenges as a team and wholeheartedly trust each other. It never fails to reaffirm the amazing support mechanism around me ❤️</p><h4>Next week</h4><p>I’ll be finalising my objectives for the year ahead. I usually struggle with these, partly because I find it difficult to focus on specific items as I’m usually working across many areas over the 12 month period.</p><p>I like the idea of having a golden thread between organisational &gt; departmental &gt; personal objectives. It contextualises the role you’re playing in moving the organisation forward. Let’s see how I get on!</p><h4>Watching</h4><p>It’s coming home 😉</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FYX5PgmoD4GbykVpD3M%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fgiphy.com%2Fgifs%2Fthreelions-world-cup-three-lions-YX5PgmoD4GbykVpD3M&amp;image=https%3A%2F%2Fmedia2.giphy.com%2Fmedia%2FYX5PgmoD4GbykVpD3M%2Fgiphy.gif%3Fcid%3D790b7611f1ba2b6a9bfa6f03ef8e287836f8fbbf701ae8a6%26rid%3Dgiphy.gif%26ct%3Dg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="271" frameborder="0" scrolling="no"><a href="https://medium.com/media/8cf85ae3b9667415959347c74e160057/href">https://medium.com/media/8cf85ae3b9667415959347c74e160057/href</a></iframe><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=beddc7214e69" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Weeknote: 4 June 21]]></title>
            <link>https://rumman.medium.com/weeknote-4-june-21-713e4e9935f4?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/713e4e9935f4</guid>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[government]]></category>
            <category><![CDATA[weeknotes]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Fri, 04 Jun 2021 09:05:34 GMT</pubDate>
            <atom:updated>2021-06-06T11:09:51.738Z</atom:updated>
            <content:encoded><![CDATA[<p>With school holidays this week, the <em>‘office’ </em>has been a lot quieter, meaning less time in meetings and more time to tick things off the to-do list like writing this week note!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kCywA90IojaWOQzM" /><figcaption>Nice weather in London</figcaption></figure><h4>Highlight</h4><p>With the Bank Holiday weekend, I was finally able to invite friends over after what feels like an eternity. Best of all, we got to finally meet one of these lockdown babies for the first time. We all unanimously agreed, he had a smashing hairline for someone who just turned 3 months old.</p><h4>X-Gov love</h4><p>I’ve received really warm feedback from the x-gov community on the digital transformation post I wrote a few weeks ago. It’s resonated with people who are going through a similar journey in their organisations. I’ve enjoyed sharing notes with colleagues like <a href="https://twitter.com/ian_vaughan">Ian</a>, <a href="https://twitter.com/liannemellor">Lianne</a> and <a href="https://twitter.com/HimalMandalia">Himal</a>. It’s helped me validate some of the thinking around what’s gone well, particularly around the areas of building teams; as well as the collective nodding on common challenges on getting stakeholders on board.</p><p><a href="https://rumman.medium.com/digital-transformation-in-government-d2521ecb36c2">Digital Transformation in Government</a></p><h4>Governance</h4><p>The topic that generated the biggest discussion was around governance and portfolio management. Coincidently, this is something myself, Reena and <a href="https://twitter.com/ricyeboah">Richard</a> have been working on this week. We’ve done some great work around the portfolio, setting up a clear front door, establishing the routes to delivery (service teams or portfolio). We’re working hard to increase the awareness of this across the organisation beyond our immediate stakeholders.</p><p>Talking of governance, I stumbled across a presentation from 2018 by <a href="https://twitter.com/tastapod">Dan North</a> on <a href="https://www.youtube.com/watch?v=wG-zBVl0A4g&amp;list=PLEx5khR4g7PIzxn476GK3Mkk19csZZjeH">Governing Agile Delivery</a>. So much of governance is seen as a blocker to delivery, but we also accept senior folk need this structure to make decisions and understand what value has been derived from investment. It’s important that we surface the right information and introduce the appropriate feedback mechanisms to help people make informed decisions.</p><h3>Rumman Amin on Twitter: &quot;Reading a bit about #Governance. @tastapod sums it up SO well:1. Flow of value &gt; utilisation of workers2. &#39;Busyness&#39; not an indicator of progress. Results are.3. Feedback is vital to reducing uncertainty4. Lead time is only game in townhttps://t.co/rKAqaRhzrA / Twitter&quot;</h3><p>Reading a bit about #Governance. @tastapod sums it up SO well:1. Flow of value &gt; utilisation of workers2. &#39;Busyness&#39; not an indicator of progress. Results are.3. Feedback is vital to reducing uncertainty4. Lead time is only game in townhttps://t.co/rKAqaRhzrA</p><h4>Recruitment</h4><p><a href="https://www.gov.uk/guidance/delivery-manager">Delivery Manager</a> — We previously started a discovery to understand how the MS Teams and Sharepoint structure works and how it can support functional document storage and records management.</p><p><a href="https://www.gov.uk/guidance/technical-writer">Tech Writer</a> — Another role I’ve started looking for is a technical writer. Documentation is so important for us, with the technology enabler projects we are working on, it’s crucial that we make the onboarding and usage of these as easy as possible.</p><h4><strong>Next week</strong></h4><p>I’m meeting with Digital SLT to continue discussions on <strong>legacy</strong>. It’s important that we start off by mapping our existing heritage estate. This will enable us to create a prioritised roadmap and inform our strategy to address the biggest challenges. At the heart of this will be our technology enabling capabilities around cloud hosting, data and common components.</p><h4>Reading</h4><p>I’m slowly making my way through this excellent book on managing legacy systems. Highly recommended!</p><p><a href="https://www.amazon.co.uk/Kill-Fire-Manage-Computer-Systems/dp/1718501188">Kill It With Fire: Managing Aging Computer Systems (And Future Proof Modern Ones)</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=713e4e9935f4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile Delivery in Government]]></title>
            <link>https://rumman.medium.com/digital-transformation-in-government-d2521ecb36c2?source=rss-85499a3dbf3c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2521ecb36c2</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[digital]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[digital-transformation]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Rumman Amin]]></dc:creator>
            <pubDate>Wed, 05 May 2021 08:00:35 GMT</pubDate>
            <atom:updated>2023-03-17T11:11:06.376Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>How to establish an agile, user-centred digital delivery function in Government organisations</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RjIxeeIpmHddNY54" /></figure><p>Delivery teams across government are working hard on exciting new projects as well as supporting existing systems and applications. In many organisations, alongside this core delivery activity, they have also been exploring transformative work to:</p><ol><li>Introduce <a href="https://www.gov.uk/service-manual/service-standard/point-6-have-a-multidisciplinary-team"><strong>multi-disciplinary teams</strong></a></li><li>Adopt <a href="https://www.agilealliance.org/agile101/12-principles-behind-the-agile-manifesto/"><strong>agile ways of working</strong></a><strong> </strong>and deliver to the <a href="https://www.gov.uk/service-manual/service-standard">GDS Service Standard</a></li><li>Establish a clear <strong>portfolio process</strong> to operate within sustainable <a href="https://www.atlassian.com/agile/kanban/wip-limits#:~:text=What%20are%20WIP%20limits%3F,inefficiency%20in%20a%20team&#39;s%20workflow.">WIP limits</a></li><li>Introduce <a href="https://xd.adobe.com/ideas/principles/human-computer-interaction/user-centered-design/"><strong>user-centred design</strong></a><strong> professions</strong> and principles</li><li>Support colleagues navigate change with <strong>clear guidance and training</strong></li><li>Improve communication and collaboration by<a href="https://medium.com/open-change/working-in-the-open-162d6d747081"><strong> working in the open</strong></a></li><li>Sign up to the digital and technology <a href="https://www.gov.uk/government/publications/cabinet-office-controls-version-5/cabinet-office-controls-policy-version-5"><strong>spend controls process</strong></a></li></ol><p>Delivering this will be a difficult endeavour given the significant cultural and technical change required, whilst maintaining capacity to deliver projects for your respective organisation.</p><h3>Problem statements</h3><p>To kick things off, it’s important to work as a community to understand what problems you are trying to solve. Some common examples:</p><ol><li>Communication and understanding of strategic priorities, leading to difficult portfolio planning and alignment of priorities.</li><li>There is insufficient representation from all professions during the triage stage when new project requests are received.</li><li>The perceived benefits of a project are not clearly surfaced at an early enough stage to support effective prioritisation.</li><li>When projects are approved there is an indeterminate period of time before it is started (Further projects are also approved in that time).</li><li>There is a lack of visibility of team capacity and availability to pick up new projects.</li><li>Operational team limits aren’t factored in when projects are being defined</li><li>Project (or phase) outcomes aren’t clearly defined and result in scope creep and delays.</li><li>Support work is prioritised in isolation of other problems in each business area which may potentially be of higher priority or bring greater benefits.</li></ol><p>Each problem statement represents a symptom of an organisation growing its capacity and capability to deliver digital services. To progress, we need some strategic initiatives around <strong>people, processes </strong>and<strong> culture</strong> to provide the structure and stability to be successful.</p><h3>People</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*XhgQdE-PIFN0B6v1" /></figure><h4>Multi-disciplinary Teams</h4><p>In many structures, you typically have project teams. These would generally be formed to solve a pre-determined output. You would identify people from a ‘pool’ to deliver a project, the team would deliver x over a limited period of time and then each person would move on to the next thing.</p><p>This isn’t a sustainable way of working for many reasons:</p><ul><li>It makes planning very difficult, as you scramble to find the right people to deliver a project</li><li>You cannot build mature teams as people constantly switch context from one temporary team to another</li><li>There is no ownership of output or long term support and development/tech debt</li><li>Very difficult to build relationships with users and stakeholders.</li></ul><p>Introducing service teams will promote local prioritisation and decision making; shifting the focus away from one-off projects and isolated bug fixes to a regular discussion between the team and stakeholders to define long-term goals that bring the most value to users. <a href="https://defradigital.blog.gov.uk/2018/10/29/funding-product-teams-not-projects/"><strong>Funding teams not projects</strong></a><strong>.</strong></p><p>This would be a team of digital specialists empowered to build and support services quickly and iteratively. Keeping the team together retains knowledge, improves ways of working, collaboration and supports better planning and prioritisation.</p><p>To give these service teams the best chance of success, embed all the people they would need to identify, understand, validate and solve whole problems. These multi-disciplinary teams would include delivery, product, technical and UCD roles.</p><p>Teams will also work closely with an empowered <a href="https://www.gov.uk/guidance/service-owner">Service Owner</a> who is accountable for the quality of the service. They have overall responsibility for developing, operating and continually improving a service.</p><p>This joint relationship between stakeholders and the team can work together to design, build and iterate a service based on the user needs and business priorities.</p><blockquote>Some organisations have also signed up for the <a href="http://techtalentcharter.co.uk/">Tech Talent Charter</a>. An amazing initiative which aims to increase diversity across the tech and digital workforce.</blockquote><h4>Training</h4><p>Put a lot of thinking and energy behind how you will support colleagues navigate through this change with clear communication, coaching, training and collaborating with them to establish best practice.</p><p>Seek the help of experienced Agile Coaches, to help prioritise learning paths, identify the correct audiences and the most appropriate medium to share the information - as well as deliver aspects of the training.</p><p>Introduce a series of open lunch and learn<em> </em>type training sessions to deliver a targeted syllabus of topics which will cover Agile ways of working, UCD principles and the GDS Service Standard. These sessions should be recorded and made available to the whole team.</p><p>Scheduled short lean coffee style drop-in sessions to troubleshoot any specific issues teams are facing. Have 121 sessions with colleagues to coach and mentor them through change.</p><p>To supplement internal training, you can create curated online training via Pluralsight for each profession and also encourage people to attend formal training. For example, GDS, Agile Project and Delivery Management (<a href="https://www.icagile.com/Agile-Delivery/Delivery-Management/Agile-Project-and-Delivery-Management">ICP-APM</a>; encourage people to become fully-fledged service assessors to take it a step further.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lLX-7ru2TO6ftIT0emnWkw.png" /></figure><p>Throughout this process, create an open space where the community can document the new processes, policies and ways of working. Eventually, you will be able to turn this documented body of knowledge in to a <a href="https://homesengland.github.io/playbook.html">Digital Playbook</a>. It will be useful to use as a reference point for your team, suppliers and the wider organisation and you should continue to iterate on it over time 👍</p><h3>Processes</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cI6ccfcw-4sLWqXU" /></figure><h4>Agile ways of working</h4><p>Embedding the <a href="https://agilemanifesto.org/principles.html">principles </a>and patterns of Agile go beyond the delivery team, but that is still a great place to start reaping the benefits of Agile and to bring consistency across teams.</p><p>Multidisciplinary teams can utilise established Agile frameworks, including Scrum, Kanban and Lean. They work in sprints, using common Agile artefacts and patterns to create an environment of self-organisation and collaboration. This includes:</p><ul><li>Daily stand-ups</li><li>Weekly backlog refinement</li><li>Monthly Show &amp; Tells</li><li>Retrospectives and Team Health Checks</li></ul><p>Alongside this, empower the delivery community to bring consistency and structure to planning tools:</p><ol><li>Open backlogs and sprint boards</li><li>Use of wiki and shared documentation</li><li>Establish access levels, security groups, board templates, requirements hierarchy structure</li><li>Utilise delivery metrics to help teams become more efficient, identify issues and support planning (Burndown, Velocity, Cycle time, Dwell time, throughput)</li></ol><p>Extend these practices to <strong>operational teams </strong>who can often be overlooked when new projects are being planned, but are essential to the delivery cycle.</p><h4>Portfolio</h4><p>The role of Digital in the organisation is to enable, empower and inspire people with great technology products and services.</p><p>In its most basic form, this translates to delivering products and services that solve the organisations most pressing problems. However, with a fixed headcount, the limited capacity will forces you to really think carefully about what problems projects are trying to solve and how it weighs up against other priorities.</p><p>Introduce a systemic, end to end view of projects with clearly defined routes to work <em>(continuous improvement or project)</em>. To ensure a sustainable pace, implement appropriate WIP limits at the portfolio level so teams in digital have enough notice to support and deliver a piece of work.</p><p>The summary of this was a system with the right checks and balances:</p><ol><li>Established a <strong>Single front door </strong>where stakeholders will work with a Business Relationship Manager to discuss all new digital projects.</li><li>Empower <strong>Product Managers</strong> to work collaboratively with stakeholders and service owners to understand user needs and define clear problem statements</li><li>Introduce <strong>Heads of professions </strong>upstream, to support and advise stakeholders, suppliers and teams, establish best practice and surface team capacity and wellbeing.</li><li>Use a <a href="https://www.scaledagileframework.com/portfolio-kanban/"><strong>Highly visual</strong></a> open, planning aid that helps everyone see the pipeline, progress of projects, blockers etc…</li><li>Surface <strong>Portfolio Metrics </strong>to help make informed decisions</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*HsPHPnO1sB8fT8HDEq_SxQ.png" /></figure><p>It’s important to get the balance right, too much governance and you can potentially become a blocker for the organisation, risking shadow IT spawning up. Not enough governance and you risk overwhelming teams.</p><p>This approach will help limit projects in progress, visualise the systemic workflow, improve collaboration between professions and help prioritise finishing over starting new where possible.</p><p>Surfacing key <strong>Portfolio Metrics </strong>help us make informed decisions:</p><ol><li>Lead time — Ave. time it takes for a new request from initial submission to being picked up by a team</li><li>Cycle time — Ave. time it takes for a team to finish once started</li><li>Aged WIP — How long a project has been in any particular stage of the process</li></ol><h3>Culture</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SGDtFbg27Pfx9rtV" /></figure><h4><strong>User-centred design</strong></h4><p>Organisations are increasingly working to the <a href="https://www.gov.uk/service-manual/service-standard">GDS Service Standard</a> and are complying with <a href="https://www.gov.uk/guidance/digital-and-technology-spend-controls-version-5">digital and technology spend controls</a>, which means that we have to take a user-centred approach for projects and meet the <a href="https://www.gov.uk/government/publications/technology-code-of-practice/technology-code-of-practice">Technology Code of Practice</a>.</p><p>This way of working is a significant culture change and you have to collaborate with colleagues across the business to introduce user-centred design professions and principles and demonstrate why it’s important to understand a perceived business or user need before committing to significant projects.</p><ol><li>A clear understanding of user and task requirements.</li><li>Incorporating user feedback to define requirements and design.</li><li>Early and active involvement of the user to evaluate the design of the product.</li><li>Integrating user-centred design with other development activities.</li><li>Iterative design process</li></ol><p>Recruit Product Management and UCD (User Research, Service Design, Interaction Design, Content Design) roles into the organisation. Encourage teams to work iteratively by starting with a Discovery to understand the problem that needed to be solved, followed by an Alpha to try experiments to solve the most important challenges before we commit and build the product or service in Beta and Live.</p><p>In an environment where there can be a perceived need to deliver at short notice, asking for early sight, the space to plan long term and the opportunity to work closely with users will be a challenging but important challenge.</p><h4>Working in the open</h4><p>Being more open and transparent is at the heart of transformative change. To deliver successful change, you have to bring people on a journey and this applied to every single item of change we are introducing. It’s also crucial that you continue to share and work in the open throughout any delivery activity.</p><p>Ask yourself, how can I get better at communicating what we are working on and share the progress teams are making to support and deliver services?</p><p>The first step for is to establish <a href="https://www.infoq.com/articles/communities-of-practice-agile-organisation/">communities of practice</a> (CoP) across professions. Multi-disciplinary teams by their nature include people from different professions so it’s important to give people an opportunity to grow with their peers. Communities are a great way to build a support network and share learning and expertise.</p><p>The second step is to run regular show &amp; tells and extend the invite to everyone. This creates an environment for the cross-pollination of ideas and is a great way for teams to showcase what they’ve been working on in recent sprints. It’s important to make the content accessible to the whole audience, but this can be challenging when discussing very technical concepts.</p><p>Finally, introduce weeknotes and encourage people to start writing blogs. <a href="https://weeknot.es/">Weeknotes </a>are a good way for the team to reflect in small updates. What’s going well, what challenges they’re facing, achievements and shout outs. This is also a good way of being open and transparent.</p><h3>What’s next</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OpH-AkoBH_hIrBst" /></figure><p>Gradually make these changes over a period of 12 to 18 months so as to not cause too much disruption. This will give you an opportunity to see how things go, get feedback from colleagues on what’s working well and what isn’t so much.</p><p>What does good look like? Well, if your purpose is to <em>‘enable, empower and inspire people with great technology products and services’</em>. You should strive to create an environment where you can support the organisation solve important challenges with digital solutions that meet users needs; whilst maintaining the wellbeing of colleagues to deliver them.</p><p>I’m aware I didn’t go into too much detail about each topic so If you have any questions or are going through your own transformation and would like to share notes, please reach out 😄</p><p><a href="https://twitter.com/rumantweets">@Rumantweets</a> ✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2521ecb36c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>