<?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 Mark Bradley on Medium]]></title>
        <description><![CDATA[Stories by Mark Bradley on Medium]]></description>
        <link>https://medium.com/@braddle?source=rss-a6cff8d2aece------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*5zFpiGuv2_WGqHo5uea4Gw.jpeg</url>
            <title>Stories by Mark Bradley on Medium</title>
            <link>https://medium.com/@braddle?source=rss-a6cff8d2aece------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 00:17:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@braddle/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[The Apprentice Team]]></title>
            <link>https://medium.com/@braddle/the-apprentice-team-cf55117bacba?source=rss-a6cff8d2aece------2</link>
            <guid isPermaLink="false">https://medium.com/p/cf55117bacba</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-career]]></category>
            <category><![CDATA[careers]]></category>
            <dc:creator><![CDATA[Mark Bradley]]></dc:creator>
            <pubDate>Thu, 09 Oct 2025 08:53:46 GMT</pubDate>
            <atom:updated>2025-10-09T09:05:03.816Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sS7z4nRQTsFSmN0RpiJeOQ.jpeg" /></figure><p>During my career, I have spent a lot of time working with early-career software engineers (university graduates, self-taught engineers, boot camp graduates and engineers on apprenticeship schemes). I have recently been thinking about how to onboard a new group of early-career software engineers into teams and organisations.</p><p>Many companies will hire a cohort of Early Career Software Engineers a few times a year and then spread the cohort amongst many teams in 1s or 2s around their businesses.</p><p>I have seen several teams that have found it very difficult to onboard and coach Early Career Software Engineers. This could be because of constant delivery pressure, not providing them with adequate time to work with Early Career Software Engineers or a lack of experienced coaches, or it could just be there is no one in the team interested in taking on teaching Early Career Software Engineers.</p><p>This is where the Apprentice Team comes in.</p><p>Instead of taking on a cohort of Early Career Software Engineers and splitting them amongst various teams you create a new team(s) (<a href="https://cloudnative.ly/everyone-is-missing-the-point-of-teams-8d6c473dd0c5">7 + or — 2 people</a>) made up of the entire cohort. Assigning each team an experienced engineer with teaching and coaching experience whose job it is to turn them into a fully functioning team. The coach should not be responsible for the team&#39;s line management.</p><p>At <a href="https://www.armakuni.com/">Armakuni</a> we believe that a team should use <a href="https://www.armakuni.com/the-ak-way">specific practices and ways of working</a> to become a high-functioning unit of delivery that can create the best experience for their customers.</p><p>Such as:</p><ul><li>Test Driven Development (TDD)</li><li>Continuous Integration / Continuous Deployment (CI/CD)</li><li>Pair / Ensemble Programming</li><li>Product Thinking</li></ul><p>The coach will tutor the team in all the skills they need to work on any feature the company requires. To achieve this, the apprenticeship team will go through several phases:</p><h3>Phase 1: Cohort On-boarding</h3><h4>Months 1–2</h4><p>The coach will support the team through the company&#39;s standard onboarding process and help them set up laptops. For most Early Career Software Engineers, this would be their first time working in the corporate world, so the onboarding may also need to cover things like:</p><ul><li>Meeting Etiquette</li><li>Business Tooling — Team, Slack, Email</li></ul><p>Once the onboarding is complete, the coach will start running some introductory training sessions covering topics like:</p><ul><li>Using Version Control in a Team</li><li>Agile</li><li>Product Thinking</li><li>DevOps Culture</li></ul><p>and introducing the team to the product they will be working on.</p><p>As very few businesses are going to want an Apprentice Team responsible for an entire product (If they do, then WooHoo! What an opportunity), the apprentice team should be aligned with an existing product team and pull work from them. The apprentice team and the existing team can share non-programming members of the team (Product Owner, Agile Coach and Designers) to support them in running agile ceremonies, understanding feature requirements and ensuring their work looks awesome and is user-friendly</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oCsq9EK5upZ9kkWYYl71OQ.jpeg" /><figcaption>The apprenticeship team share non-engineering team members with an existing product team</figcaption></figure><h3>Phase 2: Ensemble Programming (Months 3–6)</h3><p>Once Phase 1: Cohort On-boarding is complete the Apprentice Team will start the work that has been identified for them (this should be done with the coach, Product Owner, Agile Coach and team lead of the product team). As an <a href="https://softwareteaming.com/">Ensemble</a>, this work is likely to start with small bug fixes and simple UI or non-functional backend changes (e.g. Logging improvements or refactoring). As the group’s confidence grows they will pick up more complex bugs and small features.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bbOkuwLW-xauVTMGhXpMTg.jpeg" /><figcaption>The apprenticeship team takes work from an existing product team</figcaption></figure><p>During this phase, the Learning / Delivery ratio will be 60% / 40%.</p><h4>Learning Time</h4><p>Learning time will be focused on group learning with a mix of formal training provided by the coach or other experts from around the business.</p><ul><li>API interfaces</li><li>Software Architecture</li><li>Technical Debt &amp; Code Quality</li><li>Secure by Design</li><li>Containerisation &amp; Orchestration</li><li>Automated Testing<br> - Behaviour Driven Development (BDD)<br> - Test Driven Development (TDD)</li><li>Observability</li><li>Continuous Integration, Continuous Delivery &amp; Continuous Deployment</li></ul><p>The learning time would also include a simulated group project, allowing the group to get concrete practice of the training topics and exposure to all the technology they will be using on their production project.</p><h4>Learning Plans</h4><p>We will also introduce some individual learning into the plan that will allow each engineer to start learning around their individual interests.</p><p>I like to use the Learning Plan Miro Template we use at Armakuni. It encourages you to look at what you want to be, analyse your Strengths, ̶W̶e̶a̶k̶n̶e̶s̶s̶e̶s̶ Growth Edges, Opportunities and Threats, design a learning plan and develop a set of personal objectives and key results (OKR).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vUVxu8z6JoI-rZASJji7Xw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j17p232DZM9SbxNJT7ypBg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*--ruZhIQ6hNXEJvl7t6KnA.jpeg" /></figure><h4>Fortnightly Progress Check-ins</h4><p>The Coach will meet with the core Supporting Team for Progress Check-ins once a fortnight.</p><p>During these meetings, the coach will provide data on the progress of teams, their abilities and deliveries.</p><p>The coach will also provide data on the progress of individuals, identifying possible growth areas and working on plans with the group.</p><p>These meetings will provide time for the core team to pull levers on the Learning / Delivery ratio and move the group to 2 smaller ensembles.</p><h3>Phase 3 Ensemble Splits in Two (Months 6 -12)</h3><p>At the start of phase 3, the cohort will split into two smaller ensembles.</p><p>Each ensemble will take on its tickets from the shared backlog.</p><p>Each day the coach will split their time evenly between both teams. Allowing each team time to work without the Coach aswell. This will allow the apprentices to build confidence in their own skills and their teams ability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4sEa1lOS-0T-qHCvfsqtYQ.jpeg" /><figcaption>The apprenticeship team split into two ensembles, both supported by the Engineering Coach</figcaption></figure><h4>Learning / Delivery Ratio Shift</h4><p>Towards the end of phase 2 the skills within the team should be such that the amount of time learning can be reduced to a 50% / 50% ratio.</p><h3>Phase 4: Introduction of Pairing (Months 12–24)</h3><p>The Apprentice Team will start to introduce pairing into their repertoire. Enabling them to practise a different way of working and helping them to gain confidence in their ability outside of an ensemble programming session.</p><p>The pairs will receive support from the coach for around a quarter of the day at a time. This can be rebalanced if a particular pair get stuck on their work.</p><p>During phase 4 the team should be taking more responsibility for areas of the product, working with Product owners and Agile Coaches to prioritise, plan and deliver their own work. This shift should enable them to start gaining a greater understanding of product engineering and their role in delivering value to the customer.</p><h4>Learning Time</h4><p>Towards the end of phase 4, the skills within the team should be such that the amount of time spent learning can be reduced to a 20% / 80% ratio. This learning shift should map with the learning time for all engineers in the company.</p><p>The coach will continue to run structured learning sessions for the team but these will be shorter than some of the earlier sessions. They would start using <a href="https://sammancoaching.org/">Samman Coaching</a> at this stage.</p><p>The coach will also start to focus on individual learning so each engineer can deepen their knowledge relating to their individual specialisms, helping them to identify what they would like to focus on and creating their own learning path.</p><h3>Phase 5: Graduation &amp; Continuous Improvement</h3><p>At this point, the Early Career Software Engineers would no longer be apprentices but fully fledged engineers capable of working in any strong, long-lived team, capable of taking on any work.</p><p>The Coach will work with each engineer to update individual learning plans, helping the engineers to discover their unknown unknowns and expanding their knowledge in their specialism.</p><p>At this time the existing product team and the apprenticeship team should merge and split into two mixed product teams. Creating two product teams made up of engineers with differing levels of experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vyPMBQysI4tCjw1gCe1-8g.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cf55117bacba" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Avoiding Boring Training with Training from the Back of the Room]]></title>
            <link>https://medium.com/@braddle/avoiding-boring-training-with-training-from-the-back-of-the-room-a28382d46280?source=rss-a6cff8d2aece------2</link>
            <guid isPermaLink="false">https://medium.com/p/a28382d46280</guid>
            <category><![CDATA[training-courses]]></category>
            <category><![CDATA[workshop]]></category>
            <category><![CDATA[training]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[learning]]></category>
            <dc:creator><![CDATA[Mark Bradley]]></dc:creator>
            <pubDate>Wed, 26 Jul 2023 08:06:43 GMT</pubDate>
            <atom:updated>2023-07-26T08:06:43.186Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*54Inuamkg8QCkvI2WM5xbg.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@byfortytwo">FORTYTWO</a> on <a href="https://unsplash.com/">Unsplash</a></figcaption></figure><p>Recently a colleague and I ran a 2 day workshop teaching Test Driven Development (TDD) for Frontend React Engineers for one of our customers. The training went really well, all the attendees were really engaged throughout and gave some great feedback (although we should have provided some sweets). However on the second day there was a section that felt a bit flat and the energy in the room dipped. We took time to reflect on that point and realised it was the section that was the least “Back of the Room”, with long periods of lecturing and very little opportunity for involvement of the learners.</p><p>Over the last year I have been trying to improve the learning content I create using the techniques from <a href="https://www.amazon.co.uk/Training-Back-Room-Aside-Learn/dp/0787996629">Training from the Back of the Room</a> and this moment really solidified for me that using this technique improved the way I create and run training.</p><h3>What is Training from the Back of the Room?</h3><p>Training from the Back of the Room (TBR) is an approach to designing learning experiences for adults developed by <a href="https://www.bowperson.com/">Sharon L. Bowman</a> that uses the latest Neuroscience to design training materials/sessions that are brain friendly. The model helps to quickly design the most engaging learning materials/sessions that really help learning to stick.</p><figure><img alt="An image of the from cover of the book Training From the Back of The Room: 65 ways to step aside and let them learn by Sharon L. Bowman" src="https://cdn-images-1.medium.com/max/250/1*-sMIyaH7_XBFelgX4wwTdg.jpeg" /><figcaption>Sharon L. Bowman’s book Training from the Back of the Room</figcaption></figure><p>The essence of TBR is for the trainer to step back and move themselves out of the way of the learners learning by creating experiences that invite the audience to fully engage with learning rather than just being lectured at.</p><p>Two of the core models that TBR recommends using are The 4 C’s and the 6 Trumps</p><h3>The 4 C’s</h3><h4>Connections</h4><p>This is a short activity that enables the learners to make connections to</p><ul><li>What they already know or think they know about the topic — This brings any existing knowledge into working memory ready to attach new learning to</li><li>What they want to learn during the session</li><li>Other people on the training — This enables you to create a place of psychological safety to ensure learners feel comfortable joining in with a highly interactive learning experience</li></ul><h4>Concepts</h4><p>This is where the learners are introduced to new learning about the subject being taught. This should be interactive and collaborative, it should not be a long lecture by the trainer as that does not help anyone learn.</p><h4>Concrete Practise</h4><p>Putting the new learning into practise</p><h4>Conclusion</h4><p>A moment to reflect on what has been learned.</p><h3>The 6 Trumps</h3><h4>Movement trumps sitting</h4><p>Moving around gets you heart beating and pumping more blood to your brain aiding learning.</p><h4>Talking trumps listening</h4><p>Learners take more in when they say things out loud than listening to someone lecture.</p><h4>Images trump words</h4><p>We are more likely to remember a diagram or image than a large chunk of text.</p><h4>Writing trumps reading</h4><p>The act of writing down facts, the movement of your hand writing the words is more effective at helping you remember them than just reading them.</p><h4>Shorter trumps longer</h4><p>We only concentrate on something for about 10 minutes, any longer and we stop retaining the learning.</p><h4>Different trumps same</h4><p>Things that are different excite our brains making them more likely to be remembered than a lot of things that are the same.</p><h3>My Approach</h3><h4>Planning</h4><p>When I’m designing a new learning experience I’ll start in <a href="https://miro.com/">Miro</a> breaking down the subject to be covered into subtopics, thinking about what concepts should be covered. For a 1 hour session I would only cover a single topic but for longer sessions I’ll cover a number of different subtopics.</p><p>The mind map we created when designing the React TDD training looked like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/829/1*0BfKr2AAJxu9zkansMyh6w.png" /><figcaption>TDD Training Mind Map</figcaption></figure><p>We started by putting in all the concepts we could cover. We then marked the topics that we thought we would not cover during this training session. Mapping out the concepts like this gave us clear idea of the sections we wanted to cover and a little detail about what we should be including in them.</p><p>Once we had the core subtopics we created a grid of Post-Its. Across the top we had a Post-It for each of the 4 C’s. Then down the column on the left side we have each of the subtopics. Each of the C’s and Subtopics should have at least one corresponding Post-It that is an idea for the activity that will be completed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FFyHyYdPjfi-25ARV5rcwA.png" /><figcaption>High Level Plan for TDD Training</figcaption></figure><p>For the React TDD training we broke down the training into 5 subtopics</p><ul><li>What is TDD?</li><li>Arrange -&gt; Act -&gt; Assert</li><li>Refactoring</li><li>Testing React Components</li><li>Test Doubles</li></ul><p>This is how we cover each of the 4C’s for the first subtopic What is TDD?</p><h4>Connections</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*o0dT-H_JLnNHsimXwMUQOw.png" /></figure><p>This is first connection activity of the workshop, designed to get the attendees to introduce themself to each other.</p><p>The discussions then moved on to be about either their testing experience or what they though TDD was. They were also encouraged to start thinking about the topics that would be covered during the training and what they might get out of it.</p><p>The groups were split by those with testing experience and those without. This allowed us to plan the groups for the later activities to ensure each group had a good mix of experience. Doing this means that those inexperienced in testing would learn from those experienced in testing during group work. This also benefit the experienced learners because teaching something is the best way to learn it.</p><h4>Concepts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FQSdfw-xvrCD1I9njNfrZw.png" /></figure><p>For the first section of new learning (concepts) we split the group into three teams. We then gave the groups the task to research and discuss the question “what is TDD?”, we also gave each of the groups one of the three sections of the TDD Cycle (Red, Green &amp; Refactor) to research what happened during that section of the cycle.</p><p>Once the groups had finished we came together and had a 5 minute discussion about what each group had understood about “what is TDD?”, at this point we were able to correct any misunderstandings. It was also a time for the us to elaborate on any important points or add any key facts the learners may have missed.</p><p>We then went around each of the groups and got them to explain the section of the TDD cycle they were given to research. The members of the other groups were encouraged to take notes on what the other groups were teaching them.</p><h4>Concrete Practise</h4><p>We used a number of different Code Katas to give the attendees concrete practise in the various concepts we covered. For the first kata (<a href="https://github.com/armakuni/tdd-react-training/blob/main/docs/day1-exercise1-tdd-fizzbuzz.md">FizzBuzz</a>) we ran a <a href="https://www.agilealliance.org/glossary/mob-programming/">Mob Programming</a> (Mobbing) session, this allowed us to demonstrate the concepts while getting everyone involved in creating the solution.</p><p>The attendees then formed pairs to work on another similar Code Kata (<a href="https://github.com/armakuni/tdd-react-training/blob/main/projects/day1-tdd-exercise/src/leap-year.test.ts">Leap Year Calculator</a>). We used <a href="https://www.agilealliance.org/glossary/pairing">pair programming</a> so the learners continued to discuss the theory we had covered during the concepts section, learning from each other. Pairing also helps keep the pairs honest with strict TDD practises.</p><p>Other Code Katas completed during the training included:</p><ul><li><a href="https://github.com/armakuni/tdd-react-training/blob/main/docs/day1-stretch-exercise-tdd-bank-account.md">Bank Account Statement Kata</a></li><li><a href="https://github.com/armakuni/tdd-react-training/blob/main/projects/day1-react-tdd-exercise/src/Spoiler.test.tsx">Spoiler Component Kata</a> (Mobbing)</li><li><a href="https://github.com/armakuni/tdd-react-training/blob/main/docs/day1-exercise2-tdd-react.md">React Accordion Kata</a></li><li><a href="https://github.com/armakuni/tdd-react-training/blob/main/projects/day2-tire-pressure-exercise/README.md">Tyre Pressure Kata</a></li><li><a href="https://github.com/armakuni/tdd-react-training/blob/main/docs/day2-exercise3-tdd-api-client.md">Pokemon/Star Wars API Client Kata</a></li></ul><h4>Conclusion</h4><figure><img alt="A slide from the training presentation used duing the Conclutions section of the training. The slide reads: How did you find it? Split into small groups and discuss how you found your first attempt at TDD and Paring. Was it easier/harder than you thought it would be? Did you enjoy the process? Do you have any questions? write notes of your discussions on Post-Its." src="https://cdn-images-1.medium.com/max/1024/1*ZiuOcyqb6iv4gJx2KEG1Iw.png" /></figure><p>Once the attendees had finished the concrete practise we got them to form small groups, we encouraged the learners to join different groups from their pairing partner to get new perspectives.</p><p>The groups discussed how they found the practise and what they enjoyed about the process. They also asked each other any questions they had, this continued to encourage them to teach and learn from each other.</p><p>We then finished with a short discussion and each group repeated any questions they had and how it was answered. We would ask the whole group if they had anything to add to the answers before we would add any points we thought were missing.</p><p>I have now been using the Training from the Back of the Room concept on a number of different workshops and the energy and engagement in the learning is so much better.</p><p>These techniques work for in person and remote training. I have now used it a few times for both. Applying these techniques to remote training is a bit tricky but with white-boarding tools like Miro it is much easier to create training that encourages learners to engage and interact.</p><p>As a teacher I find running training so much more exciting, hearing the discussion and enthusiasm of the attendees make the experience so much more enjoyable.</p><p>I still have a lot to learn and practise with Training from the Back of the Room that should make learning even better. I’m currently planning to add <a href="https://www.bowperson.com/wp-content/uploads/2014/11/NiftyNotes.pdf">Concept Maps</a> (or Graphic Organisers) to training as a way to encourage learners to take notes.</p><p>If you are running any form of training for adults I would highly recommend you give TBR a try.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a28382d46280" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>