diff --git a/.gitattributes b/.gitattributes index 6c34d48dc7586909edb6c11cf5c0aeed14cd0fc9..3847795f8a33159cb7f0f6216d4dd582dcff73ef 100644 --- a/.gitattributes +++ b/.gitattributes @@ -34,3 +34,12 @@ saved_model/**/* filter=lfs diff=lfs merge=lfs -text *.zst filter=lfs diff=lfs merge=lfs -text *tfevents* filter=lfs diff=lfs merge=lfs -text data/insurance.pdf filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-about-yourself.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-congratulations.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-create-account.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-get-started.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-security-code.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-sign-in.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/aws-partner-network-why.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/azure-partner-portal-page.png filter=lfs diff=lfs merge=lfs -text +handbook/handbook-main/guides/cloud/images/sign-in.png filter=lfs diff=lfs merge=lfs -text diff --git a/handbook/handbook-main/README.txt b/handbook/handbook-main/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..7663701e4db5ba77baae6b70d27a91f0fd4a1cc3 --- /dev/null +++ b/handbook/handbook-main/README.txt @@ -0,0 +1,117 @@ +# Made Tech Handbook + +At Made Tech we want to positively impact the future of the country by using technology to improve society. We work with public sector organisations to modernise technology and accelerate digital delivery so that citizens can benefit from better public services. + +We're building an open and transparent company across the UK, full of people who are passionate about their work, always strive to be better, love to help others grow, and care about using digital and technology to create a better, fairer society. + +This Handbook should be the starting point for any new team members. It provides an overview of [why we exist](company/about.md), our roles, our investment into staff welfare, our team norms, and details of our processes, policies and benefits. + +## Contributing to our Handbook + +We're a company that moves fast, so we're going to need everyone to help us keep this up to date. If you encounter something that you think should be in this Handbook or spot a typo, please feel free to [open a pull request](https://github.com/madetech/handbook/pulls). If you have a question feel free to [open an issue](https://github.com/madetech/handbook/issues). This applies whether you're a Made Tech employee or not. + +For more information on contributing, including how to as a non-technical user, read our [CONTRIBUTING.md](guides/contributing_to_the_handbook.md). + +## Table of contents + +### Introduction to Made Tech + +* [About Made Tech](company/about.md) – Why we do what we do +* [Welcome Pack](company/welcome_pack.md) – All you need to know when joining Made Tech + +### Roles + +* [About Roles](roles/README.md) – Overview of our roles +* [All Roles](roles/) – Directory of roles + +### Benefits & Perks + +Balancing life and work: + +* ✈️ [Taking Holiday](benefits/taking_holiday.md) – We offer 30 days’ paid annual leave +* 🕰️ [Flexible Working Hours](benefits/working_hours.md) – We are flexible with what hours you work +* 🗓️ [Flexible Working Days](benefits/flexible_working.md) – We are flexible to the amount of days you work in a week +* 👶 [Flexible Parental Leave](guides/welfare/parental_leave.md) – We provide flexible parental leave options +* 👩‍💻 [Hybrid Working](benefits/hybrid_working.md)– We offer hybrid working for all of our staff +* 🤗 [Paid counselling](guides/welfare/paid_counselling.md) – We offer paid counselling as well as financial and legal advice + +Some little extras at work: + +* 💻 [Work Ready](benefits/work_ready.md) – On top of your Macbook, we provide a budget for other equipment you might need to get set up for work +* 💡 [Learning](guides/learning/README.md) – We provide a learning budget to help develop your skills +* 🍽️ [Lunchers](benefits/lunchers.md) – Come into the office, book your desk & be in with a chance of having lunch on us! +* 🏓 [Getting Together](benefits/getting_together.md) – We hold regular social events so you can get to know your teammates better + +Fair compensation and benefits: + +* 💷 [Transparent Salary Bands](roles/README.md) – We publish salary bands so you know you're being fairly compensated +* 👌 [Annual Salary Reviews](guides/compensation/salary_reviews.md) – We review your salary once a year +* ⛷️ [Pension Scheme](benefits/pension_scheme.md) – We provide a pension scheme which we contribute to, to help you plan for your future +* 🚄 [Season Ticket Loan](benefits/season_ticket_loan.md) – We provide loans to help you pay for your travel +* 🚲 [Cycle To Work Scheme](benefits/cycle_to_work_scheme.md) – We offer the cycle to work scheme to help pay for your bicycle +* 🚕 [Expenses Paid](guides/compensation/expenses.md) – We’re happy to cover a range of work-related expenses in line with our expenses policy +* 💻 [Help To Buy Tech](benefits/help_to_buy_tech.md) – Shop the latest gadgets,technology and now Ikea! +* 🏦 [Income Protection & Life Assurance](benefits/income_protection_and_life_insurance.md) - Financial support provision when you or your family might need it most + +### Welfare + +* [Sick Leave](guides/welfare/sick_leave.md) +* [State of Mind](guides/welfare/state_of_mind.md) +* [Employee Assistance](guides/welfare/paid_counselling.md#employee-assistance) +* [Expectations between Employees and the Organisation](guides/welfare/expectations.md) +* [Raising an Issue](guides/welfare/raising_an_issue.md) +* [Parental Leave](guides/welfare/parental_leave.md) +* [DSE and H&S training](guides/welfare/dse_hs_training.md) +* [Ethical Boundaries](guides/welfare/ethical_boundaries.md) + +### Guides & Resources + +#### Team + +* [Team Norms](team-norms) +* [Learning](guides/learning) +* [Mentorship](guides/mentorship) +* [Marketing Assets](https://github.com/madetech/marketing-assets) +* [Line Management](guides/line-management) + +#### People + +* [Equality, Diversity & Inclusion](guides/equality-diversity-and-inclusion/README.md) +* [Salary & Pay Slips](guides/compensation/salary_pay_slips.md) +* [Salary Reviews](guides/compensation/salary_reviews.md) +* [Expenses](guides/compensation/expenses.md) +* [Exit Interviews](guides/exit_interviews.md) + +#### Office + +* [Office Handbook & Access Information](guides/office/officehandbook.md) +* [Kitchen Etiquette](guides/office/kitchen.md) +* [Dress Code](guides/office/dress_code.md) + +#### IT + +* [Software & Licences](guides/it/software_licenses.md) +* [Hardware](https://github.com/madetech/handbook/blob/main/guides/it/Hardware.md) +* [Information Security](guides/it/laptop_security.md) + +#### Security + +* [Acceptable Usage Policy](guides/security/acceptable_use_policy.md) +* [BYOD Policy](guides/security/bring_your_own_device.md) +* [Device Profiles](guides/security/device_profiles.md) +* [What To Do If Your Device Is Lost Or Stolen](guides/security/lost_or_stolen.md) +* [Office Visitors](guides/security/office_visitors.md) +* [Last Day](guides/security/last_day.md) +* [Password Policy](guides/security/password_policy.md) + +#### Policies + +* [Anti-Corruption and Bribery Policy](guides/policy/anti_corruption_and_bribery_policy.md) +* [Whistleblowing Policy](guides/policy/whistleblowing_policy.md) +* [Anti-Slavery and Human Trafficking Policy](guides/policy/anti_slavery_and_human_trafficking_policy.md) +* [Dealing Code Policy](guides/policy/dealing_code_policy.md) +### Communities of Practice + +#### ☁️ Cloud and Engineering + +* 📚 [Book Club](communities-of-practice/cloud-and-engineering/book-club/welcome.md) - Check out what we're reading / have read! diff --git a/handbook/handbook-main/benefits/Unum_Help_at_hand.txt b/handbook/handbook-main/benefits/Unum_Help_at_hand.txt new file mode 100644 index 0000000000000000000000000000000000000000..0c349cb032207cd582ec903faefddc85e758e687 --- /dev/null +++ b/handbook/handbook-main/benefits/Unum_Help_at_hand.txt @@ -0,0 +1,13 @@ +# Unum Help@hand + +This benefit is available for all team members, providing you with fast, direct access to medical experts through one easy to use app. +The service provides the following: + +- Access to remote GPs: An unlimited number of video consultations with UK based doctors. +- Mental Health support: Access to therapists (typically delivered by video consultation). +- Physiotherapy: Consultation and treatment with a network of physiotherapists. +- Medical second opinions: Access to UK based private consultants. +- Life, money, and wellbeing support: Advice on a range of life and work issues (see our [employee assistance section.](https://github.com/madetech/handbook/blob/main/guides/welfare/paid_counselling.md#employee-assistance)) +- Access to a wellbeing calendar: Packed with resources, awareness dates, and support tools. + +To get started, download the app and log in using the details found in your invitation email. diff --git a/handbook/handbook-main/benefits/cycle_to_work_scheme.txt b/handbook/handbook-main/benefits/cycle_to_work_scheme.txt new file mode 100644 index 0000000000000000000000000000000000000000..1c59bab94f57fd9c709a9022b018d703436a8f20 --- /dev/null +++ b/handbook/handbook-main/benefits/cycle_to_work_scheme.txt @@ -0,0 +1,96 @@ +# Cycle To Work + +We take part in Cycle to Work as we wish to support those who wish to cycle to work whether it's for pleasure, aiming to be healthier, trying to be more green or any other reasons. +Made Tech have a limit of £2500 with CycleScheme which can be used to purchase a bike and any accessories you will need. You then pay a monthly 'salary sacrifice' to effectively 'hire' the bike and kit, over a 12 month period. Once this period has been completed you will be given options around owning your bike. The [FAQs section](https://help.cyclescheme.co.uk/article/42-what-is-an-ownership-fee) of their website has lots of information regarding these options.If you leave Made Tech before paying off the purchase, the balance will be taken from your final salary payment. + + +## Process for getting a bike through Cycle to Work: + +### How do I use CycleScheme? + +Start your application quickly and easily through the CycleScheme portal which you can access via Bob benefits. All you will need is the Employer Code which can be found in the information section of the Bob benefits CycleScheme tile. Once you have entered the Employee code go through the application process using your Payroll number (labelled Employee ID on your bob profile, or can be found on your payslip.) + +Once you have completed the application it will be sent to a member of the people team to approve your request. Once approved you will receive your eCertificate which can then be exchanged for your gear in store or online! + +If you request your product before the 18th of the month your deductions will begin the same month, however if you request your voucher on or after the 18th your deductions will begin the following month. + +### Who are CycleScheme? + +CycleScheme is a great employee benefit which offers the most cost-effective way to get new cycling equipment. The scheme is run via a salary sacrifice meaning you won’t pay tax or national insurance – this saves you between 25% and 39% on your new bike and accessories. This reduced cost is simply deducted out of your payslip over 12 months, so no need to worry about large one-off costs! + +### Is CycleScheme the only provider I can utilise this scheme through? + +Yes, as of 5th December 2022. + +### What is the maximum value I can apply for? +The maximum value you can apply for is £2500. + +### How do I know how much to apply for? + +We recommend finding your perfect bike and accessories before applying so you know exactly what amount to apply for. This way you won’t apply for too much or too little – this is really important to get right because you cannot amend your application once you have been approved. You can also use the [Savings Calculator](https://www.cyclescheme.co.uk/calculator) to find out how much you will be saving on your package. + +### How often can I use the Cycle to Work scheme? + +You can only be in one agreement at a time, the next time you will be able to make an application will be once you've repaid your instalments. So if you are going to be paying back over a year, it would be best to think about your cycling needs over the whole year, not just right now. + +### Can I use Cycle to Work to get a bike for a family member, partner or friend? + +No, the items you select must be for yourself. + +### I already own a bike – can I still apply? + +Of course! You may want to get a whole new upgrade, or a second bicycle for a different season or terrain. Just want accessories? Using the Cycle to Work scheme for accessories only is a very popular option for employees who already own a bicycle and just want to upgrade the rest of their equipment! + +### Where can I get my bike and accessories from? + +You can shop in-store or online, with over 2,600 CycleScheme retailers to choose from across the UK. + +### Do I have to get a bike? Can I just get accessories? + +Yes! You are more than welcome to just get cycle accessories. Treat yourself to a new helmet, clothing for every season, locks, lights and much more! + + +### What is an eCertificate? + +An eCertiificate is the voucher you will be given once your application is approved. This is how you can purchase your bike or any equipment or accessories. + +### Do I have to spend my eCertificate all at once? + +Although you do not have to use your eCertificate all at once, we would advise that you do as your salary sacrifice amount will be according to the total amount you applied for, even if you spend less. + +### Can I amend my application once I've applied? + +Technically once you have submitted your application, you are unable to amend it. What you would need to do is cancel your application and reapply for your new amount. + +### Do I have to cycle to work every day? +No, the government guidelines state that you should use your bike and accessories for commuting for at least 50% of its usage however you do not have to log your bikes mileage and we thoroughly encourage you to use your bike in your spare time. + +### What happens if my bike gets damaged or stolen? + +This one’s down to you! Looking after the bike is your responsibility, so we encourage you to purchase insurance. CycleScheme offers insurance options with Bikmo through their website. + +### What happens to the bike at the end of the scheme? + +Once your hire period has come to an end, CycleScheme team will get in touch to discuss your options (Own it later, Own it now and Return.) The [FAQs section](https://help.cyclescheme.co.uk/article/42-what-is-an-ownership-fee) of their website has lots of information regarding these options. + +### Who owns the bike? + +CycleScheme are the legal owners of the bike from the start of the hire period, the bike is leased to you. Once you reach the end of your initial 12 month hire period, ownership of the bike will then automatically be transferred to you depending on which ownership option you choose at the end of your initial agreement. Should you not wish to purchase the equipment you can continue to loan it until it is 4 years old at which point the bike automatically becomes yours (unless you wish to return it.) + + +### What are 'hire periods' and 'hire agreements'? + +Your hire agreement is essentially the ‘terms and conditions’ of CycleScheme, which you will sign when you apply. Your hire period is the period that this agreement is valid for - this is also the period in which you will pay your salary sacrifice (12 months.) + +### What if I leave my company within my Hire Agreement? + +We completely understand that life can be unpredictable. If you were to leave your company or be made redundant in your hire period, the remaining gross balance would simply be deducted from your last payslip. + +### How does Cycle to Work differ to Interest Free Finance that some retailers offer? + +Through CycleScheme, you will save between 25% and 39% through tax and national insurance and the cost will simply be deducted from your payslip. You’ll also get loads of free extras, discounts and benefits on the CycleScheme website which you would not get on Interest Free Finance! For example, a bike costing £1000 could cost as little as £56.60 a month over 12 months on CycleScheme - compared to £83.33 through Interest Free Finance. + +### Once I put in my application via the CycleScheme website how long will it take to process my application? + +We will review any new requests every Friday afternoon so you shouldnt be waiting for more than one week for approval from Made Tech. + diff --git a/handbook/handbook-main/benefits/flexible_working.txt b/handbook/handbook-main/benefits/flexible_working.txt new file mode 100644 index 0000000000000000000000000000000000000000..f891aa5f15a3e8bfd6d4bdfc50c8493b6e5aeb82 --- /dev/null +++ b/handbook/handbook-main/benefits/flexible_working.txt @@ -0,0 +1,18 @@ +# Flexible Working + +Generally, we work Monday to Friday in all roles. But for a variety of reasons, people may need to work fewer than 5 days per week. +We try to accommodate for this when we can. But because of client considerations, and to manage any other business impact, we have a process for requesting a flexible working pattern. + +## Some things to consider + +**Notice** - Please provide as much notice as you can - ideally 2 months or more - for a request to change your working patterns. It helps us make sure our client commitments can continue to be met. + +**Project and scheduling needs** - As project and scheduling needs change, we'll do our best to accommodate flexible working patterns. But there may be very occasional times when we need to discuss temporary or permanent changes to a flexible working schedule. We'll try to give you as much notice as we can of any possible change. + +**Getting paid** - Your salary and any bonus payments will be pro-rated as a percentage of a 5 day week. For example, if you work 4 out of 5 days, your salary and any bonus would be reduced by 20%. + +**Pension** - As your salary is reduced, so too will your individual and employer pension contributions. You may like to increase your individual contribution to account for this. + +**Trial period** - If you request a flexible working pattern, there’s usually a trial period to assess the feasibility before any final change is confirmed. + +**Reduced working hours** - We can only support reduced working hours and not compressed hours or other patterns (such as annualised hours etc). diff --git a/handbook/handbook-main/benefits/getting_together.txt b/handbook/handbook-main/benefits/getting_together.txt new file mode 100644 index 0000000000000000000000000000000000000000..27ccfc98f9d6219cb04a301cab8badd4d4a0a8b6 --- /dev/null +++ b/handbook/handbook-main/benefits/getting_together.txt @@ -0,0 +1,11 @@ +# Getting together as a team and company + +## Our monthly meet ups +Our Social Committee is made up of reps for each region, who are in charge of organising monthly regional socials. These socials will be low-key, often office based activities (don’t worry, drinks & snacks/dinner will be provided!)The intention is to facilitate more frequent gatherings, allowing us to stay connected on a regular basis 🍕🍜 + +If you have any suggestions DM one of the reps for your region, and if you would like to get involved reach out to the People Team! + +## Our Winter & Summer parties +Every year we hold a larger winter and summer event to celebrate our achievements over the last 6 months and to get together to socialise, network and mingle with our peers and wider team. + +_As drinking is exclusionary in nature to those who don't like or can't be around alcohol we make efforts to make sure it's not the centre of our culture whilst at the same time acknowledging it's important to some._ diff --git a/handbook/handbook-main/benefits/help_to_buy_tech.txt b/handbook/handbook-main/benefits/help_to_buy_tech.txt new file mode 100644 index 0000000000000000000000000000000000000000..86a098c809673cd20d4da21aed9a94380a32f5de --- /dev/null +++ b/handbook/handbook-main/benefits/help_to_buy_tech.txt @@ -0,0 +1,67 @@ +# Help to buy Tech with TechScheme + +We've signed up to TechScheme which is accessible through Bob Benefits to make it easier and more affordable for our team to buy the latest tech gadgets. + +TechScheme lets you get the latest tech, such as Smart Phones, Smart Watches and/or Game Consoles, up to a maximum value of £2,000. You apply for an eCertificate worth the value of your shopping basket - so decide what you want to buy before you apply for this perk. You then repay this amount via your salary across 12 months. Powered by Currys to allow you to choose from thousands of products, and take advantage of the sales! Your voucher is valid for up to two years, so no need to spend it all at once! + +You can now shop at Ikea for all your furtiture, flat pack & meatball needs! The process works the exact same, simply select Ikea as your chosen retailer at check out. + +## TechScheme FAQs + +### 1. How do I apply? + +Head to the TechScheme website which you can access through the Help to buy tech square on Bob Benefits, enter the Employer code (also found in the Tech square on Bob benefits) and complete the application. You will also need your payroll number (labelled Employee ID on your bob profile, or can also be found on your payslip.) + +Once you have completed the application it will be sent to a member of the people team to approve your request. Once approved you will receive your eCertificate which can then be exchanged for your shiny new tech in store or online! + + +### 2. I've applied when will I get the eCertificate? + +We will review all new applications every Friday afternoon, so you shouldnt have to wait longer than one week for Made Tech approval. Once we have approved and paid for your voucher you will then be sent this automatically from TechScheme. + +### 3. What is TechScheme? + +TechScheme allows you to buy the latest technology through your payroll. Whatever the product you purchase, you can pay back the cost over a set period of time (12 months), interest free and with no credit checks required, it's so simple. + +### 4. How much will the product(s) cost me? + +Your net pay will be reduced by a monthly amount equivalent to the total cost of the product(s) that you've chosen. This will be spread evenly over the selected period of time. + +If you request your product before the 18th of the month your deductions will begin the same month, however if you request your voucher on or after the 18th your deductions will begin the following month. + +### 5. Hold on I'm not buying the actual product? + +No, you're receiving an Instant eGift Card that you can spend online or in-store at any Currys PC World. This enables you to get total flexibility just in case something changes in-store and you can change your mind. + +### 6. Where can I get my Product? + +From Currys PC World network of over 450 stores, which have the largest selection of technology in the UK including all the top brand products. You can purchase online at www.currys.co.uk or www.pcworld.co.uk too. + +### 7. Can I spend more on top of what I buy on TechScheme? + +Yes, of course. You can use your TechScheme voucher to purchase the majority of the product and then pay for the rest! + +### 8. Who owns the product? + +As this is not a tax efficient salary sacrifice scheme, you will wholly own the product from the moment of purchase. + +### 9. Can I select more than one product? + +Yes, your spend limit is £2000, but it's up to you how use that amount all at once or over a few smaller products. + +### 10. What happens if I leave before the end of the payment period? + +If you leave before the end of the payment period, you must pay back the outstanding amount and this will deducted from your final net pay. + +### 11. What if my product gets stolen or damaged? + +It's recommended you obtain separate insurance, or check your product is covered under your home contents insurance policy. Payments from your salary will not stop or be suspended due to loss or damage of the product. + +### 12. What happens if my product breaks? + +If your product breaks you need to get in contact with Currys PC World: Within 30 days of purchase or delivery: You always have the option of an exchange or refund if the fault occurs within 30-days of purchase or delivery. You can return it to the store or arrange a pick up by calling the Knowhow contact centre on 0344 561 1234, or by emailing (customer.services@currys.co.uk) Extended range large kitchen appliances cannot be returned to one of Currys PC World stores, please call Knowhow contact centre on 0344 561 1234. Returns and exchanges can only be processed with proof of purchase. This can be the sales receipt, a bank statement or an online sales invoice. Please provide your Currys PC World order numbers when you return a product. Within each product’s guarantee period (normally 12 months from purchase or delivery), Currys PC World offer you a prompt repair service. In all cases, Currys PC World reserves the right to inspect the product and verify the fault. Please call the Knowhow contact centre on 0344 561 1234 or emailing (customer.services@currys.co.uk) to arrange a collection. To speed up the process, please have your order number to hand before calling. Currys do not cover faults caused by accident, neglect, misuse or normal wear and tear. + +### 13. How do I request a refund? + +You have a right to withdraw from the benefit and cancel the Funding Plan at any time prior to, and within 14 calendar days of, receipt of an email containing the Redemption Code, such 14 days to begin on the day after receipt of the said Redemption Code (“Cooling Off Period”). If You redeem any of Your Redemption Codes with one of the Authorised Retailers (online or in-store) at any time during the Cooling Off Period You will no longer be able to cancel this Funding Plan. +If You wish to cancel the Funding Plan in accordance with “Your Rights” described above You need to send written confirmation of Your request to cancel to Techscheme via email at info@techscheme.co.uk, or by post to Techscheme, PO Box 3809, BATH, BA1 1WX. diff --git a/handbook/handbook-main/benefits/hybrid_working.txt b/handbook/handbook-main/benefits/hybrid_working.txt new file mode 100644 index 0000000000000000000000000000000000000000..0ad8014cf3efed6826107b1d92c4c5af3d8ce908 --- /dev/null +++ b/handbook/handbook-main/benefits/hybrid_working.txt @@ -0,0 +1,57 @@ +# Hybrid Working + +We believe in people working in the best way for our teams and clients - this may sometimes be in person, remotely at home, from a coffee shop or outside of the UK. + +The best outcomes are delivered by blending different ways and places of work - and we want to empower our teams to make the best decisions for their teams, projects and relationships. + + +### Made Tech offices +As part of our Hybrid Working policy, we want to encourage organic purposeful face-to-face sessions that help build relationships and stronger teams, which in turn deliver even better work for our teams and clients. Bringing people together regularly creates more opportunities for relationships to be built within teams, across Made Tech, and with our clients and partners. + +For our group-facing team members, and our client-facing team members that do not have a client onsite requirement, we encourage 2 - 3 days a month in a Made Tech office for purpose-driven activities that will help drive valuable outputs and relationship building. + +### Client office +Each of our clients will have their own requirements for Made Tech team members to work from their offices. All client-facing team members will be required to be able to travel to their assigned client office. We expect client-facing teams to create regular opportunities to come together to collaborate and where necessary to align with a client’s specific needs + +### Exceptional Circumstances +There may be circumstances where our team members may not be able to attend sites or our offices or may need additional support to be able to do so. We encourage you to reach out to your Line Manager and/or your People Partner to discuss how we can best support you. +You can find more information about hybrid working within our Hybrid Working Policy, and the supporting policies such as TOIL, Project Assignments and Reasonable Adjustments Passport - which you view with your Made Tech account. + +### Hybrid working guidance +- Check that you're not needed on-site by a client or your team +- Ensure you're available for your team ceremonies as normal and are able to dial in without interruption +- Be a good Slack citizen and check in regularly and visibly with your team throughout the working day in public channels +- Ensure you're not expected for any in-person meetings or sessions + +### Secure Remote Working +When remote working, and when onsite with a client, it is important to pay close attention to these security guidelines in addition to your normal security practices: +- If you are in a public place, such as a coffee shop, make sure you are handling any sensitive data responsibly and securely. Can you be overseen? Is your connection secure? +- Ensure any work-related conversations can’t be overheard. If that’s not possible, try to talk in general terms, and without specific details such as names or clients + +### Working abroad +Where possible we will support short-term/ad hoc remote working from outside of the UK (for example if someone wanted to travel and work from abroad for a few weeks during the year and this was viable). +Whilst we will always try to support this, in some cases this may not be feasible. + +When considering this option, you will need to: +- Discuss with your team (as in some cases, client requirements may not support this) +- Inform your line manager +- Let the People team know +- Ensure you're familiar with our security requirements + +Some things to be aware of when thinking about working abroad: +- Client laptops - you are not able to take a client laptop outside of the UK. +- VPN - you must use the VPN to access Made Tech systems. +- Our IT support - We’re only able to provide support during UK working hours. If there is a major issue with the laptop (or other equipment, such as your charger) you would be responsible for ensuring you are able to continue working until you return to the UK. + +If you remain uncertain or you have any additional questions, please reach out to the Compliance team, Ops, or People. + +### Travel expenses +Team members may expense travel to client sites that are outside of their regional office. Travel to and from your allocated office & within your regional office area is not able to be expensed. + +#### What is part of my regional office? +- London - within the M25 +- Manchester - all Manchester postcodes (M postcodes) +- Bristol - within a 25KM radius of Bristol city centre +- Swansea - within a 25KM radius of Swansea city centre + +You will be able to use our TravelPerks platform to book trains and hotels for your journey. For more information on when and how to use this take a look at the [Travel Perk doc](https://docs.google.com/document/d/1cgASgYU9rjF-y7pa9gJ9FJ8HCBP6M3ntmdgeLZclSPo/edit) and/or head over to our TravelPerks slack channel. diff --git a/handbook/handbook-main/benefits/income_protection_and_life_insurance.txt b/handbook/handbook-main/benefits/income_protection_and_life_insurance.txt new file mode 100644 index 0000000000000000000000000000000000000000..21859c4438ae8621cb5107f8a7cae1485d40fd33 --- /dev/null +++ b/handbook/handbook-main/benefits/income_protection_and_life_insurance.txt @@ -0,0 +1,7 @@ +# Income Protection Cover + +We offer income protection cover for all Made Tech employees. If you are unable to work due to serious illness or disability this policy will pay you 75% of your salary for up to 2 years. The income protection scheme defers for the first 13 weeks of a colleague's absence and an assessment of the absence being eligible for income protection scheme will be taken by the scheme provider. + +# Life Insurance + +We offer life insurance cover for all company employees which will financially support our loved ones following death. This policy pays out 4x your annual salary. diff --git a/handbook/handbook-main/benefits/lunchers.txt b/handbook/handbook-main/benefits/lunchers.txt new file mode 100644 index 0000000000000000000000000000000000000000..238e4f44a7ce5411433a82b46dc6e2afe4a22c92 --- /dev/null +++ b/handbook/handbook-main/benefits/lunchers.txt @@ -0,0 +1,12 @@ +# Lunchers + +Once a month in each office we select 5 people to have lunch together on us! Order from your favoriute restaurant, nip to the shops, find a local cafe or head for a walk around Borough Market - the choice is yours! + +## How it works + +- At the start of the month the date for each region will be posted in the Slack channel. To be in with a chance of being selected, book your desk and make sure you are in the office on that day! +- The day before lunch the lucky lunchers will be posted in the regions Slack channel - if you cant make it, give your spot to someone else whos in. + +*You can only expense your lunch if you are chosen for lunchers.* + +If you have any questions, ask the People or Finance Team. diff --git a/handbook/handbook-main/benefits/pension_scheme.txt b/handbook/handbook-main/benefits/pension_scheme.txt new file mode 100644 index 0000000000000000000000000000000000000000..551cfa151f2f70a05f345e10c6ad27ee88dc103f --- /dev/null +++ b/handbook/handbook-main/benefits/pension_scheme.txt @@ -0,0 +1,30 @@ +# Pension Scheme + +We have introduced a much-improved pension offering for all employees (as of May 2022). The workplace pension scheme is run by Scottish Widows and follows a contribution matching model where Made Tech matches the level of contribution you decide to make. + +The pension contribution available to you is aligned to your SFIA level: +- SFIA 1: 4% employer matched +- SFIA 2-4 6% employer matched +- SFIA 5: 7% employer matched +- SFIA 6: 8% employer matched +- SFIA 7: 9% employer matched + +The minimum contribution in every level is 4% (employer matched). +There is no maximum contribution, however your salary must remain above the national minimum wage thresholds set by HMRC. +If you’d like to adjust your contributions, please [submit a request via Ask Made Tech](https://askmadetech.zendesk.com/hc/en-gb/requests/new). + +Pension contributions are deferred for your first 90 days, if you want to opt in early add the date into the "Pension Scheme" section of your Hibob profile where you will be enrolled on a 4% contribution scheme which you can adjust after your probationary period. + +Our pension scheme is based on a salary sacrifice approach which is more tax-efficient for both employer and employee. We have removed the qualifying earnings limit, which should simplify pension management for those of you who are higher rate taxpayers. If you want to calculate your contributions you can use the calculator on the [Scottish Widows](https://www.scottishwidows.co.uk/retirement/calculators-tools/how-do-you-pay-to-your-pension/salary-sacrifice/) website. + +In order to allocate your preferred contribution, or early opt in, or opt out you'll need to fill in the "Pension Scheme" section of your Hibob profile. + +- You can opt out at any point by updating the pension section of your Hibob profile in the "opted out" section. If you select to opt-out at the start of your employment, any initial deduction will be refunded if this is made within one month of the initial deduction. If you selected to opt out before the cut-off date (on the 18th) it will be processed in the same month, otherwise it will be in the following month. +Any deductions made will usually stay in the pension until you're eligible to access your money, financial advice can be obtained to assist you transferring your pension to another provider. +- There are also [Government guidelines](https://www.gov.uk/workplace-pensions/if-you-want-to-leave-your-workplace-pension-scheme) on opt-out + +You can read more about Workplace pensions on [gov.uk](https://www.gov.uk/workplace-pensions/about-workplace-pensions) + +You can read more about Pensions and some third party advice on [MoneySavingExpert](http://www.moneysavingexpert.com/savings/discount-pensions) + +For any general pensions queries please enquire via Ask Made Tech. diff --git a/handbook/handbook-main/benefits/private_medical_insurance.txt b/handbook/handbook-main/benefits/private_medical_insurance.txt new file mode 100644 index 0000000000000000000000000000000000000000..a78271564cf455834fd7a44ea2ac805b22a885e8 --- /dev/null +++ b/handbook/handbook-main/benefits/private_medical_insurance.txt @@ -0,0 +1,3 @@ +# Private Medical Insurance + +We have introduced BUPA Private Medical Insurance to employees who are SFIA 5 (Lead/Principal) and above. This policy will cover the costs of private healthcare from diagnosis through to treatment. This is a taxable benefit and is declarable on a P11D. diff --git a/handbook/handbook-main/benefits/season_ticket_loan.txt b/handbook/handbook-main/benefits/season_ticket_loan.txt new file mode 100644 index 0000000000000000000000000000000000000000..5f38691b437f6119841a7d94a494a171704c8bef --- /dev/null +++ b/handbook/handbook-main/benefits/season_ticket_loan.txt @@ -0,0 +1,9 @@ +# Season Ticket Loan + +On completion of the probation period, we offer a season ticket loan up to the value of one month's net salary. + +You will need to provide a receipt for the season ticket. + +The loan will be repaid automatically at PAYE from your net salary every month. There is no tax benefit, and no interest is payable. + +If you leave the company prior to your loan being repaid, the outstanding balance will be deducted from your final salary payment. diff --git a/handbook/handbook-main/benefits/taking_holiday.txt b/handbook/handbook-main/benefits/taking_holiday.txt new file mode 100644 index 0000000000000000000000000000000000000000..a42f5772b0dc95c9be6d94f6eba603e62c4f9adb --- /dev/null +++ b/handbook/handbook-main/benefits/taking_holiday.txt @@ -0,0 +1,70 @@ +# Taking Holiday + +We're building a high-performance organisation that delivers great software products. We recognise that this requires a lot of hard work and that for our team to perform at their highest possible level, they need to live a well-balanced life and take regular time-out for rest, relaxation and rejuvenation. + +All team members have 38 days of leave available between June and May, this is inclusive of public and bank holidays (pro-rata for part time colleagues.) We believe this policy will help us to perform at the highest possible level. + +It is important that you and your colleagues feel that holiday is highly available. That holiday is an easily accessible commodity that enables everyone to get the necessary rest that they need. + +Made Tech will support holiday requests that are up to 4 consecutive weeks, if you wish to take longer than this the additional time may be unpaid. Please see our [Flexible Working](flexible_working.md) as the alternative to Flexible Holiday in those situations. + +## How long are you taking? + +We trust you'll use your best judgement when taking holidays. This is the level of notice we expect when you take your holiday: + +* **For 1 day** – you must give at least 3 days notice +* **For 2 days** – you must give at least 1 week notice +* **For between 3 days - 4 days** – you must give at least 2 weeks notice +* **For between 1 week - 2 weeks** – you must give at least 4 weeks notice +* **For greater than 2 weeks** – you must give 3 months notice + +The notice guidance is a minimum - please aim to give your team as much notice of upcoming leave as you can. Your team, Delivery Manager and client should all agree to your leave before you schedule this in, and providing notice minimises the chance of problems being raised. Where your team plans work at a regular cadence (e.g. during sprint planning every two weeks), you should aim to make the team aware of any potential leave to help the team remain accountable for commitments made. + +The ability to book holiday/learning days at shorter notice whilst you are within the chalet is an accepted exception to the above notice periods - in those instances please check in with Scheduling to ensure you are not due to be imminently assigned to an account and let your line manager know. + +If you wish to book holiday outside of these guidelines, please make a request to your Head of Capability, Head of Industry, or Head of Business Service who will help you plan for this time off. + +## How will it affect your team? + +Having several team members away at the same time can make life really difficult for everyone else. Try to forward-plan your holiday, so it doesn't have a detrimental affect on your team members or on the company. + +We recommend you check with your Delivery Lead whenever you join a new team. Our general guideline on this is that only 1 person from a small team (less than 4) may be away at any one time. For larger teams (5+) please refer to your Delivery or Team Lead to confirm what works best for your team. + +## Who approves holiday? + +We want to ensure teams own their holidays and that includes thinking about the commercial impact of taking them. To that affect we need to make sure you've done the following before booking holiday: + +* Ask your team members if it's okay with them +* Ask your clients if it's okay with them +* Ensure your responsibilities are covered whilst you're away +* Ensure the Made Tech person leading your client workstream or your line manager provides their agreement +* Ensure that the holiday is placed into HiBob + +## How is holiday approved? + +It is the responsibility of the person agreeing to a holiday booking to ensure it is made in aligment to this policy and that the holiday will not impact the quality of service we're able to provide our clients + +## Additional considerations + +* We use the HiBob calendar when working out project allocation and the number of days being billed to clients, so it's important that it is always up-to-date and accurate. + +* Time off due to illness and/or injury are handled separately. Flexible holiday cannot be used for these types of absences. + +* If a team members performance declines significantly due to abuse of this policy, then we reserve the right to review their use of this policy. + +* If you leave Made Tech part way through the year your contractual holiday allowance will be pro-rated to account for your leave date. In some cases this might mean we'll pay you for accrued and unused holiday and in others it might mean you'll have to pay days taken over your pro-rated allowance back. + +## Festive period at Made Tech + + +### Between Christmas and New Years +* We only work for clients during the 3 days between Christmas and New Years if they specifically ask for this. Where there is a client requirement we'd look for volunteers to provide this cover. Most team members will not be working during this time. +* Please note - you will need to book this time off as holiday in HiBob unless it has been agreed that you are working. + +### December and January +Taking time off works differently for the two weeks before Christmas and the first week in January as this is a popular time for holidays. +This means we need to coordinate with our team beyond what we may do ordinarily to ensure that there is fair access to holiday and adequate cover of team members working across client deliveries. + +* We'll consult with our clients as early as possible to understand what level of cover they will need. +* Time off requests submitted for this period are typically reviewed and confirmed by mid October. + diff --git a/handbook/handbook-main/benefits/work_ready.txt b/handbook/handbook-main/benefits/work_ready.txt new file mode 100644 index 0000000000000000000000000000000000000000..e7e1c8269aeb60a65f19b39a2e8d71bad63b12f3 --- /dev/null +++ b/handbook/handbook-main/benefits/work_ready.txt @@ -0,0 +1,33 @@ +# Work Ready + +We know you're ready to work and so we want you to be work ready. We'll [equip you](../guides/it/Hardware.md) with a Macbook (or a PC if you're in Engineering or UCP and would prefer that) which will arrive at your home address prior to your start date. + +In addition to this, you have access to a one off £250 work ready allowance. The allowance allows you to purchase items that will assist you in your job role. It can be used from your first day, and doesn’t need to be used in one go. If you are working your notice period, you are unable to use the budget. + +Before utilising your work ready budget, please complete your DSE (Display screen equipment) training and DSE assessment to assist you in purchasing items required to fit in with DSE requirements. + +To utilise your work ready allowance; simply order the equipment you require then claim it back via expenses on Xero. You must have an invoice or receipt to ensure you can claim it back on Xero. Once on Xero please log the expense under ‘computer equipment <£250’. Once a claim is made you will be added to the next available weekly payment run. For any further questions on expenses please read the [expenses process](../guides/compensation/expenses.md). + +You can see how much of your allowance is left to use by looking at your profile on Bob under the Work Ready section. + +Examples of things you can order: + +- Monitor +- Adapters (HDMI, USB-C, etc.) +- Keyboards +- Mice +- Ergonomic chairs, stools, stands +- Standing desks +- Headphones +- Laptop stand +- Docking station +- Extension lead +- Laptop sleeve + +Please order items that are dispatched from the UK. If items are dispatched from outside of the UK you could receive a duty and tax bill that will also have to be deducted from your WFH budget. + +[See a list of popular purchases of office equipment](https://docs.google.com/spreadsheets/d/1aVJx2Qvd6U3H6tHkzeCOY1kVsfcuwXfmXzVWJOFsVYk/edit#gid=0) (internal link). We also have a Slack channel #x-swap-shop for anyone who wants to join and see what people are offering. + +If you are unable to claim items back yourself, please contact the operations team on either [operations@madetech.com](mailto:operations@madetech.com) or through [Ask Made Tech](https://askmadetech.zendesk.com/hc/en-gb) (internal link). + +You will be unable to purchase or expense any items during your notice period. diff --git a/handbook/handbook-main/benefits/working_hours.txt b/handbook/handbook-main/benefits/working_hours.txt new file mode 100644 index 0000000000000000000000000000000000000000..f16527b5d168deaa1b0ed7db8c8dacaae286d7d6 --- /dev/null +++ b/handbook/handbook-main/benefits/working_hours.txt @@ -0,0 +1,19 @@ +# Working Hours + +We care more about the quality of the work we produce than the amount of hours worked. We believe we individually know how we work best and can therefore set our own hours. + +## Some things to note + +**Setting hours** - We don’t have a set amount of hours you need to work in a day or a week. Many of us will vary our hours day to day while others prefer routine. + +**Start time** - We don’t have a specific start time but we do have our company update on the first Wednesday of every month at 9:30am, and weekly Friday showcases at 4:30pm. You should be in the office or dial in remotely for these meetings. + +**Ending your day** - There isn't a time we expect everyone to switch off their laptop or leave the office. If you're working shorter hours but having problems delivering on your commitments, someone is more likely to check in with you to see if everythings OK, and provide offers of support or some constructive feedback. + +**Longer hours** - The reality of working closely with clients is that there are deadlines. Sometimes working longer to make sure of a smooth launch or to help diagnose and fix a problem is needed. But we do everything we can to make sure these occasions are rare. If you regularly feel this pressure, say more than twice a year, we encourage you to raise this with a manager or another team member. + +**Other team member hours** - You might also feel pressure if you notice other team members regularly seem to work longer hours than you. We suggest finding ways to share and receive open and honest feedback. Unless someone has raised an issue with you, everything’s probably fine. + +**Commitments** - We need to respect our commitments and the time of other team members. If a meeting is scheduled, we ask everyone to be as accommodating as they can. This isn't to say you can't be responsible for setting meeting times that fit your working style better. + +**Contractual hours** - Most of our employment contracts do have set contractual hours. This is because we have a billed delivery operating model with clients that’s based on hours worked. This also helps us to adjust our flexible working policy in case that’s ever needed. diff --git a/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/edge-value-driven-digital-transformation.txt b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/edge-value-driven-digital-transformation.txt new file mode 100644 index 0000000000000000000000000000000000000000..fab06e28d80efc075be043fdb95b87b398ebf7cb --- /dev/null +++ b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/edge-value-driven-digital-transformation.txt @@ -0,0 +1,24 @@ +# EDGE: value-driven digital transformation + +## About +Authors: Jim Highsmith, Linda Luu and David Robinson +Recommended by: Chasey +_[EDGE](https://www.goodreads.com/en/book/show/43567723-edge) embraces an adaptive mindset in the face of market uncertainty, a visible, value-centered portfolio approach that encourages continual value linkages from vision to detailed initiatives, incremental funding that shifts as strategies evolve, collaborative decision-making, and better risk mitigation. This guide shows leaders how to use the breakthrough EDGE approach to go beyond incremental improvement in a world of exponential opportunities._ + +## 20th May +_Authored by Reuben_. We had our first ever session!! We went over the rough format and covered just managed to cover the introduction and "Chapter 1: The Big Picture". We wondered at whether fast meant good (it doesn't) but expected to talk about that more in later chapters. We also spoke about our [mainly negative] experiences of Agile at scale and the challenges it presents and what it means to us to be agile. Lastly, this chapter talks about the new / digital-age fitness function and we started to ask how we might measure customer value, without externalising what should be internal team metrics. Great stuff! We decided we'd read "Chapter 2: Tech@Core" and "Chapter 3: EDGE Principles" for next time, but might not expect to cover it all as Tech@Core seems an interesting subject! + +## 10th June +_Authored by Reuben_. I forgot to take notes... but we spoke about Tech@Core :D + +## 24th June +_Authored by Reuben_. I missed this session and I am indebted to Tom for running it. The team chatted about the "EDGE principles", what kinds of governance can reduce waste and increase autonomy, and asked the question of how often principles should change. + +## 8th July +_Authored by Reuben_. We had a whopper and covered two chapters - "Chapter 4: Building a Value-Driven Portfolio" and "Chapter 5: Measuring and Prioritizing Value" before deciding it was time to enjoy the Friday afternoon sun (location dependent). We were pleased to welcome Catherine (a DP) into the conversation this week and was great to have her insight! We talked about the value we get from having User Researchers in our delivery teams and working closely with us, the issues we have with teams not having the ideal relationships between the goals, bets and initiatives, and how the EDGE operating model is value-centre rather than being implementation-specific although it tends to have enterprise in mind. The measures of success example on page 81 were very good for seeing how to put customer outcomes first! + +## Resources +👉 [An interview with Linda Luu](https://www.youtube.com/watch?v=-HPnr4yuUqc) going over the high-level stuff +👉 [An introduction to value-stream mapping](https://www.youtube.com/watch?v=tGDrt8SV5H4) (spin off from 20th May) +👉 [A lean-value tree example](https://miro.medium.com/max/1094/1*9KIk8YmivQxv53lEgestAA.png) (image for those without the book) +👉 [Weighted Shortest Job First (WSJF)](https://www.scaledagileframework.com/wsjf/) from SAFe is an implementation based on Cost of Delay diff --git a/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_got_our_eye_on.txt b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_got_our_eye_on.txt new file mode 100644 index 0000000000000000000000000000000000000000..1e33d0c2f9e1977886d96c28be146680a5609c85 --- /dev/null +++ b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_got_our_eye_on.txt @@ -0,0 +1,9 @@ +# Books we've got our eye on + +Please contribute to this list if there's a book you're interested in! We'll include it in the considerations when we're ready to pick up a new book! 💚 + +| Title | Author | Watched By | +| --- | --- | --- | +| [Release It!](https://www.goodreads.com/book/show/1069827.Release_It_) | Michael Nygard | Reuben | + +[👈 Library](./library.md) \ No newline at end of file diff --git a/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_read.txt b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_read.txt new file mode 100644 index 0000000000000000000000000000000000000000..ac49eba59fa1742614ca439ddf83dbbb57b13669 --- /dev/null +++ b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_have_read.txt @@ -0,0 +1,5 @@ +# Books we've read in Book Club + +1. ### [EDGE: value-driven digital transformation](../edge-value-driven-digital-transformation.md) + +[👈 Library](./library.md) \ No newline at end of file diff --git a/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_recommend.txt b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_recommend.txt new file mode 100644 index 0000000000000000000000000000000000000000..51de9f8ba4ccf1a1f95a9caa657a3199f0a4f886 --- /dev/null +++ b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/books_we_recommend.txt @@ -0,0 +1,10 @@ +# Books we recommend + +| Title | Author | Recommended By | +| --- | --- | --- | +| [Accelerate](https://www.goodreads.com/en/book/show/35747076-accelerate) | Nicole Forsgren, Jez Humble and Gene Kim | Reuben | +| [Domain-Driven Design](https://www.goodreads.com/book/show/179133.Domain_Driven_Design) | Eric Evans | Reuben | +| [Infrastructure as Code](https://www.goodreads.com/book/show/26544394-infrastructure-as-code) | Kief Morris | Reuben | +| [Test-Driven Development: By Example](https://www.goodreads.com/book/show/387190.Test_Driven_Development) | Kent Beck | Reuben | + +[👈 Library](./library.md) \ No newline at end of file diff --git a/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/library.txt b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/library.txt new file mode 100644 index 0000000000000000000000000000000000000000..776d8a32123cf17f844483f13173849343ae2793 --- /dev/null +++ b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/library/library.txt @@ -0,0 +1,5 @@ +# Library + +- ✅ [Books we've read](./books_we_have_read.md) +- 💡 [Books we recommend](./books_we_recommend.md) +- 👀 [Books we've got our eyes on](./books_we_have_got_our_eye_on.md) diff --git a/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/welcome.txt b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/welcome.txt new file mode 100644 index 0000000000000000000000000000000000000000..07015fb4f68cf856794f7009294eb919e082edba --- /dev/null +++ b/handbook/handbook-main/communities-of-practice/cloud-and-engineering/book-club/welcome.txt @@ -0,0 +1,33 @@ +# Welcome to the Book Club + +👋 Welcome to our Cloud and Engineering Book Club! At Made Tech we are passionate about [learning](../../../guides/learning/README.md). In this Book Club, we choose a technical book in the cloud and engineering space and gather once a fortnight to discuss it. We hope to see you there soon! + +This page is about what the Book Club is all about. For all things books, take a look at our [library](./library/library.md). + +## Purpose + +As engineers in delivery teams, we want to continously improve our capabilities and how we deliver working software. By using a technical book to give our minds some direction, we will be able to share our own relevant knowledge and experiences to discuss and build on the book's content - the questions it asks of us - and how it can make us more well-rounded engineers. + +## Format? + +- We meet every other Friday at 1530 for 50 minutes. +- Anyone at Made Tech can subscribe to the club's calendar to get the invite. Just head over to the #eng-bookclub Slack channel and pick up the pinned post! +- We'll cover off an overview of the chapter. +- We'll cover off some of our own highlights. +- We'll then vote on some cards and discuss the most popular questions and deep dives that come to mind. +- At the end, we'll decide for next time. + +## What do I need to do? + +### Before the meeting + +- 💰 Use your learning budget to get your copy of the book! +- 📖 Try and read the agreed sections of the book. +- 🧐 While you read, you could try to think about any puzzles that came to mind, any challenges you'd like to pose to the group, any times you've seen the technique work/fail in real life, or just things you find insightful. +- 💡 Add your thoughts to the (internal) Trello board, which is pinned to the #eng-bookclub Slack channel. + +### During the meeting + +- 🚶‍♀️ We'll walk through the cards chapter-by-chapter +- 🗣 Chip in where you're happy to, whether that's a card you added, an opinion you want to share or a spur of the moment contribution! +- 🧘‍♀️ Or take a back seat if that's what you're comfortable with. \ No newline at end of file diff --git a/handbook/handbook-main/company/about.txt b/handbook/handbook-main/company/about.txt new file mode 100644 index 0000000000000000000000000000000000000000..6459c97af7511f17234ac85f8b0b2b7c85a2fa0d --- /dev/null +++ b/handbook/handbook-main/company/about.txt @@ -0,0 +1,34 @@ +# About Made Tech + +As a **purpose-driven organisation**, we believe the **outcomes** we create are more important than the technology we deliver. + +## Our purpose – why we do what we do + +We want to positively impact the future of the country by using technology to improve society, **for everyone**. + +We are already working with **brilliant public servants** to **modernise technology** and **accelerate digital delivery**. But we know we can do more to help those who share our vision. + +## Our vision – what we want the future to look like + +We want to **empower** the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. + +To achieve this, we help them to modernise working practices, accelerate digital delivery, drive better decisions through data and enable technology and delivery skills. + +## Our missions – how we will get there + +We empower public sector organisations by helping them to become digital by default. + +- **Modernise** legacy technology and working practices +- **Accelerate** digital service and technology delivery +- **Drive** better decisions through data and automation +- **Enable** technology and delivery skills to build better systems + +## Our values – who we are and how we operate + +**Client focus** - we can only succeed in our mission if we’re a trustworthy partner to the public sector. We build strong and lasting relationships with our clients through empathy, flexibility, and pragmatism. + +**Drive to deliver** - we have a strong drive to deliver successful outcomes for our clients and their users, working hard to keep to our commitments and rapidly delivering software that improve people’s lives. + +**Learning and mentoring** - we’re passionate about learning and growth. Whether it's improving ourselves, the team, or the organisation, we believe in the power of continuous improvement. + +**One team** - we collaborate with colleagues, clients and communities to create an environment which is inclusive, integrated, and where everyone supports delivery of the mission. diff --git a/handbook/handbook-main/company/welcome_pack.txt b/handbook/handbook-main/company/welcome_pack.txt new file mode 100644 index 0000000000000000000000000000000000000000..1ec35d155b7ee62ba1f7b04f5daf6286f2d0627e --- /dev/null +++ b/handbook/handbook-main/company/welcome_pack.txt @@ -0,0 +1,69 @@ +# Welcome Pack + +If it's your first day today, we'd just like you to know how happy we are to have you with us :) + +To give you an idea of what to expect from your on-boarding, we have written this short guide. It covers the things that we think are important for new starters and we hope it provides a basis for your successful on-boarding. + +Over the next few days and weeks we'll introduce: + +1. **Company mission, [values](about.md#our-values), business services and EOSs** - We'll talk about our mission and why the business exists. We'll tell you why we think it's important to improve software delivery in every organisation and how you can help us to achieve our mission. +2. **Peer buddy** — As part of our on-boarding process, we'll introduce you to a company buddy who will be available whenever you need them. If anything crops up (from simple questions to emergencies), feel free to let your buddy know and they will do all they can to help. + + It goes without saying that the rest of the team are here too, so there should be plenty of places to turn if you need anything. +3. [**Role expectations**](../roles/README.md) — All our team members have role expectations and we'll work with you to introduce these to you over the coming weeks. +4. **Career development 121s** — As part of your on-boarding process and ongoing career development, you'll have a monthly 121 with your Line Manager or one of the company directors. These sessions are an opportunity for us to review your progress, look at areas where we can provide support. +5. **Marketplace** — Every Friday, we run showcases. Please contribute to these and once you're feeling confident enough, look to facilitate one of them. +6. **Salary, Pensions & Expenses** — We'll take you through how our finances work, where to go to if you have any questions around salary, pensions, benefits or if you need to submit an expense claim. + +## Getting Started Checklist + +Our on-boarding checklist will be in your Hibob profile on your first day. Below are a few things this will cover. + +#### Everyone + +* [ ] Meet your buddy +* [ ] Attend first career development 121 to introduce role expectations +* [ ] Read the [Acceptable Use Policy](../guides/security/acceptable_use_policy.md) & [Bring Your Own Device Policy](../guides/security/bring_your_own_device.md) +* [ ] Ensure your own devices used for [work are secure](../guides/security/bring_your_own_device.md) +* [ ] Set up Slack account with picture, name(s), name pronunciation guide and [pronouns](https://www.mypronouns.org/) + +#### Non-Engineers +* [ ] Complete the [Github tutorial](https://guides.github.com/activities/hello-world/) + + +### Signing up for Services + +Below you'll find a list of tools that you will need to do your job. You will be setup with the accounts you'll need on your first day with us. + +Note that Google office applications (Docs, Sheets) are the preferred format for internal office documents, to be stored in Google Drive + +#### Everyone + +* [ ] Google Mail (with 2FA) +* [ ] Github (with 2FA) +* [ ] Slack (with 2FA) +* [ ] 1Password (with 2FA) +* [ ] Trello (with 2FA unless using Google Auth to login to Trello) +* [ ] HiBob + +Academy Engineers: you can skip these two for now, but you will probably need them once you graduate. + +* [ ] Xero +* [ ] Kimble + +#### Sales & Marketing + +* [ ] HubSpot +* [ ] Access to [LinkedIn Sales Navigator](https://www.linkedin.com/sales/) + +#### Engineers + +* [ ] Get access to infrastructure for delivery team + +### Setting up your Machine + +#### Engineers + +To get your machine set up with some essentials we've created [First Boot](https://github.com/madetech/first-boot). + +First Boot will install applications like Chrome, Slack, and Sequel Pro as well as installing the latest version of Ruby using `rbenv`, and the latest version of Node using `nvm`. diff --git a/handbook/handbook-main/guides/Relocation.txt b/handbook/handbook-main/guides/Relocation.txt new file mode 100644 index 0000000000000000000000000000000000000000..34236b265b2f469f9cac332fdb9276184308148d --- /dev/null +++ b/handbook/handbook-main/guides/Relocation.txt @@ -0,0 +1,16 @@ +# Relocation + + + +If you are planning to move address, you’ll need to inform us as early as possible. + + +To inform us of an upcoming move, you'll need to let the following people know: + +Your line manager -to inform them of any support you may need (booking leave to move house etc). +The People team via [people@madetech.com](mailto:people@madetech.com) - we need to know if we need to update your office location in bob. +Your head(s) of - if a location change is required, they may need to know in case this impacts your current or future projects. + + +Once you have confirmation of your new address and have spoken to the relevant people, you’ll need to update this in your bob profile. +You can do this via 'Actions > Employee Updates > Address Change'. diff --git a/handbook/handbook-main/guides/buddy_guidance.txt b/handbook/handbook-main/guides/buddy_guidance.txt new file mode 100644 index 0000000000000000000000000000000000000000..f3ed9d00c27827fa40a37bf94fe6b46234b0bd88 --- /dev/null +++ b/handbook/handbook-main/guides/buddy_guidance.txt @@ -0,0 +1,17 @@ +# Buddy Guidance + +You've been chosen to be a buddy to a new team member - Yay. Here's some guidance to help you find out what's expected. + +A buddy is a friend at Made Tech. Someone friendly who helps new team members connect and find their way, especially in their first 3 months with us when everything is new to them. + +Being a buddy is a really important way to help a new person integrate into Made Tech. +When we're back in the office, you will show them all the good lunch places near the office, take them out for a coffee or lunch and help them find their way in the local area. + +As we're working remotely currently, most or all of your interactions will happen on video calls which we call 'coffee chats'. + +## Buddies +- proactively and frequently check in with a new starter to see how they are doing. In the first 3 months you may check in 2-3 times per month. After that time you can work out what suits you both, i.e. monthly catchup/remote lunch +- offer their help and answer all questions (or direct to the right person) +- explain how things work here and where to find stuff +- are available to the new team member for any guidance and often just a chat +- are friendly and helpful humans who are here to welcome all our new team members diff --git a/handbook/handbook-main/guides/chalet_time_policy.txt b/handbook/handbook-main/guides/chalet_time_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..816e330f7c88e03b979c071b7d66306bd43f7e03 --- /dev/null +++ b/handbook/handbook-main/guides/chalet_time_policy.txt @@ -0,0 +1,168 @@ +# Chalet time policy + +This document describes how people should spend time when not on client work. This is known as Chalet Time. + +Chalet time should be used to build skills, grow Made Tech’s business and contribute to Communities of Practice. + +## What is chalet time? + +Chalet time is when people are not on client work. For example... + +- A two week gap between someone finishing the software engineering academy and going onto a client project. +- A week between a new starter joining the company and their first client project. +- A lead designer having three days between their current client project and the next. + +Occasional chalet time is a common part of a business like ours, as client work isn’t always going to perfectly match our skills and availability. It's a good time to focus on other activities. + +## Getting started in the chalet + +Please follow these steps when you join the chalet. + +### 1. Join the [`#chalet`][1] Slack channel. +This channel provides up-to-date information on chalet activities and practices. You can use it to ask questions and arrange collaborative work. +### 2. Add mandatory chalet meetings to your Google Calendar. +You can find Google Calendar links for chalet meetings pinned to the top of the [`#chalet`][1] Slack channel. +Members of the Chalet are expected attend these meetings, so that we can: + +- Help people use their chalet time well +- Share opportunities and events +- Help people with blockers +- Build a sense of community + +### 3. Join the [Chalet Community Board][2]. +Use this board to discover tasks you can undertake while in the chalet, including work with Made Tech departments and Communities of Practice. You can also learn about chalet members and their current projects. + +## Responsibility for using chalet time usefully + +Chalet members and their line managers will be responsible for ensuring this time is used usefully. + +Line management should therefore focus partly on: + +- Agree weekly goals to use chalet time according the highest priorities +- Check progress against goals for chalet time in bob +- Agree a plan to get someone onto billed client work +- Identify blockers someone has doing activities with their chalet time +- Identify if someone needs help reaching out to a part of the organisation, so that they can assist or shadow. This could involve introducing someone to a team or advocating on their behalf. + +Each Head of Capability Practice is ultimately accountable for everyone in their practice using chalet time the right way. This will be measured by the average amount of people’s time billed to a client, also known as utilisation. + +## Priorities for chalet time + +The priorities for using chalet time will always stay the same, but the activities that a chalet member should do will depend on their roles and availability. + +If there are no activities that need to be done that match the chalet member's role and availability, chalet time should be used for the next highest priority. For example, if there are no activities that someone could do to find new opportunities on client teams or new business and revenue, that person should do hiring activities. + +### 1. New opportunities on client teams + +1. Billed opportunities, where clients pay for someone’s time +2. Invested opportunities, working on a client team, but not billed to begin with, showing value first +3. Shadowing, getting experience of how teams work + +### 2. New business and revenue + +1. Bid writing - leading / pairing / shadowing / case studies / research +2. Support marketing team create content, like blogging, case studies, talks that promote Made Tech + +### 3. Hiring + +1. Pairing on interviews +2. Outreach to potential candidates + +### 4. Research and development + +1. Product development +2. Research projects + +### 5. Communities of Practice (CoP) + +- CoPs have regular meetings and ongoing activities. To participate in these, search Slack for channels starting with `#cop`. +- CoPs will post opportunities to the [`#chalet`][1] Slack channel and the [Chalet Community Board][2]. + +### 6. Learning time + +- Reading +- Training courses +- Conferences +- Pairing and group learning + +### 7. Holiday that can flexibly be moved + +## Booking & scheduling chalet time + +### 1. New opportunities on client teams + +Billed or invested time will be booked by the Scheduling team, just like when someone joins a client team. The chalet member will fill out timesheets for time spent in this team. + +Shadowing should be recorded as ‘Bench/Chalet’ in timesheets. + +### 2. New business and revenue + +Bid writing will be booked by the Scheduling team. The chalet member will fill out timesheets for time spent on the bid. + +Marketing activities should be recorded as ‘Bench/Chalet’ in timesheets. + +### 3. Hiring + +This time should be recorded as ‘Hiring’ in timesheets. + +### 4. Research and development + +This time should be recorded as ‘R&D’ time in timesheets. + +### 5. Communities of Practice + +This time should be recorded as ‘Bench/Chalet’ in timesheets. + +### 6. Learning time + +If your learning activity will make you unavailable for a delivery (eg. a conference or exam) please book this as 'Learning Time' in Bob and let your line manager know. Record this as 'Learning Time' in timesheets. + +Learning activities that won't make you unavailable for a delivery (eg. reading, group learning) should be recorded as ‘Bench/Chalet’ in timesheets. + +We're actively reviewing the Learning process so this may change. If you have any questions please post them in the [`#supply-learning-and-development`][4] Slack channel. + +### 7. Holiday + +Chalet members will [book holiday][5] in the normal way. + +## Responsibility to make activities visible and doable + +Various parts of the business will be responsible for making people aware of activities they can do with chalet time: + +### 1. New opportunities on client teams + +A list of live client accounts is pinned to the [`#chalet`][1] Slack channel. This can be used to learn about clients, and to find opportunities to join client teams. + +Line managers of chalet members will help find opportunities and advocate for them to join client teams, either billed, invested or shadowing. + +### 2. New revenue and business + +Each week, the Bids team will send the Scheduling team details of bids that chalet members can contribute to. + +The Marketing team will share tasks that chalet members can do to promote Made Tech. These will be posted in the [Chalet Community Board][2]. If you need more information about a task, ask the person who created the ticket or post in the [`#team-marketing`][3] Slack channel. + +If you have an idea for a blog post contact James Holloway of the Marketing Team. You can also contact relevant CoPs and teams for input. + +### 3. Hiring + +The Scheduling team will give the Talent Team Coordinators access to the Kimble report of who has chalet time. They can be asked to do extra hiring interviews, or undertake training to do so. + +### 4. Research and development + +The R&D team will add tasks to the [Chalet Community Board][2]. These tasks often involve helping to build products or research new opportunities. + +### 5. Communities of Practice + +Capability and Delivery Heads will maintain a visible backlog of tasks in the [Chalet Community Board][2]. Chalet members can undertake these to improve their community of practice. + +## Length of chalet time activities + +Chalet time activities must be able to deliver some value in small blocks of time: half day, 1 day or 3–5 days. This is so that chalet time can add value if someone joins a client team at short notice. + +Some activities may need more than 5 days. These should still be able to deliver business or personal value in increments of a half day, 1 day or 3–5 days. + +[1]: https://madetechteam.slack.com/archives/C03F23K2RL0 "Chalet Time Team Slack Channel" +[2]: https://trello.com/b/7lSGB2Xw/chalet-community-board "Chalet Community Board" +[3]: https://madetechteam.slack.com/archives/C01MMH7DGUA "Marketing Team Slack Channel" +[4]: https://madetechteam.slack.com/archives/C0226JKA39T "Supply Learning and Development Slack Channel" +[5]: https://github.com/madetech/handbook/blob/main/benefits/taking_holiday.md "Taking Holiday" diff --git a/handbook/handbook-main/guides/cloud/aws_certification_advice.txt b/handbook/handbook-main/guides/cloud/aws_certification_advice.txt new file mode 100644 index 0000000000000000000000000000000000000000..3c50987e9acd0c76f31d459fa6ee7201d71a91a3 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/aws_certification_advice.txt @@ -0,0 +1,143 @@ +# AWS Certification Advice + +- [AWS Certification Advice](#aws-certification-advice) + - [Purpose of this guide](#purpose-of-this-guide) + - [General](#general) + - [Certification Costs](#certification-costs) + - [Expensing an Exam](#expensing-an-exam) + - [Exams charged in USD](#exams-charged-in-usd) + - [AWS Business Training](#aws-business-training) + - [AWS Technical Training](#aws-technical-training) + - [AWS Certified Cloud Practitioner](#aws-certified-cloud-practitioner) + - [Recommended Online Training](#recommended-online-training) + - [AWS DevOps Engineer Pathway](#aws-devops-engineer-pathway) + - [AWS Certified Developer - Associate](#aws-certified-developer---associate) + - [Recommended Online Training](#recommended-online-training-1) + - [AWS Certified SysOps Administrator - Associate](#aws-certified-sysops-administrator---associate) + - [Recommended Online Training](#recommended-online-training-2) + - [AWS Certified DevOps Engineer - Professional](#aws-certified-devops-engineer---professional) + - [Recommended Online Training](#recommended-online-training-3) + - [AWS Solutions Architect Pathway](#aws-solutions-architect-pathway) + - [AWS Certified Solutions Architect - Associate](#aws-certified-solutions-architect---associate) + - [Recommended Online Training](#recommended-online-training-4) + - [AWS Certified Solutions Architect - Professional](#aws-certified-solutions-architect---professional) + - [Recommended Online Training](#recommended-online-training-5) + - [AWS Speciality Certifications](#aws-speciality-certifications) + +## Purpose of this guide + +Made Tech are an [AWS Advanced Consulting Partner](https://partners.amazonaws.com/partners/001E0000016ppWOIAY/Made%20Tech) and encourage both technical and non-technical staff to undertake AWS Training and Certifications. This guide will detail some training paths and associated costs. + +AWS provides some non-technical training via the AWS Partner Portal. Guidance on how to create an account and take advantage of this training can be found [here](aws_partner_certs.md). + +## General + +A guide on how to create an AWS Certification account and link it to your Made Tech AWS Partner Account is located [here](aws_partner_certs.md#creating-your-accounts) + +All AWS Exams can be taken remotely from home with either PSI or Pearson Vue. + +## Certification Costs + +Booking an AWS exam costs vary depending on the level of the exam. + +| Exam | Cost | Cost inc tax | +| --- | --- | --- | +| AWS Cloud Practitioner | $100 | $120 | +| AWS Associate Level (Developer, SysOps, Architect) | $150 | $180 | +| AWS Professional Level (DevOps Engineer, Architect) | $300 | $360 | +| AWS Speciality Exams (Security, Networking, Database, ML, Data) | $300 | $360 | + +Each time you pass an AWS Exam you receive a [free practice exam and 50% off voucher](https://www.certmetrics.com/amazon/candidate/benefit_summary.aspx) for the next exam. + +This means an individual could achieve all 11 AWS Certifications for $1650! + +### Expensing an Exam + +An exam can be expensed. In order to do this, follow the [expenses guide](https://github.com/madetech/handbook/blob/main/guides/compensation/expenses.md). The account should be set to `Other Training Costs` and the name of the exam used as the description. + +#### Exams charged in USD + +If the exam is charged in USD, there are two ways you can submit your expense claim in Xero. + +1. (recommended) Use the currency selection drop down within the “purchase amount” field, select `USD` and enter the amount shown on your invoice. Xero will automatically convert your expense for you to GBP. The amount converted may vary slightly compared to what you were charged. +1. Input the amount you were charged in GBP. You will then need to provide proof of purchase (bank statement etc.) which you will have to edit/merge onto the same attachment as the invoice, since Xero only allows 1 attachment. + +## AWS Business Training + +All non-tech employees are encouraged to undertake the [AWS Business Professional Training](https://aws.amazon.com/partners/training/path-bus-pro/) from the AWS Partner Portal. + +## AWS Technical Training + +All technical employees are encouraged to undertake the [AWS Technical Professional Training](https://aws.amazon.com/partners/training/path-tech-pro/) from the AWS Partner Portal. + +## AWS Certified Cloud Practitioner + +The next stage in the AWS Certification journey is the [AWS Certified Cloud Practitioner](https://aws.amazon.com/certification/certified-cloud-practitioner) which is easily achievable by both tech and non-tech employees. + +#### Recommended Online Training +1. [Stephane Maarek - Udemy](https://www.udemy.com/course/aws-certified-cloud-practitioner-new/) +2. [Pluralsight](https://www.pluralsight.com/paths/aws-certified-cloud-practitioner-clf-c02) +3. [Whizlabs](https://www.whizlabs.com/aws-certified-cloud-practitioner/) + You can do shorter tests on specific areas (databases, compute, etc.) so you can target specific knowledge. + Also if you run through them in Practice mode you can view answers and explanations as you go + + +## AWS DevOps Engineer Pathway + +After following the basic training and achieving the AWS Certified Cloud Practitioner Certification, Engineers working towards achieving the AWS DevOps Professional Certification should follow this pathway. + +### AWS Certified Developer - Associate + +The [AWS Certified Developer - Associate](https://aws.amazon.com/certification/certified-developer-associate) is probably the most enjoyable certification to work towards for software developers, covering a lot of the developer tools and fun things like Lambda/API Gateway/SQS/SNS etc... + +#### Recommended Online Training +1. [Stephane Maarek - Udemy](https://www.udemy.com/course/aws-certified-developer-associate-dva-c01/) +2. [Pluralsight](https://www.pluralsight.com/paths/aws-certified-developer-associate-dva-c01) + +### AWS Certified SysOps Administrator - Associate + +The [AWS Certified SysOps Administrator - Associate](https://aws.amazon.com/certification/certified-sysops-admin-associate) is the next step towards the DevOps Pro certification, covering the following domains. Monitoring & Reporting, High Availability, Deployment & Provisioning, Storage & Data Management, Security & Compliance, Networking and Automation & Optimisation. + +#### Recommended Online Training +1. [Cantrill.io](https://learn.cantrill.io/p/aws-certified-sysops-administrator-associate) +2. [ACloudGuru](https://learn.acloud.guru/course/aws-certified-sysops-administrator-associate) + +### AWS Certified DevOps Engineer - Professional + +The [AWS Certified DevOps Engineer - Professional](https://aws.amazon.com/certification/certified-devops-engineer-professional/) is the last step in the DevOps Pro certification pathway, covering the following domains. SDLC Automation, Configuration Management & Infrastructure as Code, Monitoring & Logging, Policies & Standards Automation, Incident & Event Response, High Availability, Fault Tolerance & Disaster Recovery. + +#### Recommended Online Training +1. [Stephane Maarek - Udemy](https://www.udemy.com/course/aws-certified-devops-engineer-professional-hands-on/) +2. [Pluralsight](https://www.pluralsight.com/paths/aws-certified-devops-engineer-professional) + + +## AWS Solutions Architect Pathway + +After following the basic training and achieving the AWS Certified Cloud Practitioner Certification, Engineers working towards achieving the AWS Certified Solutions Architect - Professional should follow this pathway. + +This pathway only consists of the Associate and Pro level Solutions Architect exams, but I would advise looking at other the Associate level courses before undertaking the AWS Solutions Architect Pro, is it is very difficult exam! + +### AWS Certified Solutions Architect - Associate + +The [AWS Certified Solutions Architect - Associate](https://aws.amazon.com/certification/certified-solutions-architect-associate/) is the Associate level Solutions Architect Certification and covers the following domains. Design Resilient Architectures, Design High-Performing Architectures, Design Secure Application & Architectures and Design Cost-Optimisted Architectures. + +#### Recommended Online Training +1. [Cantrill.io](https://learn.cantrill.io/p/aws-certified-solutions-architect-associate-saa-c02) +2. [ACloudGuru](https://learn.acloud.guru/course/aws-certified-solutions-architect-associate) + +### AWS Certified Solutions Architect - Professional + +The [AWS Certified Solutions Architect - Professional](https://aws.amazon.com/certification/certified-solutions-architect-professional) is the professional level Solutions Architect Certification and probably the most difficult AWS Exam. It covers the following domains. Design for Organisational Complexity, Design for New Solutions, Migration Planning, Cost Control and Continuous Improvement for Existing Solutions. + +#### Recommended Online Training +1. [Cantrill.io](https://learn.cantrill.io/p/aws-certified-solutions-architect-professional) +2. [ACloudGuru](https://learn.acloud.guru/course/aws-certified-solutions-architect-professional/dashboard) + + +## AWS Speciality Certifications + +1. [AWS Certified Advanced Networking - Specialty](https://aws.amazon.com/certification/certified-advanced-networking-specialty) +2. [AWS Certified Data Analytics - Specialty](https://aws.amazon.com/certification/certified-data-analytics-specialty) +3. [AWS Certified Database - Specialty](https://aws.amazon.com/certification/certified-database-specialty) +4. [AWS Certified Machine Learning – Specialty](https://aws.amazon.com/certification/certified-machine-learning-specialty) +5. [AWS Certified Security - Specialty](https://aws.amazon.com/certification/certified-security-specialty) diff --git a/handbook/handbook-main/guides/cloud/aws_partner_certs.txt b/handbook/handbook-main/guides/cloud/aws_partner_certs.txt new file mode 100644 index 0000000000000000000000000000000000000000..126576cdf9cdfbb3406f9379b38abdae8abe7230 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/aws_partner_certs.txt @@ -0,0 +1,75 @@ +# AWS Training & Certification + +- [Purpose of this guide](#purpose-of-this-guide) +- [AWS Certification](#aws-certification) +- [Creating your accounts](#creating-your-accounts) + - [AWS Training Account](#aws-training-account) + - [AWS Partner Network Account](#aws-partner-network-account) +- [Linking your Amazon and AWS Partner Accounts](#linking-your-amazon-and-aws-partner-accounts) +- [Learning Paths](#learning-paths) + - [AWS Business Professional](#aws-business-professional) + - [AWS Technical Professional](#aws-technical-professional) +- [Employee offboarding](#employee-offboarding) + +## Purpose of this guide + +Made Tech are an [AWS Advanced Consulting Partner](https://partners.amazonaws.com/partners/001E0000016ppWOIAY/Made%20Tech) and require all Made Tech employees to create a user account within the AWS Partner Portal as part of their onboarding process for a number of reasons. + + 1. Access to free AWS Partner Training materials. + 2. Linking employees personal AWS Certification accounts to our Partner account. + +# AWS Certification + +As a Made Tech employee you will be encouraged and supported in taking AWS Certifications. You are advised to create your AWS Certification account using a personal email address so any AWS Certifications you achieve belong to you. This can be the same Amazon account login that you use for doing your shopping on [Amazon](https://www.amazon.co.uk), so you maybe already have an account! + + +AWS has an extensive Training and Certification framework, and there is a lot of great content we can utilise as an AWS Partner to develop and improve our knowledge when working with AWS services. + +We aim for every Made Tech employee to achieve the AWS Cloud Practitioner Certification, and the AWS Partner Portal provides some valuable free entry level training paths towards taking the Cloud Practitioner exam. + +# Creating your accounts + +There are 2 types of accounts needed to take full advantage of the AWS Training and Certification platform. + +- [AWS Training Account](#aws-training-account) +- [AWS Partner Network Account](#aws-partner-network-account) + +## AWS Training Account + +If you have a personal Amazon account you can simply log in to [AWS Training and Certification](https://www.aws.training/SignIn) using the **left side** login. + +This will land you on yet another page where you should click `Login to your account` and will eventually land you in your [Certmetrics Account](https://www.certmetrics.com/amazon/). + +## AWS Partner Network Account + +Head over to the [AWS Partner Network registration guide](aws_partner_registration.md) that will take you through the steps to create an account on the Amazon Partner Network. + +# Linking your Amazon and AWS Partner Accounts + +In order for your AWS Certifications to appear within the Made Tech AWS Partner account, you need to link your person Amazon account to your Amazon Partner Network account. + +1. [Log in to the AWS Partner Network](https://partnercentral.awspartner.com/APNLogin) with your `@madetech.com` email address. +2. Click on `View My Profile` from the left hand `QUICK LINKS` menu. +3. Click the blue `Edit` button. +4. Under `AWS CERTIFICATION` add your personal AWS Certification email address to the `AWS T&C Account Email` field, and select `Yes` for `I consent to share my AWS Certifications with "Made Tech" *` + +Your AWS Certifications will not immediately appear, so check back at a later date. + +# Learning Paths + +## AWS Business Professional + +The recommended AWS Partner training path for non-technical roles is the [AWS Business Professional](https://aws.amazon.com/partners/training/path-bus-pro/). + +## AWS Technical Professional + +The recommended AWS Partner training path for technical roles is the [AWS Technical Professional](https://aws.amazon.com/partners/training/path-tech-pro/). + +# Employee offboarding + +When an employee leaves Made Tech, they should unlink their personal Certification email address from their `@madetech.com` AWS Partner Account. This should be done while they have access to their `@madetech.com` email address as part of their offboarding. + +1. [Log in to the AWS Partner Network](https://partnercentral.awspartner.com/APNLogin) with your `@madetech.com` email address. +2. Click on `View My Profile` from the left hand `QUICK LINKS` menu. +3. Click the blue `Edit` button. +4. Under `AWS CERTIFICATION` remove your personal AWS Certification email address to the `AWS T&C Account Email` field, and select `No` for `I consent to share my AWS Certifications with "Made Tech" *` diff --git a/handbook/handbook-main/guides/cloud/aws_partner_registration.txt b/handbook/handbook-main/guides/cloud/aws_partner_registration.txt new file mode 100644 index 0000000000000000000000000000000000000000..3a2d2a6742b9411d6554fde8b74d778fc6570bdf --- /dev/null +++ b/handbook/handbook-main/guides/cloud/aws_partner_registration.txt @@ -0,0 +1,68 @@ +# AWS Partner Network + +- [AWS Partner Network](#aws-partner-network) + - [Registration](#registration) + - [Step 1: Sign in](#step-1-sign-in) + - [Step 2: Join AWS Partner Network](#step-2-join-aws-partner-network) + - [Step 3: Let's get started](#step-3-lets-get-started) + - [Step 4: Create an APN account](#step-4-create-an-apn-account) + - [Step 5: Security code and password](#step-5-security-code-and-password) + - [Step 6: Why would you like to join APN?](#step-6-why-would-you-like-to-join-apn) + - [Step 7: Tell us about yourself](#step-7-tell-us-about-yourself) + - [Step 8: Congratulations](#step-8-congratulations) + +## Registration + +### Step 1: Sign in + +Go to the [aws.training sign in page](https://www.aws.training/SignIn) and click the right hand "Sign In" button to begin creating your Amazon Partner Network account. + +![](images/sign-in.png) + +### Step 2: Join AWS Partner Network + +Click "Join AWS Partner Network" + +![](images/aws-partner-network-sign-in.png) + +### Step 3: Let's get started + +Click "Let's get started" + +![](images/aws-partner-network-get-started.png) + +### Step 4: Create an APN account + +When creating an APN account you should use your **@madetech.com** email address to register. + +Once you have registered, a security code will be emailed to you to use in the next step. + +![](images/aws-partner-network-create-account.png) + +### Step 5: Security code and password + +Enter the security code from the email you received along with a password. + +![](images/aws-partner-network-security-code.png) + +### Step 6: Why would you like to join APN? + +Select how you heard about APN and what you are looking for support with. + +![](images/aws-partner-network-why.png) + +### Step 7: Tell us about yourself + +Fill out your contact information, whether you consent to share training and certifications with MadeTech and whether you'd like to receive AWS news and offers. + +**NOTE** + +- Use your **personal Amazon email** for the "AWS Training and Certification Account Email" section of the form in order to take your certifications with you should you leave MadeTech. + +![](images/aws-partner-network-about-yourself.png) + +### Step 8: Congratulations + +You have now registered for the AWS Partner Network + +![](images/aws-partner-network-congratulations.png) \ No newline at end of file diff --git a/handbook/handbook-main/guides/cloud/aws_sandbox.txt b/handbook/handbook-main/guides/cloud/aws_sandbox.txt new file mode 100644 index 0000000000000000000000000000000000000000..2d126aedacae1a15e246549432db111b398388ec --- /dev/null +++ b/handbook/handbook-main/guides/cloud/aws_sandbox.txt @@ -0,0 +1,95 @@ +# Made Tech AWS Sandbox + +## Overview + +The Made Tech AWS Sandbox accounts are primarily used for individuals' personal development and testing. We run [AWS SSO](https://aws.amazon.com/single-sign-on/) to simplify and secure the IAM aspect of accessing this account. + +There are 2 accounts you can use: +- [Playground account](#playground-account) +- [Devops Pairing Interviews Account](#devops-pairing-interviews-account) + +## Playground account + +### Usage Policy + +This AWS account should only be used for temporary short lived test type projects and resources are destroyed every Friday evening. + +The Terraform and config for this cleanup task lives in this [aws-sandbox](https://github.com/madetech/aws-sandbox) GitHub repo. + +### Security + +The AWS Sandbox account is restricted by several service control policies blocking creation of IAM users, and is locked down to three regions (eu-west-1, eu-west-2 and us-east-1) + +### Access + +1. Request for a new user account in the #cop-cloud Slack channel in the `SandboxUsers` group. +2. AWS SSO login credentials will be emailed to you. +3. Follow the instructions and setup MFA. +4. Login via [https://madetech.awsapps.com/start/](https://madetech.awsapps.com/start/) + +### CLI Usage + +Use [aws-vault](https://github.com/99designs/aws-vault) to run CLI commands. + +Reasons for using this tool can be found [here](https://github.com/99designs/aws-vault#how-it-works). + +1. Install [aws-vault](https://github.com/99designs/aws-vault#installing) +2. Add the following config to your `~/.aws/config` file. + ``` + [profile mt-playground] + sso_start_url=https://madetech.awsapps.com/start + sso_region=eu-west-2 + sso_account_id=261219435789 + sso_role_name=SandboxUser + output=json + ``` + + 3. Test with `aws-vault exec mt-playground -- aws sts get-caller-identity` + 4. This pops open a browser where you need to login to create a session. + 5. Run any CLI based command in the same way e.g `aws-vault exec mt-playground -- terraform apply` + +## Devops Pairing Interviews Account + +This is a separate account for use in devops pairing exercises. + +This account differs in two ways from the main sandbox: +- It allows the creation of iam users. +- It **deletes all resources inside it every day!** + +### Access +Only employees that are conducting devops pairing interviews will be given access + +1. Request your user account to be added to the `DevopsPairingInterviewer` group in the #cop-cloud Slack channel. + +### CLI Usage + +Use [aws-vault](https://github.com/99designs/aws-vault) to run CLI commands. + +Reasons for using this tool can be found [here](https://github.com/99designs/aws-vault#how-it-works). + +1. Install [aws-vault](https://github.com/99designs/aws-vault#installing) +2. Add the following config to your `~/.aws/config` file. + +``` + [profile mt-devops] + sso_start_url=https://madetech.awsapps.com/start + sso_region=eu-west-2 + sso_account_id=612473995106 + sso_role_name=SandboxUser + output=json + ``` + +## Admin actions +This section is for SSO administrators (i.e. pepole in the `@sandbox-admins` group on slack) + +### Adding new users +For when a user has requested to be added to the AWS sandbox +- Login to sso https://madetech.awsapps.com/start#/ +- Click on: `aws account` > `Made Tech` > `Management console` +- Now go to https://eu-west-2.console.aws.amazon.com/singlesignon/identity/home?region=eu-west-2#!/users +- On the top right click `add user` +- Fill in their details (use the part before the @ in their email as username) +- Add them to the "SandboxUsers" group +- They should now get a email invite to join (valid for the next 7 days) + + diff --git a/handbook/handbook-main/guides/cloud/azure_partner_certs.txt b/handbook/handbook-main/guides/cloud/azure_partner_certs.txt new file mode 100644 index 0000000000000000000000000000000000000000..4e7a082c4c0f490813a6731243c0a4f480efc088 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/azure_partner_certs.txt @@ -0,0 +1,32 @@ +# Azure Certification + +- [Azure Certification](#azure-certification) + - [Purpose of this guide](#purpose-of-this-guide) +- [Azure Partnership](#azure-partnership) +- [Linking your Azure certifications to the Azure Partner Portal](#linking-your-azure-certifications-to-the-azure-partner-portal) + +## Purpose of this guide + +Made Tech are a Microsoft Azure Partner and require all Made Tech employees with Microsoft certifications to link their Microsoft Certification Account to the Made Tech Azure Partner Portal as part of their onboarding process for a number of reasons. + + 1. Access to free Azure Partner Training materials. + 2. Maintaining and aquiring partner levels with Azure. + +# Azure Partnership + +As a Made Tech employee you will be encouraged and supported in taking Azure Certifications. You are advised to create your Microsoft Certification account using a personal email address so any Azure Certifications you achieve belong to you. + +Azure has an extensive Training and Certification framework, and there is a lot of great content we can utilise as a Microsoft Azure Partner to develop and improve our knowledge when working with Azure services. + +# Linking your Azure certifications to the Azure Partner Portal + +In order for your Azure Certifications to appear within the Made Tech Azure Partner Portal, you need to link your personal Microsoft Certification Account to the Made Tech Azure Partner Portal. + +Before you do this, you will need to have completed at least one exam or certification in the [Microsoft Learn portal](https://learn.microsoft.com/). + +1. Go to the [Partner Portal](https://partner.microsoft.com/pc/Users/MyAccount). +2. Sign in using your **Made Tech Microsoft account**. This should take you to the account page, as shown below. +3. Click on the “Associate Microsoft Learning account” button. +![](images/azure-partner-portal-page.png) +4. This will take you to a new log-in page. Here enter your personal **Microsoft Certification Account** credentials (these are the ones you used to sign up for the exam). +5. This will then redirect you back to the above account page and show that you have successfully linked your accounts to the Partner Portal. diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-about-yourself.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-about-yourself.png new file mode 100644 index 0000000000000000000000000000000000000000..f18cda15752ffeead1626c9d5f9af8c0b183bf6b --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-about-yourself.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:048a4d0ce311e5cde5e0470d0ba996fbf03b184cb2bad3a50f73008fd3620a8a +size 334522 diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-congratulations.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-congratulations.png new file mode 100644 index 0000000000000000000000000000000000000000..73d711a2dd5b9db148db5d62cbb76a3c176f43a3 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-congratulations.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:3315ed97c0cd8e4106b31c8083cba74a31497091fef46fab3eed56b8fd56432b +size 213542 diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-create-account.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-create-account.png new file mode 100644 index 0000000000000000000000000000000000000000..e017553dd01f29bc048857a237d5137c773cb1e5 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-create-account.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:9980100ff7e5203fc80c2614369f5015cc5ea268d3afb43d36423ade84eab967 +size 188717 diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-get-started.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-get-started.png new file mode 100644 index 0000000000000000000000000000000000000000..9845fafcca2718899ab000af6c4f1d7b0a2eebdc --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-get-started.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:cdc6e71a4413ff065423436bddc02b602c7843dbea9865872cb0cb6a2e5beb58 +size 526573 diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-security-code.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-security-code.png new file mode 100644 index 0000000000000000000000000000000000000000..fc5a779e59e315c264b586c1dd8fc3a0be501750 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-security-code.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:60d4b01658019350bf73f8b8548de226c8811fe35ba923ad7ad042f8eaf785ef +size 262084 diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-sign-in.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-sign-in.png new file mode 100644 index 0000000000000000000000000000000000000000..9435c393958fa55a16c2fd1bb63e6d6bb0e51900 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-sign-in.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:28078d3c91a83cd5f93db500067a377462213935b959f2a55eba9a4bab016b18 +size 200484 diff --git a/handbook/handbook-main/guides/cloud/images/aws-partner-network-why.png b/handbook/handbook-main/guides/cloud/images/aws-partner-network-why.png new file mode 100644 index 0000000000000000000000000000000000000000..7444890359211dce8a4f402a4cba1a7095ae4ba2 --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/aws-partner-network-why.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:6aeba96d31e7daaea97971fb9768c70aff34bc962112c0225d5b0e5e22231c39 +size 242078 diff --git a/handbook/handbook-main/guides/cloud/images/azure-partner-portal-page.png b/handbook/handbook-main/guides/cloud/images/azure-partner-portal-page.png new file mode 100644 index 0000000000000000000000000000000000000000..9e1da6595b72e19a126bd31cac9f0000dd04a1db --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/azure-partner-portal-page.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:dde980f3ac20291e4a520da822d197f016af5797c208d12222c348aea1f7809b +size 150863 diff --git a/handbook/handbook-main/guides/cloud/images/sign-in.png b/handbook/handbook-main/guides/cloud/images/sign-in.png new file mode 100644 index 0000000000000000000000000000000000000000..5c24433697afd13febb1f96a71810b688669695e --- /dev/null +++ b/handbook/handbook-main/guides/cloud/images/sign-in.png @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:b5ce1de71da9b4d8824bf6e30cd12ce815a27fbb4774c884bbe23887088cb4de +size 437685 diff --git a/handbook/handbook-main/guides/compensation/expenses.txt b/handbook/handbook-main/guides/compensation/expenses.txt new file mode 100644 index 0000000000000000000000000000000000000000..34418c0aa23e56d889062b6976e63a70e6fa87ec --- /dev/null +++ b/handbook/handbook-main/guides/compensation/expenses.txt @@ -0,0 +1,32 @@ +# Expenses + +There is now a fully documented Made Tech expenses policy which covers trains, travel, hotel accommodation, and reimbursement of other business expenses. As it is more detailed than the previous guidance, the policy has been changed to an internally facing document for now. [You can find the document here](https://docs.google.com/document/d/1NthAC1xepzAI07o40c6WxXHbPttNxaCidhJ22eJHD-k/edit#). + +There is additional information on [equipment to enable you to work from home](../../benefits/work_ready.md), and [eye tests](expenses/eyetest.md) on those pages. + +## Travel +Made Tech is also now using TravelPerk to enable you to book all your business travel in one place. Payment is made directly by Finance so you don’t have to pay for travel yourself. For more information on when and how to use this take a look at the [TravelPerk document](https://docs.google.com/document/d/12NiB2QxHZ5k8ajqP95fOo2I-GBKZQLuzQutKAiem0DQ/edit#) (internal link). + +### Railcards +You can expense Railcards for the use of business travel. Made Tech will reimburse the price of any yearly railcard purchased from April 26th 2023 onwards. If you leave Made Tech you will not be charged for it and dont need to return it, but you cannot expense a railcard during your notice period. + +To purchase and expense a railcard you need to; +- purchase a railcard +- add it to your TravelPerk account +- take a screenshot to show that it has been added +- share the image and receipt on Xero when expensing it back. + +## How do you expense? + +Expense claims need to be submitted via [Xero](https://login.xero.com/identity/user/login). If you don’t have a login please drop a message in #ops-finance or email [finance@madetech.com](mailto:finance@madetech.com). + +There is more detail in the policy but all claims must be made within 90 days, and will typically be paid within 2 weeks. + +There are also some approval processes in place: +- Normal expenses: Claims that align with the policy will be approved but any claims that are outside of the guidelines will need approval from your Head of Department. +- Account expenses: Expenses that are aligned to a specific delivery or account (e.g. client entertainment, travel to meetings, etc) should be agreed with the Delivery Manager and/or account team in advance. +- Events and conferences: Expenses need to be approved in advance by the relevant Head of Department. + +For all other information please read the policy document and send any questions to #ops-finance or [finance@madetech.com](mailto:finance@madetech.com). + + diff --git a/handbook/handbook-main/guides/compensation/expenses/eyetest.txt b/handbook/handbook-main/guides/compensation/expenses/eyetest.txt new file mode 100644 index 0000000000000000000000000000000000000000..2f5adc83bcfb1fd29bc563b9e099ae259fe30aeb --- /dev/null +++ b/handbook/handbook-main/guides/compensation/expenses/eyetest.txt @@ -0,0 +1,19 @@ +# Eye Test Expenses + +Everyone is able to claim back the costs of an annual eye test. You need to: + +- Book the eye test yourself and get a receipt +- Submit the receipt for the eye test through Xero, using the category 'Staff discrentionary benefit'. + +## Claiming for Lenses and Frames + +If the outcome of the eye test is that you require glasses for the use of Display Screen Equipment (DSE) or (visual/video display unit (VDU), where an ordinary prescription is not suitable, then Made Tech will make a contribution towards the costs of a pair of glasses. + +- Made Tech will pay for the lenses plus an additional £60 toward any frames that you choose. +- After you purchase your frames and lenses, submit the receipts through Xero. + +Please request that the optician provides a report/copy of the prescription indicating these are required specifically for DSE or VDU use. + +**Note:** If you use Westfield Health you may want to reclaim the cost using their service instead, especially if you wish to purchase more expensive frames. + +If you have any questions on this please contact #ops diff --git a/handbook/handbook-main/guides/compensation/salary_pay_slips.txt b/handbook/handbook-main/guides/compensation/salary_pay_slips.txt new file mode 100644 index 0000000000000000000000000000000000000000..53eaf51901b03f2ea00b7c95899270abfe3ba44e --- /dev/null +++ b/handbook/handbook-main/guides/compensation/salary_pay_slips.txt @@ -0,0 +1,9 @@ +# Salary & Pay Slips + +We're paid on the 28th of the month, or the Friday before if the 28th falls on a weekend or during a bank holiday. + +Payroll cut off usually falls on the 18th of the month and so if you started on or after that date, you would likely fall into the following month's pay run and recieve backpay for any period worked in the previous month. For example if you started on the 23rd January, your first pay day would be the 28th February and you would recieve pay from 23rd Jan - 28th Feb in that first pay check. + +Our Finance team are responsible for payroll and you will receive an invite to register for our payslip provider just before your first pay day and then receive an e mail each month on pay day confirming when your pay slip is available. + +If you've got any queries on your salary or payslip, please send these to finance@madetech.com diff --git a/handbook/handbook-main/guides/compensation/salary_reviews.txt b/handbook/handbook-main/guides/compensation/salary_reviews.txt new file mode 100644 index 0000000000000000000000000000000000000000..a973aa57d8b5c719f5e49e9d0b72264b9b7e064e --- /dev/null +++ b/handbook/handbook-main/guides/compensation/salary_reviews.txt @@ -0,0 +1,5 @@ +# Salary Reviews + +Salaries are reviewed in line with our pay review policy - once, each business financial year. They may be adjusted taking into consideration business performance, individual performance and market rates. We reserve the right not to increase salary at review. An increase one year does not set any precedent or influence any future reviews. + +The other path to a salary adjustment is via our Internal mobility process (promotions or lateral moves) within the financial year. diff --git a/handbook/handbook-main/guides/contributing_to_the_handbook.txt b/handbook/handbook-main/guides/contributing_to_the_handbook.txt new file mode 100644 index 0000000000000000000000000000000000000000..4bf09939f8bff30a901047f6fba3ce2d54b9b167 --- /dev/null +++ b/handbook/handbook-main/guides/contributing_to_the_handbook.txt @@ -0,0 +1,77 @@ +# Contributing to the Handbook + +This guide aims to make it easier to submit changes to the Handbook without using `git` or a text editor. + +## Updating and adding pages in Github + +### Creating a page + +1. [Go to the handbook.](https://github.com/madetech/handbook) +2. Click through to the folder you want. +3. Click "Create new file" +4. Type out your contents under "Edit new file" using [Markdown](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). +5. Preview your changes at any time by clicking "Preview". +6. When you're happy with your page, write a short description under "Commit new file". For example, "Add Flexible Holiday Page". +7. Select "Create a new branch for this commit" and give it a name relevant to your change. For example, "add-flexible-holiday-page". +8. Submit the change by clicking "Propose new file". +9. You will be then be able to create a Pull Request to get review of your new page. Click "Create pull request", then share the link with people! + +### Updating a page + +1. [Go to the handbook.](https://github.com/madetech/handbook) +2. Navigate to the page you wish to update. +3. Click the pencil button in the top right +4. Make the necessary changes using [Markdown](https://docs.github.com/en/github/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax). +5. Preview your changes at any time by clicking "Preview". +6. When you're happy with your page, click "Commit changes" and write a short description under "Commit message". For example "update pension scheme page to include the people team email" +7. Select "Create a new branch for this commit" and give it a name relevant to your change. For example, "update-flexible-holiday-page". +8. Submit the change by clicking "Propose changes". +9. You will be then be able to create a Pull Request to get review of your new page. Click "Create pull request", then share the link with people! + +### Addressing review + +1. Click on the "Files changed" tab on your Pull Request. +2. Click on the pencil icon in the toolbar above the file content. +3. Make your changes as before, previewing until you're happy with them. +4. Under "Commit Changes" describe what this change does. For example, "Fix typo" or "Extend section on getting a company credit card". +5. Keep the selected option as "Commit directly". You don't need to create a new branch for every change. +6. Press "Commit changes". + +### Finalising the change + +1. Get feedback from the wider company and address any feedback. Once you've had your Pull Request approved, you're ready to finalise your change. +2. On the "Conversation" tab of your Pull Request, click "Merge pull request". +3. Your new page will now be visible in the Handbook. + +## Approval and merging + +There are broadly two types of change to the handbook, each with a different approval flow. +If in doubt, default to the most strict method (Significant changes or additions) or ask for advice on Slack. + +1. Significant changes or additions +2. Uncontroversial clarifications + + +### 1. Significant changes or additions + +This includes changes to policies, changes to the way people are expected to work, changes that express a departure from a previous community norm, etc. + +1. Open pull request +2. Shout about the pull request in all relevant Slack channels. This should include announcements, but if it relates to a particular part of Made Tech, also in +the channels more relevant to those people. +3. Allow enough time for people to review and comment, remembering that they probably have busy schedules. One to two weeks is probably sensible. +4. Manage the conversation, seek approvals on GitHub, address feedback. +5. When it feels like something close to consensus is established, merge. + +Consensus is subjective, and we can't make a rule that catches all of the important ways it can look. +If you're unsure if you've got enough of it, reach out to the community on Slack. + +### 2. Uncontroversial clarifications + +This includes spelling mistakes, poorly worded sections, and writing something down that we all are doing anyway, + +1. Open pull request +2. Shout about it in relevant channels +3. Address feedback +4. Wait for an approval +5. Merge diff --git a/handbook/handbook-main/guides/equality-diversity-and-inclusion/README.txt b/handbook/handbook-main/guides/equality-diversity-and-inclusion/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..c444bffe64006c946cccd688fb93f1399e0a2a6c --- /dev/null +++ b/handbook/handbook-main/guides/equality-diversity-and-inclusion/README.txt @@ -0,0 +1,21 @@ +# Equality, Diversity & Inclusion at Made Tech + +Creating a better, fairer society is part of our purpose as an organisation. This starts with our people. + +We strive to make Made Tech an equitable, diverse and inclusive workplace and to provide a working environment that is free from discrimination at all times. + +We understand that everyone has varying needs. We’ll work to make sure that everyone’s needs are supported and met. + +We recognise that our different backgrounds, experiences, views, beliefs, cultures and physical/neurological differences represented enrich us as a company and as individuals. We embrace diversity in all of our activities and acknowledge that variety and difference are integral to the success and future development of our business. + +Read our [Equality, Diversity & Inclusion Policy](policy.md). + +## Teams and communities + +We have a number of ways we support equality, diversity and inclusion at Made Tech. + +We have a [diversity and inclusion service team](about-service-team.md) who are responsible for defining our strategy, setting KPIs and objectives, supporting the wider organisation to take action to deliver on these objectives, and reporting on progress to our leadership team and the wider company. This team is an escalation point for D&I related issues and manages the operation of equality data collection and reporting. + +We have a regular forum, our [diversity and inclusion community meetup](about-di-community.md) for discussing diversity and inclusion matters, scrutinising decisions being made by the diversity and inclusion service team, and making suggestions for future strategy. + +We support [open and closed community groups](about-open-and-closed-community.md) that meet to share experiences, raise issues and promote various aspects of diversity and inclusion. Open communities are free for anyone to join while closed communities are available to join by invite if you identify as belonging to that community. diff --git a/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-di-community.txt b/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-di-community.txt new file mode 100644 index 0000000000000000000000000000000000000000..32c0bab46e7d37cafe5dcf9887ddcc7344018289 --- /dev/null +++ b/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-di-community.txt @@ -0,0 +1,40 @@ +# Diversity and inclusion community + +The diversity and inclusion community is an opportunity for anyone at Made Tech to join the conversation on how we progress and promote diversity and inclusion across the business. + +In particular it was set up to: + +- Be open to anyone +- Meet on a regular basis +- Discuss ideas and issues +- Contribute to and review the strategy and plans of the [diversity and inclusion service team](./about-service-team.md) +- Hold the diversity and inclusion service team to account for delivering on their plan +- Review content changes before they are opened for wider review in the Handbook +- Escalate issues + +## When and how does the community meet? + +The community meets on a fortnightly basis via Google Meet. It is facilitated by a representative from the [diversity and inclusion service team](./about-service-team.md) or another nominated individual. The format uses the [Lean Coffee](https://leancoffee.org/) approach where topics can be suggested, prioritised by voting and then discussed in order. The invite is open on Google Calendar so you may add yourself to be reminded, [ask on Slack](https://madetechteam.slack.com/archives/CRAJF24CR) for more information. + +From time-to-time the diversity and inclusion service team may change the format as it sees fit to deliver on its goals and objectives. + +## Can I see what is discussed without joining? + +Minutes are added to the [inclusion repository](https://github.com/madetech/inclusion) for all meetings from the community up to 27/10/2021. +More recent minutes are available in this [Google Doc](https://docs.google.com/document/d/1JtDxGlA2v1uX2dycJQKZ_8Ff41t8jeriWqzFkGPQI7w/view) + +## How else can I get involved? + +The community also hangs out on [Slack](https://madetechteam.slack.com/archives/CRAJF24CR). You may also consider joining one or more [open or closed community groups](about-open-and-closed-community.md). + +## Who can join? + +Anyone can join the community meet up and Slack channel. It is attended by all available members of the [diversity and inclusion service team](./about-service-team.md) and anyone else who wants to join in or just watch. It’s totally fine to join for part of the meet up and to keep your camera off if you prefer. + +## How do I raise an issue? + +Issues can be raised using the Lean Coffee format ahead of and during community meetings. This can be useful for organisational-wide issues but if the issue is about someone’s personal experience it may be best to talk to a member of the [diversity and inclusion service team](./about-service-team.md) first. + +Anyone can contact the service team about an issue, or you could choose to raise it through a member of the diversity and inclusion community, or your diversity community group. Details on who to raise issues to are documented in the [#supply-diversity-and-inclusion Slack channel](https://madetechteam.slack.com/archives/CRAJF24CR). + +We have documented general guidance on [raising an issue](https://github.com/madetech/handbook/blob/main/guides/welfare/raising_an_issue.md) elsewhere in the Handbook, or you can get in touch with the People team if you’re not sure who the best person is to speak to. diff --git a/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-open-and-closed-community.txt b/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-open-and-closed-community.txt new file mode 100644 index 0000000000000000000000000000000000000000..d3d1c44e6c0e1691e0767fc3307afc95dd4039ae --- /dev/null +++ b/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-open-and-closed-community.txt @@ -0,0 +1,45 @@ +# Open and closed communities + +Open and closed community groups are collectives of individuals who come together to discuss particular challenges, ideas and experiences with regards to a particular community. These groups are self-organised, and will have their own ways of communicating and scheduling events. + +**An open community group** has open membership meaning anyone can join the group’s Slack channel, events and meetings. + +**A closed community group** is open only to those who are members of those communities. For example, to join the “women in tech” closed community group you would need to identify as a woman in order to have your request for an invite to be accepted. To join you will need to reach out to an organising member to request an invite. + +You can find a list of open and closed communities in the description of the [diversity and inclusion Slack channel](https://madetechteam.slack.com/archives/CRAJF24CR). We share this list during onboarding weeks too. + +## Starting a group + +Anyone can start an open or closed community group as long as they comply with our [Equality, Diversity & Inclusion Policy](policy.md). To start one you should: + +- Create an open or closed or both Slack channel for your group +- Notify the [diversity and inclusion service team](about-service-team.md) so they can add your group to the lists we share in Slack and during onboarding +- Document either in Slack or a shareable file the purpose of your group and details on how and when you meet +- If a closed group, provide details to the diversity and inclusion team on how someone can ask for an invite and what criteria they need to meet + +## Managing a group + +Open and closed community groups are self-organising and therefore need active management by its members to keep going. Civil servants have published a [“community development handbook”](https://www.gov.uk/government/publications/community-development-handbook/community-development-handbook) that provides lots of guidance on how to sustain a community. + +**Please note:** maintaining community groups is mentally and physically tiring – to keep the community sustainable this burden should not just fall on one or two individuals. + +## Support and budgets available + +There are a variety of ways we support open and closed communities to self-organise: + +- The culture and happiness team have budgets available for socials for your group and can provide support in organising events you may want to hold +- We have diversity and inclusion and culture and happiness budget available for paying speakers to talk at open or closed events +- We are organising a social and awareness calendar for key events that are relevant for our various community groups – this calendar enables our marketing team, employer branding and culture and happiness teams to organise and promote awareness +- Our offices can be used for meetings and our existing communication platforms (Slack, Google Meet) can be used to virtual meet + +Ask on Slack if you want to take advantage of this support. If something is not listed here, please speak to the [diversity and inclusion service team](about-service-team.md) who will be happy to find an answer as to whether we can support your request. + +## Issue escalation + +Community groups form around particular identities, needs and/or experiences. If issues are discussed by these groups, they can be raised with the diversity and inclusion service team to be reviewed and supported. + +If an individual has reported an issue to a group, it may be too much of a burden on that individual to escalate the issue themselves. In this case, a nominated individual from the group should be nominated to raise the issue on the affected individuals behalf. + +Details on who to raise issues to are documented in the [#supply-diversity-and-inclusion Slack channel](https://madetechteam.slack.com/archives/CRAJF24CR). + +We have documented general guidance on [raising an issue](https://github.com/madetech/handbook/blob/main/guides/welfare/raising_an_issue.md) elsewhere in the Handbook, or you can get in touch with the People team if you’re not sure who the best person is to speak to. diff --git a/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-service-team.txt b/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-service-team.txt new file mode 100644 index 0000000000000000000000000000000000000000..2f2631f46f9b0344ad0340ee180b9cc63d24d76e --- /dev/null +++ b/handbook/handbook-main/guides/equality-diversity-and-inclusion/about-service-team.txt @@ -0,0 +1,38 @@ +# Diversity and inclusion service team + +The diversity and inclusion service team are responsible for and empowered to shape and deliver changes to drive improvements that lead to Made Tech being a more diverse and inclusive place to work. We see this as a necessary ongoing investment needed to ensure equal opportunities are brought about by our work and that we maintain an inclusive culture as we grow. + +Specifically, the diversity and inclusion service team is funded to and is responsible for: + +- Defining our strategy +- Setting KPIs and objectives +- Co-creating change plans with other service teams +- Supporting the wider organisation to take action to deliver on these objectives +- Reporting on progress to our leadership team +- Being an escalation point with the ability to raise issues at an executive and board-level +- Manage operation of equality data collection +- Reporting on equality data to drive future decisions and investments +- Running the [diversity and inclusion community](about-di-community.md) +- Supporting [open and closed communities](about-open-and-closed-community.md) to form and operate + +## Membership + +It is a requirement that an executive director and a member of the leadership team are members of the service team to ensure the team continues to have sufficient authority to make necessary decisions. + +We will run an open recruitment process for other membership places of no less than two places being available per quarter to anyone at Made Tech. + +## Meetings + +The service team shall meet with all available members on a weekly basis to review goals, committed actions and issues. The meeting is 45 minutes and is run by the team’s directly responsible individual or a nominated other. + +The service team is also responsible for ensuring the diversity and inclusion community meets on a regular basis. + +Minutes for these meetings are publically available. +Historical records (03/09/2021 - 29/10/2021) are available on [GitHub](https://github.com/madetech/inclusion/tree/HEAD/minutes/SA-weekly) +More recent minutes (05/11/2021 onwards) are available in a [Google Doc](https://docs.google.com/document/d/1KlCwH72h7zqmbRFugwTzbcn_fawofRysWyi6qZRaZXg/view) + +## Managing issues + +The service team shall be available for issues to be raised via members of the diversity and inclusion community, open/closed communities or any other individual at Made Tech. Details on who to raise issues to should be documented in the [#supply-diversity-and-inclusion](https://madetechteam.slack.com/archives/CRAJF24CR) Slack channel. + +We have documented general guidance on [raising an issue](../welfare/raising_an_issue.md) elsewhere in the Handbook. diff --git a/handbook/handbook-main/guides/equality-diversity-and-inclusion/policy.txt b/handbook/handbook-main/guides/equality-diversity-and-inclusion/policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..cfb026eacdf69c097326b0883bfedee0660d1ae8 --- /dev/null +++ b/handbook/handbook-main/guides/equality-diversity-and-inclusion/policy.txt @@ -0,0 +1,89 @@ +# Equality, Diversity & Inclusion Policy + +## About this policy + +This policy applies to everyone who works for Made Tech, or who acts on Made Tech’s behalf. All team members have a role in promoting equality, diversity and inclusion at work. We all have a personal responsibility to comply with the policy and to ensure, as far as possible, that others do the same. + +Made Tech is responsible for this policy, and for ensuring that all our staff understand their rights and obligations as detailed within it, and for any necessary training on equal opportunities. + +This policy does not form part of your contract of employment, and we may amend it at any time. + +## The legal framework + +It is illegal to discriminate against a person on the basis of the following [Protected Characteristics](https://www.gov.uk/discrimination-your-rights): + +- Age +- Disability +- Gender reassignment +- Marital or civil partner status +- Pregnancy or maternity +- Race (including colour, nationality, ethnic or national origin) +- Religion, religious belief or similar philosophical belief +- Sex +- Sexual orientation (ie homosexuality, bisexuality or heterosexuality) + +This list doesn't cover everything that might disadvantage someone. We're interested in fairness for everyone, not just meeting our legal obligations. + +## Diversity and equal opportunities + +This is a broader concept that builds upon the progress made through equal opportunities. Everyone is different and diversity means recognising, respecting and valuing the differences we each bring to work. + +Equal opportunities and diversity work together by identifying and addressing any inequalities and barriers faced by people and by valuing, learning and benefiting from the diverse cultures in society and our staff. + +## Types of discrimination + +### Direct discrimination + +This means treating someone less favourably than you would treat others because of a Protected Characteristic. For example, rejecting a job applicant because of their religion, or not promoting someone because of their sexual orientation. This includes any less favourable treatment because you perceive a person to have a Protected Characteristic (even though they do not in fact have it), or because they associate with a person or group who has a Protected Characteristic. + +### Indirect discrimination + +This means placing someone at a disadvantage through a policy, practice or criterion that applies to everyone but adversely affects people with a particular Protected Characteristic. For example, if a company insisted that all employees work on a Sunday, this would adversely affect Christians. If such a practice or criterion cannot be justified as a reasonable means to an end, then it could be considered unlawful. + +### Harassment + +Harassment related to any of the Protected Characteristics will be unlawful if it consists of unwanted conduct that has the purpose or effect of violating a person’s dignity or creating an intimidating, hostile, offensive, degrading or humiliating environment for that person. If you feel that you have been the subject of harassment please talk to your manager, HR person or a trusted colleague in the first instance if you feel more comfortable doing this. + +### Victimisation + +This is the unfavourable treatment of a person because they have taken action to assert their own legal rights under discrimination law, or assisted someone else to do so. For example, if a disabled employee asserts in a grievance that their employer is not complying with its duty to make reasonable adjustments, and is then systematically excluded from meetings. + +## Equal opportunities in employment + +We commit to avoiding unlawful discrimination in all aspects of employment including recruitment, promotion, opportunities for training, pay and benefits, discipline, and selection for redundancy. + +### Recruitment and selection + +Person and job specifications will be limited to those requirements that are necessary for the effective performance of the job. Candidates for employment or promotion will be assessed objectively against the requirements for the position, and on the basis of merit. Similarly, other selection exercises such as redundancy selection will be conducted against objective criteria. A person’s personal or home commitments will not form the basis of employment decisions except where justified and necessary. + +We will generally advertise vacancies to a diverse section of the labour market. Our advertisements should avoid any kind of stereotyping or wording that may discourage particular groups from applying. + +Job applicants should never be asked questions which might suggest an intention to discriminate on grounds of a Protected Characteristic. For example, you may not ask an applicant if they plan to have children. + +### Working practices + +We will consider any possible indirectly discriminatory effect of our standard working practices, including the number of hours to be worked, the times at which these are to be worked, and the place at which the work is to be carried out. When considering requests for variations to these working practices we will only refuse these if we have good reasons for doing so. + +### Part-time and temporary employees + +We will treat part-time and fixed-term employees the same as comparable full-time or permanent employees, and will ensure that they enjoy no less favourable terms and conditions (albeit on a pro-rata basis where appropriate), unless different treatment is justified. + +### Disability + +We will not ask job applicants about their health or any disability before offering them a position, unless it is to check that they can perform an intrinsic part of the job, or to see if we need to make any particular arrangements to accommodate them at interview. Where necessary, job offers can be made conditional to a satisfactory medical check. + +If you are disabled or become disabled, we would ask you to tell us about your condition, so that we can support you as much as possible, and discuss with you any adjustments that may help you. + +### Monitoring questionnaires + +As part of your onboarding at Made Tech and at regular intervals thereafter you will be asked to complete an equality, diversity and inclusion monitoring questionnaire. The data we collect from these will be used to help us make decisions that help fulfil our equality, diversity and inclusion aims. + +## Breaches of the policy + +All staff members have a right to equality of opportunity, and an obligation to uphold this policy. Managers must take responsibility for implementing the policy and for taking positive steps to promote equality at work. + +If you believe that you have suffered discrimination you can raise the matter through our grievance procedure, or you can talk to your manager, the people team, or a trusted colleague in the first instance if you feel more comfortable doing this. Complaints will be treated in confidence and investigated as appropriate. + +We consider any violation of our equality, diversity and inclusion policy to be a serious matter, and, where appropriate, we may invoke the disciplinary procedure when dealing with a breach. Serious cases of deliberate discrimination may amount to gross misconduct resulting in summary dismissal. Unlawful discrimination may also result in legal proceedings against you personally and against Made Tech, and may leave you and Made Tech liable to pay compensation. + +You must not be victimised or retaliated against for complaining about discrimination. However, making a false allegation deliberately and in bad faith will be treated as misconduct. diff --git a/handbook/handbook-main/guides/exit_interviews.txt b/handbook/handbook-main/guides/exit_interviews.txt new file mode 100644 index 0000000000000000000000000000000000000000..00cefd4bb3a47d8f67faf34f3564de7374d86164 --- /dev/null +++ b/handbook/handbook-main/guides/exit_interviews.txt @@ -0,0 +1,14 @@ +# Exit interview + +A sad reality is that sometimes people will leave Made Tech. Below are a set of questions we like to ask during a 30 minute exit interview. + +- Why did you look for a new job? +- What made you accept the position? +- Did you feel that you were equipped to do your job well? +- How would you describe Made Tech culture? +- Can you provide more information, specific examples of culture? +- What could have been done to keep you? +- If you could change anything about your job what would it be? Roles, responsibilities, expectations, customers, etc. +- If you could change anything about the company what would it be? Culture, space, people, etc. + +**Disclaimer:** We found these in a [Glassdoor blog article](https://www.glassdoor.co.uk/employers/blog/7-must-ask-exit-interview-questions/). diff --git a/handbook/handbook-main/guides/hiring/career_fairs.txt b/handbook/handbook-main/guides/hiring/career_fairs.txt new file mode 100644 index 0000000000000000000000000000000000000000..af98843e943aefced0cc2d21ff5d78ab268af281 --- /dev/null +++ b/handbook/handbook-main/guides/hiring/career_fairs.txt @@ -0,0 +1,46 @@ +# Made Tech guide to career fairs + +## What does a careers fair look like? + +There are many stalls setup as a circuit around in a big hall. Students pass by the stalls asking questions about job opportunities and internships. + +Most stalls have two representatives standing to the side or in front of them. Standing behind the desk seemed to put too much of a barrier between students and representatives. Stalls typically had table clothes of the companies colors over them, some with logos. All stalls had big banners behind them with bullet point info about the companies and job opportunities at eye level. A lot of stalls had sweets or chocolate on them along with leaflets and swag ranging from totes, USB sticks, popcorn, pens, paper pads, rubix cubes. Some stalls had challenges like solving a rubix cube with a leaderboard. Some had examples of apps they'd built on laptops. A few stalls had additional podiums they brought a long. Our Google Cardboard were another example of things on tables. + +Typically the staff at the desks were recruiters or HR managers rather than people who actually work in engineering. Companies like Ford, Army, Navy, solicitors, Bloomberg and BAE systems are there. Many wore suits although some seemed much more down to earth. The big brands were the big hitters with students swarming around them for more information. Thats not to say we didn't also have 5 or so swarms during the day. + +Most students want to ask about what we do. Some are Computer Science grads, some are mechanical engineering but still interested in code. Some students are part way through their undergraduate years (3-4 years) and some will be doing postgraduate degrees (~2 years). Some want internships, some want graduate positions. Typically everyone wanted a description of what we work on but some ask about salary and length of internships and other things like day to day activities or work environment. + +On average most students stay from anywhere from 1 minute to 5 minutes. Some just want to grab leaflets but we tried opening conversations with everyone who approached. We tried talking to bigger crowds if many approached at once. Everyone even the shy ones appreciated us approaching them and having a conversation. A lot of people seemed a lot more interested in us after talking to them, most had no idea what we were about from the signage. + +## The patter(n) + +At the start we weren't sure on how to begin conversations but throughout the day we built up a fairly consistent conversation structure that worked for us: + + - Ask whether the student is studying compsci or has touched any code? + - Describe the fact we primariy build software, from anything like e-commerce stores, to complex warehousing APIs and even back office tools. + - Highlight the fact we go into other businesses to help their teams deliver better software faster. Several times we described moving organisations from delivering software every 3 months to every day. + - Go into detail about our code dojos, hack days, retreat, blogging and advise them to read our blog and github to see how we work. + - Provide Google Cardboard to take a look at the office. + - Try to take details or at least give a leaflet to every person who approaches. + - Also invite people to our office, to code dojos or whatever else if you fancy. + +## Things to try next time + + - Name badges with Made Tech logo on them + - Sweets are very popular like cadburys celebrations but should also provide vegan alternative too (biscuits or something) + - More leaflets, need around 200 probably + - Use laptop or two for taking contact details as tablet slow + - Challenge that takes maximum of a minute to complete + +## Questions we need to answer + + - How long are internships and when do they start? + - What does our graduate scheme look like? + - What are the salaries available to interns and graduates? + - Do we have any non-technical roles available? + +## Notes for next year + + - Banners should contain information about the fact we build web applications and help other companies do that + - Banner text should be at eye line as a lot of people were straining and bending over to read the text. Students seem to use this to wittle out companies, we used it as an opportunity to strike up conversations but worth making it a little easier at a glance. + - More technical attractions or gadgets or swag. AutomationLogic had a popcorn machine and beer opening USB sticks. diff --git a/handbook/handbook-main/guides/hiring/devops_pairing.txt b/handbook/handbook-main/guides/hiring/devops_pairing.txt new file mode 100644 index 0000000000000000000000000000000000000000..dd2464cbea352aab3ab1717c5dcd61703e94c3dd --- /dev/null +++ b/handbook/handbook-main/guides/hiring/devops_pairing.txt @@ -0,0 +1,22 @@ +DevOps pairing works similarly to [regular pairing](./pairing.md) +Please [read the regular pairing document](./pairing.md) before this one + +## Goals + +- Our DevOps pairing process is designed to simulate solving a real problem in a delivery. +Therefore work should be done on an actual cloud account so that the pair can work past unexpected problems + +- We insist on using infrastructure as code so that interviews can demonstrate these skills as this is often always used in a delivery + +## Preparing to pair +The DevOps pairing process needs a little more preparation than normal +- For pairing in AWS [you will need a cloud account to use](../cloud/aws_sandbox.md) +- Use [this terraform project](https://github.com/madetech/devops-pairing-terraform) to create temporary credentials for the pair + +## Writing code together +Please use one of [these scenarios](https://learn.madetech.com/technology/scenarios/cloud/) for the interview pairing exercise. + +## Ending the pairing session +When there are five minutes left in the session: +- Start to Destroy the resources created in the session +- While this is happening, it's good to ask how they thought the interview went, what they would change, how they would write tests to ensure the infrastructure has deployed correctly etc. diff --git a/handbook/handbook-main/guides/hiring/pairing.txt b/handbook/handbook-main/guides/hiring/pairing.txt new file mode 100644 index 0000000000000000000000000000000000000000..c08328ea43dc17b36556df0473a42ca622b0f27b --- /dev/null +++ b/handbook/handbook-main/guides/hiring/pairing.txt @@ -0,0 +1,78 @@ +# Pairing with interview candidates + +If you are a Made Tech employee, please refer to this [guide for Software Engineers on how to pair](https://docs.google.com/document/d/1x8fVCx-FB-VU_1EHbGU6yLDn1fDyfa5R/edit?usp=sharing&ouid=113960202795862454830&rtpof=true&sd=true). + +## Why we pair with candidates +We’re trying to hire people who we’d like to work with. This is a way to try out "working" with them. + +It won’t give us certainty, but we hope it helps us make better decisions. + +## When you’ll be needed +You're only needed for: +- The pairing, which starts 30 minutes after the start of the interview, and lasts 30 minutes +- The debrief, which usually happens directly after the 1h30 interview, and lasts about 10 minutes + +For example: +- An interview is taking place at 2pm, lasting until 3.30pm. +- You’ll be needed to pair from 2:30pm, until 3pm. +- You'll be invited to discuss the pairing from 3:30pm, for about 10 minutes ("debrief"). + +Sometimes an interview might overrun. Read the thread in slack before joining the call. + +## What you are looking for +You’ll want to answer these questions about the candidate: +- Are they prepared? +- Are they writing good quality code? +- Are they writing good quality tests? +- Are they approaching the problem in an effective way? +- Can they clearly explain their approach? +- Can they clearly explain their thought process? +- Are they easy/fun to collaborate with? + +Taking notes while pairing can help to answer these questions. + +It's good for some of your feedback to have more detail than "yes" or "no". + +## Legal guidance +Made Tech have a legal duty to ensure that interviews are fair and free of discrimination. There are [illegal interview questions](https://www.interview-skills.co.uk/free-information/interview-guide/illegal-interview-questions) that must not be asked. While it's unlikely that these would be asked directly in a pairing session, it is important that conversation doesn't stray into these areas. + +## Meeting the candidate +The Made Tech people running the interview will let you know when to join. + +It’s OK to spend five minutes getting comfortable at the beginning. Introduce yourself, ask how they are doing. + +Tell the candidate the key facts: +- The session lasts ~25 minutes. +- We’re going to tackle a small coding challenge together, but it’s OK not to “finish” it. +- That you want to pair to understand more about how they work. +- That you want them to share things out loud, so you can understand more. + +## Preparing to pair +- Ask if they’re familiar with pair programming. If not, explain briefly. +- Decide on a pairing style together. +- Ask if they’ve done a kata before. If not, explain briefly. +- Ask which kata they’d like to do. If they’re not sure, suggest one from [this list](https://learn.madetech.com/technology/katas/). Tennis or Bowling work well. +- Ask if they’re familiar with test-driven development (TDD). If not, explain briefly. +- Tell the candidate you’d like to write tests as part of doing the kata. +- If you’re remote, decide how you’ll pair. You could use Tuple, Live Share, or screen sharing. + +## Writing code together +It’s OK to help, but give space for the candidate to show their skills and knowledge. If they get stuck, guide them to the next small step. + +Ask them to write the first test. + +Keep writing code and tests until you've got five minutes left. + +It's OK to keep coding for the last five minutes, or to stop and talk with the candidate instead. + +## Ending the pairing session +It’s OK to stop coding five minutes early and talk. You would do this to: +- Ask any extra questions +- Make the candidate more comfortable (e.g. remind them it’s OK to not finish) + +## Sharing your feedback +Join the debrief and share your feedback with the other interviewers. + +It’s OK to be unsure about whether you would hire the candidate. + +Note: See [devops pairing](./devops_pairing.md) for differences to this process diff --git a/handbook/handbook-main/guides/hiring/rationale.txt b/handbook/handbook-main/guides/hiring/rationale.txt new file mode 100644 index 0000000000000000000000000000000000000000..058f189b9e8adf5d3db7832dd92137758f4c68e2 --- /dev/null +++ b/handbook/handbook-main/guides/hiring/rationale.txt @@ -0,0 +1,15 @@ +# Rationale + +We believe that our hiring process should be fair and repeatable. What do we mean by this? + +## Fair + +Made Tech is an equal opportunity employer that is committed to inclusion and diversity. There is a simple reason to this, we know that having people of all different walks of life provide us with new view points and better our ability to achieve our mission. + +## Repeatable + +We want to be able to continually hire new staff! We wish to grow and we recognise in order to do this we require a pipeline that provides consistent results. Ideally we would have a pipeline where we could increase our spend and therefore increase our levels of hiring. + +## Achieving fair and Repeatable + +In order to achieve fair and repeatable hiring we need to define a process. As with the rest of our business we experiment and iterate with our hiring process. By having a clearly defined pipeline we can optimise and change it through conversation. We can also repeat successes by repeating our process. diff --git a/handbook/handbook-main/guides/hiring/referral_policy.txt b/handbook/handbook-main/guides/hiring/referral_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..e60dd5765876bd54397bdcb12fed3ba3e2d22eaa --- /dev/null +++ b/handbook/handbook-main/guides/hiring/referral_policy.txt @@ -0,0 +1,55 @@ +# Employee Referral Policy + +The main purpose of this employee referral policy is for everyone at Made Tech to use when they need information about how Made Tech’s referral programme works. + + +## Policy Statements + +If you know someone who you think would be a good addition for a position at Made Tech, please do refer them via our [Pinpoint platform](https://made-tech.pinpointhq.com/employee-dashboard/referral_jobs). If we end up hiring your referred candidate, you may receive a referral payment if eligible. Use the policy guidelines below to determine your eligibility. + +Made Tech will give payments to employees who refer qualified candidates for our job openings. + +This is how our employee referral programme works: + + +| Monetary Amount | Roles | Payment amt on start date | Payment amt after probation | +| ------------------: | :--------------: | -------------------------:| --------------------------: | +| £500 | Apprentices | £250 | £250 | | +| £1500 | All other roles | £750 | £750 | + + +__Charity__ – should you wish to not take us up on the personal financial incentive then you can opt to make a charitable donation which we will make on your behalf to our associated charity for the given year of the campaign. + +## Who is eligible to take part? + +All our employees are eligible to take part in this program – as such the program does not include contractors or third-party vendors. + +The only other people exempt from participation are: +* Anyone working in our talent roles and hiring managers for positions for which they’re hiring. + + +## Who can be referred? + +The only groups of people who **cannot** be referred are candidates: +* That have applied and been unsuccessful in the past 6 months +* Who have terminated from employment with us for any reason within the last 18 months (for example, including resignations). +* Current contractors + +## Additional rules for rewards + +* Rewards will be processed within 30 days of each stage and processed in the next available pay run. +* We never say no to receiving a profile of a referral and will ensure that someone from our Talent team will review the profile and aim to take action within 5 working days. However, during busy periods, this may take longer. You can refer as many times as you wish. Please be sure to evaluate our roles and requirements and make a judgement on suitability to ensure everyone’s time and expectations are well managed. +* The candidate being referred must be someone the employee personally knows through a professional or a personal relationship and we will check the validity of the referral before offer stage. +* If the same candidate is referred by multiple employees, the first employee who makes the referral gets a reward, so act fast if you know someone that could be suited to our open positions. +* There is a 12 month time limit on a referred candidate, meaning if you refer someone to us and they are not right for the current positions now, you could still receive a payment if they are hired in the next 12 months. You will however not receive a payment if you leave Made Tech. +* Any financial reward is open to the usual PAYE deductions (tax), please contact People Ops via our Ask Made Tech portal should you have any questions regarding the deductions – which will be automatically made in your pay cycle. + + +Thank you to all of our Made Tech teammates for taking the time to consider their networks, social and professional as potential resources for referred candidates. + + +We may change our referral programme over time. We also reserve the right to remove certain rewards if they prove ineffective or inefficient. We’ll communicate any change in a clear and timely manner. Employees who referred candidates before a reward incentive was removed or changed will still receive the appropriate reward. + + +We’d like to remind our employees that we are an equal opportunity employer and do not discriminate against protected characteristics. We guarantee that all candidates will be given the same consideration and will pass through our established procedure. + diff --git a/handbook/handbook-main/guides/it/Hardware.txt b/handbook/handbook-main/guides/it/Hardware.txt new file mode 100644 index 0000000000000000000000000000000000000000..0868444a052b7e95a855e4e760f3c79ff54e8926 --- /dev/null +++ b/handbook/handbook-main/guides/it/Hardware.txt @@ -0,0 +1,49 @@ +# IT Hardware + +Aura look after all the laptops and other IT infrastructure in the offices. For all laptop issues or questions please email them directly [it@madetech.com](mailto:it@madetech.com). +For accessories such as monitors, keyboards, etc. take a look [here](https://github.com/madetech/handbook/blob/main/benefits/work_ready.md). + +### Laptops +Everyone at Made Tech will be given a laptop aligned to the role they do. The Linux users in Made Tech would like to specifically highlight that Engineers can request Linux machines :) + +The current standard laptop specs for new purchases are: + +**Engineers and UCD** +- MacBook Pro (14inch standard display) +- Apple M4 with 10-core CPU, 10-core GPU, 16-core Neural Engine +- 32GB unified memory +- 512GB SSD storage + +OR + +- ThinkPad X1 Carbon Gen 11 or 12 14 inch +- Core i7-1355U Processor (E-cores up to 3.70 GHz P-cores up to 5.00 GHz) +- 16GB or 32GB of RAM +- 512GB SSD +- Windows or Linux + +(Gen, processor, memory and overall spec can vary on the ThinkPads - we'll talk to you individually about options.) + +**All other roles** +- Air M3 (13 inch) +- Apple M3 chip with 8‐core CPU, 8‐core GPU and 16‐core Neural Engine +- 16GB unified memory +- 256GB SSD storage + +You may have or receive a laptop with a slightly different spec - these are older machines which are still within the 3 or 4 year replacement period (see below). + +Standard laptop specs will be reviewed annually, and as and when Apple change their specs. The last review was January 2025. + +If there is an issue with your laptop please email [it@madetech.com](mailto:it@madetech.com) + +## Laptop replacement cycles + +**Engineers and UCD** - laptops are currently replaced every 3 years, according to the age of the individual laptop, not how long a user has had it. + +**All other roles** - laptops are replaced every 4 years, according to the age of the individual laptop, not how long a user has had it. + +Please note - the replacement is due on the date the laptop was bought by Made Tech, it it not based on the model year of the laptop. + +When your laptop is due for replacement you'll be contacted by Aura to arrange for a new one to be given to you and return of the old one. You do not have to have a replacement - if you're perfectly happy with the laptop you currently have then great. You can request a replacement at any point after the 3 or 4 year mark, whichever is applicable. New laptops will be whatever the standard spec is for your role at that time. + +As of February 2025 we are running behind on replacements for Pros. We're working through in date order. diff --git a/handbook/handbook-main/guides/it/Miro.txt b/handbook/handbook-main/guides/it/Miro.txt new file mode 100644 index 0000000000000000000000000000000000000000..90de7526a2c748a71a2c3110316d7947215e24e2 --- /dev/null +++ b/handbook/handbook-main/guides/it/Miro.txt @@ -0,0 +1,44 @@ +# Miro + +All the information below and lots more useful stuff can be found on the Made Tech [Miro training board](https://miro.com/app/board/o9J_lkgJ4BU=/) (this is an internal link to a Miro board) + +## Getting access to Miro +### New starters +All new starters are automatically given a Full Miro licence when they join and are added to the Made Tech Team. + +They can be added to any board or Space in the Made Team Team by any other Made Tech Team member. To add them to another Space or client Team, that Team Admin has to invite them. + +### External users +External users **cannot** be added to the Made Tech team, they can only be added to separate client team and Spaces - see Types of Team below. The Team Admin for the client or Space can invite them. + +The licence options are: +- Free Restricted - viewing and commenting (this is free) +- Full - editing access (this costs us money) + +### Reviews +In order to keep licence costs down, access is reviewed every quarter based on usage. If a Full licence hasn’t been used in the previous 2 months it will be changed to a Free Restricted licence. This can be changed back to a Full licence at any point. The licence options are: + +- Free Restricted - viewing and commenting (this is free) +- Full - editing access (this costs us money) + +### Leavers +If you are leaving Made Tech; please transfer your boards to a new owner in advance. Any boards still owned by you at the point of offboarding will be transferred to a Team Admin. + +Leavers are removed from the Made Tech Team as part of the offboarding process. Leavers need to be manually removed from any other client or project teams by the Team Admin, though Ops will do a clear out once a quarter. + +## Types of Team +### The Made Tech Team +There is a Made Tech Team which all staff are automatically added to. This is internally facing only - external users **cannot** be added to the Made Tech team. This is so that there is no accidental sharing of internal information. + +Everyone has permissions to set up their own boards within the Made Tech Team, either as part of a Space or individually. These can be kept private, be shared with individuals or with the whole Team. + +### Client & Project Teams +There are also Client and Project Teams which individuals can request to be added to, or be invited by the Team Admin. These are completely separate from the Made Tech Team, and from each other, and have been set up to ensure that we are keeping all client data in separate and secure environments. + +These Teams are administered by the Team Admin who is a member of the project team, and only relevant project team members should be invited. + +If you need a new Team creating, contact Aura via email it@madetech.com or via Slack. + +To join an external team, click on the Made Tech team option at the top of your dashboard so you can see all the teams you have access to, click + Join team and a request will be sent to the admins for that team. + +There is more information on Ask Made Tech - search for Miro. diff --git a/handbook/handbook-main/guides/it/docker.txt b/handbook/handbook-main/guides/it/docker.txt new file mode 100644 index 0000000000000000000000000000000000000000..80e91145f709658b5ef64937af4a2315febe4fd4 --- /dev/null +++ b/handbook/handbook-main/guides/it/docker.txt @@ -0,0 +1,12 @@ +# Docker + +Docker is an open platform for developing, shipping, and running applications. Docker enables developers to separate their applications from their infrastructure so they can deliver software quickly. With Docker, they can manage their infrastructure in the same ways they manage their applications. By taking advantage of Docker’s methodologies for shipping, testing, and deploying code quickly, they can significantly reduce the delay between writing code and running it in production. + +Due to changes within Docker, from Jan 2022 any employees using a Made Tech email address must use the Made Tech licence for Docker Desktop and not an individual licence. + +## Onboarding/offboarding +If you require a Docker licence please message `it@madetech.com` with the details of the project / workstream that you need adding to. + +If you are a Delivery Manager / the Lead Engineer on a project then please ensure that you notify the Operations team if a member of your team leaves your project so that we can remove their access to that project. + +If you have left a project and are still in the team on Docker or you no longer require your licence please ensure you let the ops team know by sending a message to it@madetech.com diff --git a/handbook/handbook-main/guides/it/laptop_replacements.txt b/handbook/handbook-main/guides/it/laptop_replacements.txt new file mode 100644 index 0000000000000000000000000000000000000000..a00c3ce70d0651366fe7eb50ed13649d35749ba0 --- /dev/null +++ b/handbook/handbook-main/guides/it/laptop_replacements.txt @@ -0,0 +1,37 @@ +# Laptop replacements + +The laptop renewal period is 3 or 4 years, depending on your role and the age of the laptop, not the amount of time an individual has had it. Renewal is entirely optional - if you want to keep your current laptop that’s fine. + +- Aura will contact you to let you know the laptop is eligible for renewal. You’ll be offered a new machine in line with our agreed [laptop specifications for your role.](https://github.com/madetech/handbook/blob/main/guides/it/Hardware.md) + +- Aura will then arrange to send you a new laptop. + +- Once you've finished transferring any information from your old laptop you need to send it back to Aura. Please ensure: +- That the device is clean (no stickers) +- That the charger is included +- There is a note with your name on it so that Aura can identify who it’s from. + +If you are posting the laptop you need to ensure it’s suitably packaged and has plenty of padding to ensure a safe return. Send it with tracking and insurance to the following address: + +
+Aura Technology
+1-2 Trinity Court
+Brunel Road
+Totton
+Southampton
+SO40 3WX
+
+ +We recommend using the following method to send the laptop and charger to Aura as this both tracks and insures the laptop, and you can arrange to have the parcel collected from your home: + +[Special Next Day Delivery](https://www.royalmail.com/sending/uk/special-delivery-guaranteed-1pm) + +You can expense the postage by claiming back via Xero ([guide](../compensation/expenses.md) and [policy](https://docs.google.com/document/d/1NthAC1xepzAI07o40c6WxXHbPttNxaCidhJ22eJHD-k/edit#)), completing the following fields: +- Description: "Returning laptop to Aura for replacement" +- Account: "Postage, Freight & Courier" +- Industry: If it's a client laptop then it will depend on the client. If it's a Made Tech laptop then "Group" +- Capabilities: Your own capability +- Assign to customer: If it's a client laptop then it will depend on the client. If it's a Made Tech laptop then leave blank +- Label: Leave blank + +We do not offer an option to purchase your laptop. diff --git a/handbook/handbook-main/guides/it/laptop_security.txt b/handbook/handbook-main/guides/it/laptop_security.txt new file mode 100644 index 0000000000000000000000000000000000000000..172be7ee3857335798df2ad1a44a1936f2e8984e --- /dev/null +++ b/handbook/handbook-main/guides/it/laptop_security.txt @@ -0,0 +1,40 @@ +# Information Security + +Made Tech holds the following certifications: + +**CE+** +- Certificate number: IASME-CEP-045055 +- Date: 2022-06-30 +- Next review scheduled: 2023-06-30 + +**ISO 27001** +- Certificate number: CN/22466Q +- Date: 2022-07-12 +- Next review scheduled: 2025-10-20 + +**ISO 9001** +- Certificate number: CN/18125IS +- Date: 2022-07-12 +- Next review scheduled: 2025-07-02 + + +If you need a copy of these certifications you can find them in the [Knowledge Base](https://drive.google.com/drive/u/0/folders/1V6Gh1PJ0WeBb90i6cVYkXXHkkYHKXeuJ) (this an internal only link) + +In order to keep these certifications there's various standards we have to adhere to. Keeping our networks and equipment compliant and ensuring we're all trained is managed by Ops, but everyone in Made Tech has an individual responsibility for information security. + +You will find more information on how Ops do that and what all users need to do on the [Knowledge Base](https://sites.google.com/madetech.com/signpost/home/security) (this an internal only link) + +For any general questions use the #Ops-IT Slack channel where our response is also visible to others which can be really helpful. For requests to action or project specific queries then email [operations@madetech.com](mailto:operations@madetech.com) + +If you need information for a client or bid, email [operations@madetech.com](mailto:operations@madetech.com) + +For any urgent security issues then Slack, email or call anyone in the Ops team. + +### Useful links +- [All about Linux](https://github.com/madetech/handbook/blob/main/guides/it/linux_av.md) +- [Device profiles](https://github.com/madetech/handbook/blob/main/guides/security/device_profiles.md) + +The below are all internal only links +- [VPN - When to use it and how to access it](https://drive.google.com/drive/u/0/folders/14w3BXtsrgUqRmJ73QFhGXiCo3ufjvMmI) +- [Wifi - Staff and guest network info](https://sites.google.com/madetech.com/signpost/home/it-support) +- [Intro to InfoSec training](https://docs.google.com/presentation/d/1Ubthx1C1MOHhbf2BBvAnU2Jw3YW2Ej4e9zKhvprHgzE/edit#slide=id.g5c95da9fba_0_0) diff --git a/handbook/handbook-main/guides/it/linux_av.txt b/handbook/handbook-main/guides/it/linux_av.txt new file mode 100644 index 0000000000000000000000000000000000000000..77b55e770907c9b8641817f328c726e5973f6e86 --- /dev/null +++ b/handbook/handbook-main/guides/it/linux_av.txt @@ -0,0 +1,156 @@ +# All about Linux +In order to reach the standards for [ISO](https://www.madetech.com/blog/iso-27001-changes/) and [Cyber Essentials Plus](https://www.ncsc.gov.uk/cyberessentials/overview), all our laptops must meet a certain set of requirements. For Mac and Windows machines that is controlled remotely by our IT Partner Aura. For Linux machines that currently all needs to be done manually. + +The documentation below is valid in places and out of date (but not incorrect) in others. A new set of standards is being put together but it won't be ready until January 2022. At that point this new information will move to the internally facing Knowledge Base. + +In the meantime; Welcome! If you have any questions please join the #linuxination Slack channel! Everybody really likes Linux so whether you are new to Linux or a Linux wizard we all like questions and are all here to help. + + + +## Running a supported OS +The operating system must be a current, supported version, that continues to receive security updates. + +### Linux (Ubuntu) +Check [Ubuntu releases](https://wiki.ubuntu.com/Releases) to ensure that your version is supported. + +## Full disk encryption +**This is the most important step**. When you install your operating system there will be a checkbox to enable this. Please set a disk encryption password that fits the [password policy](https://github.com/madetech/handbook/blob/7d4a7f840a587fed5046045cbe43f8222cabb194/guides/security/password_policy.md). + +It may be possible to encrypt dual booted or manual partitions but it is simpler to erase the disk and follow the guided installation for one operating system. + +For Ubuntu select `Erase disk and install Ubuntu`, `Advanced features`, `Use LVM`, `Encrypt the new Ubuntu installation`. In the next step you will be able to set security and recovery keys. Don't forget them! + +(Note: Enabling full disk encryption after installation is a difficult and dangerous process that is best not attempted. It is most likely you will have to complete all the following steps again after a fresh (disk encrypted) install). + +## Automatic updates enabled +Security updates need to be downloaded and installed automatically (Note: it is up to users on when to apply non-security related updates). Both Ubuntu and Fedora have provisions to enable this: ++ [Ubuntu](https://help.ubuntu.com/community/AutomaticSecurityUpdates#Using_GNOME_Update_Manager) ++ [Fedora](https://fedoraproject.org/wiki/AutoUpdates#Automatic_Updates) + + +## User accounts +The user account that you use on a day to day basis must be a standard non-administrator account. If you require administrator rights to do your job, you can create a separate admin user and switch to this when required. + +### Linux (Ubuntu) + +**Note: This is optional for Linux users, though recommended by Cyber Essentials Plus.** + +A standard account is not on the `sudoers list`, so in order to run commands that require `sudo` access you can temporarily switch to an admin account, run the `sudo` command then logout of the admin user: + +```bash +su - [admin account] +sudo [command] +exit +``` + +## Account locking +User accounts should be configured to lock after a **maximum** of 10 failed login attempts for 5 minutes, log the username to the syslog if the user is not found, and apply the same settings to the root user account. + +### Linux (Ubuntu) +To enable account locking on Ubuntu add the following line to `/etc/pam.d/common-auth`, directly after the `# here are the per-package modules (the "Primary" block)` comment: + +``` +auth required pam_tally2.so onerr=fail deny=10 unlock_time=300 audit even_deny_root root_unlock_time=600 +``` + +This will: +- lock a user's account after 10 failed login attempts - this can be reduced but should not be greater than 10 +- lock the account for 5 minutes (300 seconds) +- log the username to the syslog if the user is not found +- apply the same settings to the root account. + +### Linux (Ubuntu) 22.04+ +pam_tally2.so has been replaced by pam_faillock.so
+pam_failock.so settings can be made in `/etc/security/faillock.conf` and by adding the following to the `/etc/pam.d/common-auth` file: +``` +auth [default=die] pam_faillock.so authfail +auth sufficient pam_faillock.so authsucc +``` +If you have prevented all logins by mistake with pam_tally2 you can reboot to recovery mode into a root shell to access `/etc/pam.d/common-auth`. + +#### Root account +[Ubuntu disables the root account by default](https://ubuntu.com/server/docs/security-users) by not setting a password. This allows a user to boot into a root shell via GRUB / recovery mode. To prevent this you should set a password for the root user: + +```bash +sudo passwd root +``` + +## Firewall +You should be running a local firewall configured to block any incoming traffic. + +### Linux (Ubuntu) +Ubuntu ships with `ufw`, but it is disabled by default. Enable it by running: + +```bash +sudo ufw enable +``` + +## Auto mount / auto run disabled +Your system should *not* auto mount or auto run files when media, such as a removable USB disk, is inserted. + +### Linux (Ubuntu) +In Ubuntu this feature can be disabled by selecting _"Never prompt or start programs on media insertion"_ in _Settings_ > _Removable media_. + +## VPN +You must have [Made Tech's VPN](vpn/README.md) configured on your system. + +## Anti-virus +You must be running Anti-virus software. The installed AV software must: +- be up to date (the most recent stable version, within 30 days of it's release) +- contain an up to date database of viruses and malicious software +- prevent access to, or the running of any malicious file or software (On-access scanning as opposed to scheduled scanning) + +You can test the configuration of your AV software using the test files provided by [EICAR](https://www.eicar.org/) on their ["Anti Malware Testfile" page](https://www.eicar.org/download-anti-malware-testfile/). For example, after downloading `eicar.com.txt` it should not be possible to open the file in a text editor. + +## SentinelOne +SentinelOne is the Linux Anti-virus Software of choice at Made Tech. To get set up with SentinelOne follow the instructions below + +### Step 1: Download and install the package +* [DEB Installer](https://ncrepository.z33.web.core.windows.net/sentinelone/SentinelAgent-Linux-22-1-2-7-x86-64-release-22-1-2_linux_v22_1_2_7.deb) - For Debian/Ubuntu based distributions +* [Non-Signed RPM Installer](https://ncrepository.z33.web.core.windows.net/sentinelone/SentinelAgent-Linux-22-1-2-7-x86-64-release-22-1-2_linux_v22_1_2_7.rpm) - For RHEL/Fedora Based distributions +* [Signed RPM Installer](https://ncrepository.z33.web.core.windows.net/sentinelone/Signed-SentinelAgent-Linux-22-1-2-7-x86-64-release-22-1-2_linux_v22_1_2_7.rpm) - For RHEL/Fedora Based distributions + +For Debian/Ubuntu +``` +sudo dpkg -i ~/Downloads/SentinelAgent-Linux-22-1-2-7-x86-64-release-22-1-2_linux_v22_1_2_7.deb +``` + +For RHEL/Fedora +``` +sudo rpm -i --nodigest ~/Downloads/SentinelAgent-Linux-22-1-2-7-x86-64-release-22-1-2_linux_v22_1_2_7.rpm +``` +or +``` +sudo rpm -i --nodigest ~/Downloads/Signed-SentinelAgent-Linux-22-1-2-7-x86-64-release-22-1-2_linux_v22_1_2_7.rpm +``` + +### Step 2: Register the Made Tech licence key to your SentinelOne install + +You can find the licence key in 1Password. +``` +sudo /opt/sentinelone/bin/sentinelctl management token set [licence_key] +``` + +### Step 3: Start the Service +``` +sudo /opt/sentinelone/bin/sentinelctl control start +``` + +Once installed, and you've started the service check with Ops to ensure you have registered to the SentinelOne dashboard successfully. If this was successful you can remove your previous Anti-virus solution. Should you face any problems or require support please reach out to #ops-it-support or #linuxination on Slack + +## DriveStrike +DriveStrike must also be installed on all Linux machines. It is owned and managed by the awesome Systemagic! You will receive an email from DriveStrike with an invitation to install DriveStrike shortly after starting although it is the individual's responsibility to ensure it is on their machine and the service is enabled. + +## Approved software +For Linux users anything downloaded from the main stable repositories is considered safe to install on your device. + +## UEFI Settings + +You probably want to go into the UEFI setup by hitting "Enter" to interrupt boot and then F1, and ... + +- Enable virtualization. (in "Security") + - You don't need this for containers, but you do for "proper" virtual machines +- Change the sleep state from S0 ("Windows 10") to S3 ("Linux") (in Config .. Power) + - Without doing this you may experience "hot bag syndrome", flat batteries, and lower battery life in suspend +- Enable "swap Ctrl and Fn" + - Because let's face it, the ThinkPad keyboard layout isn't right without doing this diff --git a/handbook/handbook-main/guides/it/slack.txt b/handbook/handbook-main/guides/it/slack.txt new file mode 100644 index 0000000000000000000000000000000000000000..f8147440db37ba322f4cd328467df6aabf845f31 --- /dev/null +++ b/handbook/handbook-main/guides/it/slack.txt @@ -0,0 +1,76 @@ +# Slack + +## Purpose of this guide + +Slack is one of our most important cross company tools and used extensively by everyone. This guide is not intended to be a set of rules around using slack, this document is a guide to how we use slack. This should help everyone understand how to get the most out of slack while also being able to minimise distractions, notification noise and control their own focus time, without missing important updates from their team and the wider organisation. + +# Profiles + +[Filling in your profile](https://slack.com/intl/en-gb/help/articles/204092246-Edit-your-profile) helps people find and interact with you on slack, so it is important your profile has the following information: + - Full name + - A display name/handle that is discoverable, such as your first name + - A picture (it doesn't have to be of you, but a clear view of your face is preferable.) This helps keep profiles easy to distinguish at a glance. + - Your role/working group + - Your office location + - Your Made Tech email address + +You can also optionally add the following useful information to your profile if you feel comfortable doing so: + - A pronunciation guide for your name + - Your preferred pronouns + - Personal website, interests, hobbies + - Emergency contact number + + +# Channels + +Slack channels broadly fall under the following categories:- + + - Project channels (named after the project). If you are working on that delivery, it is expected you'll be in that channel, otherwise open project channels are optional. + - Supply channels (prefixed `supply-`). These channels are used by groups focusing on how we _supply_ deliverables. Optional unless directly involved with this group. + - Demand channels (prefixed `demand-`). These channels are used by groups focusing on how we engage with other organisations. Optional unless directly involved with this group. + - Group channels (such as `ops-` or `academy-`). Channels used by operational groups, optional unless directly involved. + - Specific purpose channels (usually prefixed with their temporary purpose, for example `bid-`). Temporary channels used for teams fulfilling a specific related task. Optional unless involved with the task, and will be archived after completion. + - General channels (no prefix). Company wide chanels such as `announcements`, `help` or regional channels such as `manchester` and _community of practice_ channels prefixed with `cop-`, these channels are used for cross company communication and tend have channel specific usage expecations, which should be detailed in their channel topic. + - Off topic channels (prefixed `x-`). These channels are entirely optional to join and use, feel free to create off topic channels if your interest or hobby is not yet represented! + - Bot channels or 'firehose' channels. It is occasionally useful to setup bots that post information to specific channels periodically, it is advised that you only need to join these channels if you are involved in monitoring such information. + +Every slack user will be in `#announcements` (in fact, you cannot leave this default channel), this is so that everyone can be reached in case of an important announcement. This channel is for pre-booked annoucements only so unless you have agreed an announcement with the People Team your message probably belongs in common-room. + +There are no other channels mandatory for _all_ users, but it is expected you will be in channels relevant to your working group. + +## Private channels and group chats + +Private channels can be used for specific tasks and group chats may be used to have small private discussions if necessary. It's worth noting that everything posted on our slack is logged and could be subject to a Freedom of Information request (specifically for channels relating to public sector projects), so it is wise to always use slack as if your message could be read. + +# Notifications and Availability + +We generally understand slack is an asyncronous tool - we do not expect immediate responses or constant availability. + +The team you are working with will expect a level of availability, which can be at odds with reducing notification distractions and focus. We encourage teams to communicate openly and agree ways of working that suit the individuals and the task at hand, and we recommend utilising 'notification free' focus time and respecting focus time of others where possible. + +# Threads + +We encourage you to keep specific discussions in general channels to threads. Responding to a message by creating a thread reduces notification bloat for other users of the channel, and you will only be notified of further thread responses if you are participating in that discussion. You can 'follow' and 'unfollow' threads to further control notifications you receive. + +# @ Usage + +## @user +You use @user to get a specific user's attention in any channel where you'd like to ensure they get notified about something important. + +## @here +Using @here will notify every user who is in the channel and active, for company wide mandatory channels this will usually be used to ensure important announcements are flagged. In other channels, feel free to use @here if you believe the post is immediately relevant to every user present. Some channels can get '@here noisy' such as `#help` where people are seeking to generate awareness, it is entirely reasonable to leave or mute such optional channels. + +## @channel +Using @channel will notify everyone in the channel who is present, and bypasses some settings such as muting the channel. This is only used for messages of the utmost importance and should generaly be used sparingly. + +# Conduct + +Please remember to be courteous, polite and treat your colleagues with respect, and while off topic and non-work chat is encouraged, please remember to keep such chat work friendly! + +# Emojis, bots, integrations + +We have many custom emojis, feel free to add more and use them. + +Many of our developers have built useful bots and integrations, such as the merit bot. Feel free to use these and develop your own, if you do so it is a good idea to present new additions in a company showcase! + +Many teams find external integrations useful if working with other supported tools, from setting up CI/CD alerts to more esoteric functions. You may need to contact an administator for some additions, but generally you're free to add useful external integrations at your own discretion. diff --git a/handbook/handbook-main/guides/it/software_licenses.txt b/handbook/handbook-main/guides/it/software_licenses.txt new file mode 100644 index 0000000000000000000000000000000000000000..8838ebc6f10ec8f4199bdf387990b733f460567a --- /dev/null +++ b/handbook/handbook-main/guides/it/software_licenses.txt @@ -0,0 +1,47 @@ +# Software + +## Software and licences including SaaS +Most standard software including SaaS applications will be set up on your laptop when you receive it. A standard toolset is being put together and we're implementing a way for everyone to easily access and download what they need. + +Some software is installed on Mac or Windows laptops to ensure we can keep the hardware safe and working, and to meet our CE+ and ISO certification obligations. Please do not attempt to remove the following software: +- Kandji - this is a management platform for our Apple devices. Kandji reports back to Aura on security settings, security updates and will allow us to remotely push out settings like the Made Tech VPN connection and virus protection +- SentinelOne - this is anti-virus software +- ThreatLocker - this enables the enhanced administrator access +- N-Central - this allows Aura to provide remote support by viewing and taking control of your device + +## Requesting access to software +If you need something that isn't installed please don't just go and buy it or use a free trial - we probably already have a licence and can get you set up. In some cases we may ask you to use our standard tools rather than a personal preference as we're looking to avoid duplication in having many tools performing similar or the same job. We also need to demonstrate that we have the correct measures in place to protect our data, our clients' data, and their customers' data. The tools we use are a key part of that. + +This is not intended to place barriers in the way of teams having access to the tools they need to function, we just have to know what we're using and who is using it. + +If you would like to request new software that Made Tech doesn't currently use as standard, or if a client is requesting use of a specific tool, please use [this form](https://docs.google.com/forms/d/14yjYQttTsW38g0gUCTo5gqeUcLd1fFyk8O2pL5PyOr8/edit) to do that. This will go to the Operations Team to review and they'll come back to you directly to clarify anything and talk about set up, onboarding etc. + +## Standard Software +If you need access to existing software email [it@madetech.com](mailto:it@madetech.com) (except where indicated). This is not an exhaustive list (we're still working on that). + +- Google Workspace +- [Slack](https://github.com/madetech/handbook/blob/main/guides/it/slack.md) +- Trello +- [Miro](https://github.com/madetech/handbook/blob/main/guides/it/Miro.md) +- Salesforce / Kimble (slack #ops-kimble-support) +- 1Password +- Learnably +- HiBob (slack #team-people) +- GitHub +- Microsoft Teams +- Workable (slack #team-people) +- Xero (slack #ops-finance) + +### Role specific (Request required) +- Amazon Web Services (AWS) +- Microsoft Azure +- Jetbrains +- [Docker](https://github.com/madetech/handbook/blob/main/guides/it/docker.md) +- Figma +- Dovetail +- Consent Kit +- Adobe Creative Cloud or other Adobe applications +- Lucidchart +- Office 365 +- TablePlus +- Tuple diff --git a/handbook/handbook-main/guides/it/vpn/README.txt b/handbook/handbook-main/guides/it/vpn/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..0f00e0585e738fb723ca3243c340771d67fde9a5 --- /dev/null +++ b/handbook/handbook-main/guides/it/vpn/README.txt @@ -0,0 +1,9 @@ +## Connecting to Made Tech - VPN + + +This is a guide to connect to the Made Tech Virtual Private Network (VPN). + +- [Link to VPN instructions](https://drive.google.com/drive/folders/14w3BXtsrgUqRmJ73QFhGXiCo3ufjvMmI) + + + diff --git a/handbook/handbook-main/guides/jury_service.txt b/handbook/handbook-main/guides/jury_service.txt new file mode 100644 index 0000000000000000000000000000000000000000..76f293bfab640b50b5acd2b14645f51bcd735317 --- /dev/null +++ b/handbook/handbook-main/guides/jury_service.txt @@ -0,0 +1,12 @@ +# Jury Service + +If you are summoned for Jury Service, the process is simple... + +* Speak to your Made Tech and Client teams to let them know and to be sure that there is no reason you should ask for a postponement +* Book the appropriate amount of time off as... + * Policy Type: Out of Office (Paid) + * Reason: Jury Duty + +While at court... + +* If you are asked whether a trial lasting longer than 2 weeks will cause problems with your job, the answer is yes. If you have any questions, please check with your line manager and/or account team. diff --git a/handbook/handbook-main/guides/learning/README.txt b/handbook/handbook-main/guides/learning/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..1bcefe34ae8a07e2f4d6a5fe69cf798e4d2f2550 --- /dev/null +++ b/handbook/handbook-main/guides/learning/README.txt @@ -0,0 +1,61 @@ +# Learning and development at Made Tech + +Learning and mentoring is a core value at Made Tech. We strive to continuously learn and improve ourselves. We want to share our own knowledge with others and adopt a mentoring mindset, both with team members and clients. + + +## What resources are available? + +All team members receive an annual individual learning budget (pro rata’d) to support them with their professional development at Made Tech, whether that is for their current role or, to support their progression and career pathway at Made Tech. Individual learning budgets can be viewed and accessed via Hi Bob. + +It is important that you are investing your individual learning budget on resources that will help you to develop professionally and we will only approve requests that support this. + +We know that individuals all learn in different ways therefore there is a lot of variety in terms of how you could invest in your learning budget, examples could be (not exhaustive): + +Professional memberships +Conferences and events +Subscriptions +Specialised courses +Books +Webinars + +Individual learning budgets are there for you to invest in your professional development, therefore any resources outside of this will not be approved. In addition, individual learning budgets are not able to cover the following: + +Equipment +Software +Virtual games +Travel and expenses + +Where you spend your individual learning budget is not restricted, we would just ask that you use a reputable site if you are purchasing online so you know you are making a safe purchase. Further information on individual learning budgets and how to accces in Bob can be found in the team member guidance document. + +There is also a variety of learning content developed and shared by people at Made Tech, plus partnerships with external providers for anything that we can't deliver in-house, like certifications and specialised courses. + +### In House learning programmes + +Intro to Line Management + +We deliver an inhouse intro to line management programme for all individuals or are new to line management at Made Tech. We are currently reviewing this course and looking to launch a revised programme by Quarter 3 (Dec-Feb) + +Technical Training: Clean Code 101 + +We deliver an in person Clean Code 101 training programme, a bootcapmp covering programming concepts which is suitable for all Engineering levels. This programme is delivered througout the year - more information can be found at https://learn.madetech.com/technology/calendar/ + +Technical Training: Recapping TDD and Testing along the spectrum + +A 1.5 day in person boot camp aimed to build confidence in 'test driven development' using different tools across different areas of teating. This programme is delivered througout the year - more information can be found at https://learn.madetech.com/technology/calendar/ + +What is Consulting and How I should do it at Made Tech. + +A one day in person bootcamp covering the consulting market, how Made tech fits into that market, how to approach account strategy and influence your client. This course is suitable for all roles at Made tech. This programme is delivered througout the year - more information can be found at https://learn.madetech.com/technology/calendar/ + + +### When joining Made Tech +Based on the feedback we have received that more junior roles in Made Tech would benefit from having an increased budget available to support their development earlier in their careers, and that senior roles would benefit from investment in a more custom learning programme, we have introduced a tapered amount dependent on role level. + +### When leaving Made Tech + +Individual learning budgets will end as a benefit from the day it’s confirmed that a team member will be leaving Made Tech (e.g. when their notice has been accepted). + +## Showcases + +We have showcases every Friday between 4:30pm and 5pm. You'll have opportunities to present to the team, or learn something new from other teammates. All full-time team members should come along when work commitments allow. + diff --git a/handbook/handbook-main/guides/line-management/121s.txt b/handbook/handbook-main/guides/line-management/121s.txt new file mode 100644 index 0000000000000000000000000000000000000000..916bd0ba5595af0ec01ed1dbfd06d4fd55dc722d --- /dev/null +++ b/handbook/handbook-main/guides/line-management/121s.txt @@ -0,0 +1,43 @@ +# 121 Meetings + +You should meet frequently with your direct reports for a minimum of 1 hour per month. + +There may be periods where you meet your direct reports more frequently or for longer/more frequent times per month, such as during their probation period. + + +## What are 121's used for? +121's are dedicated time for coaching, mentoring, and giving people space to reflect and grow: + +You might talk about: + +- What is expected of my role at Made Tech? +- How do I deal with this difficult thing? +- How do I progress in my career? +- Feedback, whether given or received +- Any other topic you both feel is valuable + + +## Our 121 tool +We use the 121s section on bob to schedule and take notes of all our 121's. These notes become data points that your direct reports can use to prepare for annual reviews and promotions. A scheduled 121 will have a list of 'Talking points' (agenda) that you can setup in advance. It's also an easy way for direct reports to ask peers for feedback and set objectives for career progression. + +## Line Manager 121 expectations + +We expect you to: + +- spend a minimum of 1 hour per month with each direct report +- record 121s and notes on bob +- to start with, set the agenda and lead the 121 meetings +- provide clarity on role expectations and performance +- help prepare direct reports work towards career progression (or passing probation) +- share and encourage feedback + + +## Direct report 121 expectations + +We expect you to: + +- take ownership of setting and reviewing goals frequently +- set 'Talking points' ahead of 121's +- prepare examples of work or feedback you want to talk about +- take notes in the 121 section on bob +- over time, take the lead with setting the agenda and leading the 121 meetings diff --git a/handbook/handbook-main/guides/line-management/README.txt b/handbook/handbook-main/guides/line-management/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..c3edb97626be26dda9a415d822be64b9b7f8651f --- /dev/null +++ b/handbook/handbook-main/guides/line-management/README.txt @@ -0,0 +1,44 @@ +# Line management at Made Tech + +Line managers help others to learn and grow, deliver great results, and progress their careers. + +People who report to a line manager are called "direct reports". + +This guidance isn't complete yet. If you need help, ask: +- your own line manager +- you can search our knowledge base - Ask Made Tech, and if you can't find an answer there, feel free to raise a query +- ask one of the people partnering team +- the line manager community (**#cop-learning-line-managers** on Slack) + + +## What do I need to do as a line manager? + +### 121 meetings +Hold regular 121 (one-to-one) meetings, at least once a month. + +[See more guidance on 121s](./121s.md) + +### Probation +Help your direct reports to pass their probation period. +Work with your 'Head of' to extend or fail probations, if necessary. + +[See more guidance on probation](./probation.md) + +### Annual reviews +Hold a review once a year, reflecting on the year's highlights and challenges. +This usually includes a salary review. +This may include setting goals or themes for the coming year. + +[See more guidance on annual reviews](./annual_reviews.md) + +### Promotions +Help your direct report make a case for being promoted. + +[See more guidance on promotions](./promotions.md) + +### Help underperforming people +Help them understand where they are underperforming. +Help them plan to improve in these areas. +As a last resort, give notice of terminating employment. + +[See more guidance on helping underperformance](./performance.md) diff --git a/handbook/handbook-main/guides/line-management/annual_reviews.txt b/handbook/handbook-main/guides/line-management/annual_reviews.txt new file mode 100644 index 0000000000000000000000000000000000000000..ea50a6d106bafafb4eb0f7a885f6e9b4c44e2066 --- /dev/null +++ b/handbook/handbook-main/guides/line-management/annual_reviews.txt @@ -0,0 +1,22 @@ +# Annual Reviews + +As a line manager, one of your responsibilities is to facilitate the annual reviews of the individuals you line manage. The annual review is a retrospective of the previous year, a look ahead at the coming year and typically a [salary review](../compensation/salary_reviews.md). + +The annual review will take place between April and May each year. + +## What should I do to prepare? + +It's recommended you advise and guide your team member to collect and collate evidence of progress and growth continually through the review period. + +You should also take the time to prepare a summary of the highlights and notable events of the review period to share with your team member, and think about guidance and goals for the next review period. Try to identify key areas of growth for the coming review period, constructive feedback from the individual's team will be key to this. + +## Summary +1. Book in annual review meeting with team member +2. Gather feedback +3. Complete annual review form on Small Improvements +4. Agree and set objectives (this may be in the review or as an additional meeting if preferred) +5. Enter agreed objectives on Small Improvements + +Our [annual review](https://docs.google.com/document/d/1B9DZHdytIXpy17ns-gSWCm62MS0eCBbIWTv6otvROKA/edit) guidance provides additional information regarding processes and responsibilities. + +Reviews should always be supported throughout the year with regular 1:1’s and feedback should be actively sought at those regular intervals. diff --git a/handbook/handbook-main/guides/line-management/performance.txt b/handbook/handbook-main/guides/line-management/performance.txt new file mode 100644 index 0000000000000000000000000000000000000000..b661da0b024c273dad1e8cb12690ef88c47cc4f9 --- /dev/null +++ b/handbook/handbook-main/guides/line-management/performance.txt @@ -0,0 +1,57 @@ +# Performance Management + +At Made Tech we believe every team must promote an open, honest feedback culture and collectively work to improve and maintain psychological safety. + +Occasionally, a team will need support in helping an individual meet the expectations placed on them, which is something that will fall to you as a line manager to support on. + +There's no one-size-fits-all performance management process, it is instead a process tailored to the individual and the support they need. + +## What is performance management? + +In a general sense, the process of performance management will involve understanding the ways in which your reportee does not currently meet expectations and supporting them to work out a plan to improve. You will need to set goals and measure outcomes, which means defining how you will measure success with your reportee and their team. + +As a last resort, you may need to serve notice of termination of employment. + +## Where do we start? + +The trigger to begin a performance management process is usually concerns about an individual's ability to meet expectations is raised by their team lead, to the people team or to their line manager. + +When this happens, it's important to confirm performance management is a necessary step. + +Begin by speaking to the team lead that has raised concerns, your goal is to understand the ways in which the individual is falling short of expectations, what has been done within the team to support them and what feedback they have already received, and what successfully meeting expectations would entail. + +It's important to note that each team should provide support and give useful, constructive feedback. If you aren't satisfied this is the case, you should be clear that you believe these steps need to be taken before performance management, and you should support the team to provide the necessary feedback and review performance periodically. + +Meet with your reportee and the Head of People. The purpose of this is to begin with an empathetic approach and understand if there are external factors or issues affecting your reportee that we can provide support with, doing so may avoid direct intervention. + +The decision to begin performance management officially will be made between an individual's line manager, their team lead, and the Head of People. + + +## Performance management is necessary, what's next? + +The decision has been made to seek direct intervention, which will be your responsibility as line manager. Your next step should be to work with your reportee to form a set of measurable goals that will show they are able to meet the expectations they need to in order to succeed as part of their delivery team. + +Unfortunately, giving detailed guidance for this is difficult as it will depend heavily on the situation at hand, the people team and the line manager community of practice will support you as much as possible. Remember the key points: + - Approach the situation with empathy + - Clearly identify what we need to do, and how + - Clearly identify how we will measure success + - Clearly define the timeframe for meeting expectations + - Be honest and open about the situation - remember that feedback is information + +Review progress as often as possible, ideally every week during this process. Remember that this process can be intense and a source of anxiety, again refer to the people team for support we can offer to everyone involved. Reassure your reportee that we want to see them succeed in their role! + +## Ending performance management + +Ideally, you reportee will be able to show progress and reach the goals you've set together, and will no longer need close monitoring. Gain endorsement from their team lead that this is the case, and inform the Head of People that you'll cease performance management officially. + +It's important from here that support structures you've built together don't immediately disappear, it's recommended to keep iterating on the goals and growth plan, and to review outcomes regularly, gradually reducing the review frequency to a normal cadence. + +Reassure your reportee that having extra support and direct intervention will have no long term impact on their career growth. + +## Terminating employment + +It's really important to be explicit about what the outcomes we are looking for are and also balance that with eventual consequences of not seeing improvements to a persons performance. + +We want to do everything we can to support someone who is not meeting expectations and that is our first aim. + +In some cases, and as a last resort, we may need to serve notice of termination of employment. This would be supported by the Head of People and you should engage them in this process as soon as underperformance is identified. diff --git a/handbook/handbook-main/guides/line-management/probation.txt b/handbook/handbook-main/guides/line-management/probation.txt new file mode 100644 index 0000000000000000000000000000000000000000..2248d6d2f35e56301a8327a6d232f5f146ae9e7a --- /dev/null +++ b/handbook/handbook-main/guides/line-management/probation.txt @@ -0,0 +1,114 @@ +# Probation at Made Tech + +When someone joins Made Tech, they're "on probation" for three months. +This means their notice period is shorter - usually one week. + +At the end of probation, people either pass or fail. Most people pass. +Rarely, you'll extend probation, or pass someone early. + +This guidance is written for line managers, but may be useful for people on probation too. + +- [What happens during probation?](#what-happens-during-probation) +- [Explaining how to pass probation](#explaining-how-to-pass-probation) +- [One-to-one meetings during probation](#one-to-one-121-meetings-during-probation) +- [Finishing probation](#finishing-probation) + +## What happens during probation? + +In the first week, explain probation to your direct report. Talk about what it is, and how to pass it. + +Each week, meet them one-to-one. +Get feedback from their team, and reflect on it together. You should clarify the need for constructive feedback here - it's important to set progression goals and this helps identify areas for development. +Ensure clarity on role expectations and core values. +Talk often about whether they're on-track to pass. +Be honest and upfront about concerns or skills gaps and support your direct report by providing clarity on what those are, and discuss finding opportunities for them to demonstrate progress. + +Before the end of the probation period you must have confidence that the team member meets their role expectations and is aligned with our core values. Demonstrating both of these generally means that they are a great addition to our team and will help drive the company goals forward. Absence of either of those needs to be looked into more closely. + +### Week 6 + +This is a great time for a half way review. Discuss how their time has gone so far, reflect and review on feedback and work examples you have already discussed and identify what you want to focus on for the following 6 weeks. +Feedback is easier to receive if you give colleagues a heads up and a chance to better observe you. Send out a probation feedback request to the team leads, peers and other stakeholders they work with via Small Improvements asking to observe the team member for the following 4 - 6 week. A template 'Probation Feedback' is available to use. + +### Week 10 + +It's time to review the feedback you have received over the past few weeks. If you are missing feedback then this is a good time to nudge colleagues. +Reviewing the feedback during week 10 will allow a further 2 weeks (week 12 is your probation review) to reflect and work through anything that is unclear or outstanding. + +### Week 10 - 12 + +Please see 'Finishing probation' below. + +## Explaining how to pass probation + +Talk about what good looks like for your direct report's role. [The handbook role pages](../../roles/README.md) may help with this. +It's good to spend the first two weeks talking about this. + +Explain that feedback is useful evidence on how they're performing. + +Tell them to ask their team for feedback. You can talk to their team directly to help get more feedback, if needed. + +### Worries about failing probation + +It can be stressful to be on probation. Explain early that: + +- Most people pass +- Getting regular feedback means the result won't be a surprise +- You will guide and support them + +## One-to-one (121) meetings during probation + +Read our [general guidance for 121 meetings](./121s.md). + +In probation, focus more on: + +- Giving and receiving feedback +- Reflecting on feedback together +- Whether they're on-track to pass + +Feedback can be difficult to get. If it's not clear whether they are on-track four weeks in, ask their team for feedback directly. + +## Finishing probation + +Make a recommendation on behalf of your direct report to your 'Head of'. This is done through Hibob. + +Actioning a probation through Hibob. +This is done via your direct reports profile > Actions > Employee Updates > Probation. + +You’ll have the space to add in all feedback gathered from you and your direct report, finishing this recommendation with either a “pass”, “Extend” or “Fail” decision before submitting. +Once submitted, this will go straight to your 'Head of’ for approval. + +Highlight feedback from the team about them and a short summary of how they demonstrated meeting or exceeding their role expectations and our core values. Be sure to include balanced feedback that also includes areas for development or further focus and growth for your team member based on the feedback provided or that you have observed as line manager. + +*Your 'Head of' will make the final decision on whether to pass, extend, or fail probation, informed by your feedback* + +### Passing probation + +Once your Head of has confirmed they agree with your recommendation to pass probation, congratulate them on passing probation. Confirm their new notice period (this will be reflected in your Hibob profile under the section, Work). The People team will action post-probation benefits.* + +Decide together how often to have one-to-ones from now on (we'd recommend a minimum of monthly). + +### Failing probation + +Ensure conversations happen early on to assess and review progress during the probation period and gives your direct report an opportunity to improve. + +If there is no/limited progress, get in touch with your Head of and the People team. Explore and agree next steps. + +If the probation period has not been successful, hold a probation review meeting where you will tell the individual they haven't passed probation, and give them notice of their employment with Made Tech ending. + +It can be difficult and stressful for all involved. Talk to the People team for support. + +### Extending probation + +Sometimes, it's not clear at the end of probation if someone would succeed at Made Tech long-term. + +In these rare cases, work with your 'Head of' to extend probation, agreeing on a fixed amount of time. Let the People team know of any extension so they can update relevant systems too. + +Being on probation can be stressful. Think carefully when deciding between extending and failing. + +### Learning from failed probations + +Failed probations sometimes mean something went wrong in our hiring. + +Talk to the hiring team and the People team about a failed probation, to see if anything can be learned or changed. + diff --git a/handbook/handbook-main/guides/line-management/promotions.txt b/handbook/handbook-main/guides/line-management/promotions.txt new file mode 100644 index 0000000000000000000000000000000000000000..0cdf621e609bdd9b1e25549f0c7b5b56d6541136 --- /dev/null +++ b/handbook/handbook-main/guides/line-management/promotions.txt @@ -0,0 +1,25 @@ +# Promotions + +This guidance is written mostly for line managers. It'll help you understand how promotions work at Made Tech. + +You're responsible for supporting people you line manage when they want to get promoted. + +## When should I encourage someone to apply for promotion? + +It's difficult to provide a one-size-fits-all answer to this question, but ultimately this decision is made when both you and the individual you line manage feel that individual is ready to take on a new role. Signs this might be the case could include: + +- They exhibit some or all of the core competencies for their desired role +- They are consistently evidencing some or all attributes that are described in the [SFIA level](https://sfia-online.org/en/sfia-8/sfia-8) that corresponds to their desired role +- They have examples of exemplary work or feedback received +- They have received endorsement from the leads of their current project +- They display the potential to succeed in the desired role + +## How do I seek promotion for someone? + +Team members may apply for any open role in their career path listed on our careers page via [Workable](https://referrals.workable.com/made-tech/jobs/). If the role the individual you line manage is interested in a role that is not listed on this list please inform your head of team so we can collate date about our internal demand. +You can find more information about the promotions process in our [Promotion Guidance for client facing team members](https://docs.google.com/document/d/1LjchEGWCVxeyCo4PTYZxd1PL0DKPUx_8AoT3F67ifoo/edit) or Promotion Guidance for our group facing team members (link will be updated soon) + + +### What should I do if the promotion case is unsuccessful? + +In the event the promotion application is unsuccessful, feedback will be provided by the interviewing panel and the team members will have the opportunity to appeal. diff --git a/handbook/handbook-main/guides/mentorship/README.txt b/handbook/handbook-main/guides/mentorship/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..e4d0b507ca9d9da95c8b30f71a80f19006aa3483 --- /dev/null +++ b/handbook/handbook-main/guides/mentorship/README.txt @@ -0,0 +1,40 @@ +# Made Tech Mentorship Guide + +At Made Tech, mentorship enables Made Tech staff with the opportunity to provide guidance and support to people in the wider tech community. Mentees are able to gain new knowledge and support and develop and enhance their skills. + +## General Guidance + +* Be kind, have empathy and be supportive +* Don’t share personal information about your mentee in open forums +* Please give at least 48 hours notice before moving or cancelling your session, so that both parties have a chance to adjust their schedules +* When first meeting, take some time to outline what goals you’d like to achieve, and how long it might take to achieve them. We recommend setting somewhere between 6 and 12 sessions and reviewing at the end to see where to go from there. + +## Mentee / Mentor Matching + +Once you're matched up, we'll send an introductory email introducing you to your mentor. + +## First session guidance + +If you have a particular approach or mentorship / pairing style that you’d like to, please feel free to use it. Here are some suggestions to get the ball rolling on the first session: +1. Introduce yourselves +2. Outline goals and objectives +3. Discuss what you both would like out of the sessions - Set some [SMART Goals](https://www.mindtools.com/pages/article/smart-goals.htm) +4. Discuss preferred pairing styles - It’s likely that you will be pairing during the sessions. We recommend using Visual Studio Code Live Share +5. Discuss how frequently you would like to have sessions + +## Before your sessions + +Discuss what you will be pairing on during your sessions. In terms of what you could pair on, a good option would be to use some of the following: +- https://learn.madetech.com/technology/katas/ +- https://learn.madetech.com/technology/koans/ +- https://www.codewars.com/ + +## Any questions? + +Feel free to ask any questions in the #cop-mentoring channels or send an email to mentorship@madetech.com. + +## Mentor and Mentee Guidance + +Refer to the following guides for specific mentor/mentee guidance +- [Mentor Guidance](mentors) +- [Mentee Guidance](mentees) \ No newline at end of file diff --git a/handbook/handbook-main/guides/mentorship/mentees/README.txt b/handbook/handbook-main/guides/mentorship/mentees/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..46e48ae7a4d511566a777d52d33a6ebf07a05b39 --- /dev/null +++ b/handbook/handbook-main/guides/mentorship/mentees/README.txt @@ -0,0 +1,17 @@ +# Mentees + +## What to do once you're paired? + +After your initial session, it will be your responsibility to create sessions with your mentor. + +## Before the session + +### Learning Style + +Everybody learns differently, if you have an awareness of your learning style it might be worth sharing this information with your mentor as it may help them when pairing with you or suggesting resources to try in your own time. + +For example, if your learning style is visual you may prefer seeing diagrams when the mentor is explaining new concepts for the first time. + +### Set Your Expectations + +It might be beneficial to have a list or a mind map on the technical skills you would like to develop. You could try pair programming on coding katas (coding exercises) with your mentor instead. Codewars is a good place to sign up and start together. diff --git a/handbook/handbook-main/guides/mentorship/mentors/README.txt b/handbook/handbook-main/guides/mentorship/mentors/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..d264310c5460cd5aa7cf86c0a02c826329a71f77 --- /dev/null +++ b/handbook/handbook-main/guides/mentorship/mentors/README.txt @@ -0,0 +1,48 @@ +# Mentors + +Thank you for signing up to be a Made Tech mentor. Here’s a little guide for how to prepare and go about the sessions. + +The point of doing this is to provide an opportunity for people to expand on their coding skills from professionals in the industry, but also to provide those looking to enter the industry with an insight into what it can be like. + +As a mentor, you will be supporting people at various stages on their tech journeys, these could be people who applied to the Academy, or people who are members of various tech communities or networks. You get to help someone by sharing both your technical and non-technical knowledge and experience, helping them grow on their fundamentals or understand some tricky concepts. + +## Mentor / Mentee Pairing + +There are two ways that we will be pairing mentors with mentees + +### Academy Support + +Some people who have applied to the Academy will be allocated mentors. These will either be people who will be joining the next run of the Made Tech Academy, or who need more support for a future application. + +### Availability and Skill Match + +We may have people who get in contact either directly, or through external tech communities looking for support from a mentor with a particular skill. We will pair based on the skills they would like to develop. + +When you are paired, we will give you the following information about the mentee in order to make contact. + +- Name +- Email Address + +Please contact your mentee via email, you and your mentee should arrange the time for your sessions. + +## Booking the Sessions + +Once you’re matched up, you will be put in touch with your mentee via email and on slack. If you don’t receive a message within a couple of days of the pairing being allocated, please let me know. + +It could be useful to set up a [Calendly](https://calendly.com) account, and the mentee can use this to put time in your calendar. + +Once the first session is arranged, you’re good to go! + +## Your Sessions + +How you conduct the sessions is up to you! As mentorship is currently done remotely, all you’ll need to do is join the hangouts/zoom link created in your calendar by Calendly. + +The first session will likely be filled with introductions and discussions of expectations, but no doubt that you will both want to get coding pretty quickly. Feel free to find a plan that works for both you and your mentee. + +## Mentoring Successfully + +- Outline expectations and ground rules from the outset +- Ask the mentee their learning priorities, check that they’re on track +- Mutually set goals with your mentee +- Be clear about your contact schedule +- Hold each other accountable diff --git a/handbook/handbook-main/guides/office/clear_desk_clear_screen.txt b/handbook/handbook-main/guides/office/clear_desk_clear_screen.txt new file mode 100644 index 0000000000000000000000000000000000000000..08bf719085abc669a3ae3854eaa76ef6389e9794 --- /dev/null +++ b/handbook/handbook-main/guides/office/clear_desk_clear_screen.txt @@ -0,0 +1,23 @@ +# Clear Desk/Clear Screen + +Made Tech operates a Clear Desk/Clear Screen policy. This means that all sensitive/confidential materials should be removed from a user workspace and secured when no one is using it. + +## Clear Desk: +- All ‘Confidential’ information must be hidden from view when not being actively used +- Hard copies should be kept in locked drawers or returned to the appropriate place in the office +- Drawers/files containing sensitive information must be kept closed and locked. The keys to these drawers/files should be kept in a secure location and not left unattended at any time +- Printouts should be immediately removed from the printer +- When no longer needed, sensitive documents should be shredded in the office shredder +- Passwords to confidential material should not be left on pieces of paper, sticky notes, or left unattended on a desk + +## Clear Screen: +- If you need to leave your workstation for any reason, you should ensure your screen is locked and not visible +- If you are using multiple screens, ensure you remain aware of what is displayed on both screens +- When working outside the Made Tech Office (either from home, onsite with a client, or in a public space) ensure you remain aware of your surroundings and who may be able to view your screen. + +### Devices: +- When not in use, turn off your device to ensure disk encryption is enabled. +- USB drives or other mass storage devices should be secured a locked drawer when not in use. Personal data (as defined in the Data Protection Act 2018) must not be stored on such storage devices + +### Other: +- Confidential and restricted information should not be displayed on any whiteboards or sticky notes around the office diff --git a/handbook/handbook-main/guides/office/dress_code.txt b/handbook/handbook-main/guides/office/dress_code.txt new file mode 100644 index 0000000000000000000000000000000000000000..c6f7694144224af268a9057314e4bc348c28f001 --- /dev/null +++ b/handbook/handbook-main/guides/office/dress_code.txt @@ -0,0 +1,10 @@ +# Dress Code + +Made Tech is typically a casually dressed environment, however we have a need as an organisation to project a level of professionalism to each other, customers, potential hires, and other outside collaborators. + +This should be considered a rough guide as to acceptable dress in the Made Tech office. If you're working on-site or visiting a customer organisation you should be sensitive to their dress code and modify your dress accordingly. If in doubt please seek advice from another member of the team. + +## Generally not OK for the office: + +- Tracksuit bottoms / sweatpants +- Sports-style shorts diff --git a/handbook/handbook-main/guides/office/kitchen.txt b/handbook/handbook-main/guides/office/kitchen.txt new file mode 100644 index 0000000000000000000000000000000000000000..b32ede88f5e39ee1bd7c2a5377ce558cb11facad --- /dev/null +++ b/handbook/handbook-main/guides/office/kitchen.txt @@ -0,0 +1,36 @@ +# Kitchen Etiquette + +We share the kitchen space with each other as well as with our customers. We have put together a few guidelines for keeping the kitchen nice and tidy. + +While we don’t have a designated employee solely responsible for restocking fridges and cupboards, if you see empty stock in fridges and cupboards, please use the overstock (labelled) to restock these areas. The Ops team try to keep on top of this, but some days can be busier than others, and we may not be in the following day. We want to try and ensure everyone is greeted with stocked drinks and snacks upon arrival. + +## Coffee + +We love our coffee at Made Tech. We have fresh beans regularly delivered to the office and have multiple thermos drip coffee jugs that keep coffee lovely and fresh. Please ensure: + + - When grinding beans that no meetings are going on in the meeting room as it's very loud and can interrupt voice calls and conversations + - When you're done making coffee that you tidy up any spillages so the kitchen is left in a clean state + +## Dirty glasses, cutlery, and crockery regime + +We all appreciate a clean and orderly kitchen, and a clear sink. This is why everyone should put their dirty tableware in the dishwasher. + +Before using the dishwasher, please familiarise yourself with [accepted dishwasher loading conventions](https://www.wikihow.life/Load-a-Dishwasher). + +Please ensure: + + - When you're finished with any tableware that you rinse them and put them in the dishwasher + - When the dishwasher is full, then load it with a cleaning agent and start it + - When the dishwasher is running already, then wash your items in the sink with detergent instead + - When the dishwasher has finished and has clean items in it, empty it. Then put your dirty items inside! + +## Rubbish rules + +We are passionate about recycling at Made Tech, please familiarise yourself with which items should be recycled on [First Mile's Dry Mixed Recycling](https://thefirstmile.co.uk/business-waste/collection/mixed-recycling) page. + +When using the bins, there are a few things to keep in mind: + + - Put the right items in the right bins. Recycle! + - When recycling, make sure your items are clean + - Keep the bins clean, no one likes messy bins. When a bin accidentally gets dirty, wipe it down with some damp paper towels + - When a bin is full, remove the bin liner and close it, then put in a new bag diff --git a/handbook/handbook-main/guides/office/officehandbook.txt b/handbook/handbook-main/guides/office/officehandbook.txt new file mode 100644 index 0000000000000000000000000000000000000000..6e7e8ad991b63e92f81c79a9c0cc5545678f1ef4 --- /dev/null +++ b/handbook/handbook-main/guides/office/officehandbook.txt @@ -0,0 +1,122 @@ +# Office handbook + +Each office has its own individual office handbook packed with information to help you understand areas such as +access, meeting rooms and connecting to the internet. +Please take a look at the [main office handbook](https://docs.google.com/document/d/1trOGW8mUDmMhDLLJxZwi194WkA6liFk1j0wiAu27C3Q/edit) +(internal link) which holds general office information and links to the regional handbook for the office you are attached to. The office handbooks are also pinned to the top of the relevant office slack channel. + +For any queries regarding offices please email [operations@madetech.com](mailto:operations@madetech.com) or get in contact via slack #ops + +# How to book a desk + +You can book a desk in any office using [Office RnD](https://hybrid.officernd.com/community/madetech/dashboard?date=2023-06-02). There is more information on how to book desks for yourself, your team and any visitors [here](https://docs.google.com/document/d/1wCGrHN-prrUt8RnyNux2MshCTQ36D_rvTKTeu1qJwMk/edit) (internal link). + +# Access information + +Below is information on access and layout for each of our offices. If anyone has a disability that may require additional needs whilst in an office, please slack either #ops or email [operations@madetech.com](mailto:operations@madetech.com), and we will assist you with completing a PEEP. + +# Office etiquette + +Please leave desks and meeting rooms as you (should hopefully) find them. This means making sure all the equipment, including stationery, remotes, USB-C cables, keyboards, etc., are back where they should be. Chairs should be returned to the correct desk or room, and meeting room tables should be clear. + +## London + +### Entry to London + +Entry to the office is via the stairs. Due to the steepness of the steps, we are unable to add ramps for wheelchair access. + +There are steps at the front door to enter the building and a narrow staircase. + +There is a spiral metal staircase joining the first and second floors within the office. Alternatively, you can exit the office and use the entry staircase. + +### Layout and office information + +There are low beams on the ceiling. + +The floors are hardwood, they are fairly flat. + +The office is split over two floors. The office is all open space with one large and one small meeting room available on the second floor. The first floor has glass partitions but these do not exclude all office noise. Both floors can be quite noisy. + +The kitchen is on the second floor, and access is through double doors made of glass. They are relatively light to open and open inwards and outwards. You can access snacks and cold drinks from lower cupboards, and some snacks are laid on the counter. Kettles and coffee machines are stored on the worktops. Mugs are stored in upper cupboards. The dishwasher is integrated into the lower cupboard units. + +Most of the desks are adjustable with extension leads to plug into located on top of the desks. + +The toilets are on the first floor. They are unisex, with four stalls and one shower. + +There is a shared external garden space, which is only accessible by metal grilled stairs with a gap to the immediate right and no handrail. Anyone with balance difficulties might need assistance. + +### Health and safety information +There is no visual fire alarm, only an audio alarm. + +The office is brightly lit. + +There is no Braille in the office. + +Fire and first aid information can be found on the notice board. + +## Bristol + +### Entry to Bristol + +The office and all its facilities are on the ground floor. + +Entry to the Made Tech office does not involve steps when entering through the Runway East entrance; there are three steps and an escalator to enter through the 101 entrance. + +The office is on the same floor as the entrance and requires access via two key card-locked fire doors. + +The doors are wide enough for a standard wheelchair. + +### Layout and office information + +The desks are a set height (approximately 70 cm) with extension leads to plug into located on top of the desks. + +The office is all open plan and can get quite noisy. + +The kitchen is a shared kitchen within Runway East; there are dishwashers within the lower cabinets, as well as a full-height fridge. Cups are stored in an upper cabinet which may be difficult for some people to access without assistance. Hot drinks supplies are stored on the countertop and may be difficult to access from a lower height. + + +### Health and safety information + +There is an audio fire alarm, but no visual fire alarm. + +The office is brightly lit. + +There is no Braille in the office. + +Toilets are gendered, with accessible toilets within the gendered bathroom. Only the accessible toilets have self-contained hand-washing facilities. + +There are wheelchair accessible showers, however these are currently located within gender segregated bathrooms. + +Fire and first aid information can be found on the notice board. + +## Manchester + +### Entry to Manchester + +There is a wheelchair ramp on the left of the main building entry door with an automatic door at the top. The office is on the 4th floor; there is access via both stairs and lifts. The Manchester office is accessible to anyone using a standard wheelchair. + + +### Layout and office information + +The desks are a set height (73.5 cm tall) with extension leads to plug into located on top of the desks. One desk raiser is available, allowing one desk to be converted into a standing desk. + +Pathways within the office are wide enough to be easily accessed by a wheelchair. + +The office is all open plan and can get quite noisy. + +The kitchen is on the same floor as the office and is a shared kitchen; there are no doors to access the kitchen. Cups are stored in upper cabinets, while plates are in lower cabinets. Hot drinks supplies are stored on the countertops in the kitchen; these may be difficult for some people to access without assistance. There is a dishwasher in a lower cabinet. There is a microwave on the counter and one in the upper cabinets. + +The ground and 4th floors have accessible toilets. + + +### Health and safety information +There is a non-hearing and visual fire alarm system in the office and on the 4th-floor landing. + +The office is brightly lit. + +There is no Braille in the office. + +Fire and first aid information can be found on the notice board. + + + diff --git a/handbook/handbook-main/guides/onboarding.txt b/handbook/handbook-main/guides/onboarding.txt new file mode 100644 index 0000000000000000000000000000000000000000..a91d2f1a329a9ce48decbe2f2815cf69f2f4adfb --- /dev/null +++ b/handbook/handbook-main/guides/onboarding.txt @@ -0,0 +1,46 @@ +# Onboarding + +## Before your first day + +Once you’ve signed your contract, we’ll contact you about what you need to get ready for work. We’ll send you a laptop to your chosen address, and check that you’re all set up for working from home. +We’ll start getting you approved to work in the public sector. This is called a Baseline Personnel Security Check (BPSS). We’ll arrange an online form to be sent to you by CBS Screening, and help you through the process. + +It’s normal to have questions or worries - it’s okay to ask us to explain anything! + +## On your first day + +We currently run our onboarding remotely which means we can cover all our regions, as well as keeping people safe and well. + +We will have set up your accounts and new Made Tech email address ahead of time. +You can use these to join your onboarding morning call. +You’ll spend the morning with one of our Community Managers, who will introduce you to the wider team, and talk you through everything you need to know to be successful at Made Tech. + +Your onboarding will cover: +- all the accounts we use at Made Tech (Slack, G Suite, HiBob, etc.) +- a run through of how to use our tools (timesheets, booking holiday, etc.) +- an overview of how we do things at Made Tech + +This usually takes up the whole morning, and you’ll be handed over to your team for role specific onboarding, or an introduction to an internal team. + +## Group onboarding + +In the first week of every month, we run a group onboarding week. This includes overview sessions of all the important things you need to know - plus a chance to meet some of the wider team. +During this week we cover some overviews on: + +- People Team +- Feedback Workshop +- Commercial +- Public Sector +- Marketing +- Methodology Activity +- Feedback Role Play Session +- Finance +- Operations +- Propositions and Capabilities +- Compliance +- Scheduling +- User-Centred Design +- Agile Methodology + +If you join during group onboarding week, we’ll likely start a little earlier than usual to get you set up with accounts before you join the rest of the team. + diff --git a/handbook/handbook-main/guides/policy/anti_corruption_and_bribery_policy.txt b/handbook/handbook-main/guides/policy/anti_corruption_and_bribery_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..3cae7f6b48541d0b133f044156913ab8b3f113d0 --- /dev/null +++ b/handbook/handbook-main/guides/policy/anti_corruption_and_bribery_policy.txt @@ -0,0 +1,66 @@ +# Anti-Corruption and Bribery Policy + +## About this policy + +1. It is our policy to conduct all of our business in an honest and ethical manner. We are legally bound to comply with the provisions of the Bribery Act 2010 (“the Act”) and to uphold laws relevant to countering bribery and corruption in all jurisdictions in which we take a zero-tolerance approach to bribery and corruption and are committed to acting professionally, fairly and with integrity in all our business dealings and relationships. +1. Any employee who breaches this policy will face disciplinary action, which could result in dismissal for gross misconduct. Any non-employee who breaches this policy may have their contract terminated with immediate effect. +1. This policy does not form part of any employee's contract of employment and we may amend it at any time. It will be reviewed regularly. +1. This policy will be periodically reviewed by the Company and updated when appropriate. We will assess those relevant workers who are more likely to be exposed to situations covered by the Act, and provide appropriate training where necessary on how to implement and adhere to this policy. +1. We will communicate our anti-bribery and corruption stance to all customers, suppliers and contractors at the outset of our relationship with them, and as appropriate thereafter. + +## Who must comply with this policy? + +1. This policy applies to all persons working for us or on our behalf in any capacity, including employees at all levels, directors, officers, agency workers, seconded workers, volunteers, interns, agents, contractors, external consultants, third-party representatives and business partners. Everyone in the Company must therefore take the time to read this policy and understand how they must act and how the policy affects them. + +## Responsibility for the policy + +1. This policy has been implemented to prevent or detect any potential bribery or corruption issues for the Company. +1. The board of directors of the Company will have overall responsibility for ensuring compliance with this policy. +1. The Chief Operating Officer has been nominated by the board to specifically monitor compliance and effectiveness of this policy. The Chief Operating Officer will therefore be the point of contact for any queries or concerns in respect of the matters set out in this policy, or concerns under the Bribery Act 2010. + +## What is bribery? + +1. The Bribery Act 2010 (“the Act”) came into force on 1 July 2011. +1. Bribe means a financial or other inducement or reward for action which is illegal, unethical, a breach of trust or improper in any way. Bribes can take the form of money, gifts, loans, fees, hospitality, services, discounts, the award of a contract or any other advantage or benefit. +1. Bribery includes offering, promising, giving, accepting or seeking a bribe. It does not matter whether the advantage is given directly or through a third party. +1. Payments referred to as “facilitation payments” also fall foul of the Act. These are small payments typically made to public officials to secure or speed up routine actions, and may be classified as “inspection fees” or “licence fees”. Careful consideration should be given as to whether any such request is genuine and a proper request, or a facilitation payment. Genuine payments should be accompanied by a receipt which sets out the reason for the payment. +1. All forms of bribery are strictly prohibited, and breaching the Act is a criminal offence. If you are unsure about whether a particular act constitutes bribery, or if you have any suspicions, concerns or queries, raise it with your manager or a member of the leadership team. +1. Specifically, you must not: + 1. give or offer any payment, gift, hospitality or other benefit in the expectation that a business advantage will be received in return, or to reward any business received; + 1. accept any offer from a third party that you know or suspect is made with the expectation that we will provide a business advantage for them or anyone else; + 1. give or offer any payment (sometimes called a facilitation payment) to a government official in any country to facilitate or speed up a routine or necessary procedure +1. You must not threaten or retaliate against another person who has refused to offer or accept a bribe or who has raised concerns about possible bribery or corruption. + +## Gifts and hospitality + +1. This policy does not prohibit the giving or accepting of reasonable and appropriate hospitality for legitimate purposes such as building relationships, maintaining our image or reputation, or marketing our products and services. +1. A gift or hospitality will not be appropriate if it is unduly lavish or extravagant, or could be seen as an inducement or reward for any preferential treatment (for example, during contractual negotiations or a tender process). +1. Gifts must be of an appropriate type and value depending on the circumstances and taking account of the reason for the gift. Gifts must not include cash or cash equivalent (such as vouchers), or be given in secret. Gifts must be given in our name, not your name. +1. Promotional gifts of low value such as branded stationery may be given to or accepted from existing customers, suppliers and business partners. +1. The table below sets out the level of authorisation required for providing gifts and hospitality. + + | Value of Gift | Value of Hospitality | Level of Authorisation | + | -------------- | --------------------- | ------------------------------------ | + | Less than £100 | £0 to £100 | None required but must keep a record | + | Over £100 | £100 to £500 | Board Director | + | Above £250 | >£500 + business case | Board Decision | + +6. Gifts of a value less than £100 may be accepted with the approval of a director. No gifts of a value exceeding £100 should be accepted, and you should politely refuse the gift and advise the offerer of our policy in respect of this. If this places you in a difficult position you should refer to The Chief Operating Officer for guidance. + +## Record-keeping + +1. You must keep a written record of all hospitality or gifts given or received. +1. You must also submit all expense claims relating to any gifts or hospitality if you offer hospitality, gifts or payments to third parties in accordance with our expenses policy and record the reason for expenditure. +1. All accounts, invoices, and other records relating to dealings with third parties including suppliers and customers should be prepared with strict accuracy and completeness. Accounts must not be kept "off-book" to facilitate or conceal improper payments. + +## Donations and sponsorship + +1. The board will make any decisions in respect of the choice of the charities which the Company may support. +1. Charitable donations include not only direct payments to a charity, but also the sponsorship of individuals undertaking activities to raise money for charities. It is therefore important to give consideration when you are asked for sponsorship. +1. The Group does not make donations to political parties or political organisations. + +## How to raise a concern + +1. If you are offered a bribe, or are asked to make one, or if you suspect that any bribery, corruption or other breach of this policy has occurred or may occur, you must report it in accordance with our Whistleblowing Policy as soon as possible. This includes notifications of another person’s wrongdoing, or suspected wrongdoing. +1. Any notification will be treated in confidence and there will be no adverse consequences to any employee who refuses to pay a bribe (even if such a refusal may result in the Company losing business) or makes such a notification. +1. If you let us know as soon as you are aware of any breach or potential breach, then we can take action to protect you and the Company. diff --git a/handbook/handbook-main/guides/policy/anti_slavery_and_human_trafficking_policy.txt b/handbook/handbook-main/guides/policy/anti_slavery_and_human_trafficking_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..32db4f07da459ad7b3d9c1d84eb3eb5b3a6f0c09 --- /dev/null +++ b/handbook/handbook-main/guides/policy/anti_slavery_and_human_trafficking_policy.txt @@ -0,0 +1,35 @@ +# Anti-Slavery and Human Trafficking Policy + +## Policy statement + +1. Modern slavery is a crime and a violation of fundamental human rights. It takes various forms, such as slavery, servitude, forced and compulsory labour and human trafficking, all of which have in common the deprivation of a person's liberty by another in order to exploit them for personal or commercial gain. We are committed to acting ethically and with integrity in all our business dealings and relationships and to implementing and enforcing effective systems and controls to ensure modern slavery is not taking place anywhere in our own business or in any of our supply chains. +1. We are also committed to ensuring there is transparency in our own business and in our approach to tackling modern slavery throughout our supply chains, consistent with our disclosure obligations under the Modern Slavery Act 2015. We expect the same high standards from all of our contractors, suppliers and other business partners, and as part of our contracting processes, wherever possible we include specific prohibitions against the use of forced, compulsory or trafficked labour, or anyone held in slavery or servitude, whether adults or children, and we expect that our suppliers will hold their own suppliers to the same high standards. +1. This policy applies to all persons working for us or on our behalf in any capacity, including employees at all levels, directors, officers, agency workers, seconded workers, volunteers, interns, agents, contractors, external consultants, third-party representatives and business partners. +1. This policy does not form part of any employee's contract of employment and we may amend it at any time. + +## Responsibility for the policy + +1. The board of directors has overall responsibility for ensuring this policy complies with our legal and ethical obligations, and that all those under our control comply with it. +1. The Head of Operations has primary and day-to-day responsibility for implementing this policy, monitoring its use and effectiveness, dealing with any queries about it, and auditing internal control systems and procedures to ensure they are effective in countering modern slavery. +1. Management at all levels are responsible for ensuring those reporting to them understand and comply with this policy and are given adequate and regular training on it and the issue of modern slavery in supply chains. +1. You are invited to comment on this policy and suggest ways in which it might be improved. Comments, suggestions and queries are encouraged and should be addressed to the Head of Operations. + +## Compliance with the policy + +1. You must ensure that you read, understand and comply with this policy. +1. The prevention, detection and reporting of modern slavery in any part of our business or supply chains is the responsibility of all those working for us or under our control. You are required to avoid any activity that might lead to, or suggest, a breach of this policy. +1. You must notify your manager or the Head of Operations as soon as possible if you believe or suspect that a conflict with this policy has occurred, or may occur in the future. +1. You are encouraged to raise concerns about any issue or suspicion of modern slavery in any parts of our business or supply chains of any supplier tier at the earliest possible stage. +1. If you believe or suspect a breach of this policy has occurred or that it may occur you must report it in accordance with our Whistleblowing Policy as soon as possible. +1. If you are unsure about whether a particular act, the treatment of workers more generally, or their working conditions within any tier of our supply chains constitutes any of the various forms of modern slavery, raise it with your manager or the Head of Operations. +1. We aim to encourage openness and will support anyone who raises genuine concerns in good faith under this policy, even if they turn out to be mistaken. We are committed to ensuring no one suffers any detrimental treatment as a result of reporting in good faith their suspicion that modern slavery of whatever form is or may be taking place in any part of our own business or in any of our supply chains. Detrimental treatment includes dismissal, disciplinary action, threats or other unfavourable treatment connected with raising a concern. If you believe that you have suffered any such treatment, you should inform the Head of People immediately. If the matter is not remedied, and you are an employee, you should raise it formally. + +## Communication and awareness of this policy + +1. Training on this policy, and on the risk our business faces from modern slavery in its supply chains, forms part of the induction process for all individuals who work for us, and regular training will be provided as necessary. +1. Our commitment to addressing the issue of modern slavery in our business and supply chains must be communicated to all suppliers, contractors and business partners at the outset of our business relationship with them and reinforced as appropriate thereafter. + +## Breaches of this policy + +1. Any employee who breaches this policy will face disciplinary action, which could result in dismissal for misconduct or gross misconduct. +1. We may terminate our relationship with other individuals and organisations working on our behalf if they breach this policy. diff --git a/handbook/handbook-main/guides/policy/dealing_code_policy.txt b/handbook/handbook-main/guides/policy/dealing_code_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..08776662f960ad40f64f8f8c55e4ee663e5c1276 --- /dev/null +++ b/handbook/handbook-main/guides/policy/dealing_code_policy.txt @@ -0,0 +1,221 @@ + +# Dealing code + +## Introduction +The purpose of this code is to ensure that the directors of Made Tech Group plc (the **Company**), and certain employees of the Company and its subsidiaries, do not abuse, and do not place themselves under suspicion of abusing, Inside Information and comply with their obligations under the Market Abuse Regulation as in force in the UK (and which applies to the Company as its shares are admitted to trading on AIM) and the AIM Rules. + +Part A of this code contains the Dealing clearance procedures which must be observed by the Company’s PDMRs and those employees who have been told that the clearance procedures apply to them. This means that there will be certain times when such persons cannot Deal in Company Securities. + +Part B sets out certain additional obligations which only apply to PDMRs. + +Failure by any person who is subject to this code to observe and comply with its requirements may result in disciplinary action. Depending on the circumstances, such non-compliance may also constitute a civil and/or criminal offence. + +Schedule 1 sets out the meaning of capitalised words used in this code. + +## Part A - Clearance procedures + +1. **Inside Information** + + 1.1. You cannot at any time tell anyone (including your family, friends and business acquaintances) any confidential information about the Company. In addition, if any information you have about the Company is Inside Information you cannot: + + >(A) deal in any Securities of the Company or any instruments linked to them; + > + >(B) recommend, encourage or induce somebody else to do the same; and/or + > + >(C) disclose the Inside Information, except where you are required to do so as part of your employment or duties (you will know if this is the case). + + 1.2. This behaviour is known as “insider dealing”. The prohibition applies even if you will not profit from the dealing. + +2. **Dealing By Restricted Persons** + + 2.1. It is the Company’s policy that certain individuals from time to time be designated as a Restricted Person, because of their involvement in a particular transaction or business situation (for example, the annual results process) which means they may have access to Inside Information. You will be notified if you have been designated a Restricted Person and will also be notified when you are no longer a Restricted Person. If you are a PDMR you will always be considered a Restricted Person. + + 2.2. The Board has absolute discretion to designate any employee as a Restricted Person, thereby restricting that employee from Dealing in securities of the Company, at any time. + + 2.3. A Restricted Person must not Deal in any Securities of the Company without obtaining clearance to Deal in advance in accordance with paragraph 3 of this Share Dealing Code. + + 2.4. The definitions of ‘Dealing’ and ‘Securities’ of the Company are very broad and will capture nearly all transactions in the Company’s shares or debt instruments (or any derivatives or financial instruments, including phantom options) carried out by a Restricted Person, regardless of whether such transaction is carried out for the account of the Restricted Person or for the account of another person. + +3. **Clearance to Deal** + + 3.1. You must not Deal for yourself or for anyone else, directly or indirectly, in Company Securities without obtaining clearance from the Company in advance. + + 3.2. Applications for clearance to Deal must be made in writing and submitted to the Company Secretary using the form set out in Schedule 2, applications for clearance to Deal by the Company Secretary must be made in writing and submitted to the Chief Financial Officer. + + 3.3. You must not submit an application for clearance to Deal if you are in possession of Inside Information. If you become aware that you are or may be in possession of Inside Information after you submit an application, you must inform the Company Secretary as soon as possible and you must refrain from Dealing (even if you have been given clearance). + + 3.4. You will receive a written response to your application, normally within five working days. The Company will not normally give you reasons if you are refused permission to Deal. You must keep any refusal confidential and not discuss it with any other person. + + 3.5. If you are given clearance, you must Deal as soon as possible and in any event within two working days of receiving clearance. + + 3.6. Clearance to Deal may be given subject to conditions. Where this is the case, you must observe those conditions when Dealing. + + 3.7. You must not enter into, amend or cancel a Trading Plan or an Investment Programme under which Company Securities may be purchased or sold unless clearance has been given to do so. + + 3.8. Different clearance procedures will apply where Dealing is being carried out by the Company in relation to an employee share plan (e.g. if the Company is making an option grant or share award to you, or shares are receivable on vesting under a long-term incentive plan). You will be notified separately of any arrangements for clearance if this applies to you. + + 3.9. If you act as the trustee of a trust, you should speak to the Company Secretary, or designated director, about your obligations in respect of any Dealing in Company Securities carried out by the trustee(s) of that trust. + + 3.10. You should seek further guidance from the Company Secretary, or designated director, before transacting in: + + >(A) units or shares in a collective investment undertaking (e.g. a UCITS or an Alternative Investment Fund) which holds, or might hold, Company Securities; or + > + >(D) financial instruments which provide exposure to a portfolio of assets which has, or may have, an exposure to Company Securities. + + This is the case even if you do not intend to transact in Company Securities by making the relevant investment. + +4. **Further guidance** + + **If you are uncertain as to whether or not a particular transaction requires clearance, you must obtain guidance from the Company Secretary before carrying out that transaction.** + +## Part B – Additional provisions for PDMRs + +5. **Circumstances for refusal** + + You will not ordinarily be given clearance to Deal in Company Securities during any period when there exists any matter which constitutes Inside Information or during a Closed Period. The Company may also consider it appropriate to withhold clearance when there is sensitive information relating to the Company (e.g. the Company is in the early stages of a significant transaction but the existence of such transaction does not yet constitute Inside Information). + +6. **Notification of transactions** + + 6.1. You must notify the Company and the FCA in writing of every Notifiable Transaction in Company Securities conducted for your account as follows: + >(A) Notifications to the Company must be made using the template in Schedule 3 and sent to the Company Secretary, or designated director, by you or as soon as practicable and in any event within one business day of the transaction date. You should ensure that your investment managers (whether discretionary or not) notify you of any Notifiable Transactions conducted on your behalf promptly so as to allow you to notify the Company within this time frame. + > + >(E) Notifications to the FCA must be made within two working days of the transaction date electronically using the PDMR Notification Form on the FCA’s website . If you would like, the Company Secretary can assist you with this notification, provided that it is asked for within one working day of the transaction date. + + 6.2. Once you have notified the Company of a Notifiable Transaction as required by 4.1(A), it will be required to make a market announcement of the Notifiable Transaction within two working days of the transaction date. The Company will use the information in the notification sent to the Company Secretary in order to release the relevant RNS. + + 6.3. If you are uncertain as to whether or not a particular transaction is a Notifiable Transaction, you must obtain guidance from the Company Secretary, or designated director. + +7. **PCAs and investment managers** + + 7.1. You must provide the Company with a list of your PCAs and notify the Company promptly of any changes that need to be made to that list. + + 7.2. You should ask your PCAs not to Deal (whether directly or through an investment manager) in Company Securities during Closed Periods and not to deal on considerations of a short-term nature. A sale of Company Securities which were acquired less than a year previously will be considered to be a Dealing of a short-term nature. + + 7.3. Your PCAs are also required to notify the Company and the FCA electronically using the PDMR notification form on the FCA’s website , within two working days of every Notifiable Transaction conducted by them or for their account. You should inform your PCAs in writing of this requirement and keep a copy; the Company Secretary (or designated director) will provide you with a letter that you can use to do this. If your PCAs would like, the Company Secretary (or designated director) can assist them with the notification to the FCA, provided that your PCA asks the Company Secretary (or designated director) to do so within one business day of the transaction date. + + 7.4. You should ask your investment managers (whether or not discretionary) not to Deal in Company Securities on your behalf during Closed Periods. + +## Schedule 1 - Defined terms + +**Closed Period** means any of the following: +1. the period of 30 calendar days before the release of a preliminary announcement of the Company's annual results or, where no such announcement is released, the period of 30 calendar days before the publication of the Company's annual financial report; and + +1. the period of 30 calendar days before the publication of the Company's half-yearly financial report; or + +1. any other period that the Board, in its absolute discretion, designates as a close period. + +**Company Securities** means any publicly traded or quoted shares or debt instruments of the Company (or of any of the Company’s subsidiaries or subsidiary undertakings) or derivatives or other financial instruments linked to any of them, including phantom options. + +**Dealing** (together with corresponding terms such as **Deal** and **Deals**) means any type of transaction in Company Securities, including purchases, sales, the acceptance or exercise of options, the receipt of shares under share plans, using Company Securities as security for a loan or other obligation and entering into, amending or terminating any agreement in relation to Company Securities (e.g. a Trading Plan or Investment Programme). + +**FCA** means the Financial Conduct Authority. + +**Inside Information** means information which relates to the Company or any Company Securities, which is not publicly available, which is likely to have a non-trivial effect on the price of Company Securities and which an investor would be likely to use as part of the basis of their investment decision. + +**Investment Programme** means a share acquisition scheme relating only to the Company’s shares under which: (A) shares are purchased by a Restricted Person pursuant to a regular standing order or direct debit or by regular deduction from the person’s salary or director’s fees; or (B) shares are acquired by a Restricted Person by way of a standing election to re-invest dividends or other distributions received; or (C) shares are acquired as part payment of a Restricted Person’s remuneration or director’s fees. + +**Market Abuse Regulation** means the Market Abuse Regulation as in force in the United Kingdom from time to time. + +**Notifiable Transaction** means any transaction relating to Company Securities conducted for the account of a PDMR or PCA, whether the transaction was conducted by the PDMR or PCA or on behalf of the PDMR or PCA by a third party and regardless of whether or not the PDMR or PCA had control over the transaction. This captures every transaction which changes a PDMR’s or PCA’s holding of Company Securities, even if the transaction does not require clearance under this code. It also includes pledging or lending Company Securities, gifts of Company Securities, the grant of options or share awards, the exercise of options or vesting of share awards and transactions carried out by investment managers or other third parties on behalf of a PDMR, including where discretion is exercised by such investment managers or third parties and including under Trading Plans or Investment Programmes. Further details of transactions which are deemed Notifiable Transactions are set out in Schedule 4. + +**PCA** means a person closely associated with a PDMR, being: + +(A) the spouse or civil partner of a PDMR; or + +(B) a PDMR’s child or stepchild under the age 18 years who is unmarried and does not have a civil partner; or + +(C) a relative who has shared the same household as the PDMR for at least one year on the date of the relevant Dealing; or + +(D) a legal person, trust or partnership, the managerial responsibilities of which are discharged by a PDMR (or by a PCA referred to in paragraphs (A), (B), or (C) of this definition), which is directly or indirectly controlled by such a person, which is set up for the benefit of such a person or which has economic interests which are substantially equivalent to those of such a person. + +**PDMR** means a person discharging managerial responsibilities in respect of the Company, being either: + +(A) a director of the Company; or + +(B) any other employee who has been told is a PDMR. + +**Restricted Person** means: + +(A) a PDMR; or + +(A) any other person who has been told by the Company that the clearance procedures in Part A of this code are applied. + +**Trading Plan** means a written plan entered into by a Restricted Person and an independent third party that sets out a strategy for the acquisition and/or disposal of Company Securities by the Restricted Person, and: + +(A) specifies the amount of Company Securities to be dealt in and the price at which and the date on which the Company Securities are to be dealt in; or + +(B) gives discretion to that independent third party to make trading decisions about the amount of Company Securities to be dealt in and the price at which and the date on which the Company Securities are to be dealt in; or + +(C) includes a method for determining the amount of Company Securities to be dealt in and the price at which and the date on which the Company Securities are to be dealt in. + +## Schedule 2- Clearance application template + +**Made Tech Group plc** **(the Company**) + +**Application for clearance to deal** + +If you wish to apply for clearance to deal under the Company’s dealing code, please complete sections 1 and 2 of the table below and submit this form to the Company Secretary (or designated director). By submitting this form, you will be deemed to have confirmed and agreed that: + +(i) the information included in this form is accurate and complete; + +(ii) you are not in possession of inside information relating to the Company or any Company Securities; + +(iii) if you are given clearance to deal and you still wish to deal, you will do so as soon as possible and in any event within two working days; and + +(iv) if you become aware that you are in possession of inside information before you deal, you will inform the Company Secretary (or designated director) and refrain from dealing. + +|**1.**|**Applicant**|| +| - | - | - | +|a)|Name|| +|b)|Contact details|*[please include email address and telephone number.]*| +|**2.**|**Proposed dealing**| +|a) |Description of the securities |*[e.g. a share, a debt instrument, a derivative or a financial instrument linked to a share or debt instrument.]*| +|b)|Number of securities|*[If actual number is not known, provide a maximum amount (e.g. “up to 100 shares” or “up to [€1,000] shares”).]*| +|c)|Nature of the dealing|*[Description of the transaction type (e.g. acquisition; disposal; subscription; option exercise; settling a contract for difference; entry into, or amendment or cancellation of, an investment programme or trading plan).]*| +|d)|Other details|*[Please include all other relevant details which might reasonably assist the person considering your application for clearance (e.g. transfer will be for no consideration).]*

*[If you are applying for clearance to enter into, amend or cancel an investment programme or trading plan, please provide full details of the relevant programme or plan or attach a copy of its terms.]*| + +## Schedule 3 - Notification template + +**Made Tech Group plc** **(the** **Company**) + +**Transaction notification** + +Please send your completed form to Debbie Lovegrove (debbie.lovegrove@madetech.com]. If you require any assistance in completing this form, please contact Debbie Lovegrove. + +|**Name**| | +| - | - | +|**Position**| | +|**Is this notification for a dealing you have undertaken or is the notification on behalf of one of your PCAs (person closely associated with you)?** | | +|**If it is on behalf of one of your PCAs please provide their name and relationship to you**|*[If the PCA is a legal person, state its full name including legal form as provided for in the register where it is incorporated, if applicable.]*| +|**Initial notification / amendment**|*[Please indicate if this is an initial notification or an amendment to a prior notification. If this is an amendment, please explain the previous error which this amendment has corrected.]*| +|**Nature of the transaction**|*[e.g. purchase, sale, transfer of shares/contract for difference, participation in a placing, grant or exercise of options]*| +|**Details of the transaction(s)**|

*[please also provide contract notes if available]*


*[Where more than one transaction of the same nature (purchase, disposal, etc.) of the same financial instrument are executed on the same day and at the same place of transaction, prices and volumes of these transactions should be separately identified in the table below, using as many lines as needed. Do not aggregate or net off transactions.]*


***Date******Volume of shares******Price per share***
---
---
---
| +|

**Aggregated information**

**Aggregated volume**

**Price**

|

*[Please aggregate the volumes of multiple transactions when these transactions:*

*- relate to the same financial instrument;*

*- are of the same nature;*

*- are executed on the same day; and*

*- are executed at the same place of transaction.]*

*[Please state the metric for quantity.]*

*[Please provide:*

*- in the case of a single transaction, the price of the single transaction; and*

*- in the case where the volumes of multiple transactions are aggregated, the weighted average price of the aggregated transactions.]*

*[Please state the currency.]*

| +|**Place of the transaction(s)**|*[on market or outside of a trading venue?]*| +|**Date of Transaction**|*[Date of the particular day of execution of the notified transaction, using the date format: YYYY-MM-DD and please specify the time zone.]*| + + +## Schedule 4 - Notifiable Transactions + +|**Transaction**| +| :- | +|An acquisition, disposal, short sale, subscription or exchange| +|The acceptance or exercise of a share option or award, including of a share option/award granted to managers or employees as part of their remuneration package, and the disposal of shares stemming from the exercise and/or vesting of a share option/award| +|Entering into or exercising equity swaps| +|Transactions in or related to derivatives, including cash-settled transactions| +|Entering into a contract for difference on a financial instrument of the Company| +|The acquisition, disposal or exercise of rights, including put and call options, and warrants| +|Subscriptions to a capital increase or debt instrument issuance| +|Transactions in derivatives and financial instruments linked to a debt instrument of the concerned issuer, including credit default swaps| +|Conditional transactions, upon the occurrence of the conditions and actual execution of the transactions| +|Automatic or non-automatic conversion of a financial instrument into another financial instrument, including the exchange of convertible bonds to shares| +|Gifts and donations made or received, and inheritance received| +|Transactions executed in index-related products, baskets and derivatives| +|Transactions executed by a manager of an alternative investment fund in which the PDMR or its PCA has invested| +|Transactions executed in shares or units of investment funds, including alternative investment funds (AIFs)| +|Transactions executed by a third party under an individual portfolio or asset management mandate on behalf or for the benefit of a PDMR or their PCA| +|Borrowing or lending of shares or debt instruments of the Company or derivatives or other financial instruments linked to them| +|The pledging or lending of financial instruments by a PDMR or a PCA. A pledge or similar security interest, of financial instruments in connection with the depositing of the financial instruments in a custody account does not need to be notified, unless and until such time that such pledge or other security interest is designated to secure a specific credit facility| +|Transactions undertaken by persons professionally arranging or executing transactions or by another person on behalf of a PDMR or a PCA, including where discretion is exercised| +|Transactions made under a life insurance policy, where the policyholder is a PDMR or a PCA and they bear the investment risk and have the power or discretion to make investment decisions in relation to the policy. No notification obligation is imposed on the insurance company| + diff --git a/handbook/handbook-main/guides/policy/whistleblowing_policy.txt b/handbook/handbook-main/guides/policy/whistleblowing_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..bbd097bc79cb3024084687c27b8dbdecafdedee4 --- /dev/null +++ b/handbook/handbook-main/guides/policy/whistleblowing_policy.txt @@ -0,0 +1,47 @@ +# Whistleblowing Policy + +## Whistleblowing policy + +1. We are committed to conducting our business with honesty and integrity and we expect all team members to maintain high standards. Any suspected wrongdoing should be reported as soon as possible. +1. This policy covers all employees, officers, consultants, contractors, casual workers and agency workers. +1. This policy does not form part of any employee's contract of employment and we may amend it at any time. + +## What is whistleblowing? + +Whistleblowing is the reporting of suspected wrongdoing or dangers in relation to our activities. This includes bribery, facilitation of tax evasion, fraud or other criminal activity, miscarriages of justice, health and safety risks, damage to the environment, safeguarding issues and any breach of legal or professional obligations. + +## How to raise a concern + +We hope that in many cases you will be able to raise any concerns with your manager. However, where you prefer not to raise it with your manager for any reason, you can: +- contact the Head of People and/or Head of Operations. Contact details are at the end of this policy. +- email whistleblowing@madetech.com (which will be confidentially sent to the same roles named above) + +We will arrange a meeting with you as soon as possible to discuss your concern. You may bring a colleague or union representative to any meetings under this policy. Your companion must respect the confidentiality of your disclosure and any subsequent investigation. + +## Confidentiality + +We hope that all employees will feel able to voice whistleblowing concerns openly under this policy. Completely anonymous disclosures are difficult to investigate. If you want to raise your concern confidentially, we will make every effort to keep your identity secret and only reveal it where necessary to those involved in investigating your concern. + +## External disclosures + +The aim of this policy is to provide an internal mechanism for reporting, investigating and remedying any wrongdoing in the workplace. In most cases you should not find it necessary to alert anyone externally. + +The law recognises that in some circumstances it may be appropriate for you to report your concerns to an external body such as a regulator. We strongly encourage you to seek advice before reporting a concern to anyone external. Protect operates a confidential helpline. Their contact details are at the end of this policy. + +## Protection and support for whistleblowers + +- We aim to encourage openness and will always support whistleblowers who raise genuine concerns under this policy, even if they turn out to be mistaken. +- All colleagues are legally protected if they make a qualifying disclosure. +- Whistleblowers must not suffer any detrimental treatment as a result of raising a genuine concern. If you believe that you have suffered any such treatment, you should inform your Line Manager, the Head of People or your People Partner immediately. +- You must not threaten or retaliate against whistleblowers in any way. If you are involved in such conduct you may be subject to disciplinary action. +- However, if we conclude that a whistleblower has made deliberate, false allegations maliciously, the whistleblower may be subject to disciplinary action. +- Protect operates a confidential helpline. Their contact details are at the end of this policy. + +## Contacts + +| Contact | Details | +| ------------------------------------------------ | -------------------------------------------------------------------------------------------------- | +| Head of People | Nina-Marie Purcell
nina-marie.purcell@madetech.com | +| Head of Operations | Sam Paice
sam.paice@madetech.com | +| Whistleblowing email | whistleblowing@madetech.com +| Protect
(Independent whistleblowing charity) | Helpline: 0203 117 2520
E-mail: whistle@pcaw.co.uk
Website: https://protect-advice.org.uk | diff --git a/handbook/handbook-main/guides/process/mentoring/supporting_and_mentoring_other_engineers.txt b/handbook/handbook-main/guides/process/mentoring/supporting_and_mentoring_other_engineers.txt new file mode 100644 index 0000000000000000000000000000000000000000..ad67e87219688df51bc516096217e083b3126e4c --- /dev/null +++ b/handbook/handbook-main/guides/process/mentoring/supporting_and_mentoring_other_engineers.txt @@ -0,0 +1,67 @@ +# Supporting and Mentoring other Engineers + +## Constructivist Learning Theory + +> Constructivist teaching is based on the belief that learning occurs as learners are actively involved in a process of meaning and knowledge construction as opposed to passively receiving information. Learners are the makers of meaning and knowledge. + +Our experience in mentoring and coaching has shown us we gain the most knowledge and understanding not through simply providing answers and solutions to questions or problems but instead by helping provide tools and information through which others can shape their own answers. We can often help another engineer when they ask a question by asking further questions to help frame thinking or providing potential sources of information that will provide further guidance to them. + +## Patience + +It is fundamental that when mentoring we show patience, people learn at different speeds and some concepts may be much harder for others to grasp than they were for you. If you find that frustration seems to be creeping in from either party you should stop and take a break, clear your head and try to reset the tone of conversation. Try to get to the root of where the frustration is coming from, are you communicating the concepts you're discussing in clear and understandable language? Have you misunderstood the question? Take time with the learner to make sure you both are on the same page wherever possible. + +## Responding to questions + +When a colleague asks a question it's important that we try our best to make them feel listened to and understood, if they are new to this process it's probably worth explaining why we aren't directly answering their request. Explain the value we place on helping others to find the tools to solve their own problems rather than solving/answering directly for them + +### Clarifying the question + +Does the person asking the question have all the tools to adequately clarify the problem they are facing? If they can't it's probably best trying to guide them towards being able to better frame the problem they're facing and developing language around it. + +If they have the language but are struggling to explain the root cause you can try applying [5 whys](https://en.wikipedia.org/wiki/5_Whys) as a method of helping them focus in on it. + +### Guidance and leading over Answers + +Where possible when asked a question the best possible response is either a prompt or question that will help the learner explore their situation deeper without feeling they've been spoon fed or simply given a solution. + +We value providing others the tools to assemble their own learnings, to help with this we should phrase questions in a way that allows for open discussion and prompts consideration on the topic we're dealing with. Avoiding providing solutions or responding with closed Answers/Questions can shut down the ability for the asker to form their own understandings and views on the problem they are facing. + +### Sources of information + +Does the learner know the best place to look for information that could help answer their question? Do they know the correct terms to find this if they were to [Google it](#google-it)? If they don't, guide them towards some good resources you know or if you're both struggling to find something that helps provide further understanding throw it out to the team via the #slack-overflow channel in our slack. + +It's worth bearing in mind where possible that providing multiple types of resources (video, audio, text, workshop) is potentially the most beneficial way to accommodate people with disparate learning styles. + +In the [Academy Workshops repo](https://github.com/madetech/academy-workshops) you can find a variety of workshops that we have worked on and peer reviewed that can help provide resources or even questions/discussion topics that can be used with learners. + +### Pair on it + +Pairing can also be an effective method of helping a colleague with a question, it's important that we remember the aim is to help them develop a solution for themselves so this may involve taking more time in the navigation role than you would normally with pairing. Prompt them to discuss their thinking and what potential solutions they think there are as they go, if they are struggling with this work with them to break it down into smaller chunks and get them to build a plan for tackling these chunks (This can be done on paper or with pseudo-code, it's more about the thought process really). + +Even if you're not driving it's important to maintain pairing discipline; asking questions and sticking to breaks and timers. + +### Training behaviours + +Where necessary or valuable we should look at improving a Developer Behaviour like one of the [XP values](http://www.extremeprogramming.org/values.html) + +### Training skills + +Sometimes it will be necessary to help the learner develop a skill based on how they ask their question. If they are struggling to clarify the problem their facing they may need help working on their debugging skills. When we do this we may take a more closed approach the first time (as the learner may need more of a walkthrough) but in future situations the learner should require less explicit support. + +### Open questions + + +> Open questions have the following characteristics: +> - They ask the respondent to think and reflect. +> - They will give you opinions and feelings. +> - They hand control of the conversation to the respondent. + +When working on mentoring a colleague we want to have discussions around our aims and the questions/problems they are facing. By using open questions we can try and provoke these discussions instead of allowing simple yes or no answers. + +### Google it + +Googling the problem can sometimes be the best way to highlight to a learner that it's not required to have an exhaustive knowledge of all the documentation around a subject, once you've made them feel listened to suggest this approach to them. If they are struggling to clarify the problem enough you should try and work on this with them first. + +### Solving their problem + +Sometimes a problem will be tricky enough that trying to provide guidance can take significantly longer time than you can fully devote to a mentee, in these rare instances it's ok to help provide a solution but you should talk through it with them as you go and try to ensure they've understood it. diff --git a/handbook/handbook-main/guides/process/people/capability_procedure.txt b/handbook/handbook-main/guides/process/people/capability_procedure.txt new file mode 100644 index 0000000000000000000000000000000000000000..3bc0da428fe562d37359eec8d09550ba7c9cae83 --- /dev/null +++ b/handbook/handbook-main/guides/process/people/capability_procedure.txt @@ -0,0 +1,26 @@ +# Capability Procedure + +In cases where employees are not meeting the expectations that have been clearly defined to them, and after an expectation health check has been performed, we follow the [Acas Code of Practice on Discipline Procedures](http://www.acas.org.uk/publications). + +## Expectation Health Check + +Before we escalate to formal proceedings, an expectation health check will be performed by a Director. Capability Procedures usually include measures to identify and address issues, our expectation health check seeks to address issues before reaching that stage. + +In the case where a health check has failed to address issues raised, a formal performance review procedure will be followed. + +## Formal Performance Review + +- Step 1: If it is decided a formal performance review must be carried out, Made Tech will notify the employee in writing of the reasons why and be invited to a meeting to discuss the problem. +- Step 2: Made Tech will then hold the meeting to discuss the problem, allowing the employee to present their case. The employee has the right to bring a companion* with them. +- Step 3: Made Tech will then decide on appropriate action to be taken. If it is decided that the employee has been performing unsatisfactorily, the employee will be given a written warning that includes the details of the performance issue, and the timescale in which the issue must be addressed. +- Step 4: If the issue has not been rectified within the time period, a final written warning will be issued stating another timescale in which the issue must be addressed and the consequences if the issue is not addressed. + +\*Companion can include a paid official of a trade union, a lay trade union official that can provide evidence of experience in these matters, or a colleague. In certain circumstances we may also allow representatives from other organisations if particularly relevant to the grievance such as Citizens Advice Bureau. + +## Consequences of a not addressing a final written warning + +The most likely consequence of not addressing concerns within the time period set out in a final written warning will be dismissal. Other consequences may include demotion or loss of seniority. + +The employee will be informed as soon as possible of the reasons of their dismissal, the date on which the employment contract will end, the appropriate period of notice and their right to appeal. + +Where an employee feels that the decision of dismissal is wrong or unjust they should appeal against the decision. Appeals will be heard within a reasonable timeframe in the form of a meeting. Employees should let Made Tech know the grounds for their appeal in writing. Employees have the right to be accompanied in their appeal meeting. Made Tech will then notify the employee in writing the results of the appeal hearing as soon as possible. diff --git a/handbook/handbook-main/guides/process/scheduling/hiring_contractors.txt b/handbook/handbook-main/guides/process/scheduling/hiring_contractors.txt new file mode 100644 index 0000000000000000000000000000000000000000..54f1e4414747bca1be5ec2607df8280c404e9a63 --- /dev/null +++ b/handbook/handbook-main/guides/process/scheduling/hiring_contractors.txt @@ -0,0 +1,82 @@ +# HOW TO HIRE A CONTRACTOR + +Definition of contractor: An externally sourced individual Off-payroll worker, working to deliver specific outcomes on a single client project for a predetermined length of time. + +Definition of Hiring Manager: The person responsible for the contractor. + +**This process is for when it is highly likely that there are no internal capability for a skillset available for a project. As per usual process, this should be determined in conjunction with Scheduling before this process kicks off.** + +1. To initiate a request with the Talent team, [This form](https://docs.google.com/forms/d/1HgIwXsW80r2RIpD0T4Oj6nHXsjOvoRF41CuJ9mHY4X0/edit) will need to be completed. Scheduling will work with you to fill this out. + * [from May 2021- the Scheduling team will complete an IR35 assessment to define whether the role falls inside or outside of IR35]. + +2. The Talent team will add selected recruitment agencies to the vacancy who will upload them to [Workable](https://made-tech.workable.com/backend) (our internal applicant tracking system) and tag the Hiring Manager for evaluation feedback on the system. +3. The Hiring Manager can then directly deliver feedback and arrange interviews directly through the system. +4. Once you have identified a candidate to offer, please inform the Talent team so they can relay feedback correctly and negotiate the offer where necessary. +5. When we have an accepted offer and start date, the People team will complete the administration and contract, the Scheduling team will be kept informed. + * [from May - When a contractor begins work, they must complete an IR35 re-assessment to confirm the in-practice IR35 status of the role.] + +## Points to consider + +* The client project team are responsible for the contractor. Please inform the agency and/or talent partner who the timesheet approver is. + +* It is the project team’s responsibility to inform the Scheduling team of the contractor’s end date so that the contract notice can be served in time + +* Billable contractors need to complete a Made Tech timesheet. This may be in addition to the agency timesheet. + +* Line managers are responsible for the accuracy of both timesheets. + +* Contractors cannot be unbilled or in the chalet without written approval from the relevant Market Principal. + +* Contractors must be attached to a single, specific project and set of outcomes. To transfer a contractor to a new project, a new assessment must be done and **a new contract must be issued** to remain IR35 compliant. The Scheduling team will facilitate this change in contract with the People Team + +* Contractors must carry out the work specified in their contract i.e lead engineer for HMRC. They are not able to work on internal projects or work for other Made Tech clients without this agreed and the contract adjusted to reflect this arrangement. + +* If there is a known break between projects i.e one project finishes and there’s a 2 week break, the contractor should take this time as unbilled leaved. The People team can support these conversations. + + ## FAQs + + **What are contractors permitted to do (and not do) whilst with Made Tech?** + + Contractors **shouldn’t be required** to attend company updates or social events, however they may be invited and go of their own accord. + + They shouldn’t receive training, line manage anyone or, work on multiple projects at one time. However, it is acceptable to share knowledge or train the team. + + Contractors should not work on internal projects whilst contracted to work on client projects due to IR35 legal requirements. This is also cost prohibitive. If the scope of work, client or other elements of their contract e.g. hours, days, day rate, changes, we need to update the contract to reflect this. Please inform scheduling asap in case this affects financial reporting and the systems need amending. + + + + **Who are the right people to interview for these roles to ensure we are getting the right skills for the project?** + + The project teams will be expected to interview contractors because they sit outside of the standard hiring process and there’s an urgency to the request. If the project lead (tech lead or delivery manager) would like specific expertise, Scheduling can help to determine the right person in the business to request time from. + + + + **Who determines the contractor rates and makes a decision on margin?** + + The rate for the role must be included in the contractor request form. The Talent team will use this as a guide to understand maximum limits for a role, however, will use market rates for a role and the charge out rate will not be shared with an agency or candidate. + Using the [rate card and calculator](https://docs.google.com/spreadsheets/d/11LkRvm5gGnSeAxp_3i1H-_jlfWWpqXEM3Xz5SLAeVRE/edit#gid=368177954), you can see if a candidate falls within the acceptable range, and if not, it will need a decision from the project lead and Market Principal. For any additional evidence or questions around market information, please contact the talent team. + + + + **Who is responsible for finding contractors other opportunities within the business and managing either their notice or contract change/extension?** + + Scheduling will check that the current project does not need them further, if there are no known opportunities, they will then offer this role out to all markets in Slack. If there are no needs, the People team will be contacted to serve their contract notice period. + + **How is notice served? Can I terminate a contractor earlier than the agreed end date?** + + Please inform the Scheduling team as soon as you anticipate a contractor will no longer needed on the project. We usually set an expectation of 1 calendar weeks’ notice but this is contract dependent so please check beforehand with Scheduling. + + This will be initiated with the People team who manage contracts and will inform the agency if required. + If a project unexpectedly finishes, we may be liable to pay the notice period. Where there is a financial impact to Made Tech, the Market Principal needs to be informed. + + We should aim to give the contractor as much notice as possible that the project is coming to an end. + + + + **Who should decide if a contractor can be unbilled for a certain period and who pays for this time?** + + Contractors should not be unbilled and we expect them to be working 5-days a week on client-work, except where we have agreed an onboarding period of half a day or where there is Market Principal approval. The start date needs to be agreed with the client and communicated to the contractor. If there’s any change in start date, the contractor should start in line with that date and should be informed if this change. The contract will also need to be updated. There should not be a period where the contractor is unbilled. Where there is a break between projects, the contractor will be asked to take holiday in between. + + + +For any other questions not covered please refer to the [Ops Scheduling Slack Channel](https://madetechteam.slack.com/archives/CFCSJJVML). diff --git a/handbook/handbook-main/guides/process/scheduling/how_scheduling_works.txt b/handbook/handbook-main/guides/process/scheduling/how_scheduling_works.txt new file mode 100644 index 0000000000000000000000000000000000000000..6705b61abecfa71e136ebff1feb05e1cc1613f8e --- /dev/null +++ b/handbook/handbook-main/guides/process/scheduling/how_scheduling_works.txt @@ -0,0 +1,16 @@ +# How Scheduling Works + +Scheduling, or the art of getting the right people supporting the right activities in the business, is really about pulling the right stakeholders together to agree the best outcome. + +This guide sheds some light on the typical needs the Scheduling area of the business supports, who is involved in servicing these needs, and what decisions are we aiming to reach. + + + +| What is the need? | How do scheduling team find out? | What decision are we making? | Who is involved in the decision? | Who is informed of the outcome? | +|-------------------------------------------|--------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| +| New billable person joins the business | New joiners alerted by people team | Where will this person have the biggest business impact and where will this individual have the best onboarding experience? | Market Principal | People Team
Delivery Lead of team individual is joining
Service Area Owner (in the case of joining a Service Area team) | +| Billable person to support sales activity | Ask from a demand service team | Is this a priority for the business? Who is the best and most readily available person to give this sales activity the best chance of success? | COO (to validate priority)
Demand team member
Market Principal (where decision impacts billable team member on a delivery, or where sale is tied to a market) | Individual
Delivery Lead of impacted team | +| New account or workstream team | Confirmation from lead on sales opportunity | What is the best team we can assemble to deliver the outcome? | Market Principal
Head of Delivery | Individual(s)
Delivery Lead of impacted team (if individual is moving teams)
Demand Team member | +| Billable person released from delivery | Forecast weekly review or
Delivery Lead alerts scheduling | Where will this person have the biggest business impact or what is the best opportunity for their personal development? | Market Principal | Individual
Delivery Lead of team individual is joining
Service Area owner (in the case of joining a Service Area team) | +| Change an existing delivery team | Forecast weekly review or
Delivery Lead alerts scheduling | What is the most optimal team shape, and who is best and most readily available to support this team? | Market Principal
Delivery Lead
Head of Delivery (where change impacts account or workstream leads) | Individual(s)
Delivery Lead of impacted team (if individual is moving teams)
Service Area owner (if individual is moving teams) | +| Team members to support service area | Ask from a Service Area owner | Is this a priority for the business? Who are the best and most readily available people to support this need? | COO (to validate investment)
Service Area Owner | Individual(s)
Delivery Lead of impacted teams
Market Principal | \ No newline at end of file diff --git a/handbook/handbook-main/guides/process/scheduling/how_to_timesheet.txt b/handbook/handbook-main/guides/process/scheduling/how_to_timesheet.txt new file mode 100644 index 0000000000000000000000000000000000000000..838c9dde676cb1bacedde64ac0bf9db2abc74372 --- /dev/null +++ b/handbook/handbook-main/guides/process/scheduling/how_to_timesheet.txt @@ -0,0 +1,85 @@ +# How to timesheet + +## General + +We use [Kimble](https://www.kimbleapps.com/) to complete timesheets. All resources on how to complete and approve timesheets are in the [Knowledge base](https://sites.google.com/madetech.com/signpost/home/kimble-resources?authuser=0) (including a link for login through Single Sign-On (SSO)). + +Made Tech billable hours are 35 per week, 7 hours per day full time. Part-time hours are prorated according to your agreed hours. + +Only billable team members need to complete a timesheet (including contractors) and you will be notified at your onboarding session if you need to complete one. The timesheet must be completed to account for all of your time in the working week (excluding contractors). + +Timesheets are approved by your Delivery Manager or Project lead for client work (including non-billable projects), and Operations or service area lead for internal projects such as Sales or Marketing. + +Any absences i.e. Holiday, Medical leave, etc still need to be recorded in the People Team system (currently HiBob). + +## When to submit your time + +Time sheets need to be submitted weekly **every Friday by 12pm** and we use the data to directly invoice our clients. + +When the end of the month falls on a weekday other than Friday, you will be asked to submit a timesheet up until the end of the month. This will be in addition to the Friday timesheet meaning you need to complete 2 in a week. + +E.g. June 30 falls on a Tuesday, your timesheet needs to be submitted up until Tuesday i.e. 7 hours for Monday and 7 hours for Tuesday. The rest of the week (Wednesday to Friday) will be included in the Friday timesheet. + +## What categories should I allocate my time to? + +All of your 35 hours should be allocated to the category/ies where you spend your time. This will either be a client project or an internal project or a combination of both. + +## Client projects + +Client projects are separated into 3 categories; Billed, Investment and Chalet, you will be allocated to one as appropriate by the Scheduling team. + +Billed is where we are charging the client for your time and indicated by a ‘BIL’ in the project title. + +Investment is where we are investing time with the client but not charging them for your time, you are available should another suitable billed opportunity come up. This is indicated by a ‘INV’ in the project title. + +Chalet is where you are not assigned to a client and are completely available for billed opportunities and internal projects. This is indicated by a ‘BEN’ in the project title. + +## Made Tech internal projects + +You may be asked to support internal Made Tech initiatives while on a billed engagement. This includes activities such as hiring, bid writing, helping with our academy, or supporting one of our service areas. + +Where these commitments total less than 5 hours per week, they should be included in our standard operating overhead and should not be accounted for separately from billed hours. + +Some internal activities do not count towards the 5 hours as our clients benefit from them indirectly. These include: + +* Line management (1:1s etc.) +* Taking part in communities of practice + +When the total internal commitment exceeds 5 hours in a week, each commitment should be allocated in its entirety to the appropriate project in Kimble and not included in billable hours. + +Please ensure that you get approval in advance from your account team for all non-delivery commitments. You must also get agreement from the relevant service area leader before booking any time against their service area project. + +## How to submit your timesheet + +We use Kimble to complete timesheets. All resources on how to complete and approve timesheets are in the [Knowledge base](https://sites.google.com/madetech.com/signpost/home/kimble-resources?authuser=0). + +### Why we need you to do timesheets + +Timesheet data directly drives our client invoicing. Incomplete and incorrect timesheets can lead to us under or overcharging clients which can create significant challenges for account and finance teams. + +Timesheet data also creates wider business-critical data about utilisation, client investments and time spent on other activities that's needed for reporting and planning. + +### Why we need you to do timesheets weekly +Whilst we invoice our clients monthly it's vitally important that the data driving these invoices is accurate at a week by week level. Many clients do check the individual items driving an invoice to validate that they've been correctly charged by us. Weekly timesheets ensure we capture time spent while it's fresh in our memories. + +Doing them weekly provides immediate visibility of time spent for line and delivery managers to create better quality project level conversations about time spent and weekly-level understanding of budget burn-down for client conversations. This allows us to update our monthly revenue forecast in real time: helping us understand whether we're on course to meet projected income due to things like sick leave, or last minute changes to time allocation, and readjust targets and cashflow forecasts as we go. + +It’s important that the data is accurate and complete at the end of every week. That means midday on Friday, not 9am the following Monday morning. A number of business processes - including scheduling, revenue forecasting and cashflow - need accurate data to drive them on a Monday. Any timesheet submitted after 12pm on a Friday impacts our ability to generate good quality data and causes significant extra work for the Ops and Finance teams. Please do them on time! + +## Timesheet approval process + +Once a team member has submitted their timesheet on Friday by 12pm, Delivery Managers and Service Area owners need to [approve their team's timesheets](https://trello.com/c/k12r2uja/40-approving-timesheets) by 1pm. + +### Why we need to approve timesheets + +Timesheet data directly drives our client invoicing, so it’s important it’s accurate and complete at the end of every week. It will also save you time when checking invoice accuracy at the end of the month. When approving timesheets for the week we need to: +* Check your team has completed their timesheet in full; and has accurately recorded the time they spent on the project (inc. absences like illness and holidays) +* Account for any differences between the team’s forecast time and their actual time spent and report this to the Operations team + +The review and approval process should take 5-10 minutes; and picking up any errors or unexplained differences saves the business a lot of time! + +We also ask that if you are going on holiday, that you allocate it to another Delivery Manager or senior member of the team. Scheduling can change this in Kimble, and change it back to you when you return. + +## Contact us + +If you have any questions on timesheets, contact the Ops team in Slack using the #Kimble Support channel. diff --git a/handbook/handbook-main/guides/security/acceptable_use_policy.txt b/handbook/handbook-main/guides/security/acceptable_use_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..a881334a8ff1368cad566eaa8799c31bfc0a3b2f --- /dev/null +++ b/handbook/handbook-main/guides/security/acceptable_use_policy.txt @@ -0,0 +1,70 @@ +# Acceptable Use Policy + +This Acceptable Use Policy (AUP) details how all users of any Made Tech IT device or service must behave, and is based on Made Tech’s guiding principles of treating people fairly and like adults. We trust our team members to do the right thing, and this policy is here to help guide individuals when they seek advice in how they should conduct themselves in any situation. + +The AUP policy outlines the acceptable use of equipment and services at Made Tech and puts in place rules to protect everyone who uses them. Inappropriate use of equipment and services exposes both Made Tech and our clients to risks. These risks include virus attacks, compromise of network systems and services, and legal action. + +As with any policy, there are consequences to non-compliance, including potential disciplinary action being taken which may lead to dismissal and/or criminal proceedings. + +Made Tech endeavours to continually improve all policies and if you have feedback, please contact the Operations Team. + +Below are the minimum expectations for accessing those services appropriate to your role and responsibilities. + +## I will act with integrity at all times + +I will use the Made Tech service for the purpose it is intended for at all times, and not do anything knowingly that could harm the integrity or reputation of Made Tech. + +## I will use any Made Tech issued devices properly +I understand Made Tech issued devices are issued for work purposes and I agree to return them for inspection as and when required. I will return it on leaving the employment of Made Tech or when it is no longer required unless otherwise agreed with Made Tech prior to leaving. + +## Personal Use +I will exercise good judgement at all times regarding the reasonableness of any personal use + +## I will enable 2-factor authentication where this is available +2-factor authentication (2FA) requires two forms of authentication, often a password and a code, sometimes sent via SMS or an application. It helps protect user accounts in the case that your password is somehow exposed. + +## If my device is stolen or missing, I immediately report it +Lots of information can be extracted from stolen or misplaced laptops, even in some cases when the disk has been encrypted. Report a missing machine quickly, better safe than sorry. We use remote device management to remotely wipe data from your device in the event that it is stolen. You should report all stolen items to the IMS Manager or CSO, who will record the incident. + +## I will backup my work in the right place +Information saved on a device is at risk of loss or theft and will not be backed up. To protect against theft, laptops are encrypted. Made Tech backs up data stored on G-Suite, GitHub, and Slack. Each team at Made Tech has their own Team Drive and it is the responsibility of those teams to maintain what is kept in those drives. All data must be copied to these locations to ensure there is no data loss in the event of your laptop becoming unusable. + +## I follow the guidance around passwords +Keep passwords secure and do not share accounts with anyone else. You are responsible for the security of your passwords and account. + +## I will not share my laptop with anyone else, including under a separate user account +The laptop you use for working should not be used by anyone else; for example a partner having a separate user account or sharing a generic login. + +## I will not open unfamiliar email attachments, and I will always check the actual address for links in emails, even from trusted colleagues +Phishing and in particular spear phishing (which targets specific individuals within a specific organisation) is a genuine threat with recorded attacks everyday. + +## I report anything that could be a security incident +If you experience or see anything suspicious, or anything that you know breaks one of our security policies, report it to either the IMS manager or CSO. As a general rule, if you are not sure whether to report something, report it anyway. We'd always rather know. + +## I will manage software responsibly +Made Tech needs to account for, and report against all its software assets to comply with best industry practice, so you should install any software in accordance with the licensing requirements. You should also not remove any software installed by the Made Tech Internal IT team without first agreeing a case for doing so, and should install updates promptly if requested. + +## I ensure any software I use is up to date +You are responsible for keeping your device software up to date with updates and security patches. The Made Tech Internal IT Services team, will from time to time audit and validate the status of your device. + +## I use any admin privileges I receive responsibly +I will ensure the Admin Account on Made Tech IT issued equipment remains accessible to the Made Tech Internal IT Team at all times. + +## I am careful when using bluetooth connections +Bluetooth is enabled on your device and can be used safely within an office or your home. Its use outside of those environments is not recommended as they may be easily compromised. + +## I use my email account responsibly +Use of your company email addresses should be for work-related content only. Do not use your email address to login to non-work related websites or social media + +## I am conscious of my web footprint +Be aware that your online profiles and activity may link back to Made Tech so be aware of this when you publish anything online + +## I am responsible when using personal devices on Made Tech networks +The Made Tech Staff Wifi may be accessed using personal devices subject to these Rules and the Made Tech BYOD policy. +If you're using your own device on the Made Tech network, do not use it for anything which is not acceptable at work. + +## I abide by the Made Tech network security and monitoring policies +The intentional bypassing of Made Tech network security and monitoring, such as via Tor or VPN, is forbidden. + +## I follow the Made Tech Secure Device OS Administration policies +No user account is to be provided with administrative privileges on secure devices unless a case has been agreed by the IMS management team and/or leadership. The administrator account is to be used for all higher level access. Administrator passwords are to be stored securely. diff --git a/handbook/handbook-main/guides/security/access_control.txt b/handbook/handbook-main/guides/security/access_control.txt new file mode 100644 index 0000000000000000000000000000000000000000..471e267c83dbb7596fd1d6081cc20a3e7dea2b15 --- /dev/null +++ b/handbook/handbook-main/guides/security/access_control.txt @@ -0,0 +1,13 @@ +# Access Control + +## Team-level access control + +Made Tech access controls reflect that: +- We trust our team members to act responsibly, and to abide by the Acceptable Use Policy +- We trust our team members to access appropriate sites when using the internet + +It is the responsibility of teams (delivery teams and business teams) to ensure that team members have the appropriate access to the information and services they need to perform their role. Access to additional tools or licenses can be obtained by contacting it@madetech.com. + +On delivery teams it is the Delivery Lead who should ensure that team members can access the information and services required to work on a client delivery. The Delivery Lead should also ensure that this access is revoked when a team member leaves the team, or a delivery shuts down. + +For business teams, it is the responsibility of the Head of Department to ensure that all team members have the appropriate level of access to tools and services. e.g. for the People Team, it is the responsibility of the Head of People. For the Operations Team it is the Head of Operations. diff --git a/handbook/handbook-main/guides/security/bring_your_own_device.txt b/handbook/handbook-main/guides/security/bring_your_own_device.txt new file mode 100644 index 0000000000000000000000000000000000000000..b78a86f617dd626cbb21eee9e477cab5a054d7f9 --- /dev/null +++ b/handbook/handbook-main/guides/security/bring_your_own_device.txt @@ -0,0 +1,92 @@ +# Bring Your Own Device Policy + +This document highlights things you should think about, and how you manage your own device while working on Made Tech products and services. Not only the data you work with but also the software you have installed and how you protect it - like antivirus software. + +This only applies to you if you’re using your own device for Made Tech work. Devices aren’t just desktop and laptops - they include, for example, tablets and smartphones. + +## Using and managing your device + +If you’re using your own device for Made Tech work, it means you’re being trusted to use company proprietary data appropriately and keep that information or data you hold safe. + +### Don’t ‘jailbreak’ your device +‘Jailbreaking’ is the process of removing hardware and software vendor restrictions for the purpose of custom modifications (for example, installing unapproved applications or changing the user interface in an unsupported way). + +You must not use a jailbroken device for any Made Tech work or to handle any company proprietary data, including logging into Made Tech services which include (but is not limited to) G-Suite, Slack, password management software, etc. + +### Keep your software up to date +You must keep your software up to date. Old versions of software are often vulnerable to attack. Update all the software on your device whenever a new version is available. This includes: + +- Your device’s operating system +- Web browsers +- Extensions +- Plug-ins + +You must update your software within 14 days of a new verison being released. + +### Use endpoint protection software +Unless your device is operating iOS or ChromeOS, your device must have endpoint protection software installed, which must also be kept up to date. + +Endpoint protection is more than just antivirus software, and usually includes a firewall and may have other tools to protect your device, like network threat detection. + +Any device you plug into the device, like an external USB device, must also be scanned for viruses. We recommend doing a full scan at least once a month. + +### Set a password/passphrase +Your device must require a password/passphrase to login, return from screensaver or wake from sleep. Your device will lock the screen (or start the screensaver) after no more than 2 minutes of the device being idle. + +### How you manage passwords/passphrases +Your password/passphrase must conform to the Made Tech Password Policy. You should also use a password manager and 2FA. + +### How you connect your device to networks +We have our own VPN which automatically authenticates with G Suite. Everyone can use the service (not only engineers) for a more secure experience (i.e. protecting yourself when using a public WiFi). To connect to the VPN, please refer to the [guide found in the Handbook.](../it//vpn/README.md) + +### Disk Encryption +You must encrypt all your data storage devices. This includes: + + - hard disks (including on smartphones and tablets) + - cloud storage + - USB sticks + +If these aren’t encrypted, people can see any data that’s on them or install viruses without you noticing + +### Turn your device off, rather than putting it to sleep +Depending on the device, data may only be encrypted when the device itself is turned off. So please be aware that closing the lid to put the device to sleep won’t necessarily enable encryption; in which case the data will not be protected. + +If your device will not be used for a significant period of time, we suggest turning it off entirely to ensure disk encryption is enabled. Most modern operating systems will allow you to resume all the files/applications that were open before shutdown. + +Turning off your device to ensure disk encryption is enabled is important if your device will be unattended. This could include when inside a backpack or carrying case when travelling, as those can be lost or stolen + +### Store data in Made Tech cloud services +Company proprietary data should be stored in Made Tech tools. Check what your team is using. Do not store data locally on your device, ensure it's synced to the relevant cloud service. + +If you are working offline and cannot access the cloud service, you can make a temporary local copy. Make sure you update the version stored in the cloud service as soon as possible, and then delete your local copy in a way that the files can’t be recovered. + +### Delete/erase data properly +When company proprietary data is no longer required it should be securely erased so it cannot be recovered. This must be completed for any data that is personal or sensitive in any other way - such as credentials or contracts. + +If the data storage in which the data resides is encrypted, usually destroying the decryption passphrase is sufficient to render the data unreadable. + +If files or folders need to be removed from within some data storage, then overwriting techniques may be required. Overwriting techniques must meet [government requirements](https://en.wikipedia.org/wiki/Infosec_Standard_5) and should at least overwrite the data once, using randomly generated data. + +### How to use peripherals +It is easy for a device like a USB mouse or keyboard to be modified to try and insert malicious software such as a virus or key logger that captures what you type. + +Bluetooth and peripheral devices such as (USB mice or keyboards. drawing tablets or even presentation ‘clickers’ can be used to extract data. + +**Are they yours?** +Be sensible about how you attach peripherals to your device, particularly if the device is not yours. Even if the person handing you a USB is trustworthy, the USB may have been infected with malware such as a virus without them knowing. + +### Administrator accounts +One technique to prevent malware from spreading through your account into the rest of your device and data is to use a separate user account for managing the device and installing software. Made Tech employs this technique on the devices it issues, and you are encouraged to do the same. + +### Secure Development +It is your responsibility to ensure that you or your device does not accidentally or on purpose, introduce a vulnerability into Made Tech environments or services. You could also use a separate user account on your device for development work to help keep your Made Tech work separate from any other work, and personal use, like social media. + +### Remote Access Tools +Don’t use unattended Remote Access Tools (“RAT”) on devices containing or accessing company proprietary data. RATs can be useful for accessing your device from another location, but could also enable an attacker to do the same. + +Unattended Remote Access Tools should not be installed on devices you use for your Made Tech work. Most operating systems come with remote access software, like VNC or SSH. These software items are OK, but should not be used as an inbound ‘service’. Given the nature of these tools and the potential risks they can introduce, we want to conduct a risk assessment of them before their use in Made Tech. + +### Reporting an issue +You must tell Made Tech if your device that is used in connection with your Made Tech work is lost, stolen or otherwise compromised as soon as possible. You should report anything suspicious to a member of the Operations Team as soon as possible. + +If you suspect that your device may be compromised (has a virus etc), you should telephone them rather than email them. Your emails could transfer malware from your device to other people or into Made Tech systems and services. diff --git a/handbook/handbook-main/guides/security/confidentiality_agreements.txt b/handbook/handbook-main/guides/security/confidentiality_agreements.txt new file mode 100644 index 0000000000000000000000000000000000000000..eab395fb2111fe827c240285b8b3fdae8b698ed0 --- /dev/null +++ b/handbook/handbook-main/guides/security/confidentiality_agreements.txt @@ -0,0 +1,5 @@ +# Confidentiality Agreements and NDAs + + - If clients ask about whether our team are covered by confidentiality agreements, we can let them know that all employees sign **Terms and Conditions of Employment** which include clauses for confidentiality and intellectual property. + - Company Non-Disclosure Agreements (NDA’s) are included in contracts raised with contractors. A template for our NDA can be found [here](https://docs.google.com/document/d/1YESByvaOv06azyq6JTNqmD9vsHh224lQ9urKV0p4_pY/edit) + - If you are looking to record or take photos of our team for any purpose, please remember that no recording equipment may be used in internal, supplier, or customer meetings without the **knowledge and consent** of all those present in the meetings diff --git a/handbook/handbook-main/guides/security/data_protection.txt b/handbook/handbook-main/guides/security/data_protection.txt new file mode 100644 index 0000000000000000000000000000000000000000..5ecd4412e390bdb5df7de8f833a42a08b900f750 --- /dev/null +++ b/handbook/handbook-main/guides/security/data_protection.txt @@ -0,0 +1,27 @@ +# Data Protection + +Made Tech complies with regulations under the European General Data Protection Regulation (GDPR) and Data Protection Act 2018. It is the company’s policy to protect and hold safe all Personal Information which it requires or needs to possess in the performance and management of its operation. + +Under GDPR, an individual has the right to be informed whether or not their personal data is being processed and, if so, to be informed of the following: + - What personal data is being processed + - The purposes for which the personal data is being processed + - Who, if anyone, the personal data is disclosed to + - The extent to which the personal data is being used to make automated decisions relating to the individual + +Below are guides for team members on the course of action to take if they receive a request regarding personal data. + +## Made Tech Data + +For Made Tech data (e.g. requests from Made Tech employees about personal data), please forward any requests from your team on to the Operations team who will process it thusly: + - We will acknowledge receipt of the data subject’s request. + - We will ask for two proofs of identity to confirm requester ID. + - We will follow up and ask for information on the types of data in question (e.g. type and timeframe) + - We will process the request accordingly and respond to the data subject in line with the legislation. + - We will inform the individual that a record of their basic information (e.g. name and company) may be kept with a note to not contact again. + - We may ask for input and/or provision of data from other teams to comply with the request. + +## Customer and Partner Data + +Where a customer or partner makes a request about their data, seek written approval from them that they have verified the request and authorise Made Tech to collate and release this data from systems we have access to. They will also need to provide proof of ID for the requester. + +Once this is done, you can respond the request in line with the process outlined above. diff --git a/handbook/handbook-main/guides/security/device_profiles.txt b/handbook/handbook-main/guides/security/device_profiles.txt new file mode 100644 index 0000000000000000000000000000000000000000..ee808be5de633ba2f109b7c875a2ba8e9b749be9 --- /dev/null +++ b/handbook/handbook-main/guides/security/device_profiles.txt @@ -0,0 +1,8 @@ +Made Tech uses standard builds for the devices issued to team members to facilitate support and maintenance, and help enforce security standards. + +As part of our commitment to secure working practices and maintaining our current Cyber Essential Plus (CE+) Certification, we install separate admin and user device profiles on laptops. This restriction prevents the accidental downloading and installation of malicious software on company devices and protects both Made Tech and our customers. + +An application called ThreatLocker is installed on all Macs. When an application install is required that needs admin privileges, ThreatLocker will either allow you to proceed if the application is pre-approved or present the option to request the level of access needed to install the app. More information is available [here](https://aura.eu.itglue.com/1102831304982679/docs/3345396642005183). + +The situation for Linux users is slightly different. More information is available [here](https://github.com/madetech/handbook/blob/main/guides/it/linux_av.md). + diff --git a/handbook/handbook-main/guides/security/document_sharing.txt b/handbook/handbook-main/guides/security/document_sharing.txt new file mode 100644 index 0000000000000000000000000000000000000000..1bbd8dac310f53cba61d22737dfbcf1ac959a5ed --- /dev/null +++ b/handbook/handbook-main/guides/security/document_sharing.txt @@ -0,0 +1,12 @@ +## Sharing documents outside Made Tech + +We know that many teams collaborate directly with clients, suppliers and partners through our Google Workspace, and that working that way is a key part of both our culture and process. We want to enable that whilst also making sure that we’re only granting access to information to people who need it for as long as they need it. + +- We should only share drives and docs with business email addresses: don’t add personal accounts (including your own!) to any Made Tech owned file without clearing this with the Ops team. +- Only grant edit access where you know this is needed: ‘View’ or ‘Comment’ access is usually fine for guests, so please use these by default. +- Wherever possible set an expiration date for access (this is a new update from Google workspace as of November 2022 which allows you to add an expiration date when sharing a file). +- Remove external access to folders and files when it’s no longer needed. +- Please regularly review any shared drives, folders or files you manage to make sure permissions and access are correct - especially for any external users. +- We’re now logging all external sharing and downloading and we’ll be looking to build some better processes and controls to manage this in a rapidly growing organisation (and in line with our ISO27001 certification). + +Contact the Ops team at #ops-infosec on slack if you want help reviewing the structure or permissions on any folders you own; or if you have any clients, partners or other stakeholders using personal emails for legitimate access to our data. diff --git a/handbook/handbook-main/guides/security/last_day.txt b/handbook/handbook-main/guides/security/last_day.txt new file mode 100644 index 0000000000000000000000000000000000000000..55c658d2f9400b4f6cecb5866b259f8055286a0a --- /dev/null +++ b/handbook/handbook-main/guides/security/last_day.txt @@ -0,0 +1,10 @@ +On your last day for Made Tech, your access to Made Tech services will stop at 1715. If you need access past that point then please speak to your Line Manager or Delivery Manager before your last day. + +Before that point, please ensure you’ve completed the below closing down tasks: + +- If you are the owner of any Google documents, Miro boards or Trello boards which relate to the project, please transfer the ownership to another member of your team. +- If you have access to Github, check if your teams have access to the information and add them if not. Approve or reassign any changes or anything created so your team has access to them. +- If you have a Client laptop ensure you have spoken to your Delivery Manager about how to return that. +- Completed your timesheet up to and including your final day. + +Aura will be in touch regarding returning your laptop a week before you leave. You'll find information [here](https://github.com/madetech/handbook/blob/main/guides/security/leavers_laptop.md) on how to return your laptop to them. diff --git a/handbook/handbook-main/guides/security/leavers_laptop.txt b/handbook/handbook-main/guides/security/leavers_laptop.txt new file mode 100644 index 0000000000000000000000000000000000000000..bea259942edad49f2e4b2f88eeb553c32b4e6f88 --- /dev/null +++ b/handbook/handbook-main/guides/security/leavers_laptop.txt @@ -0,0 +1,30 @@ +# Returning your laptop if you're leaving + +If you're leaving Made Tech we are going to need your laptop back. Please ensure that you've copied or moved any personal information from the laptop before your last day - the laptop will not be usable +after that point and we will not re-open an account to allow you to have access. The laptop will be wiped so all information will be removed. + +You need to send the laptop back to Aura as soon as possible after your last day. Please ensure: +- That the device is clean (no stickers) +- That the charger is included +- There is a note with your name on it so that Aura can identify who it’s from. + +If you are posting the laptop you need to ensure it’s suitably packaged and has plenty of padding to ensure a safe return. Send it with tracking and insurance to the following address: + +
+Aura Technology
+1-2 Trinity Court
+Brunel Road
+Totton
+Southampton
+SO40 3WX
+
+ +We recommend using the following method to send the laptop and charger to Aura as this both tracks and insures the laptop, and you can arrange to have the parcel collected from your home: + +[Special Next Day Delivery](https://www.royalmail.com/sending/uk/special-delivery-guaranteed-1pm) + +You can expense the postage by claiming back via Xero - in the description of the xero expense add ‘returning laptop to Aura'. +You will have access to Xero to submit expense claims for about a week after your last day. +If you are returning the laptop after this point you will need to email the receipt of the laptop postage to [finance@madetech.com](mailto:finance@madetech.com) and you will be reimbursed. + +We do not offer an option to purchase your laptop. diff --git a/handbook/handbook-main/guides/security/lost_or_stolen.txt b/handbook/handbook-main/guides/security/lost_or_stolen.txt new file mode 100644 index 0000000000000000000000000000000000000000..7903aee054cbaa2397e3137135d8f4f06ac21ca7 --- /dev/null +++ b/handbook/handbook-main/guides/security/lost_or_stolen.txt @@ -0,0 +1,36 @@ +# Lost stolen devices + +## What to do when a device is lost or stolen +Any lost or stolen devices (laptops, mobiles or tablets) pose a security threat to both us and our clients. So if this happens to you, don’t panic! Please follow the steps below and let us know as soon as you can. This process is in place to help you - you won’t get shouted at. + +## Made Tech laptop is lost or stolen +If your Made Tech Laptop is lost or stolen, please contact the Police as soon as possible. You should provide them with the following details: + +- Office address (London, Manchester or Bristol) +- Your address +- Where and when you believe it was stolen or lost. + +You also need to contact the Business Operations Team asap so they can disable the device to ensure it cannot be used to access Made Tech data. You can do this via Slack: #ops-it-support or email: [Operations@madetech.com](mailto:operations@madetech.com). + +Following this, please email Compliance with as much detail as possible including the crime number. [Compliance@madetech.com](mailto:compliance@madetech.com). + +## Client laptop is lost or stolen +If your Client issued laptop is lost or stolen, please contact the Police as soon as possible. You should provide them with the following details: + +- Office address (London, Manchester or Bristol) +- Your address +- Where and when you believe it was stolen or lost. + +You also need to contact your Delivery Manager asap so they can liaise with the Client so the Client can disable the device to ensure it cannot be accessed. + +Following this, please email Compliance with as much detail as possible including the crime number [Compliance@madetech.com](mailto:compliance@madetech.com). Please also contact Operations so they are aware of the incident, either via Slack: #ops-it-support or email: [Operations@madetech.com](mailto:operations@madetech.com). + +## Personal Devices lost or stolen (laptop, mobiles and tablets) +If your personal device is lost or stolen and it contains any Made Tech data (eg. email, Slack), please contact the Police as soon as possible. + +You also need to contact the Business Operations Team asap so they can remove the device from your Made Tech profile to ensure it cannot be used to access Made Tech data. You can do this via Slack: #ops-it-support or email: [Operations@madetech.com](mailto:operations@madetech.com). + +Following this, please email Compliance with as much detail as possible including the crime number [Compliance@madetech.com](mailto:compliance@madetech.com). + +## Further help +If you are affected by your loss or theft then please reach out to our People Team, Mental Health First Aiders or just reach out, you are not on your own diff --git a/handbook/handbook-main/guides/security/office_visitors.txt b/handbook/handbook-main/guides/security/office_visitors.txt new file mode 100644 index 0000000000000000000000000000000000000000..05d6e23c8949a9a42f5f657419911c97fac9078d --- /dev/null +++ b/handbook/handbook-main/guides/security/office_visitors.txt @@ -0,0 +1,26 @@ +# Visitors and Office Security + +Keeping our physical surroundings safe is an important part of ensuring our work remains secure. Robust office security ensures we maintain the safety of our buildings, team members, and visitors. + +## Planning ahead +Please ensure that all visitors are booked into the relevant office in advance using the Office RnD system. You can find more information on how to do this, and book them a desk if required, [here](https://docs.google.com/document/d/1wCGrHN-prrUt8RnyNux2MshCTQ36D_rvTKTeu1qJwMk/edit#) (internal link). + +## On arrival +Ask all visitors to check in using the Office RnD app on the iPad. The member of the team they are here to visit will be alerted by email and Slack but you can also let them know directly. Please keep the visitor in the relevant waiting area until a team member arrives - don't let them wander around the office alone. +Visitors should be given a visitor lanyard. + +If someone tries to enter the office and you feel uncomfortable, you are within your rights to challenge their reasons for entry (gently). + +### Unauthorised Access +Attackers may attempt to gain access to our offices in order to do Made Tech or our clients harm. They may use techniques to gain your trust, take advantage of inattention, or capitalise on your desire to be helpful to gain access. + +**Remain vigilant for:** +- Anyone you do not recognise trying to gain access to (or already in) the office +- Anyone trying to follow you into the communal stairway or office +- Anyone trying to observe the access codes for the communal stairway or Made Tech office +- Anyone who cannot provide a credible reason for gaining access to the building or office +- Anyone who cannot name the member of the Made Tech team they are visiting +- Anyone trying to pressure you for information about our building or office + +Remember, it is always ok to (politely) challenge any request for access from an unknown individual. +If you are an employee and a team member is challenging you, please remember they are just trying to be security conscious so help them out and demonstrate you work here. diff --git a/handbook/handbook-main/guides/security/password_policy.txt b/handbook/handbook-main/guides/security/password_policy.txt new file mode 100644 index 0000000000000000000000000000000000000000..93b7521960b4124e8400bfc763dbf8d77a3b646a --- /dev/null +++ b/handbook/handbook-main/guides/security/password_policy.txt @@ -0,0 +1,26 @@ +# Password and 2FA/MFA policy +Strong password and use of 2FA (two factor authentication) or MFA (Multi Factor Authentication) are important aspects of device and software security. We all have passwords for multiple systems that are used for business related purposes and it is important for all team members to take the appropriate steps to secure their passwords. The full password policy is available [here](https://docs.google.com/document/d/1oUzqF5TkdUQmXpQp-9fIficeQ0O-TYbwOK6koMFsSWE/edit) (internal link). + +## Password Creation +- Passwords must be sufficiently strong such as to make cracking or guessing difficult. Where possible, passwords should be randomly generated (you can do this using 1password) +- Do not use the same password for access to Made Tech systems as for any personal accounts. If you do this, and your Made Tech password is compromised, it will open your personal accounts up to vulnerabilities and vice versa. + +## 1Password +Made Tech uses 1Password as its main password repository. 1Password is administered and maintained by Aura. There are group vaults which are managed by the teams who use them, but also private vaults where you can store your own information. + +Please use this as your only password management tool for Made Tech and client passwords. + +Your password to access 1Password should conform to the password policy. Biometrics is an acceptable method of accessing 1Password and the 1Password extension on Google Chrome is also fine to use. + +## Password Security +Cracking passwords or a brute force attack are not the only ways in which individuals with bad intentions can get into the Made Tech systems. Social engineering also makes us vulnerable. Attackers will use techniques to gain your trust, or take advantage of inattention or a desire to be helpful to obtain passwords. +- Be aware of someone using social engineering to gain access to your password / account +- Do not store passwords on your device outside of 1Password +- Do not write passwords down +- Be sure you're entering your password in to a legitimate website +- Passwords should generally not be shared. When these is need to share a piece of secure information do so via 1Password + +In all cases, report anything you think is amiss! + +## 2FA/MFA +Wherever possible Made Tech enforces 2FA/MFA or implements SSO. Please ensure you are enabling 2FA where it is available. diff --git a/handbook/handbook-main/guides/security/security_clearance_guidance.txt b/handbook/handbook-main/guides/security/security_clearance_guidance.txt new file mode 100644 index 0000000000000000000000000000000000000000..60591ca547e0ab352cb90272b69ad5f08dfb8b15 --- /dev/null +++ b/handbook/handbook-main/guides/security/security_clearance_guidance.txt @@ -0,0 +1,33 @@ +# Guidance for Security Cleared (SC) Employees + +## General Information +With an increasing number of Made Tech’s clients requiring security cleared resources to work on their projects, we encourage all client-facing colleagues to consider applying for the appropriate level of security clearance. + +The Made Tech Compliance Team (compliance@madetech.com) manages security clearance activities, and will provide helpful information to you before your clearance application is started. Please note that there are minimum residency and work history requirements that need to be met before your application can be commenced. + +All new joiners whose role may need SC at some point are asked whether they already have SC. There is a possibility that existing SC clearance holders may be able to transfer their existing clearance to Made Tech, depending upon who issued it and how long it has left to run. For further details, you should contact our Compliance Team. + +There are different routes for requesting Security Clearance (SC) and the route taken depends on the project. There is [more information here](https://docs.google.com/document/d/1hVPR5nvnbwzkAcZHogTqKl8HHpACZKwHyXayB3lr0SY/edit) (internal link). + +### Timings +Timings to be cleared are a minimum of 25 working days (5 weeks) from the point the application and all relevant information has been received. However it is usual for timings to be significantly longer. + +At the current time, it can take between 8-12 weeks for an application to be assessed and security clearance to be granted. This is outside of Made Tech’s control, so an early application into the process is recommended. You will be informed as soon as we become aware of any progression of your application. + +### Applying for Security Clearance +If you wish to apply for security clearance, the Compliance Team will require a small subset of personal data to create an application for you. This should be sent, when requested, by private message to the Compliance Team member. For data protection reasons, it should not be posted in common areas, including open Slack channels. + +### Security Clearance Records +Made Tech’s Compliance Team maintains records of all security clearances within the Company, and will securely share details with the People Team and Scheduling Team as required for legitimate business purposes. If you have any questions about the status of your security clearance, or that of one of your direct reports, you should contact the Compliance Team. + +### Safeguarding your Security Clearance +Your security clearance is an important and valuable asset that should be protected. As a holder of a security clearance, you must follow Government requirements and ensure that details of your clearance (a) are only communicated to those that have a genuine need to know, and (b) are never posted on social media or similar open forums. + +### Changes in Circumstances +Certain changes in your personal circumstances will require you to notify the appropriate vetting authority and your employer. This applies if you, for example: +- Get married, enter a civil partnership or start living with a partner as a couple +- Are arrested, are refused bail, receive a police caution, reprimand or final warning or are convicted of an offence +- Acquire a new nationality or renounce one that you previously held +- There is a significant change in your financial circumstances + +In these circumstances, you should check with the Compliance Team who will confirm the correct means of notifying the appropriate vetting authority and liaise with appropriate support routes internally also. diff --git a/handbook/handbook-main/guides/security/taking-mt-laptops-abroad.txt b/handbook/handbook-main/guides/security/taking-mt-laptops-abroad.txt new file mode 100644 index 0000000000000000000000000000000000000000..b4002df1af7e77ed8866b339ad61fcbdcbe7bc69 --- /dev/null +++ b/handbook/handbook-main/guides/security/taking-mt-laptops-abroad.txt @@ -0,0 +1,7 @@ +## Taking Made Tech laptops abroad + +If you’re off on holiday we’d suggest that you shouldn’t be taking your laptop with you, however if you’re planning on working anywhere outside of the UK, here are some steps you need to take before you do: + +- Talk to your DM and the People Team first, to ensure you have permission to work outside of the UK (some clients will not allow this). +- Contact Operations via slack #ops-it-support or email [operations@madetech.com](mailto:operations@madetech.com) to let them know. +- When using your laptop outside of the UK ensure you are using the Made tech VPN. If this is not installed please see [instructions](https://drive.google.com/drive/folders/14w3BXtsrgUqRmJ73QFhGXiCo3ufjvMmI) on how to do that before you go. diff --git a/handbook/handbook-main/guides/welfare/dse_hs_training.txt b/handbook/handbook-main/guides/welfare/dse_hs_training.txt new file mode 100644 index 0000000000000000000000000000000000000000..3919645093a2a233032acb3e271d25f31f9d38ce --- /dev/null +++ b/handbook/handbook-main/guides/welfare/dse_hs_training.txt @@ -0,0 +1,11 @@ +# DSE & Health & Safety Training + +Made Tech has a legal duty to ensure the health, safety and welfare of everyone whilst at work. +We want to make sure everyone can work productively and safely and understand where people might need other adjustments to do so. +Our health, safety and well-being at work are important to how we deliver services to our communities and how we are treated at work so Made Tech asks that you complete DSE (display screen equipment) and H&S (health & safety) training. + +You will receive an email link from IHASCO to complete the two training sessions. Each course will take approx 45 mins (including the assessment), +but you don’t have to do it all at once; you can start a course and return to it. +However, we ask that you complete it within 30 days of starting at Made Tech. + +More information can be found [here](https://docs.google.com/document/d/1m5nvVRHLcSWrP4xbf-GKYf-NTxQN11RZ8K_MC9_kgHE/edit) (internal link) diff --git a/handbook/handbook-main/guides/welfare/ethical_boundaries.txt b/handbook/handbook-main/guides/welfare/ethical_boundaries.txt new file mode 100644 index 0000000000000000000000000000000000000000..bf974b8914a53056ce359753fae4a5265d81c28f --- /dev/null +++ b/handbook/handbook-main/guides/welfare/ethical_boundaries.txt @@ -0,0 +1,7 @@ +# Ethical Boundaries + +We recognise that there may on occasion be certain client accounts, or certain types of industry or project activity, that people feel uncomfortable working with - or in - for valid personal reasons. + +At Made Tech nobody will be forced to work on a client engagement in which they're not comfortable. If you feel this way about any recent client wins or new engagements we're expecting to kick-off, please let it be known to the Scheduling team so we can factor this in to any team shape planning. If there are issues relating specifically to the client, we will also look to pick these up via other channels if appropriate. + +Our [project assignment guidance](https://docs.google.com/document/d/1cgASgYU9rjF-y7pa9gJ9FJ8HCBP6M3ntmdgeLZclSPo/edit) will also help understand scenarios and situations where it is possibly to challenge a potential project placement. diff --git a/handbook/handbook-main/guides/welfare/expectation_health_check.txt b/handbook/handbook-main/guides/welfare/expectation_health_check.txt new file mode 100644 index 0000000000000000000000000000000000000000..caf364a5081cb446bc8eae7fd209d89f8fed0e19 --- /dev/null +++ b/handbook/handbook-main/guides/welfare/expectation_health_check.txt @@ -0,0 +1,49 @@ +# Expectation Health Check + +We believe the expectations between Made Tech and staff create a healthy tension that has a positive impact on both in equal measure. Occasionally these expectations will not be met for one reason or another. If Made Tech is not meeting the expectations of staff, an employee can [raise an issue](raising_an_issue.md). + +In the case where an employee is not meeting the expectations of Made Tech or another member of staff we can perform an expectation health check. This document outlines the procedure. + +## What to do before requesting a health check + +Before a health check is requested, we recommend issues are raised as informally as possible. Very much similar to the start of our [raising an issue](raising_an_issue.md) guidance we recommend the following steps. + +### Before a health check have a conversation with the person involved + +The first thing you can do, if you feel comfortable and able, is raise the issue directly with the person involved. This type of direct and informal approach is encouraged and we expect your colleagues who are approached responsibly to respond in a similar manner. By vocally mentioning that an expectation is not being met or that performance is less than expected, the member of staff can reflect and work to improve the situation, seeking help where necessary. + +### Before a health check raise feedback via line manager 121 + +If you feel unable to have a conversation directly with the person involved, and they are a member of staff at Made Tech then you can encourage them to discuss the issue in their next line manager 121 session by raising the feedback through that process. + +Feedback provided this way is not anonymous but can add a layer of indirection and ensure that the issue is discussed with another member of the team. We hope this will trigger conversations amongst those in the session and we would expect proactive action to happen off the back of that session. + +### Before a health check ask a colleague to intervene on your behalf + +You may ask a colleague or director to intervene informally on your behalf. In some situations you may not feel able to directly approach the person or people involved and so going via a third party to informally raise your concern for you is another option available to you. + +## How to request a health check + +If the previous steps have not led to expectations being met or performance being improved then you can request a health check. You can request a health check from a Director. Once you request a health check the following steps will be taken: + +- Director will book a meeting in ASAP with whoever requested a health check to discuss their concerns +- If the Director feels appropriate informal steps have been unsuccessful in improving the situation a meeting will be booked with the employee concerned to discuss the issue and the impact it's having on the organisation +- If the issue is not addressed within two weeks or the situation escalates then the Director will notify the employee that an expectation health check will be performed + +## Performing a health check + +The purpose of a health check is to clearly identify expectations that are not being met and then to define clear steps to be taken to resolve the situation. Health checks are a slightly more formal process for being explicit about issues, it is not a capability procedure or performance review. + +The following steps will be taken in order to perform the health check: + +- Director will book a meeting with the employee who has been identified as not meeting expectations, the purpose of the meeting is to clearly define expectations that are not currently being met, these expectations will then be sent in writing to the employee along with instructions for next steps +- The employee will be asked to identify causes (illness and mental wellbeing are valid causes!) for why the expectations are not being met and define steps that can be taken to address the situation +- The employee will then be invited to share their thoughts ahead of another meeting +- During the next meeting the Director will either agree with, or suggest changes to the employees identified causes, steps for addressing and a timescale in which they are to be addressed. If the employee has been unable to identify causes and steps for addressing the Director will define these with the employee +- The plan will then be sent in writing to the employee +- On a weekly basis the plan will be reviewed and based on feedback from both the employee and if necessary their colleagues the Director will track progress towards achieving the plan +- We expect the health check to be reviewed and resolved within the defined timescale + +## What to do if a health check cannot resolve an issue + +In some cases, the health check will be unsuccessful in its aim of addressing unmet expectations. In this case, our formal [capability procedure](../process/people/capability_procedure.md) will be followed. diff --git a/handbook/handbook-main/guides/welfare/expectations.txt b/handbook/handbook-main/guides/welfare/expectations.txt new file mode 100644 index 0000000000000000000000000000000000000000..c0d675c796da9e693d1d55259733afef9d4ec1ec --- /dev/null +++ b/handbook/handbook-main/guides/welfare/expectations.txt @@ -0,0 +1,19 @@ +# Expectations between Made Tech and staff + +As an employee embarking on a career with Made Tech you will have expectations about what that means in terms of your role within the organisation, job security, progression, work life balance and having a comfortable workplace. Made Tech too will have expectations on the employee in terms of the role they play in the organisation. + +We think these expectations create a healthy tension between employee and employer and we seek to be explicit about these expectations all of the time. There should be no surprises. + +The healthy tension is a good thing because it means together the individual has their needs met by their employment and the organisation gets closer to achieving its vision due to the contribution of the employee. + +## Employees expectations of Made Tech + +As an employee I expect Made Tech to clearly define my role within the business as well as career progression paths. I also expect for Made Tech to provide me with a comfortable workplace and respect my right to a healthy work life balance. Finally, I expect Made Tech to hold itself accountable against the company values. + +If the staff expectations are not being met by the organisation then we encourage staff to [raise an issue](../welfare/raising_an_issue.md). The only way issues can be resolved is by discussing them and working constructively to improve the situation. Everything needs work, organisations are no different. + +## Made Tech expectations of staff + +As an organisation we expect an employee to understand their role within the business and meet the expectations of their role. Role expectations should be introduced as part of the onboarding process for all roles. Expectations should be reviewed on a regular (usually monthly) basis with a Director or Line Manager. + +From time to time, an issue with an employee not meeting expectations will occur. Team members may also occasionally have concerns over the performance of their colleagues. We can perform an [expectation health check](expectation_health_check.md) in this case. diff --git a/handbook/handbook-main/guides/welfare/leave-and-time-off.txt b/handbook/handbook-main/guides/welfare/leave-and-time-off.txt new file mode 100644 index 0000000000000000000000000000000000000000..ff9b45d19e0ec555800d94a75b3097bce2f95678 --- /dev/null +++ b/handbook/handbook-main/guides/welfare/leave-and-time-off.txt @@ -0,0 +1,30 @@ +Here is a list of the time off types in HiBob and some examples of what they should be booked for : + +## Holiday +We have adopted a flexible holiday policy, where each team member is given the flexibility to take whatever holiday they need. +Please see our [flexible holiday page](https://github.com/madetech/handbook/blob/main/benefits/taking_holiday.md) + +## Sick +We recognise that for our team to perform at the highest possible level, they need to be healthy in mind and body. +Please see our [sick policy page](https://github.com/madetech/handbook/blob/main/guides/welfare/sick_leave.md) + +## Medical Leave +Medical leave should be used when you need some time off for a medical appointment or medical procedure, where you are not able to flex your time to make up any hours. When you book this leave in HiBob, please select the reason for your medical leave so that we can make sure we put any support in place for you. Your line manager will need to approve this leave. + +## Learning Time +This is for your personal learning time that can be used flexibly, more information can be found on our [learning page](https://github.com/madetech/handbook/blob/main/guides/learning/README.md) + +## Unpaid Leave +This may be requested to support extended absences or unexpected scenarios where advanced notice is unable to be given. Approval from your line manager is required for this type of leave. + +## Compassionate Leave +This is discretionary paid time off when dealing with an upsetting or sensitive situation such as a bereavement. Approval from your line manager is required for this type of leave. + +## Parental Leave +This is for longer-term leave such as maternity/paternity and will require approval from your line manager and the People team. +More information can be found on our [flexible parental leave page](https://github.com/madetech/handbook/blob/main/guides/welfare/parental_leave.md) + +## Jury Service +This is for jury service Approval is required from your line manager for this leave and the organisation will ordinarily pay you at your existing salary level for this scenarios. + + diff --git a/handbook/handbook-main/guides/welfare/paid_counselling.txt b/handbook/handbook-main/guides/welfare/paid_counselling.txt new file mode 100644 index 0000000000000000000000000000000000000000..54f851eb9e104ec1f77c6ce75a5b083f347fe939 --- /dev/null +++ b/handbook/handbook-main/guides/welfare/paid_counselling.txt @@ -0,0 +1,28 @@ +# Paid counselling + +## Unum Employee Assistance + +We have setup an employee assistance programme to provide our team with advice on a range of life and work issues, including: counselling, financial, legal, and family concerns, as well as tools and information to support health and wellbeing. + +- Unlimited Remote GP consultations +- Unlimited Mental Health consultations and support +- Fit/Sick notes (available at a cost of £15) +- 360 Wellbeing score +- Nutritional and Personal training sessions +- 1:1 Lifestyle coaching +- Savings and discounts +- Legal and financial support + + +### Getting assistance + +- Access help via the help@hand mobile app. You'll receive an email in your Made Tech inbox to activate your account. This will be available to you from week 1. +- **Contacting help@hand** email help-at- hand@squarehealth.com or call 0333 577 7805. + +### Confidentiality + +We will be informed when the phone line and online service is used, and we will be alerted to what category of query/advice was made. We will not be provided any other details on the contents of your call or use of the service, nor will we be told who accessed the service. + +## Other options + +You are also welcome to pick your own therapist/counsellor. We will contribute £360 per year towards these sessions. diff --git a/handbook/handbook-main/guides/welfare/parental_leave.txt b/handbook/handbook-main/guides/welfare/parental_leave.txt new file mode 100644 index 0000000000000000000000000000000000000000..a37007023c22bd6e8ab3b42107fcc9d2542bc857 --- /dev/null +++ b/handbook/handbook-main/guides/welfare/parental_leave.txt @@ -0,0 +1,61 @@ +# Maternity, paternity, adoption and shared parental leave + +Whether you or your partner are having a baby, you're adopting a child or having a baby through a surrogacy arrangement, Made Tech encourages you to take leave so you can welcome the new child (or children!) into your family. Our paid parental leave is the same for all! + +**Note:** You will have to have worked at Made Tech for at least 26 weeks at the point of the child/children's birth to be eligible for these benefits. + +## Maternity and adoption leave + +We provide 12 weeks maternity/adoption leave at full pay. [If you’re eligible](https://www.gov.uk/employers-maternity-pay-leave), you’ll get statutory pay for a further 39 weeks. You can take up to a total of 52 weeks. + +For adoption leave, only one parent can take this type of leave. The other parent will need to take paternity leave or shared parental leave. + +The breakdown of pay is: + +- 12 weeks at 100% pay (from Made Tech) +- 6 weeks at 90% pay (statutory maternity/adoption pay) +- 33 weeks at statutory or 90% pay whichever is lower (statutory maternity/adoption pay) +- return to work on reduced hours (30 hours) for 4 weeks on full pay to phase back into full time work + +See the detailed government guidelines: [www.gov.uk/employers-maternity-pay-leave](https://www.gov.uk/employers-maternity-pay-leave) and [https://www.gov.uk/employers-adoption-pay-leave](https://www.gov.uk/employers-adoption-pay-leave). + +## Paternity leave +We provide 12 weeks paternity leave at full pay and the option of shared parental leave. + +The breakdown of pay is: + +- 12 weeks at 100% pay +- return to work on reduced hours (30 hours) for 4 weeks on full pay to phase back into full time work + +See the government guidelines: [www.gov.uk/paternity-pay-leave](https://www.gov.uk/paternity-pay-leave). + +## Shared parental leave + +We provide 12 weeks shared parental leave at full pay and up to 39 weeks at statutory pay. + +The breakdown of pay is as follows if you qualify for SPL: + +- 12 weeks at 100% pay (from Made Tech) +- 6 weeks at 90% pay (statutory shared parental pay) +- 33 weeks at statutory or 90% pay whichever is lower (statutory maternity/adoption pay) +- return to work on reduced hours (30 hours) for 4 weeks on full pay to phase back into full time work + +The rules around SPL are fairly complex. See the government guidelines: [https://www.gov.uk/shared-parental-leave-and-pay](https://www.gov.uk/shared-parental-leave-and-pay). + +## Neonatal Care Leave + +You may be eligible for Neonatal Care Leave in addition to your parental leave should your child require further hospital care when born. There are two tiers of Neonatal Care Leave, and accrual can be from a minimum of 1 week up to a maximum of 12 weeks, but it will depend on individual circumstances. + +As we appreciate that any need for this type of leave will likely arise during sensitive and stressful moments, please contact your People Partner to discuss this in more detail. They will work closely with you to manage any leave needs in the best way possible. + +## Other Considerations + +We offer a number of additional company benefits which may be attractive to new parents, including [remote/offsite working](../../benefits/hybrid_working.md), [a generous holiday allowance](../../benefits/taking_holiday.md), [flexible work weeks](../../benefits/flexible_working.md) and [flexible working hours](../../benefits/working_hours.md). + +### Who do I need to inform about upcoming parental leave? + +Please email people@madetech.com to request parental leave and include your child/children's due/adoption date. You should also inform your team lead so they can plan for your absence. The people team will inform scheduling if you are in a client facing team. + +### When do I need to inform you about upcoming parental leave? + +At least 15 weeks before the baby's due date. Find out more about [notice periods.](https://www.gov.uk/employers-maternity-pay-leave/notice-period) diff --git a/handbook/handbook-main/guides/welfare/raising_an_issue.txt b/handbook/handbook-main/guides/welfare/raising_an_issue.txt new file mode 100644 index 0000000000000000000000000000000000000000..cfc64e58ddd03b884fe1b14f5f5b793d5fc08dbe --- /dev/null +++ b/handbook/handbook-main/guides/welfare/raising_an_issue.txt @@ -0,0 +1,70 @@ +# Raising an Issue + +From time to time people may have problems or concerns about their colleagues, customers, company leadership, work environment and so forth. We want everyone in the organisation to be empowered to raise an issue and have it dealt with swiftly and fairly. + +## Have a conversation with the person involved + +The first thing you can do, if you feel comfortable and able, is raise the issue directly with the person involved. This type of direct and informal approach is encouraged and we expect your colleagues who are approached responsibly to respond in a similar manner. This approach may be particularly appropriate to dealing with matters of speech and expression, where individuals may not be aware that their behaviour is causing distress. + + +## Raise the issue via your line manager + +If you feel unable to have a conversation directly with the person involved, and they are a member of staff at Made Tech, then you can discuss this further with your line manager. They can help you find a way to discuss this directly with the person or discuss other routes to help resolve the issue. + +In particular, if you have a grievance you feel unable to raise with your line manager and feel unable to raise directly, you should raise this issue with the people team who can help. + +## Speak to your People Partner + +Sometimes you might not be sure how to resolve the issue, or who you should speak to about it for some advice. If this is the case, then you can speak to your People Partner or email people@madetech.com. + +## Seek Third Party Advice + +We provide staff access to a [employee wellbeing service](paid_counselling.md#employee-assistance) which includes a phone number you can call for third party advice on HR issues. + +You can also call the [Acas](http://www.acas.org.uk/index.aspx?articleid=2042) on 0300 123 1100, Monday-Friday 8am-6pm. + +## Mediation + +At the time of writing we do not have anyone with mediation training at the company but if necessary we can bring in third party mediators to deal with disputes informally. + +You can find out more about Mediation from [Acas](http://www.acas.org.uk/index.aspx?articleid=1680). + +If you wish to enter a mediation process, please ask the people team to request mediation. + +## Formal Grievance Procedure + +From time to time people may have problems or concerns about their colleagues, leadership, their work environment and so on. We want everyone at Made Tech to be empowered to raise an issue.Grievances are concerns, problems or complaints that team members raise with their employer. + +While we will always try and resolve a grievance informally, this might not always be possible and in these cases we will follow our formal grievance procedure, which you can find [here.](https://docs.google.com/document/d/1AvlCHjgIlvGfITFQVE9aSUarbZ7fDwuuYgHTUqD9OB8/edit) If you raise a formal grievance, the following steps will be taken: + +- Step 1: You should write a letter or email to people@madetech.com setting out the details of your grievance and how it might be resolved. +- Step 2: Made Tech will then arrange a formal meeting to discuss the issue as soon as possible. You have the right to bring a companion* with you. We will then adjourn the meeting to investigate the issue further. +- Step 3: We will then decide what action, if any, to take. The outcome, and an explanation of how the decision was reached, will be communicated to you in writing. +- Step 4: You have the right to appeal the outcome if you believe it was unfair. The appeal will be heard as quickly as possible, and efforts will be made to involve an impartial appeal hearing manager who has not already been a part of the grievance procedure. The outcome of the appeal will be communicated in writing. + +\*Companion can include a paid official of a trade union, a lay trade union official that can provide evidence of experience in these matters, or a colleague. + +More information on solving workplace disputes can be found on gov.uk: https://www.gov.uk/solve-workplace-dispute + +## Arbitration Tribunals and Civil Courts + +If you cannot resolve your problem in the workplace, you may have the right to make a claim to an Industrial Tribunal or Fair Employment Tribunal. + +You should seek advice from LRA before starting any procedure. + +You can find information on how to make a claim on gov.uk: https://www.gov.uk/employment-tribunals + +## Disciplinary Procedure +We always prefer to handle minor misdemeanours in an informal way, however in the event of misconduct at Made Tech, we follow a formal disciplinary (conduct) procedure detailed in our policy [here.](https://docs.google.com/document/d/1qIp6jGlUD726J4zJ8A-ZpOzxNw28EwZP/edit) + +This policy applies to misconduct and gross misconduct from our team members, and it includes what is and is not acceptable behaviour at Made Tech. + +We would always start the process with an investigation to understand what has happened, this could lead to a disciplinary meeting. The possible outcomes of a disciplinary meeting could be no further action, or a warning depending on the facts of the case. + +Should a team member’s actions be considered gross misconduct, this could then lead to suspension and/or dismissal. You would be given the right to appeal if you were given a warning or dismissed. + +If you are involved in or have been affected by a conduct procedure, you can reach out for support from: + +- The people team +- Our [Employee Assistance Programme](https://github.com/madetech/handbook/blob/main/guides/welfare/paid_counselling.md#employee-assistance) +- [ACAS](https://www.acas.org.uk/) (the Advisory, Conciliation and Arbitration Service) diff --git a/handbook/handbook-main/guides/welfare/sick_leave.txt b/handbook/handbook-main/guides/welfare/sick_leave.txt new file mode 100644 index 0000000000000000000000000000000000000000..776e765626b719d3df32b3df27771d1eb0e04d88 --- /dev/null +++ b/handbook/handbook-main/guides/welfare/sick_leave.txt @@ -0,0 +1,30 @@ +# Sick Leave + +We recognise that it requires a lot of hard work to perform at the highest possible level and our mental and physical wellbeing is an important foundation for this. + +Beyond taking sick leave when you have a cold or flu we appreciate that you may need to take a day when you feel burned out or when you're impacted by depression. Your Line Manager and the People team are here to help explore all your options when it comes to taking any type of leave and support you with your specific wellbeing needs so you can focus on getting better. + +When people get sick we ask that they follow these guidelines: + +* If you're sick and need to take time off to get well you will be supported by your Line Manager. + +* We can provide support if you need help with your [state of mind](state_of_mind.md). + +* If you need assistance with your sickness, you can use our [employee assistance programme](paid_counselling.md#employee-assistance). + +* On your first day off, let your team know (Slack, email, etc.), or the operations team if you are on the Chalet, that you'll be away and what you had planned for that day. Aim to let them know as early as possible, by start of business, so they can factor your absence into their tasks for the day. + +* Provide regular updates to your team, and an expected return date as soon as you have one. + +* If you need to take several days of sick leave, you may need to provide a fit note from a healthcare professional. The number of days meets the current government guidance for employees [government guidance for employees](https://www.gov.uk/government/publications/the-fit-note-a-guide-for-patients-and-employees). + +* Record your sick leave on HiBob, for every day that you are on sick leave. + +* The Account Team will have to report you as absent without reason to the People Team by 10:30 AM if we haven't heard from you. They will then get in touch, and if unable to get a hold of you, will call your emergency contact at 11:30 AM. + +* On your return to work, we’ll ask that you complete a return to work form on HiBob to make sure you’re well enough to come back to work, and agree any support we can put in place + +* If you accrue ten or more days or five occasions of sick leave annually, then your Line Manager will check in with you to find out how we can best support you. We want to ensure that we aren't putting you under too much pressure, and that you're not unhappy with your current role. + +* If you accrue more than ten days of sick leave in a 12 month rolling period then this may be paid as Statutory Sick Pay. +Please read our Absence Policy (available on our DMS) for full clarity on what’s available and processes supporting sickness absence. diff --git a/handbook/handbook-main/guides/welfare/state_of_mind.txt b/handbook/handbook-main/guides/welfare/state_of_mind.txt new file mode 100644 index 0000000000000000000000000000000000000000..ab6174d123c42b97a12c280c04940b6ea47ce9af --- /dev/null +++ b/handbook/handbook-main/guides/welfare/state_of_mind.txt @@ -0,0 +1,15 @@ +# State of Mind + +We want every one to be happy, including our team. To that end we try and provide [flexible ways of working](../../benefits/flexible_working.md) so that we can have a healthy work/life balance. + +Sometimes though, personal circumstances, stress at work, and other factors can affect our state of mind. Rather than consider this shameful, or brushing it under the carpet, we want to recognise that we aren't always going to be happy and nor should we be expect to be. + +## Supporting each other + +We are a team and it is our duty to care for each other and ourselves, the latter being just as important as the former. + +- Take time off when you're not feeling great mentally +- Ask a colleague, friend, family member for support or lend an ear if you can, sharing helps +- If a colleague looks like they're struggling or need help, be extra kind and supportive, ask if they need help +- If you want confidential advice or phone counselling you can use our [employee assistance programme](paid_counselling.md#employee-assistance) +- If you feel like you're really in trouble, please ask a director or colleague for help, we can provide assistance in whatever shape it need take, from extending time off to providing a course of [counselling](paid_counselling.md) diff --git a/handbook/handbook-main/roles/Associate Business Analyst.txt b/handbook/handbook-main/roles/Associate Business Analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..c33633ba220ded5cb80a19cc22ce215a699c670a --- /dev/null +++ b/handbook/handbook-main/roles/Associate Business Analyst.txt @@ -0,0 +1,51 @@ +# Associate Business Analyst + +Associate Business Analysts will work alongside more senior team members to help deliver products and services that bring value to their users through: +- Identifying business problems and opportunities +- Conducting research to understand the public sector domain, people, organisation, processes and technology +- Explore, elicit and analyse business and user needs +- Identify areas for improvement and explore feasibility of options +- Understand any business and policy constraints that need to be considered, and assess the implications + +## Key responsibilities +### Scope +Associate Business Analysts receive direction from more senior business analysts but are responsible for the output of specific tasks. At this level, you will have limited skills and will work with others or under supervision. You will support stakeholder relationship management. + +### Practice +Applies the following practices as an Associate Business Analyst, within an engagement: +- Agile working, demonstrates experience and awareness in Agile, advises on how and why Agile methods are used, and provides a clear, open and transparent framework for teams to deliver. +- Business analysis, supports the identification, investigation, analysis, and communication of complex business problems and opportunities, and helps to ensure proposed solutions meet business and user needs whilst under supervision. +- Business modelling, understands basic business modelling techniques, supports the representation of business situations, and visualises distinct business processes as directed. +- Business process improvement, provides outputs to support the design and implementation of process improvements and efficiencies in business operations and services. +- Business process testing, applies business analysis and evaluation skills to support the design, execution, and assessment of business process tests and usability evaluations. +- Methods and tools, applies appropriate tools and techniques to support the planning, analysis, development, testing, implementation, and improvement of systems and services. +- Requirements definition and management, supports the identification, analysis, capture, and validation of business and user requirements, and manages requirements and their prioritisation within a defined scope. +- Stakeholder relationship management, identifies, analyses, manages, and monitors relationships with and between internal and external stakeholders, and communicates with stakeholders clearly and regularly under supervision. +- Systems analysis, supports the analysis of IT system capabilities, identifies and specifies system requirements, and supports developing specifications and models for bespoke IT systems or software packages. +- Testing, understands the stages and purpose of testing, supports the representation of business scenarios, and traces requirements to develop functionality. +- User experience analysis, supports the analysis and prioritisation of user experience needs, understands how needs tie to system, product, or service requirements, and makes data-informed decisions based on user research findings. + + +## Community of Practice (CoP) +Engages and participates within Made Tech communities of practice to: +- Recognise when to ask for further guidance and support and identify how to improve how we work. For example, discussing and sharing approaches, ideas and examples of practice. + +## Key measures +- Delivery of good public services for users with clients, shown through relevant measures, for example. data, metrics, KPIs or the passing of service standards. +- Personal performance aligned with DDaT, evidenced through peer feedback. + +## Competencies +Associate Level Business Analysts display Made Tech’s values, relevant DDaT capabilities. +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +The salary for this role is location dependant: + +UK: TBC +London & South East: TBC + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/README.txt b/handbook/handbook-main/roles/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..f507e4aceb7801ab0f20279476dcc0edb0aa966a --- /dev/null +++ b/handbook/handbook-main/roles/README.txt @@ -0,0 +1,117 @@ +# Roles at Made Tech + +This is a list of roles at Made Tech including details on the skills and seniority level they operate at. + +We have listed roles here so that you can learn about what roles we have and how we are organised. If you are looking for open vacancies, visit the [careers page on our website](https://madetech.com/careers). + +## Seniority levels + +We use the SFIA Framework to indicate seniority. We use prefixes in role titles to indicate their SFIA level. + +| SFIA Level | Role prefix | Examples | +| :- | :- | :- | +| [SFIA 1](https://sfia-online.org/en/sfia-8/responsibilities/level-1) | Academy | Academy Designer, Academy Software Engineer | +| [SFIA 2](https://sfia-online.org/en/sfia-8/responsibilities/level-2) | Associate | Associate Designer, Associate Software Engineer | +| [SFIA 3](https://sfia-online.org/en/sfia-8/responsibilities/level-3) | Mid | Designer, Software Engineer | +| [SFIA 4](https://sfia-online.org/en/sfia-8/responsibilities/level-4) | Senior | Senior Designer, Senior Software Engineer | +| [SFIA 5](https://sfia-online.org/en/sfia-8/responsibilities/level-5) | Lead | Lead Designer, Lead Software Engineer | +| [SFIA 6](https://sfia-online.org/en/sfia-8/responsibilities/level-6) | Principal | Principal Designer, Principal Software Engineer, Head of Capability Practice | +| [SFIA 7](https://sfia-online.org/en/sfia-8/responsibilities/level-7) | Director | Director of Capability Practice | + +## Role teams + +We have grouped them by relevant teams so that you can find relevant roles together: + +- [Delivery Management](#delivery-management) +- [User-Centred Practice](#user-centred-practice) +- [Cloud & Engineering Practice](#cloud--engineering-practice) +- [Data Practice](#data-practice) +- [Cyber Security Practice](#cyber-security-practice) + +## Delivery Management + +Delivery Management +- [Delivery Support Analyst](delivery_support_analyst.md) +- [Associate Delivery Manager](associate_delivery_manager.md) +- [Delivery Manager](mid_delivery_manager.md) +- [Senior Delivery Manager](senior_delivery_manager.md) +- [Lead Delivery Manager](lead_delivery_manager.md) +- [Principal Delivery Manager](principal_delivery_manager.md) + +Leadership +- [Head of Delivery Management](head_of_delivery_management.md) + +## User-Centred Practice + +Product +- [Associate Product Manager](associate_product_manager.md) +- [Product Manager](mid_product_manager.md) +- [Senior Product Manager](senior_product_manager.md) +- [Lead Product Manager](lead_product_manager.md) +- [Principal Product Manager](principal_product_manager.md) + +Business Analysis +- [Business Analyst](mid_business_analyst.md) +- [Senior Business Analyst](senior_business_analyst.md) +- [Lead Business Analyst](lead_business_analyst.md) +- [Principal Business Analyst](principal_business_analyst.md) + +Content Design +- [Senior Content Designer](senior_content_designer.md) ([SFIA Level 4](https://sfia-online.org/en/sfia-8/responsibilities/level-4)) +- [Lead Content Designer](lead_content_designer.md) ([SFIA Level 5](https://sfia-online.org/en/sfia-8/responsibilities/level-5)) +- [User-Centred Design Principal](principal_ucp.md) ([SFIA Level 6](https://sfia-online.org/en/sfia-8/responsibilities/level-6)) + +User Research +- [User Researcher](mid_user_researcher.md) ([SFIA Level 3](https://sfia-online.org/en/sfia-8/responsibilities/level-3)) +- [Senior User Researcher](senior_user_researcher.md) ([SFIA Level 4](https://sfia-online.org/en/sfia-8/responsibilities/level-4)) +- [Lead User Researcher](lead_user_researcher.md) ([SFIA Level 5](https://sfia-online.org/en/sfia-8/responsibilities/level-5)) +- [User-Centred Design Principal](principal_ucp.md) ([SFIA Level 6](https://sfia-online.org/en/sfia-8/responsibilities/level-6)) + +Design including interaction and service design +- [Associate Designer](associate_designer.md) ([SFIA Level 2](https://sfia-online.org/en/sfia-8/responsibilities/level-2)) +- [Designer](mid_designer.md) ([SFIA Level 3](https://sfia-online.org/en/sfia-8/responsibilities/level-3)) +- [Senior Designer](senior_designer.md) ([SFIA Level 4](https://sfia-online.org/en/sfia-8/responsibilities/level-4)) +- [Lead Designer](lead_designer.md) ([SFIA Level 5](https://sfia-online.org/en/sfia-8/responsibilities/level-5)) +- [User-Centred Design Principal](principal_ucp.md) ([SFIA Level 6](https://sfia-online.org/en/sfia-8/responsibilities/level-6)) + +## Cloud & Engineering Practice + +Software Engineering + - [Associate Software Engineer](associate_software_engineer.md) ([SFIA Level 2](https://sfia-online.org/en/sfia-8/responsibilities/level-2)) + - [Software Engineer](mid_software_engineer.md) ([SFIA Level 3](https://sfia-online.org/en/sfia-8/responsibilities/level-3)) + - [Senior Software Engineer](senior_software_engineer.md) ([SFIA Level 4](https://sfia-online.org/en/sfia-8/responsibilities/level-4)) + - [Lead Software Engineer](lead_software_engineer.md) ([SFIA Level 5](https://sfia-online.org/en/sfia-8/responsibilities/level-5)) + - [Principal Software Engineer](principal_technologist.md) ([SFIA Level 6](https://sfia-online.org/en/sfia-8/responsibilities/level-6)) + +Technical Architecture + - Lead Technical Architect + - Principal Technical Architect + +Cloud Engineering + - Associate Cloud Engineer + - Cloud Engineer + - Senior Cloud Engineer + - Lead Cloud Engineer + - Principal Cloud Engineer + +## Data Practice + +Data Engineering + - Associate Data Engineer + - [Data Engineer](mid_data_engineer.md) + - [Senior Data Engineer](senior_data_engineer.md) + - [Lead Data Engineer](lead_data_engineer.md) + - [Principal Data Engineer](principal_data_engineer.md) + +Data Science + - Data Scientist + - [Senior Data Scientist](senior_data_scientist.md) + - Lead Data Scientist + - Principal Data Scientist + +## Cyber Security Practice + +Security Engineering + - Senior Security Engineer + - [Lead Security Engineer](lead_security_engineer.md) + - [Principal Security Engineer](principal_security_engineer.md) diff --git a/handbook/handbook-main/roles/associate_delivery_manager.txt b/handbook/handbook-main/roles/associate_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..680e7c5fdd4ebc6574cf6b29d35e274a2b545fed --- /dev/null +++ b/handbook/handbook-main/roles/associate_delivery_manager.txt @@ -0,0 +1,104 @@ +# Associate Delivery Manager + +You’ll work as part of a delivery team. You’ll provide administrative and delivery assistance so the team can deliver to their full potential, while you develop the skills of a Delivery Manager. + +## Your role at Made Tech + +As an Associate Delivery Manager, you will work alongside a more senior delivery manager, shadowing and providing support, until you’re confident enough to deliver an element yourself under guidance and mentorship. You will pair with the Delivery Manager and observe how they triage and solve problems, to provide you with confidence and experience to move into an autonomous delivery role. +Although you will probably not have experience managing software delivery, you’ll use cross-functional skills to support your delivery team. Initially you will expect the majority of your tasks to be directed by your delivery partner, but you will start to identify items you can support autonomously during team ceremonies and sprint planning. + +You use empathy and effective listening skills to help the team collaborate. You will use your previous project management experience to support the identification and management of project dependencies, risks and issues alongside your delivery lead. After observing team ceremonies and building relationships with the client stakeholders, you will start to take responsibility for running meetings, answering client questions and unblocking team problems. + +With support, you will use your excellent attention to detail to ensure the project is delivered within budget, using tools such as Google Sheets to match up the time spent by the team with the amount of work left to complete. +You are passionate about learning and developing your skill set, and are an active member of the Delivery Community of Practice (COP). You spend time learning from other Capabilities (cloud & engineering, user-centred design, product & business analysis) about what good looks like in their areas of expertise. + +## Definition of success + +Success as an Associate Delivery Manager is predominantly measured by how you support the delivery team, your accuracy and attention to detail, and building rapport with stakeholders. It is also assessed based on personal development and learning, as you move towards autonomy and being solely accountable for a delivery. + +## Expected outcomes +* Enabling a team by identifying and unblocking dependencies +* Accuracy in all items worked on (for example budget trackers, meeting notes, timesheet approval) +* Contribute to the Delivery Community of Practice +* Becoming autonomous and accountable for a delivery through personal development, learning, mentorship and shadowing + +### KPIs +* Timesheet accuracy +* Learning & development objectives + +## Responsibilities +Associate Delivery Managers are responsible for delivering the above outcomes by collaborating with other members of their delivery team. + +### Project Level Delivery Assurance +- Support the Delivery Lead to manage scope, budget and quality +- Feed into the status of quality and risk reported to heads of delivery on a weekly basis +- Support the delivery team by facilitating ceremonies, doing administrative tasks and unblocking dependencies with guidance +- Support the delivery lead with identifying and managing risks, issues and dependencies +- Where directed, review and approve timesheets, invoices and Kimble forecasts, ensuring accuracy at all stages + +### Personal Development +* Regularly gather and act on feedback about personal development +* Define and work towards a learning and development plan to ensure you are able to autonomously manage a project as quickly as possible + +### Growing Made Tech’s Impact +* Build relationships with stakeholders within your project, and engage with other experts in the organisation for example at the client Community of Practice + +### Community and Thought Leadership +* Share successes and failures with the Delivery Community to support the evolution of ways of working, techniques, and technologies across Made Tech +* Contribute to developing a thriving community of practice and shared identity + +## Competencies and behaviours + +Associate Delivery Managers are expected to be operating at, or working towards, [SFIA level 3](https://sfia-online.org/en/sfia-8/responsibilities/level-3) in all five competencies. The below list describes specific competencies and behaviours that you’ll need in this role. + +We don’t expect you to tick all the boxes when you join. We'll work together to define learning and development objectives that help you meet these competencies on your way to promotion. + +### Articulation and role modelling of Made Tech values, purpose, and vision +* Describe each with examples +* Demonstrate role modelling + +### Commercial awareness +* Be able to point to and interpret the project commercial fundamentals for your workstream (Statements of Work, Purchase Orders, Gross Profit Margin, Forecasting, Burndown) +* Understand and describe how the Delivery Lead ensures that the team is on track to meet the deliverables defined in the SOW + +### Time management and prioritisation +- Demonstrate prioritisation +- Demonstrate time management + +### Effectively manage delivery risk and quality +* Demonstrate supporting a Delivery Lead to perform risk management activities including identification, assessment, mitigation, assessment and reporting to key stakeholders +* Describe how the delivery team defines and monitors quality + +### Coach teams to successfully deliver projects +* Understand and explain the differences between Kanban, Scrum, and Waterfall - and when best to use them +* Understand and articulate what your team is doing to ensure they adhere to best practices such as Security, DevOps, User Centred Design and Data Ethics +* Be able to explain the purpose of the GDS phase you are currently working on (Discovery/Alpha/Beta/Live) +* Demonstrate knowledge of where to find and how to use the GDS service standard +* Be able to explain the Roles and Responsibilities of all of the roles on the team you are working on + +### Facilitation and communication +* Demonstrate experience of running ceremonies and facilitating meetings - with post meeting feedback +* Demonstrate experience of producing accurate documentation or meeting notes + +### Trust building with your seniors, peers, juniors and client stakeholders +* Demonstrate with feedback from seniors, peers, juniors and client stakeholders +* Demonstrate moving towards taking ownership for the success of the delivery, through feedback from your Delivery Lead + +### Continuous improvement and feedback +* Demonstrate positive response to feedback with course correction +* Demonstrate providing regular feedback for team members + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + + +## Salary and location +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help diff --git a/handbook/handbook-main/roles/associate_designer.txt b/handbook/handbook-main/roles/associate_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..74b5dc88ba8db9796ee90467c639daf3a0654034 --- /dev/null +++ b/handbook/handbook-main/roles/associate_designer.txt @@ -0,0 +1,63 @@ +# Associate Designer + +- Location: mainly remote with occasional office and client visits +- Offices: London, Bristol, Manchester, and Swansea +- Salary: Please refer to the job advert when this role is live +- SFIA: Level 2 + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +Associate Designers are practitioners who collaborate with others to tackle challenges faced by people and society. They work within a team to design and deliver public services. They do this by understanding problems and creating solutions that work equally well for users and stakeholders. They are active members of a healthy user-centred design (UCD) community and culture at Made Tech. + +Associate Designers might: +- have a degree in a subject like UX design or interaction design +- be a graduate of a vocational course in UX design +- already be a product designer, UX designer, service designer, or interaction designer + +## Key responsibilities + +## Scope + +- Responsible to a Senior Designer for assisting in the design and delivery of public services +- Hands-on design for one product/team under guidance from a more senior designer +- Recognises when to ask for further guidance and support +- Work is reviewed regularly +- Contributes to communities of practice, discussing and sharing suggestions, approaches and ideas - including proactively seeking feedback on own work + +## Practice + +- Come up with creative solutions to problems revealed in research +- Make things real by prototyping your ideas +- Take responsibility for sharing your own work with your team +- Improve your designs over time +- With the support of your team, explain your design decisions to stakeholders + +## Community + +- Take part in Made Tech community activities + +## Key measures + +- Delivery of good public services for users in partnership with Made Tech’s clients + +## Competencies + +- Client focus +- Drive to deliver +- Learning +- Facilitation +- Thinking through making + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/associate_product_manager.txt b/handbook/handbook-main/roles/associate_product_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..9d2ee121bf156986645ee0745c0c36c0a14bce7e --- /dev/null +++ b/handbook/handbook-main/roles/associate_product_manager.txt @@ -0,0 +1,61 @@ +# Associate Product Manager + +Associate Product Managers make sure products and services deliver measurable value, by exploring: + +- **user needs** - defined through comprehensive research +- **organisational needs** - defined by the requirements placed upon or introduced by the client (e.g. legislation) +- **service needs** - non-functional requirements + + +## Key responsibilities + +## Scope +Associate Product Managers: +- Assist work on a single engagement or work on a low risk, simple engagement +- Have some experience of Product Management practices, principles and approaches or a related discipline +- Engage within the community of practice +- Display the [Associate Product Manager DDaT competencies](https://www.gov.uk/guidance/product-manager#associate-product-manager) and [SFIA Level 2 Behaviours](https://sfia-online.org/en/sfia-8/responsibilities/level-2) + +Associate Product Managers should expect to regularly have their work peer-reviewed and work under direction of their line manager. + +## Practice +Applies or assists application of the following practices as Associate Product Manager, within an engagement: + +- identifies value for users, services and organisations using research and analysis +- prioritises work to deliver increments of value to users +- makes sure engagements have measurable outcomes +- negotiates product governance by recommending the definitions of ready and done, and developing success criteria +- can identify, understand and manage issues and risks +- participates as a team member, seeking opportunities for collaboration and continuous improvement +- assists the delivery manager to track progress and show our work to clients and colleagues +- applies the agile mindset to enable best practice and realisation of value +- enables teams to be effective by fostering a culture that supports psychological safety + +## Community of Practice (CoP) +Engages and participates within Made Tech communities of practice to: + +- build an inclusive and supportive culture +- recognise when to ask for further guidance and support and identify how to improve how we work, for example, by discussing and sharing approaches, ideas and examples of practice +- understand the role and activities of Product Managers, to develop their practice + +## Key measures +- Delivery of good public services for users with clients, shown through relevant measures, for example. data, metrics, KPIs or the passing of service standards +- Personal performance aligned with DDaT and SFIA grade, evidenced through peer feedback + +## Competencies +Associate Product Managers display Made Tech’s [values](https://github.com/madetech/handbook/blob/main/company/about.md), relevant [DDaT capabilities](https://www.gov.uk/guidance/product-manager) and [SFIA (Level 2)](https://sfia-online.org/en/sfia-8/responsibilities/level-2) behaviours. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/associate_software_engineer.txt b/handbook/handbook-main/roles/associate_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..c2a8d4fc5b980c26aecdb6563e14350cc2f2b7ff --- /dev/null +++ b/handbook/handbook-main/roles/associate_software_engineer.txt @@ -0,0 +1,29 @@ +# Associate Software Engineer + +Our engineers build software that makes our clients happy. They prefer problem solving over completing tasks, love learning from colleagues, and work as a unified team to help deliver projects that make a real difference to people’s lives. + +## Your role at Made Tech + +We primarily write and deliver custom software for the public sector. Technical excellence for us isn’t about delivering to feature lists. We place a strong emphasis on outcome-based delivery, making sure our clients’ goals are understood and achieved with the technology we deploy. + +Our teams have used Ruby with Rails and Sinatra, ES6 with React and Angular 2, and C# with .NET Core. We don’t limit ourselves and we expect all of our engineers to be keen on learning new technologies. Automation is important to our teams, so we make sure there’s a CD pipeline set up to build, test, and release. We’re usually responsible for setting up clients’ infrastructure, too. For example, on AWS, GCP or Azure using tools like Terraform. Though, sometimes we opt for a Platform as a Service like Heroku. + +## What experience are we looking for? + +All of our Software Engineers are trained first as an Academy Software Engineer within our 12-week academy programme. + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +We don't hire directly for Associate Software Engineer roles at Made Tech. We prioritise our hiring opportunities towards our Software Engineering Academy. You’ll need to complete our 12-week academy programme. After your first 6 months at Made Tech, you’ll be in a position to pass probation and become an Associate Software Engineer with us. Learn more about our academy and find out when we’re accepting applications at https://www.madetech.com/careers/academy. We’d still love to hear from you if you feel our academy or more senior engineering roles aren’t a good fit for you. If you have any questions, drop us a line at [careers@madetech.com](mailto:careers@madetech.com). diff --git a/handbook/handbook-main/roles/delivery_director.txt b/handbook/handbook-main/roles/delivery_director.txt new file mode 100644 index 0000000000000000000000000000000000000000..e240b9cd9c76ecf72248947dd3272ecb4bba58e3 --- /dev/null +++ b/handbook/handbook-main/roles/delivery_director.txt @@ -0,0 +1,102 @@ +# Delivery Director + +Our Delivery Directors are each responsible for the successful delivery of our entire portfolio of client activity in an industry. +You will be pivotal in leading our delivery across multiple clients within the industry and managing client relationships at the most senior level. +Commercially experienced with deep client delivery expertise, you will be responsible for overseeing a portfolio of client revenues in excess of £10million per annum. +You will ensure the successful execution of projects, client delight, team engagement, and the continued growth of our business within the public sector. + +## Outcomes + +Our Delivery Directors report directly to the Chief Delivery & Transformation Officer with a dotted line to the relevant Industry Director. Successful Delivery Directors are able to build teams that connect our Capability Practices, Industry Practices and clients. + +Key outcomes for Delivery Directors: +* Demonstrate leadership and expertise in your Industry and in professional services delivery +* Support Industry and Made Tech commercial growth balanced with delivery quality and risk +* Develop senior relationships with client counterparts and stakeholders to build Made Tech’s reputation, reach and impact +* Support the development of the Delivery Managers within your Industry +* Contribute to the ongoing development of the Delivery Management practice and other Capability Practices as a member of the Capability Leadership Team + +## Responsibilities + +1. Enable client success +* Ensure the successful delivery of client outcomes within your portfolio +* Support clients in the achievement of their wider outcomes through becoming a trusted advisor and building a senior network within their organisations +* Support the Delivery Managers working on your engagements to ensure the right client outcomes are achieved + +2. Develop, nurture and maintain strong stakeholder and peer relationships +* Build peer-to-peer relationships within our clients, wider industry and the Made Tech business +* Anticipate and understand client needs and objectives to drive alignment of our services, solutions and propositions +* Be a visible and active member of relevant forums, bodies and communities - internally and externally - to build strong stakeholder networks, support personal and professional development, and represent the Made Tech brand. +* Bring clients across government together where they have common problems and to build valuable networks through introductions, community events or thought leadership + +3. Enable Made Tech commercial success +* Support the growth (revenue and margin) of the industry + * Ensure proposals are produced and delivered successfully + * Ensure proposal teams are suitably resourced + * Ensure solutions are appropriately scoped (incl. team shapes) + * Invite Capability Practices and subject matter experts to contribute to the growth of your accounts +* Own the financial performance of the engagements across the Industry portfolio + * Drive delivery teams to deliver or exceed target margin + * Work with Capability Practice leads to ensure appropriate staffing of engagements + * Work with the Delivery Managers within your Industry portfolio to monitor project budgets, margins, and revenues, and support them to implement strategies to maximise profitability +* Support the growth of industry-specific skills + * Build and maintain Industry community of practice to develop the virtual team + * Create a forward view of the required skills and capabilities for the Industry. Support the Capability Practices in inclusive hiring and developing appropriate skills +* Bring Industry and client-specific insights back into the business + * Support the development of Industry-specific propositions + * Collaborate with Industry and wider Made Tech leadership to develop and execute strategies for business growth within the accounts, industry and business + * Identify new opportunities and markets for expansion. +* Ensure Industry and account forecasts are accurate + +4. Ensure delivery is consistently of the highest quality from Made Tech +* Provide delivery leadership across multiple client accounts and effectively delegate to the Delivery Managers within your Industry portfolio (dotted-line reports) + * Ensure engagements are delivered on time, within scope, and within budget + * Manage project teams and resources effectively +* Identify performance issues and work with the account teams and Capability Practices to ensure these are addressed +* Work with the Capability Practices to ensure that the appropriate tools, templates, approaches, methodologies and playbooks are actively used on deliveries +* Coach our Delivery Managers and wider delivery community +* Support the development of the Delivery Management practice +* Ensure compliance with Made Tech and client legal, governance and reporting standards +* Drive continuous improvement across all of our deliveries + +## Competencies & Experience + +The Delivery Director role is part of the Capabilities Leadership Team and is currently graded at SFIA Level 6. In addition to this, the below competencies and behaviours will be expected: +* Role modelling of Made Tech’s values and behaviours +* Alignment to our purpose, and our vision +* Strategic thinking and planning +* Commercial awareness +* Results-oriented +* Passionate about delighting the customer; anticipate and solve client problems, not just respond to demand +* Time management including balancing multiple priorities +* Performance management of indirect reports +* Prioritise diversity and inclusion in goals and day-to-day activity +* Inspiring leadership and open communication +* Deep client and industry expertise; an understanding of their unique issues and insight/ experiences from other projects +* Manage delivery and reputational risk, maintain velocity and ensure solution safety +* Engage early on client business problems and delivery issues +* Able to align the relevant teams to Industry Verticals +* Improve client focus across our business + +And the type of experience we anticipate you will bring: +* You’ll have proven experience in project and programme management, or delivery management, preferably in the digital, software and services industry +* Proven track record of successfully managing and delivering large-scale projects and portfolios (revenues of £1m-£10m+) +* Experience of engaging at senior levels on strategy and developing relationships based on your subject matter expertise +* Experience of account or business growth through any combination of supporting bids, client relationship building, solution shaping, senior consulting engagements or similar +* Strong leadership and team management skills. You’ll have actively coached, mentored and managed (directly or matrix) diverse teams achieving demonstrable positive people results +* Excellent financial acumen and budget management skills +* Strong problem-solving and decision-making capabilities +* Knowledge of the UK public sector, the Industry you’ll be leading in, and the unique requirements that the sector and industry bring is highly desirable +* Relevant certifications are also a plus. + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +## Salary and location + +We adopt a hybrid approach and anticipate that most roles will spend a mixture of time within our offices, client sites and working remotely. We have offices in London, Bristol, Manchester, and Swansea and our clients are across the UK. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. diff --git a/handbook/handbook-main/roles/delivery_support_analyst.txt b/handbook/handbook-main/roles/delivery_support_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..1e2f6f6943e644c8d2e0a7a934307b6f38daf94d --- /dev/null +++ b/handbook/handbook-main/roles/delivery_support_analyst.txt @@ -0,0 +1,81 @@ +# Delivery Support Analyst (PMO) + +Salary: Please refer to the job ad when this role is live +Location: Bristol, London, Manchester or Swansea with hybrid-working policy + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Your role at Made Tech +The Delivery Support Analyst in PMO at Made Tech plays an essential role in ensuring the seamless execution and oversight of the company's digital transformation engagements. + +This role will see you managing workstream reporting, ensuring compliance with Statements of Work (SoW), and maintaining a comprehensive RAID (Risks, Assumptions, Issues, Dependencies) log across all Made Tech engagements. + +This involves capturing and managing the demand for resources within each workstream or SoW, coordinating with the Scheduling team to raise and manage resource requests, and working closely with workstream leads to ensure the appropriate allocation of resources. + +The Delivery Support Analyst will play a crucial role in maintaining the structure and efficiency of the project lifecycle. + +The Delivery Support Analyst supports the account onboarding of new team members and supports the creation of rotation plans as necessary, ensuring smooth transitions and consistent team performance within the PMO office. + +The Delivery Support Analyst also tracks budgets and capacity within each workstream or SoW, actively highlighting risks and issues to the accountable Delivery Manager, which is vital for maintaining project alignment with financial and operational goals. + +Furthermore, this role ensures accurate and timely completion of timesheets across all workstreams, which is essential for effective budget management and resource planning. + +The management of team work plans, schedules, and on-site registers also falls under the PMO's purview, allowing for the consistent and organised execution of projects. + +Beyond operational management support, the Delivery Support Analyst at Made Tech is responsible for producing timely, visual, and client-ready reports on all aspects of the engagements. + +These reports are crucial for communicating the current status, risks, and progress to various stakeholders, including the C-Suite, ensuring transparency and informed decision-making. + +The Delivery Support Analyst also supports the team with logistical tasks, such as booking travel and accommodation, facilitating key meetings and ceremonies with stakeholders, and overseeing dependencies and issue monitoring. + +These activities contribute to the overall health and success of the workstreams and SoWs, allowing the PMO office to play an integral role in maintaining project momentum and resolving challenges as they arise. + +The Delivery Support Analyst also plays an active role in presenting and reporting on engagement status at agreed frequency levels to a wide range of stakeholders across the business. + +Finally, the Delivery Support Analyst creates and maintains all key engagement documentation, or collaborates with the Delivery Manager to bring in additional expertise when needed. + +This documentation is vital for keeping a detailed and organised record of project activities, decisions, and changes. + +As an active participant in the Delivery Management community, this role not only helps to drive the successful delivery of current engagements but also contributes to the continuous improvement of project management practices within Made Tech, ensuring that the organisation remains agile, efficient, and responsive to client needs. + +## Responsibilities + +* Manage work stream reporting, SoW compliance reporting and overall RAID log for Made Tech’s engagements +* Capture and manage demand for resources within each of the Made Tech account workstreams/ SoWs. Work with Scheduling to raise/ manage resource requests and work with workstream leads to verify appropriate resource allocation +* Support onboarding new team members and create rotation plans where appropriate +* Track budget and capacity within each work stream/ SoW, highlighting risks and issues to Delivery Manager +* Ensure accurate and timely timesheet completion across all work streams/ SoWs +* Manage team work plans/ schedules and on-site register +* Provide timely and visual client-ready reporting on all of the above +* Support the team with travel and accommodation booking as required. +* Facilitate key meetings/ ceremonies with stakeholders where appropriate +* Oversee dependencies, action/ issue monitoring, and controls and help to perform health checks work streams/ SoWs +* Create and maintain all key engagement documentation, or work with the Delivery Manager to bring additional specialist knowledge onboard +* Present and report on engagement status to the agreed frequency level to a range of stakeholders across the business, up to C-Suite level. Be an active participant in the Delivery Management community within the engagement and Made Tech + +### Expected outcomes + +* Reduce the time delivery managers are spending on internal-facing activities to optimise client-facing time. +* Reduce the cost of internal-facing activities through centralisation, standardisation and automation. +* Improve quality and accuracy of products through centralisation, standardisation and automation. + +### KPIs: +* Delivery Management effort freed up. +* Quality and accuracy. + +### Definition of success: +Success as a Delivery Support Analyst is measured by smooth, efficient and high-quality implementation of delivery operational work to enable account teams to run more efficiently and focus on high-value activities for our clients. + +### Skills people must have +Don’t worry - we don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these competencies on your way to promotion. + +* Experience leading or supporting business change programs or portfolios. Programme office delivery experience within the full lifecycle of cross functional projects (software engineering, user experience, architecture, etc.) +* Experience in managing/ influencing colleagues and peers to achieve required business outcomes (timesheet compliance, policy adherence, etc.). Able to use soft power to create influence and know when to escalate to achieve required outcomes +* Experience of project scheduling, risk management, budget management, and tracking the realisation of benefits +* Clear and confident communication skills; able to partner and work with stakeholders from client organisations and across the business, including C-Suite executives +* Experience in managing the activities of a project team in a matrixed project organisation + +### Certifications: +Certified ScrumMaster or equivalent (for Agile projects) would be desirable but not essential. diff --git a/handbook/handbook-main/roles/finance_business_partner.txt b/handbook/handbook-main/roles/finance_business_partner.txt new file mode 100644 index 0000000000000000000000000000000000000000..55b04d0b4f8ad99946f2e170f18a5ac798e5726d --- /dev/null +++ b/handbook/handbook-main/roles/finance_business_partner.txt @@ -0,0 +1,91 @@ +# Summary + +A commercially-focussed business partner with financial expertise who has strong analytical experience, facilitates collaborative and informed decision making, can influence commercial decisions, and can negotiate people’s buy-in to deliver on the company's financial and strategic objectives. + +# The Role at Made Tech + +Our finance team is a critical partner in driving business growth and profitability. + +As a Finance Business Partner, you will play a pivotal role in connecting finance with the broader business. Acting as a strategic advisor to departmental heads and senior management, you will provide insights, analysis, and financial leadership to support data-driven decision-making. + +This role goes beyond traditional financial reporting — you will be forward looking, able to identify patterns, and proactively engage commercial leaders. You will identify opportunities that create value and foresee and mitigate risks to commercial decisions. You will contribute confidently, clearly, and with sensitivity as you build your own knowledge and relationships across the company. You will drive high performance, seek efficiencies, and develop creative solutions to complex challenges. + +A positive attitude and desire to create a collaborative culture is a must. You should have the ability to work on your own initiative, as well as being a good team player - joining a team committed to the success of Made Tech. + +Reporting to the Financial Controller, this role will see you proactively engaging the business on financial performance, sharing insights and gathering feedback. You will be technically strong, and commercially astute. You will prepare - and may need to create - your own financial models for reporting, forecasts and budgets using google office suite. + +At Made Tech, we’re collectively continuing to grow a culture that is happy, healthy, safe and inspiring for people of all backgrounds and experiences, so we encourage all people from underrepresented groups to apply for roles with us. Have we caught your interest? Please read on… + +## Definition of Role Success + +Success involves; +* having a good understanding of the business units’ strategies and service principles; +* ensuring data accuracy; +* providing regular insights that enlighten and bring numbers to life; +* influencing key commercial decisions; +* having a mindset of continuous improvement; +* ensuring financial performance is collectively owned and understood by all relevant stakeholders; and +* ensuring feedback on financial activity, processes and performance is gathered and used to help drive better business processes. + +## Key Responsibilities + +**Business partnering:** +Act as a trusted advisor and a primary point of contact between finance and other departments (primarily commercial and delivery teams). Build strong relationships and communicate effectively. + +**Strategic financial planning:** +Partner with business leaders to shape and execute financial strategies that align with company goals. Provide forward-looking financial insights, analysis and commentary to drive operational efficiencies and anticipate future needs. + +**Budgeting & forecasting:** +Understand financial trends including sales, revenue, margin, and productivity. Create budgets and forecasts in collaboration with relevant business units, ensuring alignment with strategic objectives. Track performance and provide meaningful and actionable insights to ensure that goals are achieved. Challenge assumptions to ensure robust and realistic plans. + +**Sales and delivery support** +Support commercial teams in pricing sales contracts and working with finance, operations and commercial teams to ensure that appropriate project KPIs are understood, tracked and actioned in order to ensure that projects run to plan and delivery risks are mitigated. + +**Financial reporting:** +Ensure regular, accurate, timely, and transparent financial reporting. Provide insights beyond the numbers, turning complex data into actionable recommendations. + +**Data & Technology Integration:** +Leverage modern SaaS tools, dashboards, and data analytics to automate processes, improve decision-making speed, and enhance business visibility on key business metrics. + +**Data integrity and change management:** +Drive continuous improvement initiatives across finance and business processes ensuring a consistent approach to data integrity, collation, analysis and interpretation. Champion the adoption of new technologies, systems, and methodologies to enhance agility and efficiency and manage structured change programs. + +## Competencies, behaviours, experience and/or qualifications + +**Financial Expertise:** +Proven experience in financial analysis, budgeting, forecasting, modelling techniques and business partnering. A track record of using data to drive strategic decisions. + +**Strong Analytical & Problem-solving Skills:** +Ability to dissect complex financial data, identify trends, and communicate actionable insights clearly. + +**Stakeholder Management:** +Excellent communication and interpersonal skills, with a strong ability to influence senior leaders and collaborate across functions. Making finance easy to understand for non-finance people. Actively seeking feedback on both self, team and systems and processes regularly. Demonstrate positive response to feedback with course correction. + +**Business Acumen:** +Understanding of how financial decisions impact business strategy, operational performance, and long-term growth. + +**Tech-savvy:** +Demonstrable google sheets skills, and experience with Kimble and SalesForce is an advantage. An appetite for leveraging technology to drive efficiency. + +**Agile & Adaptable:** +Ability to thrive in a fast-paced, dynamic environment. Comfortable with ambiguity and adept at managing change. Able to effectively manage multiple priorities. + +**ESG/Sustainability Focus:** +Experience with - or passion for - integrating financial and sustainability goals is a plus. +Articulation and role modelling of Made Tech values, purpose, and vision + +**Qualifications:** +We are looking for a person who has completed their professional accounting qualification (ACA/ACCA/CIMA qualified (or equivalent)) with experience in a similar finance role, preferably within a professional services and fast-growth company. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +### Salary and location +We mainly work remotely but you will need to go to the office usually a few times a month. We have offices in London, Bristol, Manchester, and Swansea. +The salary for this role is experience dependant though our pay philosophy is to hire and develop: + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +Office: London preferred but open to Bristol and Manchester. (Remote 3-4 days per week) diff --git a/handbook/handbook-main/roles/head_of_delivery_management.txt b/handbook/handbook-main/roles/head_of_delivery_management.txt new file mode 100644 index 0000000000000000000000000000000000000000..f9221291e21d04aa2714fef485dae30e8e4f5028 --- /dev/null +++ b/handbook/handbook-main/roles/head_of_delivery_management.txt @@ -0,0 +1,81 @@ +# Head of Delivery Management + +Our Head of Delivery Management is responsible for managing all client delivery. They head the Delivery Management Organisation (DMO) which is responsible for connecting industry and capability practices to ensure we maintain high quality standards and continually mitigate risks in order to deliver successful outcomes. + +To foster collaboration across capability practices, the Delivery Management Organisation is responsible for facilitating creation of cross-capability materials and training. They are responsible for growing the delivery management team ahead of demand, managing the performance of delivery experts, and supporting career development. + + +## Outcomes + +The DMO has a set of outcomes and KPIs that work towards our organisational purpose, vision, and missions. To be successful the DMO must work as one team with Industry Practices, Capability Practices and Business Services as well as with clients. + +Key outcomes for the Head of Delivery Management and the DMO: + +- Manage quality and risk of all delivery as we scale +- Growth of delivery management team headcount slightly ahead of demand +- Maximise utilisation and make the most of bench time by investing it to support sales, career development and training of delivery managers, and continuous improvement of the DMO +- Maximise retention of delivery managers by building a strong delivery identity and career pathways +- Balance retention and profitability to grow a healthy delivery organisation while minimising costs + +## Responsibilities + +The Head of Delivery Management is responsible for delivering the above outcomes by collaborating with the business. They report to the Executive Director for Delivery and Capabilities who is their line manager and representative in the Executive Committee. + +### Strategy and management + +- Influence policy and strategy on behalf of the DMO +- Contribute to annual/quarter planning and be responsible for the delivery of goals +- Support integration and collaboration of the Delivery Management Organisation and Capability Practices with each other and the wider organisation + +### Service delivery and delivery assurance + +- Manage delivery across all workstreams by embedding delivery managers into Industry Practices +- Report to Executive Committee on a weekly basis the status of quality and risk across all deliveries +- Facilitate creation of set of centralised resources with capabilities + +### Hiring and careers + +- Scale supply of delivery managers ahead of demand +- Management of delivery managers including performance, progression, career paths and succession planning +- Maintain high-levels of motivation and retention in the delivery management team + +### Demand Generation + +- Bid support, quality assurance and sponsorship + +### Community and thought leadership + +- Continuously improve service delivery and ways of working based on past successes and failures +- Foster thriving community of practice and shared identity +- Consistently deliver thought leadership content and work with marketing to promote and drive growth +- Encourage cross-community and multi-disciplinary collaboration + +## Competencies + +The Head of Delivery Management role is expected to be filled by Principals or Directors operating at SFIA level 6 or above in all five competencies due to the high impact and scale this role operates at. In addition to this, the below competencies and behaviours will be expected. + +- Articulation and role modelling of values, purpose, and vision +- Strategic thinking and planning +- Commercial awareness +- Time management including balancing multiple priorities +- Performance management of direct and indirect reports +- Prioritise diversity and inclusion in goals and day to day activity +- Inspiring leadership and good communication +- Trust building with your seniors, peers and juniors +- Continuous improvement and feedback + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/head_of_managed_services.txt b/handbook/handbook-main/roles/head_of_managed_services.txt new file mode 100644 index 0000000000000000000000000000000000000000..631dd7e71b4100547426d832e0c83289781f0eb1 --- /dev/null +++ b/handbook/handbook-main/roles/head_of_managed_services.txt @@ -0,0 +1,63 @@ +# Head of Managed Services + +Our Head of Managed Services will be responsible for building an exceptional operation to manage the transition to live - and ongoing running - of our clients’ services, applications, data, infrastructure and cloud estates. + +We believe that Managed Services, done effectively, can significantly enhance citizen and user experiences, bolster the resilience of public services, and continually improve the applications that deliver essential capabilities to our society. + +The successful candidate will join the existing practice to help us to grow, develop and support the sale of a set of differentiated offerings covering the end-to-end design, transition and support for a wide range of IT services, platforms and products. They will develop a team of engineering, cloud, data, user-centred and managed service professionals, engage with our clients on their business priorities and challenges, and guide and monitor client engagements across Made Tech. + +This role reports directly to the Chief Delivery & Transformation Officer. + +## Role Description + +Our Head of Managed Services is a member of Made Tech’s leadership team with the responsibility and autonomy to define strategic plans that accelerate the growth of both the practice and wider business. + +You will be responsible for the revenue, margin and utilisation of the practice, collaborating with the other practice, industry and delivery heads to drive excellent services for our Public Sector clients. + +The right person for this role will do this by combining their experience of IT service management, passion for simplification and legacy modernisation, and their established industry network with Made Tech's unparalleled experience of delivering digital services and digital transformation for the public sector. + +### Your role at Made Tech + +* Grow the Managed Services practice at Made Tech; alongside our industry leadership teams, develop trusted relationships with our clients to identify specific growth opportunities and proactively take new ideas to our clients to help them solve their biggest problems +* Develop the Managed Services propositions; establish Made Tech as an innovator and thought leader in the space, sharing our differentiated approach to improve services across the public sector +* Lead the Managed Services practice; hire, develop, motivate and coach a team that understands the user/client needs as well as the technology we are supporting across the public sector +* Deliver a profitable Managed Services business; balance complex client needs with highly performing, suitably leveraged and cost effective teams +* Shape our service offering; define and deploy the operational processes and approaches that underpin our migration, modernisation, improvement (cost and experience) and managed service activities +* Provide subject matter expertise; lead the migration and operations offerings on our existing client accounts, guiding the account teams to building strategic plans that deliver on our goals +* Be a trusted advisor; build strategic relationships with C-Level stakeholders across our public sector client base and the wider industry +* Be the point of escalation; support the team for service impacting issues/ incidents, conduct major service reviews with key clients and liaise with high profile stakeholders +* Help develop our integrated client proposition; align the Managed Services strategy and offerings to our Transformation, Security, Engineering and Cloud offerings to ensure a comprehensive service to our clients. + +### The following skills will be assessed during the application process + +**Client Advisory** +* Understanding of the issues and challenges that the public sector faces in supporting and transforming legacy applications, as well as minimising the risk of future legacy technology +* Experience building trusted advisor relationships with senior client stakeholders within the public sector. + +**Practice vision** +* Strategic vision; ability to align services with evolving societal requirements and public sector objectives +* User-centric approach; strong commitment to designing and improving services based on user needs and experiences +* Continuous improvement and innovation; proficiency in engaging with stakeholders, including end-users and public sector teams, to identify and implement improvements and incorporate new technology to enhance service performance, user satisfaction and accessibility +* Data-driven decision making; utilise data analytics to inform strategic decisions, identify opportunities for change and optimise service delivery. + +**Routine growth** +* Experience developing targeted propositions and go-to-market plans based on client needs and ability to contract/ buy for managed service offerings and propositions +* Experience of working with sales professionals and commercial responsibility for strategic organisational goals +* Experience in running migration and support services for platforms, user-facing digital and data services, cyber security operations +* Experience of support capabilities including fully outsourced and outcome based, embedded capabilities, service design, transition and support product implementation/ integration. + +**People and partnerships** +* Experience of building and managing high performing service management teams and creating the operating model to provide a cost-effective client-facing experience +* Experience of owning a cost-centre and of working with commercial functions to grow a profitable practice +* Experience of managing partnerships and suppliers to provide a consolidated and seamless managed service offering to clients of varying levels of service maturity +* Understanding of the support and operations tooling landscape, experience of cross organisation integrations and the development of automated monitoring and alerting frameworks. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +## Salary and location +We have a hybrid-working policy with visits to clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. diff --git a/handbook/handbook-main/roles/head_of_service_line.txt b/handbook/handbook-main/roles/head_of_service_line.txt new file mode 100644 index 0000000000000000000000000000000000000000..e7698f04226131750984d163c1054d17fa9456c8 --- /dev/null +++ b/handbook/handbook-main/roles/head_of_service_line.txt @@ -0,0 +1,70 @@ +# Head of Service Line + +Our Heads of Service Line are responsible for building world class professional services practices and developing demand for a set of propositions and capabilities within a particular functional expertise such as user-centred design, product, software engineering, data, cyber security, and more. + +## Outcomes + +Heads of Service Lines share a common set of outcomes and KPIs that work towards our organisational purpose, vision and missions. To be successful they must work as one team with Industry Practices, the Delivery Management Organisation and Business Services. They should: + +- generate public sector demand for a set of capabilities +- help make sure there’s high growth of revenue and headcount +- maximise utilisation and make the most of bench time by using it to invest in career development, training, and sales +- maximise retention by building a strong practice identity and clearly defining career pathways +- balance retention and profitability to grow a healthy delivery organisation while minimising costs + +## Responsibilities + +A Head of Service Line is responsible for delivering the above outcomes by collaborating with the business. They report to the Executive Director for Delivery and Capabilities who is their line manager and representative in the Executive Committee. + +### Strategy and management + +- Influence policy and strategy on behalf of the Capability Practice +- Contribute to annual/quarterly planning and be responsible for the delivery of goals +- Support integration and collaboration of the Delivery Management Organisation and Capability Practices with each other and the wider organisation + +### Demand Generation + +- Develop and maintain capability and industry-specific go-to-markets and propositions +- Work closely with industries to meet growth targets +- Provide bid support, quality assurance, and sponsorship + +### Hiring and careers + +- Scale supply of capability team ahead of demand +- Management of capability team including performance, progression, career paths and succession planning +- Maintain high levels of motivation and retention in the capability team + +### Community and thought leadership + +- Continuously improve service delivery and ways of working based on past successes and failures +- Foster thriving community of practice and shared identity +- Consistently deliver thought leadership content and work with marketing to promote and drive growth +- Encourage cross-community and multi-disciplinary collaboration + +## Competencies + +- Articulation and role modelling of values, purpose, and vision +- Strategic thinking and planning +- Commercial awareness +- Time management including balancing multiple priorities +- Performance management of direct and indirect reports +- Prioritise diversity and inclusion in goals and day-to-day activity +- Inspiring leadership and good communication +- Trust building with your seniors, peers, and juniors +- Continuous improvement and feedback + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for a Head of Service Line role, you can see details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_bid_manager.txt b/handbook/handbook-main/roles/lead_bid_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..956942ff7ed918d41633f1ed759e4c195bb2543c --- /dev/null +++ b/handbook/handbook-main/roles/lead_bid_manager.txt @@ -0,0 +1,68 @@ +# Lead Bid Manager + +Reporting to the Head of Bids and Frameworks, you will lead the bid process from early presales to proposal submission and then signature. As the COO of your bids, you will direct and inspire your team to produce winning responses. You will have a strong understanding of public sector procurement, DDaT principles, market trends and competitor activity to feed into the wider bid strategy. + +We believe this is an exciting opportunity to work in one of our industry’s most critical and complex functions. The successful applicant will be a subject expert and recognised leader within that team. + +## Summary + +Made Tech want to positively impact the future of the country by using technology to improve society, for everyone. We believe being design and product-led can create positive outcomes in the public sector through critical services enabled by technology. We have been through a period of significant growth and are looking to expand to accommodate our future pipeline. That is where you come in. + +## Responsibilities + +* Work closely with our Client Partners, forming a bid leadership team to drive opportunities forward. +* Influence and collaborate with Made Tech’s wider leadership team to ensure bids align with our ethos, strengths and customer insight. +* Be accountable for Building, directing and managing the matrixed teams that support individual responses. +* Take ownership of planning activity and building timelines for the bid, holding team members to account for their input. +* Direct, coach and support the team on the job, to help them produce the best output and set a standard for quality. +* Be financially and commercially literate and able to guide and influence those components of the bid. +* Write well yourself and provide best practice writing guidance and correction for your team +* Be accountable for larger opportunities with minimal supervision and direction. +* Apply knowledge of services and technical offering to shaping bids and proposals +* Take learning from retrospectives and use them to improve our biding practices + +## Skills + +### Skills you must have + +* A minimum of 5 years experience working primarily in UK public sector technology. +* A strong understanding of agile methodologies and digital transformation, including user-centred design principles. +* Excellent communication and interpersonal skills, with a strong ability to influence and enable collaboration across functions and a strength in creative writing with an eye for detail. +* An ability to roll your sleeves up and be the person to take ownership. +* Empathy and the ability to build relationships quickly across teams and across the organisation. +* At a conceptual level, understand our technical offering (DDaT). +* A proven track record of winning large-scale government contracts +* An understanding of social value initiatives and an ability to create and articulate them. + +### Desirable (not essential) skills +* Demonstrable skills and evidence of design work in Google Suite and an appetite for leveraging technology to drive efficiency +* Experience specifically in B2B technology services or business process outsourcing + +## Behaviours + +* **Client Focus** - a need to put the most compelling offer possible in front of the client +* **Drive to Deliver** - able to take ownership of the response, pushing it through the business within the timeframes we have been given +* **Learning and Mentoring** - an appetite to grow and learn while passing on your own experience to your teams and colleagues +* Actively seeking feedback on both self, team and systems and processes regularly. Demonstrate positive response to feedback with course correction +* **One team** - contributing to the ongoing improvement of the function at Made Tech, sharing experiences and successes as well as learning points + +## Key measures + +* Win rate +* Revenue versus spend +* Bid team and stakeholder feedback +* Response quality +* Client, peer, and partner feedback + +## Salary, work perks and benefits + +* Location: Any UK Made Tech Office Hub (Bristol, London, Manchester and Swansea) +* Hybrid-working +* Salary: We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! + diff --git a/handbook/handbook-main/roles/lead_business_analyst.txt b/handbook/handbook-main/roles/lead_business_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..ed0660434e9f32dbb0c3ef627eaccce4dc4b8cf3 --- /dev/null +++ b/handbook/handbook-main/roles/lead_business_analyst.txt @@ -0,0 +1,72 @@ +# Lead Business Analyst + +Lead Business Analysts help teams deliver products and services that bring value to their users through: +Identifying business problems and opportunities +Conducting research to understand the public sector domain, people, organisation, processes and technology +Explore, elicit and analyse business and user needs +Identify areas for improvement and explore feasibility of options +Understand any business and policy constraints that need to be considered, and assess the implications + + +# Key responsibilities + +## Scope + +A lead business analyst has a good understanding at an enterprise/strategic level of an organisation and works in highly complex problem spaces, typically spanning multiple products or services. + +At this role level, you will: +- Take responsibility for investigative work to determine business requirements and specify effective business processes, through improvements in information systems, information management, practices, procedures, and organisation change. +- Select, adopt and adapt appropriate business analysis methods, tools and techniques; selecting appropriately from predictive (plan-driven) approaches or adaptive (iterative/agile) approaches. +- Collaborate with stakeholders at all levels, in the conduct of investigations for strategy studies, business requirements specifications and feasibility studies. +- Prepare business cases which define potential benefits, options for achieving these benefits through development of new or changed processes, and associated business risks. + +## Competencies + +Lead Business Analysts display [Made Tech’s values](https://github.com/madetech/handbook/blob/main/company/about.md), relevant [DDaT capabilities](https://www.gov.uk/guidance/business-analyst--2#:~:text=Skill%20level%3A%20practitioner-,Lead%20business%20analyst,system%20in%20a%20project%20or%20programme%20of%20work.%20(Skill%20level%3A%20practitioner),-Head%20of%20business) and [SFIA (Level 5)](https://sfia-online.org/en/sfia-8/responsibilities/level-5) behaviours. + +## Skills needed for this role + +Applies the following practices as a Lead Business Analyst, within an engagement: + +- Agile working, coach and lead teams in Agile and Lean practices, determine the right approach for the team, and think of new ways to achieve the right outcomes. +- Business analysis: Set the direction for business analysis, guide decision making, influence strategic plans, and ensure solutions align with organisational vision. +- Business modelling, set the direction of scope and methodology for representing complex situations, and document conceptual models to support strategic planning. +- Business process improvement, identify opportunities to perform activities in alternative ways, lead exploration of process efficiency improvements, and oversee implementation. +- Business process testing, direct the application of business analysis skills to support design, execution, and assessment of business process tests and usability evaluations. +- Consultancy (business analysis), provide advice, guidance and recommendations, propose methodologies and approaches to implementation, frame problems, and troubleshoot as needed. +- Enterprise and business architecture (business analyst), translate business drivers into objectives, define required capabilities, and support organisational changes to meet business objectives. +- Methods and tools, set direction, assess effectiveness of approaches, recommend tools for organisational collaboration and build capability. +- Requirements definition and management, direct approach to requirements management, influence prioritisation of complex requirement sets, and ensure solutions align with organisational vision. +- Stakeholder relationship management (business analysis), develop engagement strategies, lead communication with stakeholders, and act as point of consultation and escalation to resolve conflict. +- Systems analysis, set direction for identification and analysis of IT system capabilities, identify gaps in functionality, and bring business and technical concepts together to form recommendations. +- Testing (business analysis), recommend value of testing, advise on business scenarios, and develop acceptance criteria to ensure requirements can be traced to develop functionality. +- User experience analysis, advise on approach to analysis, prioritisation, and validation of user experience needs, recommend techniques, and articulate how they affect system design. + + +## Community of Practice (CoP) +Engages and participates within the Made Tech and client communities of practice to: + +- build an inclusive and supportive culture +- recognise when to ask for further guidance and support and identify how to improve how we work, for example, by discussing and sharing approaches, ideas and examples of practice +- direct work within the community of practice, ensuring strategic objectives are achieved +- mentor and coach others within the community, acting as a thought leader, to support their development and practice +- advance product-led thinking internally and externally + +## Work perks and benefits +Take a look at the [Benefits & Perks](https://github.com/madetech/handbook/blob/350005eb3769ef05338461af6413e4553aee54b2/benefits/made_tech_benefits_box.md) section to see what we can offer you. + +## Sales +Collaborates with Principal Business Analysts to ensure that engagements are effective, efficient and profitable, and identify avenues of potential work through highlighting opportunities + +## Key measures +- Delivery of good public services for users with clients, shown through relevant measures, for example. data, metrics, KPIs or the passing of service standards +- Personal performance aligned with DDaT and SFIA grade, evidenced through peer feedback + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_content_designer.txt b/handbook/handbook-main/roles/lead_content_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..810b503992d6176da233ac1b0bf5211067715f57 --- /dev/null +++ b/handbook/handbook-main/roles/lead_content_designer.txt @@ -0,0 +1,72 @@ +# Lead Content Designer + +* Location: mainly remote with occasional office and client visits +* Offices: London, Bristol, Manchester, and Swansea +* Salary: Please refer to the add when the job is live +* SFIA: Level 5 + + +## Summary + +Made Tech wants to positively impact the future of the country by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We are building a community of designers and researchers to support the public sector growing demand for a design-led approach to service delivery. + +Lead Content Designers are expert practitioners who influence and mentor others. They work with teams and clients to design and deliver public services. They do this by setting the direction, assuring the quality of content delivery across teams, and leading multiple or highly complex services. They have an essential role in creating a healthy User-Centred design (UCD) community and culture at Made Tech. + +## Key responsibilities + +### Scope + +- Responsible to the UCD Principal for success of designing and delivering good public services +- Oversees multiple products, concerned about consistency +- Hands-on content design and design leadership for products and teams +- Acts as the content design subject matter expert, facilitating the design process and communicating design decisions to teams and stakeholders +- Takes an active role in the User Centred communities, leading on developing good practice +- Work happens completely autonomously without regular need for review +- Concerned about retention, hiring, and team quality +- Mentors and coaches within the content design community and line manages designers + +### Practice + +- Turn team conversations and research into user-centred content to create a shared understanding of problems to solve and ideas to test +- Make things real, by caring about content enough to ensure everyone can use public services +- Make public services simple to explain and understand, by removing complexity and keeping designs focused on creating outcomes for people and society + +### Leading teams + +- Assure the quality of content delivery within your team +- Show teams by doing, good habits for sharing and improving content + +### Community + +- Line management of content designers +- Support the hiring and onboarding of content designers +- Help define Made Tech design principles through delivering good public services +- Help establish a design studio culture at Made Tech and client offices +- Represent user-centred design publicly and internally + +### Client and sales + +- Build relationships with clients, earning their trust and understanding their needs +- Support the sales team to win new work and review bids relating to UCD + +## Key measures + +- Delivery of good public services for users with clients +- Case studies of how to design and deliver good public services and outcomes +- Growth and happiness of UCD community at Made Tech + +## Competencies + +- Client Focus +- Drive to Deliver +- Learning and Mentoring +- Experienced in their Profession +- Facilitation +- Thinking through Making + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_data_engineer.txt b/handbook/handbook-main/roles/lead_data_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..239871571475eb2d458955740f37c2b071d03a42 --- /dev/null +++ b/handbook/handbook-main/roles/lead_data_engineer.txt @@ -0,0 +1,58 @@ +# Lead Data Engineer + +Our Lead Data Engineers enable public sector organisations to embrace a data-supported approach by providing data platforms and services that are high-quality, cost-efficient, and tailored to our clients' needs. They manage teams to develop, operate, and maintain these services. They make sure they’re providing maximum value to data consumers, including analysts, scientists, and business stakeholders. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are secure, user-centric, data-driven and freed from legacy technology. A key component of this is developing modern data systems and platforms that drive informed decision-making for our clients. You will also work closely with clients to help shape their data strategy. + +You may play one or more roles according to our clients' needs. Sometimes the role is very hands-on and you'll both manage the team and contribute to a project, delivering engineering work including code as well as upskilling members of the client team. At other points, you might play more of a technical architect role, making sure that the wider context of a delivery is considered and maintaining alignment between the operational and analytical aspects of the engineering solution. + +As a senior member of the data capability within Made Tech, you will also be responsible for our hiring and continued development of the team, as well as representing us both internally to the organisation and publicly via presentations. At times, you will participate in the bid process of winning new contracts as a technical representative for the capability, using your data expertise to demonstrate the value that we can deliver. You will also line-manage members of the team up to a senior level. + +You’ll need to have a drive to deliver outcomes for users and have a desire to mentor teams. You will need to be comfortable sharing your knowledge and skills with others. We'd love to hear some examples of times you’ve mentored, coached, and contributed to the growth of team members. Maybe you’ve written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + +## What skills and experience are we looking for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +- Working directly with customers and users +- Strong understanding of the possible architectures involved in modern data system design (e.g. warehouses, lakes and meshes) +- Designing and implementing efficient data transformation processes at scale, both in batch and streaming use cases +- Owning the cloud infrastructure underpinning data systems through a DevOps approach +- Agile practices such as Scrum, XP, and/or Kanban +- Showcasing and presentation skills +- Evidence of self-development – we value keen learners +- Empathy and people skills + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working at a technology consultancy +- Pair programming +- Working with data scientists to productionise advanced data deliverables, such as machine learning models +- Infrastructure-as-Code (e.g. Terraform, Cloud Formation) +- Working knowledge of statistics +- Working within bid teams to win contracts exceeding value of £1m +- Working with multidisciplinary digital and technology teams +- Working within the public sector +- Experience in hiring, forming and running teams + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +The salary for this role is location-dependent: + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_delivery_manager.txt b/handbook/handbook-main/roles/lead_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..d5150cc5b3b6105be0371209eb1695d79bcbc303 --- /dev/null +++ b/handbook/handbook-main/roles/lead_delivery_manager.txt @@ -0,0 +1,120 @@ +# Lead Delivery Manager + +Successfully leading complex digital projects to make sure that our clients have great experiences and achieve brilliant outcomes, and our teams deliver to their full potential. + +## Your role at Made Tech + +Lead Delivery Managers are accountable for successful project delivery in a complex environment. This might mean a small, but complex delivery involving a lot of consultancy such as a policy focused discovery, a larger delivery programme with several delivery teams, or multiple small, less complex engagements. + +You will work as part of a cross-functional delivery team, which might include client stakeholders and partner agencies. You will personify servant leadership, promoting a collaborative approach to ensure projects deliver the desired outcomes for users and customers, working together to identify and manage risks and issues that arise. Depending on the size of the account you are working on, you may be the most senior line of project escalation - or you may work closely with a delivery principal as part of a wider programme. + +While you are an expert in agile delivery, you are also pragmatic and understand that other delivery approaches may be more appropriate for a specific situation when working in consultancy and the public sector. Therefore, you will define the delivery approach and team shape collectively with the team and client stakeholders. You will inspire trust with senior stakeholders, and guide and coach clients throughout the delivery process, using your influence to continuously iterate and approve team processes. You will be able to support product managers with defining and delivering against a roadmap, in order to monitor whether the project is on track and facilitate conversations about backlog priority, scope, and budget. + +As a delivery leader, you will contribute to Made Tech beyond the scope of your delivery. This will include participating in and contributing to the Delivery Community of Practice (COP), managing the performance and development of a number of delivery managers and supporting recruitment activities. You should also start to contribute to growing Made Tech’s impact, for example through maintaining and growing your professional network, contributing to thought leadership, content and events, identifying sales opportunities within the account you are working on, or taking part in the sales bid process. + + +## Definition of success + +Success as a Lead Delivery Manager is predominantly measured by delivering successful outcomes for our clients. It’s also assessed through contribution to Made Tech, and effective line management and coaching relationships. + +### Expected outcomes +* Effective quality and risk management +* Accountable for ensuring accurate and timely adherence to all critical business processes within the delivery +* Balance client satisfaction and team happiness with Made Tech’s commercial goals +* Contribute to growing Made Tech’s impact +* Contribute to the Delivery Community of Practice +* Accelerate the career of other Delivery Managers through line management, coaching and mentoring, and knowledge sharing + +### KPIs +* Quality +* Risk +* Project Gross Profit Margin (GPM) +* Forecast accuracy +* Invoice accuracy + +## Responsibilities + +Lead Delivery Managers are responsible for delivering the above outcomes by collaborating with other members of the Delivery Management Organisation, their Account Management Team, team members, client stakeholders and internal business partners e.g. scheduling, hiring. + +### Project Level Delivery Assurance +* Accountable for ensuring delivery success, including scope, budget and quality +* Report to Heads of Delivery on a weekly basis the status of quality and risk +* Manage team resourcing to balance successful client delivery, team happiness and Made Tech commercial objectives +* Ensure compliance and accuracy of all critical business processes (time sheeting, invoicing, forecasting, delivery assurance reporting) +* Ensure commercial activities (Statements of Work, purchase order numbers, supplier contracts for partners, IR35 assessments for contractors, raising staffing demands) + +### Hiring and Careers +* Support hiring activities including interviewing and outreach +* Management of Senior Delivery Managers including performance, progression and satisfaction +* Ensure regular feedback (constructive and/or appreciative) is shared with all individuals working on projects you are accountable for + +### Growing Made Tech’s Impact +* Support bids, using your knowledge and experience to review and contribute to bids +* Ensure your clients are motivated to bring repeat business and recommend our services to others +* Identify opportunities for Made Tech to deliver value for the client beyond the current project +* Build relationships with stakeholders within your project, and engage with other experts in the organisation for example at the client Community of Practice +* Promote Made Tech and develop your personal reputation in the industry by producing thought leadership content, expanding your personal network and attending events + +### Community and Thought Leadership +* Share successes and failures with the Delivery Community to support the evolution of ways of working, techniques, and technologies across Made Tech +* Contribute to a set of centralised resources and templates for potential reuse +* Contribute to developing a thriving community of practice and shared identity + +## Competencies and behaviours +Lead Delivery Managers are expected to be operating at, or working towards, [SFIA level 5](https://sfia-online.org/en/sfia-8/responsibilities/level-5) in all five competencies. In addition to this, the below list describes specific competencies and behaviours that you’ll need in this role. + +We don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these competencies on your way to promotion. + +### Articulation and role modelling of Made Tech values, purpose, and vision +* Describe each with examples +* Demonstrate role modelling + +### Commercial awareness +* Articulate project commercial fundamentals (Statements of Work, Purchase Orders, Gross Profit Margin, Forecasting, Burndown) +* Display accountability for managing commercial activities within deliveries +* Be able to demonstrate that the team is on track to meet the deliverables defined in the SOW +* Be able to recall and describe key Made Tech case studies, including where you were not directly involved in the project + +### Time management including balancing multiple priorities +* Demonstrate prioritisation, and consistent delivery of multiple goals simultaneously + +### Performance management of direct and indirect reports +* Demonstrate fast remediation of performance issues, including highlighting issues to the Head of Delivery and requesting support where necessary +* Demonstrate encouragement and mentoring of high performers, to support them towards successful promotions +* Maintain compliance with all expectations of line management at Made Tech +* Demonstrate providing regular feedback for team members + +### Effectively manage delivery risk and quality +* Demonstrate planning of and implementation of risk management activities including identification, assessment, mitigation, assessment and reporting to key stakeholders +* Demonstrate activities to ensure that delivery teams have appropriate practices in place to define and meet required quality levels +* Articulate approach to managing budget and burndown within the project, being able show how this is being managed + +### Coach teams to successfully deliver projects +* Articulate the benefits and use cases of a wide variety of delivery approaches, methods and tools - for example Kanban, Scrum, Scaled Agile, Waterfall, XP and Design Sprints +* Describe the fundamentals of best practices in other capabilities, including Security, DevOps, User Centred Design and Data Ethics +* Be able to explain the GDS service standard and how to meet each point, the purpose of each phase of the GDS Service Manual and the Roles and Responsibilities of all of the DDAT roles that make up a Service Team +* Be able to describe and advocate for the Made Tech propositions +* Demonstrate advocacy of best practice delivery with teams and clients + +### Deliver consultancy to clients as part of a formal or informal arrangement +* Demonstrate experience of designing and running workshops with client stakeholders, including post-workshop feedback + +### Trust building with your seniors, peers, juniors and client stakeholders +* Demonstrate with feedback from seniors, peers, juniors and client stakeholders + +### Continuous improvement and feedback +* Demonstrate positive response to feedback with course correction + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_designer.txt b/handbook/handbook-main/roles/lead_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..9ca7fb35cd4a4135b24aec02496ac4fe31ff0e75 --- /dev/null +++ b/handbook/handbook-main/roles/lead_designer.txt @@ -0,0 +1,108 @@ +# Lead Designer + +- Location: mainly remote with occasional office and client visits +- Offices: Bristol, London, Manchester, and Swansea +- Salary: Please refer to the job advert when the role is live +Note: Any new joiners will be offered a salary in the bottom third of this range +- SFIA: Level 5 + +Lead Designers at Made Tech are specialists in their design discipline(s). In this case, we’re looking for an expert practitioner in Interaction and Service Design who is able to coach, mentor and lead other designers within the Interaction and Service Design discipline at Made Tech. Success in this role means guiding the work of other designers within the Interaction and Service Design discipline to deliver positive outcomes. + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +Lead Designers at Made Tech are… + +**Expert practitioners** +* Able to develop new and novel approaches to highly complex design challenges, based on fundamental interaction and service design principles. +* Act as a leader and advocate for the Interaction and Service Design practice internally and externally. Able to coach and mentor others, and define the interaction and service design standards which others will apply. Influences the organisation, clients, partners and peers on the contribution of interaction and service design. +* Develop a wide breadth of knowledge across the industry or business. + +**Take the initiative and are fully responsible for their own outcomes** +* Work is often self-initiated. Able to define an approach from first principles, and propose alternative ways to deliver. +* Fully responsible for meeting objectives on an engagement. + +**Responsible for overall interaction and service design outcomes of engagements** +* Understand the relationship between interaction and service design, other disciplines, and wider client organisational requirements. +* Defines what ‘good’ interaction and service design looks like on an engagement, enabling and holding others to account for producing high quality outputs and deliverables +* Establish milestones and have a significant role in the assignment of tasks and/or responsibilities. Makes decisions which impact the success of assigned work, i.e. results, deadlines and budget. +* Lead on user and client collaboration throughout all stages of work. Ensures users’ needs are met consistently through each work stage. + +**Highly accountable** +* Comfortable with owning a problem and are committed to seeing it through to resolution +* Actively look to deliver a positive outcome, even if they can’t personally do it + +**Have a growth mindset** +* Always willing to learn and develop + +**Candid-but-kind communicators** +* Give feedback often +* Understand that a balance of positive and constructive feedback is the most effective way to work +* Comfortable having difficult conversations + + +## Key responsibilities + +## Scope + +* Responsible to the Head of Interaction and Service Design or a UCD Principal +* Hands-on design and design leadership for products and teams to assure the successful design and delivery of public services through technology. +* Acts as an interaction-and-service-design subject matter expert, facilitating the design process and communicating design decisions to teams and setting expectations with stakeholders. +* Takes an active role in the Service and Interaction Design community, leading on, developing, and sharing good practice. +* Influencing team shapes to balance profit, utilisation and client needs at all stages of delivery (Bid stage, project initiation, with ongoing regular review) and iteration) +* Actively supports retention, hiring, and team quality +* Mentoring and coaching within the design community and line management of other designers + +## Practice + +* Create a shared understanding of problems to solve and ideas to test +* Make things real through storytelling and uncovering the ‘why’ +* Caring about design enough to make sure everyone can use public services +* Make use of the Made Tech playbooks where they exist and support their development +* Make public services simple to explain, understand, and use by removing unnecessary complexity and keeping designs focused on creating positive outcomes for people and society. + +## Leading teams + +* Assure the quality of design delivery across multiple teams. +* Raise and manage delivery risks to prevent them becoming issues using clear mitigation and management plans +* Introduce good habits for sharing and improving design work into teams. + +## Community + +* Line management of designers +* Support the hiring and onboarding of designers (contract and permanent) +* Help define Made Tech design principles through delivering effective public services +* Represent and advocate for user-centred design publicly and internally + +## Sales + +* Build relationships with clients, earning their trust and understanding their needs +* Support the sales team to win new work by contributing and reviewing bids relating to UCD +* Contribute to marketing materials (blogs, case studies, talks). + +## Key measures + +* Case studies of how to design and deliver good public services and outcomes +* Contributing to the growth and happiness of the UCD community at Made Tech +* Deliver your project objectives on time and to the expected standard +* Display the Made Tech values and behaviours reflected in feedback from colleagues and clients +* Ensure your team members (direct reports and account team members) feel fully supported and engaged - provision of regular 1:1s, an effective cascade of information and progression of development plans. + +## Competencies + +* Client Focus - a need to put the most compelling offer possible in front of the client +* Drive to Deliver - able to take ownership of the response, pushing it through the business inside the timeframes that we have been given. +* Learning and Mentoring - an appetite to grow fast and learn while passing on your own experience to your teams and colleagues +* One team - contributing to the ongoing improvement of the function at Made Tech, sharing experiences and successes as well as learning points. + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_product_manager.txt b/handbook/handbook-main/roles/lead_product_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..73f28ce0961a876f3f5c70cf9c490d33dc7ad72f --- /dev/null +++ b/handbook/handbook-main/roles/lead_product_manager.txt @@ -0,0 +1,60 @@ +# Lead Product Manager + +Reporting to the Discipline Head of Product Management, Business Analysis and Innovation, our Lead Product Manager role is responsible for leading on product across multiple client assignments. + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design and product-led can create positive outcomes in the public sector through critical services enabled by technology. We are building a community of designers, researchers and product professionals to support the public sector's growing demand for a user-centred, design and product led approach to how services are delivered. +As a Lead Product Manager, reporting to the Discipline Head, you’ll enable public sector organisations to better design services that improve society. You will be expected to role model and lead teams with best practice in product management. + +You will work as part of cross-functional teams which might include other Made Tech team members, stakeholders and partner agencies. You will inspire trust in the team, guide and coach teams through the product process and use your influence to continuously iterate and improve ways of working and processes. + +## Responsibilities + +* You will be expected to work in a self initiated manner, modelling leadership in a collaborative and inclusive manner +* Collaborate and influence the wider Made Tech team and our clients to deliver high quality work aligned with our customers vision and needs +* Influence decision making which impacts success. This might include scoping work, prioritisation, deadlines, budgets and evaluating risk +* Work across more than one assignment for a client at one time +* Coach, support and people manage other members of the Product Management team. To steer them and their teams towards successful delivery for our clients, enabling them and holding them accountable for producing high quality outputs and deliverables +* Maintain a broad technical knowledge of product management, user-centred design and technical practices, be able to shape strategy, proposals, statements of work and roadmaps +* Be a leader in and heavily contribute to Made Tech’s community of practice for Product and contribute to other disciplines +* Assist in developing and growing the discipline and user-centred practice in line with business needs, hiring and line managing product managers, developing the capability, propositions and playbooks to create a uniquely Made Tech way of embedding design and product-led thinking into all that we do + +### Skills people must have + +* Experience in helping grow product teams though community, hiring and line management +* Excellent understanding and passionate articulation of the value of product and user-centred design +* Experience and evidence of delivering user centred products and services from ideation through to maintenance phases +* Experience of assisting to develop product communities of practice as a leader or leading member of a high-performing practice +* Ability to support and coach others to grow their skills, product capabilities and to take on more responsibility for client-facing projects +* Able to educate and mentor team members, colleagues and peers in the wider business on developing product and agile delivery as a core discipline +* Experienced in working directly with customers and users, and able to drive teams to deliver excellent outcomes for users +* Working within a design consultancy/senior product leadership role in the public sector, health or allied areas +* Strong empathy and relationship building skills + +At this point, we hope you're feeling excited about Made Tech and the opportunity. Even if you don't feel that you meet every single skill, we still encourage you to apply. Get in touch with our talent team if you’d like an informal chat about the role and your suitability before applying. + +### Desirable (not essential) skills + +* Working with sales teams to build client relationships, develop opportunities and win new work +* Working in the open - building the trust within teams to share little and often +* Experience in re-designing legacy services and products +* Maintaining a deep working knowledge of product,design and research techniques +* Experience in people management + + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We work in a hybrid manner with on-site requirements for in-person presence when considered most beneficial for the activity (team meetings, workshops, onboarding for example). You may also need to visit clients where on-site requirements are necessary and/or beneficial. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_security_engineer.txt b/handbook/handbook-main/roles/lead_security_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..50712b1cfa3bc6322df7cb18c366334eaa83fcf9 --- /dev/null +++ b/handbook/handbook-main/roles/lead_security_engineer.txt @@ -0,0 +1,61 @@ +# Lead Security Engineer + +Our Lead Security Engineers enable public sector organisations to mitigate cyber and information security risks across an increasingly complex and threatened mix of technology-enabled services. They lead teams to make sure digital and data services are securely designed and built from the outset, and work with technology teams to make sure entire platforms are securely monitored with timely incident response. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. Underpinning this is a need for us to do this securely, handling public data safely, and defending against increasing cyber and information security risks. + +As a Lead Security Engineer you will work closely with clients to help inform their security strategy and to ensure our teams are delivering secure digital services and cloud-based platforms, aligned to our customers risk tolerance. You’ll need to have a drive to deliver outcomes for users. You’ll be expected to upskill clients and Made Tech delivery teams, including pair programming with other engineers. + +You will need to be comfortable sharing your knowledge and skills with others. We’d love to hear some examples of mentoring, coaching and growing team members. Maybe you will have written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + + +## What skills and experience are we looking for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +* Working directly with clients +* Leading cyber engineering workstreams and embedding into digital, data and technology teams to upskill them while managing risk and compliance +* Shaping cyber and information security strategy and managing continuous risk reduction across multiple digital or data services and cloud-based platforms +* End-to-end security involvement, including governance, risk and compliance, operational security, supply chain security and secure user management +* Identifying security issues in existing system designs, digital services (products) and platforms, including recommending mitigations that balance cost, risk and usability +* Strong understanding of integrating security as part of a multidisciplinary approach to delivering digital services (products) and platforms utilising a DevSecOps approach and enabling Continuous Security as part of wider CI/CD tools and practices +* Up-to-date understanding of, and ensuring compliance to, security standards and regulations including GDS Technology Code of Practice, NCSC Cyber Principles, ISO27001, SoC, NIST, PCI, and GDPR +* Up-to-date understanding of testing the security of software and infrastructure using appropriate security tools including automated cloud-based tooling +* Up-to-date understanding of network security (e.g. OSI, TCP/IP), web application security (e.g. OWASP) and cryptographic controls (e.g. PKI, TLS) +* Up-to-date understanding of identity management and authentication/authorisation products and patterns +* Evidence of self-development – we value keen learners +* Empathy and people skills + + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +* Working at a technology consultancy +* Pair programming +* A relevant cyber and information security qualification (one of: CISSP, SSCP, CISM, CRISC, CAP, CPP, GCHQ-certified * Master’s degree in cyber security, or a PhD that is relevant to cyber security) +* Penetration testing qualifications (one of: OSCP, CREST, TIGER or equivalent) +* Working within bid teams to win contracts exceeding value of £1m +* Working with multidisciplinary digital and technology teams +* Working within the public sector +* Hiring, forming and running teams + + + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_software_engineer.txt b/handbook/handbook-main/roles/lead_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..2e5ffefd6be7c24485a2a2042014997925d43e7e --- /dev/null +++ b/handbook/handbook-main/roles/lead_software_engineer.txt @@ -0,0 +1,71 @@ +# Lead Software Engineer + +Our Lead Software Engineers work with organisations to deliver digital, data and technology outcomes that improve society. They do this by establishing and managing teams to deliver software in public sector organisations. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country. We help public sector organisations deliver quality software to help citizens get more from public services. We work alongside brilliant public servants to modernise technology and accelerate digital delivery. + +You will combine technical excellence, drive to deliver, and coaching to achieve better outcomes for our clients and their users, and establish strong engineering cultures within organisations. You’ll work on a variety of different problems, including monoliths, microservices, and upskilling colleagues and clients. + +Depending on our clients' needs you may play one or more roles. Sometimes the role is very hands-on and you'll be the most senior engineer on the team delivering software. Other times you’ll be more of a technical architect in one or more teams. + +You will need to be a person who enjoys a varied workload, is happy to switch between being more and less hands-on, but don't see yourself stepping away from code any time soon. It might be that you're stronger as a tech lead or a tech architect, or only have experience in one area. That's okay as long as you have an interest and willingness to broaden your expertise. + +You will have the opportunity to work across a variety of technologies and will need to be comfortable doing so. Our teams have used Ruby with Rails and Sinatra, ES6 with React and Angular, C# with .NET Core, Java with Spring, Python with Django, and plenty more stacks. We don’t limit ourselves to particular technologies and we expect all of our engineers to be keen on learning new skills. + +High-performing software delivery teams need to be empowered to iteratively and rapidly deliver changes all the way through to production. To do this we combine our extensive cloud automation knowledge with DevOps culture. + +We've been using AWS from the start and as Advanced Partners are go-to experts within the public sector. We use a range of IaaS, PaaS and FaaS depending on the needs of our users, in this case software teams, such as EC2, Lambda, ECS, Kubernetes, Heroku, CloudFoundry, Azure App Services, and more. We use VPC and PrivateLink for connecting to on-premise, legacy systems. We also use API Gateway, S3, CloudFront, SQS, SNS, SES, RDS, and many other services provided by AWS. You will have the opportunity to use and learn these technologies. We also offer official AWS and other cloud training. + +We make sure we document our architecture and infrastructure as code, using technologies such as Terraform and OpenAPI. Containerisation is a big part of empowering our teams to develop, deploy and scale their applications, as is using AWS Lambda and avoiding the complexity of stateful services altogether. + +For us, DevOps is about culture rather than roles and titles. Even though this role is for someone with strong DevOps experience, the biggest impact you will have is in coaching and helping teams use the platforms you build. You won't be building infrastructure in isolation or tasked with deploying other people’s work into production. You'll empower teams with the mantra “you build it, you run it”! + +We have a team of polyglot programmers (which you might already consider yourself to be), who are versed in a mix of paradigms such as object-oriented, functional, declarative, event-based and aspect-oriented. You will need to be comfortable sharing your knowledge and skills with others. We’d love to hear some examples of times you’ve mentored, coached, and contributed to the growth of team members. Maybe you’ve written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + +## What skills and experience do we look for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +- Working directly with clients and users +- Working within multidisciplinary teams with product, design, and technology working within the same cycles +- Agile practices such as Scrum, XP, and/or Kanban +- Showcasing and presentation skills +- Writing code with test-driven development +- Working with many programming languages +- Working with many databases +- Working with APIs +- Working with a cloud platform such as AWS, GCP and/or Azure +- Influencing architecture and teams +- Debugging experience in a range of systems +- Evidence of self-development – we value keen learners +- Empathy and people skills + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working at a technology consultancy +- Pair programming +- Component-based design techniques such as using pattern libraries, styled-components, CSS-in-JS, BEM, and/or SUIT CSS +- Debugging infrastructure +- The React ecosystem including a test-driven approach +- Infrastructure as code technology like Terraform and Cloud Formation +- Use of architectural decision records +- Writing blog posts and giving talks + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/lead_user_researcher.txt b/handbook/handbook-main/roles/lead_user_researcher.txt new file mode 100644 index 0000000000000000000000000000000000000000..de0250722cf92bea9ebaed8d333698d7595e03b0 --- /dev/null +++ b/handbook/handbook-main/roles/lead_user_researcher.txt @@ -0,0 +1,76 @@ +# Lead User Researcher + +- Location: mainly remote with occasional office and client visits +- Offices: London, Bristol, Manchester, and Swansea +- Salary: please refer to the job ad when it is live +- SFIA: Level 5 + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +Lead User Researchers are expert practitioners who influence and mentor others. They work with teams to deeply understand people’s lives, services, organisations, and outcomes for the public sector. They do this by making sure that teams take a user-centred, evidence-based approach to service design and delivery. They can lead a team to understand a complex policy area and identify the most value in focusing. They have an essential role in creating a healthy User-Centred design (UCD) community and culture at Made Tech. + +## Key responsibilities + +## Scope + +- Responsible to the Head of User-Centred Design for successfully informing the design and delivery of public services +- Oversees multiple products, concerned about consistency +- Hands-on research and research leadership for products and team +- Acts as the research subject matter expert, facilitating the design process and communicating design decisions to teams and setting expectations with stakeholders +- Takes an active role in the user-centred communities, leading on developing good practice +- Work happens completely autonomously without regular need for review +- Concerned about retention, hiring, and team quality +- Mentors and coaches within the research community and line manager researchers + +## Practice + +- Scope focus of research, so everyone involved has a shared understanding of successful outcomes +- Plan research that informs the design of public services that are helpful, usable and successful +- Put research participants at ease, so they're comfortable sharing information +- Analyse and interpret research findings so that teams can confidently confirm or challenge their understandings of problems and ideas + +## Leading teams + +- Involve whole teams in user research to build their understanding and empathy for people using and running public services +- Assure the quality of decisions across multiple teams +- Share research freely and often +- Make decisions based on research findings; model this behaviour to the rest of your team + +## Community + +- Line management of user researchers +- Support the hiring and onboarding of designers and researchers +- Help define Made Tech design principles through delivering good public services +- Help establish a design studio culture at Made Tech and client offices +- Represent user-centred design publicly and internally + +## Client and sales + +- Build relationships with clients, earn their trust and understand their needs +- Support sales team to win new work and review bids relating to UCD + +## Key measures + +- Delivery of good public services for users with clients +- Case studies of how to design and deliver good public services and outcomes +- Growth and happiness of the UCD community at Made Tech + +## Competencies + +- Client focus +- Drive to deliver +- Learning and mentoring +- Experienced in their profession +- Facilitation + +## Work perks and Benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/mid_application_support_engineer.txt b/handbook/handbook-main/roles/mid_application_support_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..4dd376f91979acc91c89fe9ce54f77a379957756 --- /dev/null +++ b/handbook/handbook-main/roles/mid_application_support_engineer.txt @@ -0,0 +1,61 @@ +# Application Support Engineer + +Delivering technical services to support, maintain and improve live services across the public sector. + +As an application support engineer at Made Tech you will work collaboratively within delivery teams transitioning live services without disruption from incumbent suppliers, deliver enhancements and provide ongoing maintenance and BAU support. + +## Role Description + +As an application support engineer at Made Tech you will work collaboratively within Managed Service teams onboarding new services without disruption, deliver enhancements, provide ongoing maintenance and support services, as well as continuously improving both digital services and service operations using DevSecOps practices and data-driven user analytics. + +Operating within a managed service environment, you will maintain a range of digital services, data services, and platform offerings. You will maintain application management procedures and documentation and manage application enhancements through to live operation. + +### Competencies & Experience + +The list below describes specific competencies and behaviours that you’ll need in this role. + +Don’t worry - we don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these competencies as part of your progression in the team. + +* You’ll have experience of common ITSM tooling such as ServiceNow, ZenDesk, PagerDuty and/or JIRA Service Desk +* You’ll have experience of working with agile methodologies and agile ways of working +* You’ll have experience of ITIL methodologies and terminology +* You’ll have experience of tiered and/or swarm models of incident management +* You’ll have experience of cloud technologies such as AWS, Azure or GCP +* You’ll be experienced with at least one programming language and be able to demonstrate knowledge of SOLID principles, Object-Oriented programming and TDD +* You’ll be familiar with IaC (Infrastructure as Code) such as Terraform + +### Responsibilities + +* Taking part in proactive knowledge transfer activities with incumbent suppliers +* Code review and quality analysis including the review of complete services, including the implementation of code scanning tooling +* Reviewing and improving technical documentation such as architecture overviews, deployment process definition and incident resolution runbooks +* Ensuring that all requests for support are dealt with according to a set standards and procedures, and suggesting ways to improve those processes over time +* Participating in incident investigation/root cause analysis and delivering resolutions targeting the root cause within agreed SLAs +* Implementing application enhancements to improve business performance, applying a holistic product lens to services +* Collaborating with technical subject matter experts (SMEs), security operations and user research to ensure user-centred high quality outcomes +* Providing out of hours support where necessary - shifts managed via on-call rota +* Responding to security incidents in alignment with agreed standards and best practice such as NCSC guidance +* Automating the monitoring of application performance including the setting up of cloud and application level monitoring tooling +* Implementing ongoing improvements to monitoring, logging and the continuous review of alerting thresholds +* Providing guidance to users and 1st line support agents — including enhanced levels of support following new/updated software releases +* Updating documentation such as knowledge base articles, playbooks and service definitions +* Implementing processes that maintain application data, backups and ensuing appropriate recovery processes are in place to meet data retention needs +* Implementing application enhancements and ensuring their successful release through automated delivery pipelines +* Estimating time and effort required for software development +* Applying test-driven development, ensuring appropriate test coverage and evidencing the outcomes of testing +* Design, build and maintain CI/CD pipelines including automated testing supporting multiple environments +* Maintaining infrastructure, ensuring compliance, upgrading live services +* Collaborating with other stakeholders e.g. User Centred Design, product management to refine the continuous improvement backlog +* Being an active member of Made Tech’s communities of practice, sharing knowledge and learning from others. + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +## Salary and location + +We adopt a hybrid approach and anticipate that most roles will spend a mixture of time within our offices, client sites and working remotely. We have offices in London, Bristol, Manchester, and Swansea and our clients are across the UK. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. diff --git a/handbook/handbook-main/roles/mid_business_analyst.txt b/handbook/handbook-main/roles/mid_business_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..18868309f913662758030b93abfc0600eeb29188 --- /dev/null +++ b/handbook/handbook-main/roles/mid_business_analyst.txt @@ -0,0 +1,67 @@ +# Business Analyst + +Business Analysts help teams deliver products and services that bring value to their users through: +- **Identifying business problems and opportunities** +- **Conducting research to understand the public sector domain, people, organisation, processes and technology** +- **Explore, elicit and analyse business and user needs** +- **Identify areas for improvement and explore feasibility of options** +- **Understand any business and policy constraints that need to be considered, and assess the implications** + + +# Key responsibilities + +## Scope + +Business analysts can expect to work independently and autonomously and will lead on small to medium size projects and support larger, more complex ones. + +At this role you will: +Investigate operational needs, problems and opportunities +Contribute and assist in producing recommendations of improvements with regards to technologies and processes of the organisation. +Support the design and creation of Acceptance Testing + + +## Competencies + +Business Analysts display Made Tech’s [values](https://github.com/madetech/handbook/blob/main/company/about.md), relevant [DDaT capabilities](https://www.gov.uk/guidance/business-analyst--2#:~:text=Skill%20level%3A%20awareness-,Business%20analyst,data%2Dinformed%20decision%20making%2C%20based%20on%20user%20research.%20(Skill%20level%3A%20working),-Senior%20business%20analyst) and [SFIA (Level 3)](https://sfia-online.org/en/sfia-8/responsibilities/level-3) behaviours. + +## Skills needed for this role + +Applies the following practices as a Business Analyst, within an engagement: + +- Agile working, Identify and compare delivery methods, measure outcomes and adhere to MVPs and priorities. +- Business analysis, Apply structured approaches to identify, investigate, and communicate complex business problems and opportunities. +- Business modelling, Understand potential changes and how business processes, systems, and data interact. +- Business process improvement, Lead the analysis, design, prioritisation, and implementation of process and business changes. +- Business process testing, Support the design, execution, and assessment of business process tests and usability evaluations within a project. +- Methods and tools, Select and use the most appropriate tools and techniques to support the planning, analysis, development, testing, implementation, and improvement of systems and services within a project. +- Requirements definition and management, Coordinate and review the prioritisation of requirements and use appropriate requirements management life cycle methods. +- Stakeholder relationship management, Manage and monitor relationships with and between internal and external stakeholders. +- Systems analysis, Identify and analyse IT system capabilities and develop models and system requirements for bespoke IT systems or software packages. +- Testing, Develop acceptance criteria, review prototypes, test plans and test outcome reporting. +- User experience analysis, Apply techniques to analyse, validate, and prioritise user experience needs and present findings to support data-informed decision-making based on user research. + +## Key measures + +- Delivery of good public services for users with clients, shown through relevant measures, for example, data, metrics, KPIs or the passing of service standards +- Personal performance aligned with DDaT and SFIA grade, evidenced through peer feedback +## Community of Practice (CoP) + +Engages and participates within the Made Tech and client communities of practice to: + +- build an inclusive and supportive culture +- recognise when to ask for further guidance and support and identify how to improve how we work, for example, by discussing and sharing approaches, ideas and examples of good practice + +## Work perks and benefits + +Take a look at the [Benefits & Perks](https://github.com/madetech/handbook/blob/350005eb3769ef05338461af6413e4553aee54b2/benefits/made_tech_benefits_box.md) section to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/mid_content_designer.txt b/handbook/handbook-main/roles/mid_content_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..2d43e8e8c54fa514e1ad245595c36b65d6819c5b --- /dev/null +++ b/handbook/handbook-main/roles/mid_content_designer.txt @@ -0,0 +1,72 @@ +# Content designer + +* Location: hybrid policy with office and client visits +* Offices: London, Bristol, Manchester, and Swansea +* Salary: please refer to the job ad when the role is live + +Made Tech wants to positively impact the country's future by using technology to improve society. We know that putting user needs at the heart of our design approach is the best way of achieving this. We're building an expert community of content designers, interaction designers, service designers and user researchers to work with our public sector clients. +Content Designers work with other design and research specialisms to design services that give users the information they need, in the right format, at a time that works for them. This is a collaborative role that can have a real impact on the success of service delivery. They are active members of a growing user-centred service line (Strategy & Design) at Made Tech. + +## About the role + +A content designer is responsible for creating, evaluating, updating and reviewing content at all stages of the end-to-end user journey. +At this role level, you will: +* work collaboratively in multidisciplinary teams to focus on the needs of the user and create content that meets them +* use evidence and analytics to make content decisions and be able to explain them well +* be confident talking to stakeholders at all levels and able to use your knowledge and expertise to influence decision-making +* have an understanding of the government service standard and how to work to meet its requirements +* contribute to and use style guides and content patterns + +Skills needed for this role level +* Agile working +* Team working +* Content concepts and prototyping +* Stakeholder relationship management +* Strategic thinking +* User focus +* User-centred content design +* Contribute to the culture at Made Tech + +## Practice and craft + +* Experience of working and designing as part of an Agile team +* Experience of designing for different platforms such as web, app and email +* Knowledge of WCAG standards and able to design accessible content +* Able to take complex content and concepts and simplify them +* Able to work with subject matter experts to create clear and accurate content +* Able to design using key guidance including a, design system, style guide and tone of voice +* A working knowledge of design tools including, Figma, Mural and Miro +* Able to contribute to creating a design history. +* Experience of working with researchers to test and iterate content +* An understanding of how to track and measure the effectiveness of content + +## Working in teams + +* Assure the quality of content design delivery within their team +* Introduce good habits for sharing and improving design work +* Able to work with others to interrogate design problems and propose solutions +* Able to articulate ideas and design thinking into presentations and other documents +* Able to present work and ideas confidently when required + +## Key measures + +* Delivery of clear and accessible public services + +## Competencies + +* Client focus +* Drive to deliver +* Learning and mentoring +* Experienced in their profession +* Facilitation +* Thinking through making + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. diff --git a/handbook/handbook-main/roles/mid_data_engineer.txt b/handbook/handbook-main/roles/mid_data_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..8d1df6c869c188bec8442a9a46925e6c7ef7e72f --- /dev/null +++ b/handbook/handbook-main/roles/mid_data_engineer.txt @@ -0,0 +1,55 @@ +# Data Engineer + +Our Data Engineers enable public sector organisations to embrace a data-driven approach by providing data platforms and services that are high-quality, cost-efficient, and tailored to the clients’ needs. They develop, operate, and maintain these services. They make sure they provide maximum value to data consumers, including analysts, scientists, and business stakeholders. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. A key component of this is developing modern data systems and platforms that drive informed decision-making for our clients. + +As a Data Engineer, you'll play a hands-on role as a contributor to client projects, focusing on both delivering engineering work as well as upskilling members of the client team. + +As a member of the data capability within Made Tech, you will also participate in our hiring process and continued development of the team, as well as representing us both internally to the organisation and publicly via presentations. You’ll need to have a drive to deliver outcomes for users and have a desire to mentor teams. + +You will need to be comfortable sharing your knowledge and skills with others. Maybe you’ve written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + +## What skills and experience are we looking for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +- Working directly with clients and users +- Designing and implementing efficient data transformation processes at scale, in either batch or streaming use cases +- Contributing to the cloud infrastructure underpinning data systems through a DevOps approach +- Basic understanding of the possible architectures involved in modern data system design (e.g. warehouses, lakes, and meshes) +- Agile practices such as Scrum, XP, and/or Kanban +- Showcasing and presentation skills +- Evidence of self-development – we value keen learners +- Empathy and people skills + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working at a technology consultancy +- Pair programming +- Working with data scientists to productionise advanced data deliverables, such as machine learning models +- Infrastructure-as-Code (e.g. Terraform, Cloud Formation) +- Working knowledge of statistics +- Working with multidisciplinary digital and technology teams +- Working within the public sector + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! + diff --git a/handbook/handbook-main/roles/mid_delivery_manager.txt b/handbook/handbook-main/roles/mid_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..62d051e5ba2389b5a915dc4d6d0c9fe55c6343a5 --- /dev/null +++ b/handbook/handbook-main/roles/mid_delivery_manager.txt @@ -0,0 +1,116 @@ +# Delivery Manager + +Work as part of a Delivery Team to make sure the team is able to deliver successful projects. + +## What does the job entail? + +Delivery Managers support delivery teams to meet their full potential. This will probably include facilitating scrum ceremonies and monitoring project budget, supporting team admin and managing project risk. You may work with a Lead or Principal Delivery Manager to manage stakeholder relationships, ensure successful delivery outcomes and lead external workshops. + +As a Delivery Manager, you will work on a small or mature agile team and learn on the job. At this level, you may work alongside a more senior delivery manager on a larger team, shadowing and providing support, or working to deliver an element yourself under guidance and mentorship. You will work under general direction and attempt to solve problems with your delivery team, but will seek out and accept guidance where necessary. + +You’ll use cross-functional skills to support your delivery team to deliver successful outcomes to the client. You use empathy and effective listening skills to help the team collaborate. You will use your previous project management experience to identify and manage project dependencies, risks and issues collectively with the team. You use your communication skills to help communicate complex information to technical and non-technical stakeholders, and facilitate discussions within a multidisciplinary team. You will be able to answer most questions that client stakeholders ask, but know who to speak to for more complex issues or queries. + +With support, you will use your excellent attention to detail to ensure the project is delivered within budget, using tools such as Google Sheets to match up the time spent by the team with the amount of work left to complete. + +You are passionate about learning and developing your skill set, and are an active member of the Delivery Community of Practice (COP). You spend time learning from other capabilities (cloud & engineering, user-centred design, product & business analysis) about what good looks like in their areas of expertise. + + +## Definition of success + +Success as a Delivery Manager is predominantly measured by effectively contributing to a team, to support them in delivering successful outcomes for our clients. It is also assessed based on personal development and learning, as you move towards autonomy and being solely accountable for a delivery. + +### Expected outcomes +* Effective quality and risk management +* Enabling a team by identifying and unblocking dependencies +* Accurate and timely adherence to all critical business processes within the delivery +* Contribute to the Delivery Community of Practice +* Contribute to growing Made Tech’s impact +* Becoming autonomous and accountable for a Delivery through personal development, learning, mentorship and shadowing + +### KPIs +* Quality +* Risk +* Timesheet accuracy +* Invoice accuracy +* Learning & development objectives + +## Responsibilities + +Delivery Managers are responsible for delivering the above outcomes by collaborating with other members of their delivery team. + +### Project Level Delivery Assurance +* Ensure delivery success with support, managing scope, budget and quality +* Feed into the status of quality and risk reported to Heads of Delivery on a weekly basis +* Support the Delivery Team by facilitating ceremonies, doing administrative tasks and unblocking dependencies +* Work with the team to identify and manage risks, issues and dependencies, escalating where necessary +* Review and approve timesheets, invoices and Kimble Forecasts, ensuring accuracy at all stages + +### Personal Development +* Ensure regular feedback (constructive and/or appreciative) is shared with all individuals working on your projects +* Regularly gather and act on feedback about personal development +* Define and work towards a learning and development plan to ensure you are able to autonomously manage a project as quickly as possible + +### Growing Made Tech’s Impact +* Ensure your clients are motivated to bring repeat business and recommend our services to others +* Identify opportunities for Made Tech to deliver value for the client beyond the current project +* Build relationships with stakeholders within your project, and engage with other experts in the organisation for example at the client Community of Practice + +### Community and Thought Leadership +* Share successes and failures with the Delivery Community to support the evolution of ways of working, techniques, and technologies across Made Tech +* Contribute to developing a thriving community of practice and shared identity + +## Competencies and behaviours + +Delivery Managers are expected to be operating at, or working towards, [SFIA level 3](https://sfia-online.org/en/sfia-8/responsibilities/level-3) in all five competencies. In addition to this, the below list describes specific competencies and behaviours that you’ll need in this role. + +Don’t worry - we don’t expect you to tick all of these when you join. We'll work together to define learning and development objectives that help you meet these competencies on your way to promotion. + +### Articulation and role modelling of Made Tech values, purpose, and vision +* Describe each with examples +* Demonstrate role modelling + +### Commercial awareness +* Articulate project commercial fundamentals (Statements of Work, Purchase Orders, Gross Profit Margin, Forecasting, Burndown) +* Describe how they are supporting commercial activities within their delivery +* Be able to demonstrate that the team is on track to meet the deliverables defined in the SOW + +### Time management and prioritisation +* Demonstrate prioritisation and time management + +### Effectively manage delivery risk and quality +* Demonstrate working with a team to perform risk management activities including identification, assessment, mitigation, assessment and reporting to key stakeholders, with support as required +* Demonstrate activities to ensure that delivery teams have appropriate practices in place to define and meet required quality levels, with support as required +* Articulate approach to managing budget and burndown within the project, being able show how this is being managed + +### Coach teams to successfully deliver projects +* Articulate the benefits and use cases of a variety of delivery approaches, methods and tools - for example Kanban, Scrum, and Waterfall +* Understand why it’s necessary to collaborate with capability experts (e.g. Lead Engineer / Lead Designer) to ensure deliveries adhere to best practices such as Security, DevOps, User Centred Design and Data Ethics +* Be able to explain the purpose of the GDS phase you are currently working on (Discovery/Alpha/Beta/Live), and where applicable, what to expect in the next phase +* Demonstrate knowledge of where to find and how to use the GDS service standard +* Be able to explain the Roles and Responsibilities of all of the roles on the team you are working on + +### Facilitation and communication +* Demonstrate experience of running ceremonies and facilitating meetings - with post meeting feedback +* Demonstrate experience of presenting information to stakeholders using reports or presentations + +### Trust building with your seniors, peers, juniors and client stakeholders +* Demonstrate with feedback from seniors, peers, juniors and client stakeholders +* Demonstrate moving towards taking ownership for the success of the delivery, through feedback from your Delivery Lead + +### Continuous improvement and feedback +* Demonstrate positive response to feedback with course correction +* Demonstrate providing regular feedback for team members + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! + diff --git a/handbook/handbook-main/roles/mid_designer.txt b/handbook/handbook-main/roles/mid_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..9e436956a139d427c21e06ec55c62b64ae4f4ee5 --- /dev/null +++ b/handbook/handbook-main/roles/mid_designer.txt @@ -0,0 +1,63 @@ +# Designer + +- Location: mainly remote with occasional office and client visits +- Offices: London, Bristol, Manchester, and Swansea +- Salary: £29,750 - £42,500 with a London-weighting of £31,237 - £44,625 +- SFIA: Level 3 + +Designers might already be a Product Designer, UX Designer, Service Designer or Interaction Designer. + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +Designers are experienced practitioners who collaborate with others to tackle challenges faced by people and society. They work within a team to design and deliver public services. They do this by influencing the direction, assuring the quality of design delivery within their team and by leading the end-to-end design of a chosen service. They are active members of a healthy user-centred design (UCD) community and culture at Made Tech. + +## Key responsibilities + +## Scope + +- Responsible to a Senior Designer for successfully designing and delivering good public services +- Hands-on design for one product/team +- Acts as the design subject matter expert on a product team, facilitating the design process and communicating design decisions to the team and stakeholders +- Expected to find out potential problems, shape them, and conduct solutions +- Recognises when to ask for further guidance and support +- Work is reviewed with the occasional need for direction or implementation changes +- Contributes to communities of practice, discussing and sharing suggestions, approaches and ideas - including proactively seeking feedback on own work + +## Practice + +- Knows how to turn team conversations and research into drawings and prototypes to create a shared understanding of problems to solve and ideas to test +- Make things real by caring about content and interaction design enough to make sure everyone can use public services +- Make public services simple to explain and understand by removing complexity and keeping designs focused on creating outcomes for people and society + +## Leading teams +- Assure the quality of design delivery within their team +- Introduce good habits for sharing and improving design work + +## Community + +- Take part occasionally in the hiring of designers and researchers +- Help define Made Tech design principles through delivering good public services +- Contribute to a design studio culture at Made Tech and client offices + +## Key measures + +- Delivery of good public services for users with clients + +## Competencies + +- Client focus +- Drive to deliver +- Learning and mentoring +- Experienced in their profession +- Facilitation +- Thinking through making + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/mid_product_manager.txt b/handbook/handbook-main/roles/mid_product_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..021cf0ced4ab9bc7eeaf4ede0229e2a6b604fec1 --- /dev/null +++ b/handbook/handbook-main/roles/mid_product_manager.txt @@ -0,0 +1,60 @@ +# Product Manager +Product Managers make sure products and services deliver measurable value, by exploring: + +- **user needs** - defined through comprehensive research +- **organisational needs** - defined by the requirements placed upon or introduced by the client (e.g. legislation) +- **service needs** - non-functional requirements + + +# Key responsibilities +## Scope +Product Managers: + +- work on a single engagement +- are practitioners of Product Management practices, principles and approaches +- engage within the Community of Practice +- display the Product Manager DDaT competencies and SFIA Level 3 Behaviours + + +## Practice +Applies the following practices as Product Manager, within an engagement: + +- identifies value for users, services and organisations using research and analysis +- prioritises work to rapidly deliver increments of value to users +- makes sure engagements have measurable outcomes +- negotiates product governance by guiding the definitions of ready and done, and developing success criteria +- can identify, understand and manage issues and risks +- understands the roles of related disciplines and participates as a team member, seeking opportunities for collaboration and continuous improvement +- works with the delivery manager to track progress and show our work to clients and colleagues +- when necessary, coaches client teams to instil product-thinking +- applies the agile mindset to enable best practice and realisation of value +- enables teams to be effective by fostering a culture that supports psychological safety + + +## Community of Practice (CoP) +Engages and participates within the Made Tech and client communities of practice to: + +- build an inclusive and supportive culture +- recognise when to ask for further guidance and support and identify how to improve how we work, for example, by discussing and sharing approaches, ideas and examples of practice + +## Key measures +- Delivery of good public services for users with clients, shown through relevant measures, for example, data, metrics, KPIs or the passing of service standards +- Personal performance aligned with DDaT and SFIA grade, evidenced through peer feedback + +## Competencies +Product Managers display Made Tech’s [values](https://github.com/madetech/handbook/blob/main/company/about.md), relevant [DDaT capabilities](https://www.gov.uk/guidance/product-manager#product-manager) and [SFIA (Level 3)](https://sfia-online.org/en/sfia-8/responsibilities/level-3) behaviours. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/mid_software_engineer.txt b/handbook/handbook-main/roles/mid_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..8c1e769f4b6c91cacc6a3b73c9c1bb87d1a9516f --- /dev/null +++ b/handbook/handbook-main/roles/mid_software_engineer.txt @@ -0,0 +1,54 @@ +# Software Engineer + +Our engineers create digital, data and technology outcomes that improve society by delivering and architecting software. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country with digital technology. We help public sector organisations deliver quality software to help citizens get more from public services. We work alongside brilliant public servants to modernise technology and accelerate digital delivery. + +As an engineer you’ll actively contribute to planning of work and the development of features, helping to define the features and approach to delivering them. You will proactively pick up complex features, seeking guidance and support when needed to complete them, and be comfortable architecting and delivering simple features in new contexts. + +You will have the opportunity to work across a variety of technologies and will need to be comfortable doing so. Our teams have used Ruby with Rails and Sinatra, ES6 with React and Angular, C# with .NET Core, Java with Spring, Python with Django, and plenty more stacks. We don’t limit ourselves as a company to particular technologies and we expect all of our engineers to be keen on learning new skills. + +High-performing software delivery teams need to be empowered to iteratively and rapidly deliver changes all the way through to production. We have a team of polyglot programmers (which you might already consider yourself to be) who are versed in a mix of paradigms such as object-oriented, functional, declarative, event-based and aspect-oriented. You will need to be comfortable sharing your knowledge and skills with others, and be willing to learn new technologies and skills. + +## What experience are we looking for? + +We look for the following experience. But when we’re hiring for this role, if you don’t have some of the experience listed below, don’t let that stop you from applying! + +- Writing code with tests +- Delivery within an agile environment +- Working with more than one programming language +- Working with databases +- Working with or knowledge of cloud platforms such as AWS, GCP and/or Azure +- Debugging experience with a range of systems +- Evidence of self-development – we value keen learners +- Understanding of clean architecture (Object Oriented Programming, SOLID Principles, Code Smells) + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working directly with clients and users +- Working within multidisciplinary teams with product, design, and technology working within the same cycles +- Showcasing and presentation skills +- Agile practices such as Scrum, XP, and/or Kanban +- Pair programming +- Writing code with test-driven development +- Familiarity with architectural and design patterns + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/mid_user_researcher.txt b/handbook/handbook-main/roles/mid_user_researcher.txt new file mode 100644 index 0000000000000000000000000000000000000000..8655c00cb44a6f8a53de37e84631bdf2fac18d24 --- /dev/null +++ b/handbook/handbook-main/roles/mid_user_researcher.txt @@ -0,0 +1,71 @@ +# User Researcher + +- Location: mainly remote with occasional office and client visits +- Offices: London, Bristol, Manchester, and Swansea +- Salary: Please refer to job advert when this role is live +- SFIA: Level 3 + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +User researchers are experienced practitioners who collaborate with others to understand challenges people and society face. They work within a team to inform the design and deliver public services. They do this by leading user research with real people, ensuring what their team is learning in research informs the end-to-end design of a chosen service. + +## Key responsibilities + +## Scope + +- Responsible to a senior user researcher for successfully informing the design and delivery of good public services +- Hands-on research for one product/team +- Acts as the research subject matter expert on a product team, facilitating the design process and communicating research decisions to the team and stakeholders +- Expected to find out potential problems, shape them, and conduct solutions +- Recognises when to ask for further guidance and support +- Work is reviewed with the occasional need for direction or implementation changes +- Contributes to communities of practice, discussing and sharing suggestions, approaches and ideas - including proactively seeking feedback on own work + +## Practice + +- Plan research that informs the design of public services, so they’re useful, usable and create successful outcomes +- Do research with people that makes them comfortable sharing details of their lives, that teams must understand to design good services +- Analyse and interpret raw research into findings so that teams can confidently confirm or challenge their understandings of problems and ideas +- Has experience and interest in user centred, lean and agile research methodologies including: + - Usability testing + - Contextual enquiry + - Rapid research +- Understands and applies research ethics and GDPR + +## Contributing to teams + +- Involve whole teams in user research to build their understanding and empathy for people using and running public services +- Assure the quality of decisions within their team with support from research community +- Introduce good habits for sharing and improving design work into teams + +## Community + +- Take part occasionally in the hiring of designers and researchers +- Help define Made Tech design principles through delivering good public services +- Contribute to a design studio culture at Made Tech and client offices + +## Key measures + +- Delivery of good public services for users with clients + +## Competencies + +- Client focus +- Drive to deliver +- Learning and mentoring +- Experienced in their profession +- Facilitation + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/practice_head_application_platform_support.txt b/handbook/handbook-main/roles/practice_head_application_platform_support.txt new file mode 100644 index 0000000000000000000000000000000000000000..8b2c0d30a2315ecb685a4309733aea1c9cbe7eb1 --- /dev/null +++ b/handbook/handbook-main/roles/practice_head_application_platform_support.txt @@ -0,0 +1,73 @@ +# Head of Practice - Application & Support + +Service Line: Managed Services +Reporting to the Head of Managed Services, this role is one of three Head of Practice roles each with accountability for one of our Managed Service practices: Application & Platform Support, Service Delivery & Transition and Helpdesk & End User Compute + +## Role Description + +### About the role + +As a part of our technical leadership team, you will enable public sector organisations to better use technology to improve society, and create experiences that benefit users across the UK. You will be responsible for leading a world class professional services practice; defining best practice, building and coaching teams, being a champion for Made Tech’s managed service both internally and externally and evolving our propositions and practices. + +As a Head of Practice, reporting to the Head of Managed Services, you will work closely with our client facing teams to inform their strategy and ways of working. You will ensure teams are delivering to a high quality and are consistently showcasing best practice. You will work to ensure an exceptional employee experience, and that the team of application & platform support engineers have the skills and experiences they need to deliver for our clients and their users; whilst also considering their individual development plans. You will be responsible for defining the overarching technology strategy for the service line; developing new propositions to meet the ever changing client needs and introducing standards, tools and methods in areas such as platform alerting and data quality monitoring. + +You will work closely with other Heads of Practice and Solution Managers to support the growth of the service line. This will include shaping solutions and writing bid responses, maintaining and growing your professional network, contributing to thought leadership through content and events, and collaborating with clients as an advisor, partner and consultant. + +### The following skills will be assessed during the application process + +The below list describes specific skills and experiences that you’ll need in this role. + +Don’t worry - we don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these expectations. + +**Key competencies** +* Strong understanding of ITIL ways of working +* Strong understanding of software engineering practices +* Strong understanding of cloud platform and data platform technologies +* Evidence of proactive self-development and the development of those in their team +* Ability to multi-task and confidently prioritise yourself and others + +**Key skills** +* Maintaining a deep working knowledge of application and platform support methods, technologies and techniques - be a subject matter expert that guides account teams and client conversations +* Excellent understanding and passionate articulation of the value of high quality application & platform support +* Ability to innovate, understand the challenges facing the public sector, and apply learnings taken from the private sector +* An understanding of the commercial position of working in a consultancy/advisory role within the public sector +* A practical understanding of cyber security and data protection requirements as they apply to the public sector, and the ability to define governance that ensures compliance +* Able to educate or mentor team members, colleagues and peers in the wider business on the offerings of a managed service capability +* Line management and coaching skills +* Oversee delivery and drive excellence across the practice +* Confident ability to be a thought leader in the application & platform management space, both internally and externally +* Able to build successful relationships with our clients and colleagues across Made Tech +* Articulate value-add to clients and a differentiated approach through the development of joined-up propositions as solutions to client problems, and go-to market plans based on real-world client needs + +**Key experiences** +* Growing and running technology teams in a live service environment; including hiring, developing, motivating and coaching a team to deliver lasting change +* Developing technology communities as a leader or member of a high-performing team +* Working directly with clients and users, and able to drive teams to deliver measurable outcomes +* Designing standards for Level 2 and/or Level 3 technical support teams, including generating templates for key work products such as disaster recovery plans and runbooks +* Implementing service management tooling and processes to improve the efficiency of live service support teams +* Working in multidisciplinary digital and technology teams, including product, design, operational and testing roles +* Solutioning and sizing teams based on complex client and user requirements, including capacity planning for continuous improvement activities +* Working with sales teams to build client relationships, develop opportunities and win new work +* Work as a trusted advisor across all levels, including building strategic relationships with C-Level stakeholders across the public sector +* Analysing the cost and benefit of service management and monitoring tooling +* Working alongside transition managers to define best practice for onboarding new digital and technology services into a live service support team +* Managing partnerships and suppliers to provide a consolidated and seamless service offering to clients +* Owning a cost-centre and of working with commercial functions to grow a profitable practice +* Defining and implementing standardised approaches to maintenance including patching and upgrading + +### Key measures +* Growth and development of the application & platform support practice (both revenue and headcount) in line with business needs +* Margin and utilisation of the practice as part of overall managed services service line +* Quality of the services delivered to our clients, by members of the practice, as measured by SLAs, KPIs, XLAs etc. within statements of work +* Case studies, publications and speaking engagements on how to design and deliver excellent live service support + +## Salary and location + +We adopt a hybrid approach and anticipate that most roles will spend a mixture of time within our offices, client sites and working remotely. We have offices in London, Bristol, Manchester, and Swansea and our clients are across the UK. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. diff --git a/handbook/handbook-main/roles/practice_head_business_analysis_change.txt b/handbook/handbook-main/roles/practice_head_business_analysis_change.txt new file mode 100644 index 0000000000000000000000000000000000000000..2f34a7ed6c0c5796cdc81d4540e4dc32bc219a22 --- /dev/null +++ b/handbook/handbook-main/roles/practice_head_business_analysis_change.txt @@ -0,0 +1,96 @@ +# Head of Business Analysis & Change + +Our Head of Business Analysis & Change is responsible for leading a world-class professional services practice and developing demand for a set of propositions and capabilities to meet the needs of our clients and to support the strategic growth of our business. + +We believe that good design, research-driven policy, technical excellence, continuous innovation and improvement, and effectively managed change can significantly enhance citizen and user experiences, bolster the resilience of public services, and help to improve the applications that deliver essential services to our society. + +The successful candidate will lead the practice to help us to develop and support the sale of a set of differentiated offerings covering transformation, business analysis, change, for a wide range of public services. They will develop a team of Business Analysts, Transformation Leads & Change Practitioners to engage with our clients on their business priorities and challenges, and they will guide and monitor client engagements across Made Tech. + +In addition the Head of Practice will be responsible for engaging with our clients to understand their challenges and build lasting, trusted advisor relationships. They will also oversee client deliveries to help ensure quality and drive the sharing of best practice across our engagements and industries. + +This role reports directly to the Head of Strategy & Design Service Line. + +## Role Profile + +* Our Head of Business Analysis & Change is a member of the Strategy & Design Service Line leadership team with the responsibility to develop the capability of the practice to meet business needs and to accelerate the growth of both the practice and wider business. +* You will be responsible for the revenue, margin and utilisation of the practice, collaborating with the other practice, service line, industry and delivery heads to drive excellent services for our Public Sector clients. You will also be responsible for the output of your team working on client projects, proposals and capability development. +* The right person for this role will do this by combining their technical discipline experience, leadership skills and industry network with Made Tech's unparalleled experience of delivering digital services and digital transformation for the Public Sector. + +## Responsibilities + +* Grow the Business Analysis & Change practice at Made Tech (revenue and headcount); develop trusted relationships with our clients to identify specific growth opportunities and proactively take new ideas to our clients to help them solve their biggest problems. +* Develop joined-up propositions as solutions to client problems; establish Made Tech as an innovator and thought leader in the space, sharing our differentiated approach to improve services across the public sector. +* Lead the Business Analysis & Change practice; hire, develop, motivate and coach a team that understands the user/client needs as well as the technology and lasting change that we are delivering across the public sector. +* Deliver a profitable practice; balance complex client needs with highly performing, suitably leveraged and cost effective teams. +* Help to shape our Service Line and Made Tech; define and articulate the client-facing solutions that support our Industry strategies and help to turn them into client engagements through client conversations, presenting externally as a thought leader and contributing directly to bids. +* Provide subject matter expertise; lead the client conversations as a subject matter expert, and guide and support the account teams to build strategic plans that leverage the practice capability. +* Be a trusted advisor; build strategic relationships with C-Level stakeholders across our public sector client base and the wider industry +* Oversee our deliveries and drive excellence in our engagements; take a hands-on interest in our client deliveries, guide and mentor our delivery teams and liaise with high profile stakeholders and key clients to ensure satisfaction with our contributions. + +## Skills + +### Clients + +* Understanding of the issues and challenges that the public sector faces in delivering services that make the best use of data and digital capabilities, transforming legacy infrastructure, and taking an innovative and user-centric approach. +* Ability to innovate and take learnings from the commercial sector, other countries and advances in technology and apply them to UK Public Sector challenges to create tangible solutions for our clients. +* Experience building trusted advisor relationships with senior client stakeholders within the public sector. + +### Leadership + +* Experience of building and managing high performing, consulting teams and creating the leveraged engagements to provide a cost-effective, profitable, successful client-facing delivery. +* Experience of owning a cost-centre and of working with commercial functions to grow a profitable practice. +* Experience of managing partnerships and suppliers to provide a consolidated and seamless service offering to clients. + +### Practice + +* Experience developing targeted propositions and go-to-market plans based on real-world client needs. +* Experience of working with sales professionals and commercial responsibility for strategic organisational goals. +* Experience in running engagements that span multiple capabilities for user-facing digital and data services in the public sector. + +### Business Analysis and Change + +* Strategic feasibility analysis: + * Able to assess strategic options and their validity against business objectives. +* Organisational design & transformation: + * Familiar with operating model change methodology. + * Analysing an organisation's structure and roles/responsibilities, defining future capability requirements. + * Assessing the effectiveness of decision-making processes and governance +* Operating model analysis: + * Evaluating the current technology landscape and its impact on operations. + * Aligning operating model components with overall business strategy. +* Business modelling: + * Determine the scope and methodology for the representation of complex transformation across an organisation. + * Document conceptual models to support client strategic planning and decision making. +* Strategy definition: + * Evaluate the internal and external environment of an organisation + * Facilitate workshops to support clients to define business objectives + * Formulate strategies to support clients to achieve their outcomes. +* Agile expert: + * Awareness of agile transformation delivery. +* Consulting expert: + * Provide advice and recommendations to stakeholders based on your significant specialist knowledge and experience. + * Lead the definition of business analysis & change offerings and develop subsequent proposals to pitch to senior clients. +* Enterprise and business architecture: + * Work with limited direction to translate business drivers, goals and constraints into business objectives for clients. + * Help to define required capabilities and support organisational changes to create operating models that meet client business objectives. +* Senior stakeholder management: + * Develop engagement strategies and lead on communication with stakeholders at all levels. + * Actively establish relationships and apply the benefits of professional networks. + * Act as a point of consultation and escalation to resolve conflict in complex situations for your team. +* User experience analysis: + * Advise on the approach to analysis, prioritisation and validation of user experience needs. + * Recommend a range of techniques to analyse the user experience and ensure that it meets business and user needs. + * Articulate and communicate how user experience needs affect the design of a system in a project or programme of work. +* Transformation Leadership: + * Drives innovation and inspires new ways of thinking + * Ability to articulate a compelling vision that motivates and aligns teams towards common goals + * Leads teams and takes responsibility for achieving outcomes + +## Salary and location + +We work in a hybrid manner with on-site requirements for in-person presence when considered most beneficial for the activity (team meetings, workshops, onboarding for example). You may also need to visit clients where on-site requirements are necessary and/or beneficial. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + diff --git a/handbook/handbook-main/roles/principal_business_analyst.txt b/handbook/handbook-main/roles/principal_business_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..be22dd0aec7282da2973fee4f74d7e1928e454c9 --- /dev/null +++ b/handbook/handbook-main/roles/principal_business_analyst.txt @@ -0,0 +1,128 @@ +# Principal Business Analyst +**Delivering world class client engagements.** + +Our Principal Business Analysts are responsible for leading and delivering on strategically significant and complex client engagements across our portfolio of public sector clients. +We believe that great delivery stems from: +* a thorough understanding of our clients and their needs +* strong practice skills and subject matter expertise +* excellent leadership +* a clear vision of lasting and effective change in a public sector environment +* the ability to translate meaningful strategy into effective implementation + +We expect our Principal Business Analysts to bring all of this and to enthuse our strategy, analysis and design teams, and clients with the same passion. +The successful candidate will lead the Business Analysis aspects of one or more of our client engagements while overseeing the wider delivery within the account (or industry) and practice when appropriate. + +They will bring thought leadership and best-practice, honed through hands-on experience in both the private and public sector. They will work with product managers, user researchers, transformation leads, data analysts and client product owners to make ongoing recommended improvements to drive better user and business outcomes. + +They will often be responsible for leading transformation projects, helping teams to understand complex business scenarios, translating business drivers, goals and constraints into business outcomes, to define required capabilities that will enable our clients to expedite organisational change. + +Working in an Agile delivery setting alongside consultants, product managers, service designers, user researchers and transformation leads, the Business Analysis Principal will oversee and be responsible for the hands-on delivery of business agility improvements. + +They will be comfortable blending the just in time delivery of key business analysis artefacts into the delivery teams with continuous discovery and ideation of longer term epics and features. + +They will also coach and develop team members on their engagements providing them with detailed performance feedback, as well as monitoring overall delivery to achieve the highest levels of client satisfaction. + +In addition, our Principal Business Analysts are responsible for engaging with our clients to understand their challenges and build lasting, trusted advisor relationships. They will also oversee multiple and concurrent client deliveries to help ensure quality and drive the sharing of best practice across our engagements and industries. + +## Role Description + +Our Principal Business Analysts are members of the Strategy and Design Practice leadership team. Part of their responsibility is to develop the capability of the practice to meet business needs and to accelerate the growth of the practice, their account and the wider business. + +Principal Business Analysts are responsible for the practice and service line-specific delivery elements of an engagement/ account as well as shared ownership for the overall delivery of client outcomes. They leverage client and delivery insight to support the account and industry teams to identify opportunities and develop client solutions. + +The right person for this role will do this by combining their Business Analysis experience, leadership skills and industry network with Made Tech's unparalleled experience of delivering digital services and digital transformation for the Public Sector. + +### Your role at Made Tech + +* Collaborate with clients to understand their needs and provide solution advice in your role as a trusted advisor and shape solutions that leverage Made Tech's wider capabilities and credentials. +* Assess project performance as a part of the billable delivery team, QA Business Analysis deliverables and outcomes, and ensure client satisfaction. +* Deliver Business Analysis elements alongside client and Made Tech delivery teams. +* Coach and mentor team members as well as providing direction to enable them to achieve their engagement outcomes and to develop their careers. +* Act as a business analysis authority to provide oversight and ensure alignment with internal and industry best practices. Ensure engagement experience is captured and used to improve standards and contribute to Made Tech knowledge. +* Work as part of a wider consulting team on large scale transformation and lead change projects in the public sector. +* Participate in business development activities, including bids and pre-sales within the account, industry and practice. Coach team members on their contributions and oversee the relevant technical aspects of the proposal submission. +* Undertake people management responsibilities, including performance reviews and professional development of your engagement and practice colleagues. +* Serve as a thought leader within Made Tech, our account engagements and the wider public sector and represent the company at industry events. + +## Skills and experience + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, we still encourage you to apply. + +### Clients + +* Understanding of the issues and challenges that the public sector faces in developing policies and services that make the best use of data and digital capabilities, transforming legacy infrastructure, and taking an innovative and user-centric approach. +* Ability to take learnings from the commercial sector and other countries and apply them to UK challenges to create tangible solutions for our clients. +* Experience building trusted advisor relationships with senior client stakeholders within the public and commercial sectors. + +### Leadership + +* Experience of building and leading high performing, consulting teams and creating the leveraged engagements to provide a cost-effective, profitable, successful client-facing delivery. +* Leadership of bids and solution shaping to produce compelling proposals that help Made Tech win new business and grow the industry. +* Experience of managing third-party partnerships and suppliers (in conjunction with Made Tech colleagues) to provide a consolidated and seamless delivery team to clients. +* A strong user-centred approach with a commitment to improving services based on user needs and experiences. +* Able to use data analytics to inform strategic decisions, identify opportunities for change and optimise client service delivery. + +### Practice and industry growth + +* An expert Business Analysis practitioner with experience in both the public and commercial sectors. +* Experience in delivering complex and difficult engagements that span multiple capabilities for user-facing digital and data services in the public sector. +* Experience in identifying opportunities based on client needs and developing targeted solutions to progress the development of the opportunity. +* Experience of working with sales professionals and commercial responsibility for strategic organisational goals. + +### Business Analysis Skills + +* Agile Practices: + * Coach and lead teams in Agile and Lean practices challenging, evaluating and iterating the approach. + * Ability to use innovative approaches to achieve right outcomes. +* Business Analysis: + * Ability to propose a business analysis approach for projects / programmes / sector. + * Ability to create conceptual models to facilitate strategic planning in complex environments, identifying tactical priorities. + * Ability to assess feasibility of proposed solutions against an organisational vision. +* Business Analysis Leadership: + * Seek opportunities for reuse and learning, establishing and maintaining wider relationships across the profession. + * Lead on coaching and mentoring for business analysis and co-ordinate the business analysis community. + * Plan and prioritise business change deliverables across multiple teams, minimising dependencies and risks. + * Coach and mentor others in business analysis. +* Consulting expert: + * Provide advice and recommendations to stakeholders based on your significant specialist knowledge and experience. + * Lead the definition of Business Analysis offerings and develop subsequent proposals to pitch to senior clients. +* Enterprise Architecture: + * Ability to define business drivers and goals into business objectives, influencing and shaping organisational strategies. + * Ability to create operating models, defining required capabilities. + * Ability to analyse IT system capabilities, identifying and driving business innovation opportunities. +* Value Creation: + * Develop and own a business case coaching others on identifying benefits, balancing user and business needs. + * Communicate the delivery of incremental value building the case for an approach to value through prioritisation of complex needs. + * Ability to identify, drive and lead large scale transformational change. +* Stakeholder Relationship management: + * Direct the stakeholder relationship strategy ensuring stakeholders objectives are set. + * Influence and negotiate with senior stakeholders to resolve issues and enable progress. +* Strategic Leadership: + * Support and coach others in creating and implementing a successful long-term strategy. + * Influence and persuade stakeholders to support delivery of the strategy supporting strategic decision making ensuring strategic alignment. + +### People Management + +* Ambassadors of belonging at Made Tech, advocating and championing organisational commitments and priorities, recognising their role in modelling the way and embodying our values. +* Compelling communicators, ensuring key information is swiftly cascaded, understood, and feedback gathered and shared. +* Using their coaching skills to enable people to be their best, regularly and routinely providing meaningful, positive and constructive feedback. +* Make decisions that support the best interests of the business while recognising that our people are its foundation. Strive to achieve the best outcomes for individuals through persuasive and persistent efforts, ensuring these decisions uphold both the short- and long-term sustainability of the business. +* Inspire innovation and spark curiosity, encourage people to be positively disruptive and challenge the status quo. +* Seek collective success above personal glory, strive to ensure a constant culture of inclusion, trust and transparency. +* Lead your direct reports and positively influence the wider organisation as an inspiring people manager in line with our people manager objectives and key results. + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. diff --git a/handbook/handbook-main/roles/principal_data_consultant.txt b/handbook/handbook-main/roles/principal_data_consultant.txt new file mode 100644 index 0000000000000000000000000000000000000000..5d0d2839e5328be52c670375b53b55a859138d4e --- /dev/null +++ b/handbook/handbook-main/roles/principal_data_consultant.txt @@ -0,0 +1,56 @@ +# Principal Data Consultant + +Reporting to the Head of Data, the Principal Data Consultant supports the Made Tech mission to enable public sector organisations to better use technology in order to improve society. They do this by building and managing strategic relationships, leading accounts, finding new opportunities and advising as a senior technology leader across multiple clients. + +## Summary + +We help public sector organisations deliver quality technology solutions to help citizens get more from public services. To do this we work alongside brilliant public servants to modernise technology and accelerate digital delivery. + +As Principal Data Consultant you will work closely with our customers senior leadership to help inform their strategy and to ensure our consulting teams are delivering to a high quality and are aligned to our customers technology vision. + +Working with leadership within Made Tech and the Data & AI practice you will ensure our engagements with customers are aligned to our growth goals and you will play a pivotal role in identifying new opportunities and winning work. Running bid teams, supporting the wider sales team and developing new business is critical to this role. + +You will help to coach and support Data & AI team members as well as colleagues from Cloud & Engineering and other practices to steer our project teams towards success. You will also have input into hiring and line managing colleagues. + +While this is not a hands-on technical role, the importance of credibility in internet-era approaches to digital, data and technology in the public sector cannot be understated. You will be expected to maintain a broad technical knowledge of modern data practices, be able to shape data strategy and roadmaps, and hold others to account for technical quality. + +As a data leader within Made Tech you will be expected to maintain and grow your professional network. You will be expected to contribute to thought leadership, content and events and should have a proven track record of doing so. + +### What experience are we looking for? + +We look for the following experience. But when hiring for this role, if you don’t have some of the experience listed below, don’t let that stop you from applying! +* Working directly with customers and users +* Working within a technology consultancy or data/ strategy role within a public sector facing or commercial organisation +* Shaping data strategy, delivery roadmaps and approaches to quality, ethics and governance +* Developing a data practice, capability or function +* Combining data strategy, data science, analytics and engineering to deliver an outcome +* Strong understanding of modern data platform architectures, including data warehouses, data lakes, data lake houses and data mesh +* Strong understanding of best practice DataOps and MLOps and how to deploy them +* Up-to-date understanding of the capability of various data engineering and science technologies, especially Apache Spark +* Strong understanding of agile ways of working +* Up-to-date understanding of key cloud platforms' data offerings, including AWS and/ or Azure +* Evidence of self-development – we value keen learners + +### Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable + +* Central Digital & Data Office’s Data Ethics Framework +* Leadership of a data capability or function +* Working within an account or programme leadership team +* Working within bid teams to win contracts exceeding value of £1m +* Working with multidisciplinary digital and technology teams +* Working within the public sector +* Experience in hiring, forming and running teams + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +## Salary and location + +We adopt a hybrid approach and anticipate that most roles will spend a mixture of time within our offices, client sites and working remotely. We have offices in London, Bristol, Manchester, and Swansea and our clients are across the UK. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. diff --git a/handbook/handbook-main/roles/principal_data_engineer.txt b/handbook/handbook-main/roles/principal_data_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..b1fee2c190695bdaf8e48ff2ba96742a54646670 --- /dev/null +++ b/handbook/handbook-main/roles/principal_data_engineer.txt @@ -0,0 +1,64 @@ +# Principal Data Engineer + +Our Principal Data Engineers enable public sector organisations to transform service delivery with data to improve society, for everyone. They provide our most senior data leadership and support to our clients and teams. They build and manage key relationships with clients, and manage data consultancy and delivery across one or more accounts. They also support sales. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. To do this we work alongside brilliant public servants to drive better decisions through data and automation. + +As a Principal Data Engineer you will work closely with our clients' senior leadership teams to help inform their data strategy, as well as ensuring our teams are delivering to a high quality and aligned with our clients' data vision. You’ll need to have a drive to deliver outcomes for users. Working alongside delivery, client and other capability principals, you will help shape account plans and be responsible for delivering against them. + +Working with Made Tech's leadership team you will ensure our work with customers is aligned to our growth goals and you will play a pivotal role in identifying new opportunities and winning work. Running bid teams, supporting sales teams and developing new business is critical to this role. + +You will coach and support Lead Data Engineers to steer their teams towards success. You will also be responsible for hiring and line managing Lead Data Engineers. + +While this is not a hands-on coding technical role, the importance of credibility in internet-era approaches to digital, data and technology in the public sector cannot be understated. You will be expected to maintain a broad technical knowledge of modern data practices, be able to shape data strategy and roadmaps, and hold others to account for technical quality. + +As a data leader within Made Tech you will be expected to maintain and grow your professional network. You will be expected to contribute to thought leadership, content and events and should have a proven track record of doing so. + +## What experience are we looking for? + +We look for the following experience. But when we’re hiring for this role, if you don’t have some of the experience listed below, don’t let that stop you from applying! + +- Working directly with customers and users +- Working within a technology consultancy +- Shaping data strategy and approaches to quality, ethics and governance +- Developing a data capability or function +- Combining data science, analytics and engineering +- Strong understanding of various architectures including data warehouses, data lakes, data lake houses and data mesh +- Strong understanding of best practice DataOps and MLOps +- Up-to-date understanding of various data engineering technologies including Apache Spark, Databricks and Hadoop +- Strong understanding of agile ways of working +- Up-to-date understanding of various programming languages including Python, Scala, R and SQL +- Up-to-date understanding of various databases and cloud-based datastores including SQL and NoSQL +- Up-to-date understanding of cloud platforms including AWS and/or Azure and their data offerings +- Evidence of self-development – we value keen learners + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Central Digital & Data Office’s Data Ethics Framework +- Leadership of a data capability or function +- Working within an account or programme leadership team +- Working within bid teams to win contracts exceeding value of £1m +- Working with multidisciplinary digital and technology teams +- Working within the public sector +- Experience in hiring, forming and running teams + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) + to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/principal_delivery_manager.txt b/handbook/handbook-main/roles/principal_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..76b8f82169ac4fbf0949db66d2cf1bde6320afca --- /dev/null +++ b/handbook/handbook-main/roles/principal_delivery_manager.txt @@ -0,0 +1,139 @@ +# Principal Delivery Manager + +Our Principal Delivery Managers are accountable for the successful delivery of a portfolio of projects while developing senior client relationships and demonstrating delivery leadership. + +## Your role at Made Tech + +Delivery principals work with delivery, technical and design leads to ensure projects deliver the desired outcomes for users and customers. As an expert in delivery, you’ll define the delivery approach and team shape, inspire trust with senior stakeholders and guide clients through the delivery process from the first client engagement. As the most senior line of project escalation on your account, you’ll collaborate with delivery teams and client stakeholders to identify and manage risks and solve issues that arise. The majority of these activities will be value adding, and chargeable to the client. + +While this is not a hands-on delivery role, the importance of credibility in internet-era approaches to digital, data and technology in the public sector cannot be understated. You will maintain a broad knowledge of modern delivery practices and support teams to deliver quality outcomes that meet the needs of users and clients. As the most senior delivery professional on your account, you will be accountable for ensuring the teams within your portfolio have appropriate processes and ways of working in place to manage budget, quality, team well-being, and risks that could impact successful delivery. + +Delivery principals form part of the Delivery and Project Management Office leadership team and contribute to the successful delivery of change and improvement initiatives. This includes fostering a best-in-class Community of Practice (CoP), managing the performance and development of a number of delivery managers, promoting learning and development, supporting recruitment, and contributing to quarterly and annual goals. + +As someone in a senior role within a matrix management organisation, you will build effective relationships with other senior leaders within the business, enabling you to contribute to Made Tech playbooks and thought leadership. You will support the well-being and development of all team members within your porfolio, by ensuring they receive regular feedback and learning opportunities. + +As a delivery leader within Made Tech you will maintain and grow your professional network. You will contribute to Made Tech’s growth, working with marketing on thought leadership, content and events, and supporting sales with responding to bids. + + +## Definition of success + +Delivery Principal accomplishment is demonstrated by growing Made Tech’s impact, delivering high value services to our clients, and accelerating the careers of others in both Delivery Management and other capabilities within your portfolio. + +### Outcomes +* Manage quality and risk of all account deliveries +* Maximise time spent on value-adding activities that are chargeable to the client +* Ensure accurate and timely adherence to all critical business processes within the account +* Balance client satisfaction and team well-being with Made Tech’s commercial goals +* Develop and deliver an effective Account Growth strategy with other members of the Account Management Team +* Contribute to growing Made Tech’s impact +* Demonstrate leadership and expertise in public sector delivery +* Contribute to the Delivery Community of Practice +* Accelerate the career of other Delivery Managers through line management, coaching, mentoring & knowledge sharing + +### KPIs +* Billability +* Quality +* Risk +* Account/ Project Gross Profit Margin (GPM) +* Forecast accuracy +* Invoice accuracy +* Revenue contribution +* Employee Engagement (eNPS) + +## Internal Stakeholders + +As a Delivery Principal you are responsible for delivering the above outcomes by collaborating with other Delivery Principals, the rest of the Account Management Team, Delivery/Design/Technology leads within your projects, client stakeholders and internal business partners e.g. scheduling, hiring, people team. + +As a matrix organisation you will have a dual reporting line. +* The Head of Delivery will be your line manager and is responsible for your career development, and oversees the approach to Delivery across the organisation. +* The Delivery Director and Industry Director for your Industry, who work across the accounts in an industry to build client relationships and sector knowledge that contributes to Industry growth. + +### Strategy +* Contribute to and deliver on Account Strategy +* Contribute to and support Delivery Management capability improvement initiatives +* Account Level Delivery Assurance + +### Accountable for ensuring delivery success +* Report to the Head of Delivery and Industry Delivery Director every week the status of quality and risk +* Oversee project planning and delivery, reporting on progress against expected milestones +* Manage team resourcing to balance successful client delivery, team happiness and Made Tech commercial objectives +* Oversee compliance and accuracy of all critical business processes (time sheeting, invoicing, forecasting, delivery assurance reporting) +* Oversee commercial activities (Statements of Work, purchase order numbers, supplier contracts for partners, IR35 assessments for contractors, raising staffing demands) + +### Hiring and Careers +* Support hiring activities including interviewing and outreach +* Management of Delivery Managers including performance, progression and satisfaction +* Ensure regular feedback (constructive and/or appreciative) is shared with all individuals working on projects you are accountable for + +### Growing Made Tech’s Impact +* Take the lead on bids, using your knowledge and experience to understand the problem and shape our response +* Ensure your clients are motivated to bring repeat business and recommend our services to others +* Identify opportunities for Made Tech to deliver value for the client beyond the current project +* Build relationships with senior stakeholders within your account +* Promote Made Tech and develop your personal reputation in the industry by producing thought leadership content, expanding your personal network and attending events + +### Community and Thought Leadership +* Share successes and failures with the Delivery Community to support the evolution of ways of working, techniques, and technologies across Made Tech +* Contribute to the Industry Community, to support the identification of common problems that can be developed into propositions +* Contribute to a set of centralised resources and templates for potential reuse +* Contribute to developing a thriving community of practice and shared identity + +## Competencies and behaviours +Delivery Principals are expected to be operating at, or working towards, [SFIA level 6](https://sfia-online.org/en/sfia-8/responsibilities/level-6) in all five competencies. In addition to this, the below list describes specific competencies and behaviours that you’ll need in this role. + +We don’t expect you to tick all of these when you join. We'll work together to define learning and development objectives that help you meet these competencies. + +### Articulation and role modelling of Made Tech values, purpose, and vision +* Describe each with examples +* Demonstrate role modelling + +### Commercial awareness +* Articulate business fundamentals (USP, profitability, risks, target market) +* Demonstrate advocacy and prioritisation of business fundamentals +* Display accountability for managing commercial activities within deliveries +* Be able to recall and describe key Made Tech case studies, including where you were not directly involved in the project + +### Time management and prioritisation +* Demonstrate prioritisation, delegation and consistent delivery of multiple goals simultaneously + +### Performance management of direct and indirect reports +* Demonstrate fast remediation of performance issues +* Support direct reports with performance remediation of indirect reports +* Demonstrate encouragement and mentoring of high performers, to support them towards successful promotions +* Maintain compliance with all expectations of line management at Made Tech + +### Lead teams to effectively manage risk and quality within workstreams +* Demonstrate planning of and implementation of risk management activities within programme of projects, including consistent and reliable risk management processes and reporting to key stakeholders +* Demonstrate activities to ensure that projects, teams and functions have appropriate practices in place to meet required quality levels + +### Coach teams to successfully deliver projects +* Have working knowledge of a wide variety of delivery approaches, methods and tools - for example Kanban, Scrum, Scaled Agile, Waterfall, Lean, XP and Design Sprints +* Recall examples of coaching teams on best practices in other capabilities, including Security, DevOps, User Centred Design and Data Ethics +* Be able to explain the GDS service standard and how to meet each point, the purpose of each phase of the GDS Service Manual and the roles and responsibilities of all of the DDAT roles that make up a Service Team +* Be able to describe and advocate for the Made Tech propositions +* Demonstrate advocacy of best practice delivery with teams and clients + +### Deliver consultancy to clients as part of a formal or informal arrangement +* Demonstrate experience of designing and running workshops with client stakeholders, including post-workshop feedback +* Demonstrate experience taking responsibility for understanding client requirements, collecting data, delivering analysis and problem resolution. + +### Trust building with your seniors, peers, juniors and client stakeholders +* Demonstrate with feedback from seniors, peers, juniors and client stakeholders + +### Continuous improvement and feedback +- Demonstrate positive response to feedback with course correction + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We do not mandate time on-site, but in-person collaboration is important for fostering effective relationships, and would expect Delivery Principals to spend time with their teams and with their clients. We have offices in London, Bristol, Manchester, and Swansea, and have clients with hubs all over the country. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/principal_product_manager.txt b/handbook/handbook-main/roles/principal_product_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..c18041979fadf140343da68ee71c22b4b1355b4d --- /dev/null +++ b/handbook/handbook-main/roles/principal_product_manager.txt @@ -0,0 +1,126 @@ +# Principal Product Manager +**Delivering world class client engagements.** + +Our Principal Product Managers are responsible for leading and delivering on strategically significant and complex client engagements across our portfolio of public sector clients. + +We believe that great delivery stems from: +* a thorough understanding of our clients and their needs +* strong practice skills and subject matter expertise +* excellent leadership +a clear vision of lasting and effective change in a public sector environment +* the ability to translate meaningful strategy into effective implementation + +We expect our Principal Product Managers to bring all of this and to enthuse our design teams and clients with the same passion. +The successful candidate will lead the Product Management aspects of one or more of our client engagements while overseeing the wider delivery within the account (or industry) when appropriate. + +They will bring thought leadership and best-practice, honed through hands-on experience in both the private and public sector. They will work with user researchers, service designers, business analysts, data analysts and client product owners to make ongoing recommended improvements to drive better user and business outcomes. + +They will often be responsible for creating a product vision helping to translate it into a UX strategy that can deliver a category leading user experience, driving impact and reach across multiple user groups. + +Working in an Agile delivery setting alongside product designers, the Principal Product Manager will oversee and be responsible for the hands on delivery of product improvements and end to end journeys across all channels including app and web. + +They will be comfortable blending the just in time delivery of key product artefacts into the delivery teams with continuous discovery and ideation of longer term features and usability improvements. + + They will also coach and develop team members on their engagements providing them with detailed performance feedback, as well as monitoring overall delivery to achieve the highest levels of client satisfaction. + +In addition, our Principal Product Managers are responsible for engaging with our clients to understand their challenges and build lasting, trusted advisor relationships. They will also oversee multiple and concurrent client deliveries to help ensure quality and drive the sharing of best practice across our engagements and industries. + +## Role Description + +Our Principal Product Managers are members of the Strategy and Design Practice leadership team. Part of their responsibility is to develop the capability of the practice to meet business needs and to accelerate the growth of the practice, their account and the wider business. + +Principal Product Managers are responsible for the practice and service line-specific delivery elements of an engagement/ account as well as shared ownership for the overall delivery of client outcomes. They leverage client and delivery insight to support the account and industry teams to identify opportunities and develop client solutions. + +The right person for this role will do this by combining their Product Management experience, leadership skills and industry network with Made Tech's unparalleled experience of delivering digital services and digital transformation for the Public Sector. + +### Your role at Made Tech + +* Collaborate with clients to understand their needs and provide solution advice in your role as a trusted advisor and shape solutions that leverage Made Tech's wider capabilities and credentials. +* Assess project performance as a part of the billable delivery team, QA Product Management deliverables and outcomes, and ensure client satisfaction. +* Deliver Product Management elements alongside client and Made Tech delivery teams. +* Coach and mentor team members as well as providing direction to enable them to achieve their engagement outcomes and to help support and develop their careers. +* Act as a Product Manager to provide oversight and ensure alignment with internal and industry best practices. Ensure engagement experience is captured and used to improve standards and contribute to Made Tech knowledge. +* Work as part of a wider consulting team on large scale transformation and lead change projects in the public sector. +* Participate in business development activities, including bids and pre-sales within the account, industry and practice. Coach team members on their contributions and oversee the relevant technical aspects of the proposal submission. +* Undertake people management responsibilities, including performance reviews and professional development of your engagement and practice colleagues. +* Serve as a thought leader within Made Tech, our account engagements ,the wider public sector, and represent the company at industry events. + +## Skills and experience + +### Clients + +* Understanding of the issues and challenges that the public sector faces in developing policies and services that make the best use of data and digital capabilities, transforming legacy infrastructure, and taking an innovative and user-centric approach. +* Ability to take learnings from the commercial sector and other countries and apply them to UK challenges to create tangible solutions for our clients. +* Experience building trusted advisor relationships with senior client stakeholders within the public and commercial sectors. + +### Leadership + +* Experience of building and leading high performing, consulting teams and creating the leveraged engagements to provide a cost-effective, profitable, successful client-facing delivery. +* Leadership of bids and solution shaping to produce compelling proposals that help Made Tech win new business and grow the industry. +* Experience of managing third-party partnerships and suppliers (in conjunction with Made Tech colleagues) to provide a consolidated and seamless delivery team to clients. +* A strong user-centred approach with a commitment to product managing and improving services based on user needs and experiences. +Able to use data analytics to inform strategic decisions, identify opportunities for change and optimise client service delivery. + +### Practice and industry growth + +* An expert Product Management practitioner with experience in both the public and commercial sectors. +* Experience in delivering complex and difficult engagements that span multiple capabilities for user-facing digital and data services in the public sector. +* Experience in identifying opportunities based on client needs and developing targeted solutions to progress the development of the opportunity. +* Experience of working with sales professionals and commercial responsibility for strategic organisational goals. + +### Product Management Skills + +* Agile Practices: + * Coach and lead teams in Agile and Lean good practices challenging, evaluating and iterating the approach through the life cycle. + * Experiment with new and innovative ways of working to improve delivery across a project or within client organisations. +* Value Creation: + * Develop and own a business case throughout the life cycle, coaching others on identifying benefits, balancing user and business needs. + * Communicate the delivery of incremental value building the case for an approach to value through product strategy. +* Product Life Cycle Management: + * Lead and coach teams through phases of the life cycle ensuring effective support is in place for the product or service and its users. + * Predict, prevent, mitigate and manage potential risks at different phases of the life cycle highlighting to clients where required. +* Managing Product Outcomes: + * Use data to prioritise decisions for multiple or complex projects, products or services. + * Identify opportunities to share and connect product data across boundaries. + * Expert in using a range of effective research approaches, coaching others in making decisions that meet user needs across a range of channels. + * Champions use of user-insights in teams to inform strategic decisions to provide the best user experience. +* Product Leadership: + * Seek opportunities for reuse and learning, establishing and maintaining wider relationships across the profession. + * Lead on coaching and mentoring for product management and co-ordinate the product management community. +* Product Management: + * Set the strategy and vision for products, collaborating with others to create a prioritised roadmap for products. + * Plan prioritised work across multiple teams, minimising dependencies and risks. + * Coach and mentor others in product management. +* Stakeholder relationship management: + * Direct the stakeholder relationship strategy ensuring stakeholders objectives are set. + * Influence and negotiate with senior stakeholders to resolve issues and enable progress. +* Strategic Leadership: + * Support and coach others in creating and implementing a successful long-term strategy. + * Influence and persuade stakeholders to support delivery of the strategy supporting strategic decision making, ensuring strategic alignment. +* Consulting expert: + * Provide advice and recommendations to stakeholders based on your significant specialist knowledge and experience. + * Lead the definition of Product Management offerings and develop subsequent proposals to pitch to senior clients + +### People Management + +* Ambassadors of belonging at Made Tech, advocating and championing organisational commitments and priorities, recognising their role in modelling the way and embodying our values. +* Compelling communicators, ensuring key information is swiftly cascaded, understood, and feedback gathered and shared. +* Using their coaching skills to enable people to be their best, regularly and routinely providing meaningful, positive and constructive feedback. +* Make decisions that support the best interests of the business while recognising that our people are its foundation. Strive to achieve the best outcomes for individuals through persuasive and persistent efforts, ensuring these decisions uphold both the short- and long-term sustainability of the business. +* Inspire innovation and spark curiosity, encourage people to be positively disruptive and challenge the status quo. +* Seek collective success above personal glory, strive to ensure a constant culture of inclusion, trust and transparency. +* Lead your direct reports and positively influence the wider organisation as an inspiring people manager in line with our people manager objectives and key results. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location +We have a hybrid-working policy with offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. + diff --git a/handbook/handbook-main/roles/principal_security_engineer.txt b/handbook/handbook-main/roles/principal_security_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..6bc837703e3183547bca53f91bd4bcfb40182154 --- /dev/null +++ b/handbook/handbook-main/roles/principal_security_engineer.txt @@ -0,0 +1,64 @@ +# Principal Security Engineer + +Our Principal Security Engineers enable public sector organisations to mitigate cyber and information security risks across an increasingly complex and threatened mix of technology-enabled services. They provide senior security leadership and support to our clients and teams, build and manage key relationships with clients, manage security and risk across one or more accounts, and support sales. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. Underpinning this is a need for us to do this securely, handling public data safely, and defending against increasing cyber and information security risks. + +As a Principal Security Engineer you will work closely with our clients’ senior leadership to help inform their security strategy and to make sure our teams are delivering secure digital services and cloud-based platforms, aligned to our clients’ risk tolerance. Working alongside delivery, client and other capability principals, you will help shape account plans and be responsible for delivering against them. + +Working with Made Tech's leadership you will make sure our work with customers is aligned to our growth goals and you will play a pivotal role in identifying new opportunities and winning work. Running bid teams, supporting sales teams and developing new business is critical to this role. + +You’ll need to have a drive to deliver outcomes for users and have a desire to mentor teams. You will coach and support Lead Security Engineers to steer their teams towards success. You will also be responsible for hiring and line managing Lead Security Engineers. + +While this is not a hands-on coding technical role, the importance of credibility in internet-era approaches to digital, data and technology in the public sector cannot be understated. You will be expected to maintain a broad technical knowledge of modern cyber security practices, be able to shape security strategy and roadmaps, and hold others to account for technical quality. + +As a security leader within Made Tech you will be expected to maintain and grow your professional network. You will be expected to contribute to thought leadership, content and events and should have a proven track record of doing so. + +## What skills and experience are we looking for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +* Working directly with customers +* Working within a technology consultancy +* Developing a cyber and information security capability or function +* Shaping cyber and information security strategy and managing continuous risk reduction across an organisation, portfolio and/or multiple programmes +* End-to-end security involvement, including governance, risk and compliance, operational security, supply chain security and secure user management +* Identifying security issues in existing system designs, digital services (products) and platforms, including recommending mitigations that balance cost, risk and usability +* Strong understanding of integrating security as part of a multidisciplinary approach to delivering digital services (products) and platforms utilising a DevSecOps approach and enabling Continuous Security as part of wider CI/CD tools and practices +* Up-to-date understanding of, and ensuring compliance to, security standards and regulations including GDS Technology Code of Practice, NCSC Cyber Principles, ISO27001, SoC, NIST, PCI, and GDPR +* Up-to-date understanding of testing the security of software and infrastructure using appropriate security tools including automated cloud-based tooling +* Up-to-date understanding of network security (e.g. OSI, TCP/IP), web application security (e.g. OWASP) and cryptographic controls (e.g. PKI, TLS) +* Up-to-date understanding of identity management and authentication/authorisation products and patterns +* Evidence of self-development – we value keen learners +* Empathy and people skills + + +## Desireable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Leadership of a cyber and information security capability or function +- A relevant cyber and information security qualification (one of: CISSP, SSCP, CISM, CRISC, CAP, CPP, GCHQ-certified Master’s degree in cyber security, or a PhD that is relevant to cyber security) +- Penetration testing qualifications (OSCP, CREST, TIGER or equivalent) +- Working within bid teams to win contracts exceeding value of £1m +- Working with multidisciplinary digital and technology teams +- Working within the public sector +- Experience in hiring, forming and running teams + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/principal_technologist.txt b/handbook/handbook-main/roles/principal_technologist.txt new file mode 100644 index 0000000000000000000000000000000000000000..28b971bbdf69dbc9cf5d865434735ffd67b7b878 --- /dev/null +++ b/handbook/handbook-main/roles/principal_technologist.txt @@ -0,0 +1,57 @@ +# Principal Technologist + +Our Principal Technologists enable public sector organisations to better use technology to improve society. They do this by building and managing strategic relationships, leading accounts, finding new opportunities and advising as a senior technology leader. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society. We help public sector organisations deliver quality software to help citizens get more from public services. We work alongside brilliant public servants to modernise technology and accelerate digital delivery. + +As a Principal Technologist you will work closely with our clients’ senior leadership team to help inform their strategy, and make sure our teams are delivering to a high quality and are aligned to our clients' technology vision. As part of an account team, you will help shape account plans and be responsible for delivering against them. + +Working with Made Tech's regional and group leadership you will make sure our work with customers is aligned to our growth goals and play a pivotal role in identifying new opportunities and winning work. Running bid teams, supporting the wider sales team, and developing new business is critical to this role. + +You’ll need to have a drive to deliver outcomes for users and a desire to mentor teams. You will coach and support Lead Software Engineers to steer their teams towards success. You will also be responsible for hiring and line managing them. + +While this is not a hands-on technical role, the importance of credibility in internet-era approaches to digital and technology in the public sector cannot be understated. You will be expected to maintain a broad technical knowledge of modern software development practices, be able to shape technology strategy and roadmaps, and hold others to account for technical quality. + +As a technology leader within Made Tech you will be expected to maintain and grow your professional network. You will be expected to contribute to thought leadership, content and events, and should have a proven track record of doing so. + +## What experience are we looking for? + +We look for the following experience. But when we’re hiring for this role, if you don’t have some of the experience listed below, don’t let that stop you from applying! + +- Working directly with customers and users +- Working within a technology consultancy +- Strong understanding of agile ways of working +- Strong understanding of software engineering practice +- Strong understanding of cloud technologies +- Evidence of self-development – we value keen learners +- Empathy and people skills + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working within an account or programme leadership team +- Working within bid teams to win contracts exceeding value of £1m +- Working with multidisciplinary digital and technology teams +- Working within the public sector +- Experience in hiring, forming and running software teams +- Experience in legacy application modernisation +- Maintaining a deep working knowledge of technology and programming languages + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/principal_ucp.txt b/handbook/handbook-main/roles/principal_ucp.txt new file mode 100644 index 0000000000000000000000000000000000000000..29f4b81f0fee9a15362c8827670576dd2cdac05a --- /dev/null +++ b/handbook/handbook-main/roles/principal_ucp.txt @@ -0,0 +1,104 @@ +# User-Centred Practice (UCP) Principal + +- Offices: London, Bristol, Manchester, and Swansea +- Salary: Please refer to the job ad when this role is live. +- SFIA: Level 6 +- Minimum of 50% of time billed on client work + +Reporting to one of four Discipline Heads to support with multi-disciplinary account leadership across the four disciplines: +* Product Management and Business Analysis +* Interaction and Service Design +* User Research +* Content Design + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being user centred and product-led can create positive outcomes in the public sector through critical services enabled by technology. + +We are building a community of designers, researchers and product professionals to support the public sector's growing demand for a user-centred, design and product led approach to how services are delivered. + +As a Principal, reporting to the Discipline Head, you’ll enable public sector organisations to better design services that improve society. You will be expected to role model and lead teams with best practice in your discipline and across disciplines and the wider business. + +You will do this by: +* building and managing strategic relationships with our clients +* supporting wider user-centred practice community +* leading accounts +* finding new opportunities +* advising as a senior practice leader + + +As part of all roles at Made Tech, we strive to be: +* client focused +* driven to deliver +* always learning and mentoring others +* acting as ‘One team’ + +## Responsibilities + +Embedding our values into the principal role, you will: +* maintain a broad technical knowledge of user-centred design practices, be able to shape strategy, statements of work and roadmaps +* grow and lead multidisciplinary teams +* work closely with our clients' senior leadership teams to help inform their digital, design and product strategy +* ensure our teams are delivering to a high quality and aligned with our clients' vision. +* have a drive to deliver outcomes for users +* work alongside delivery, client and other capability principals to help shape account plans and be responsible for delivering against them +* be 80-90% client-facing +* coach and support multi-disciplinary teams to steer towards success +* be an active contributor to the UCP Senior Leadership Team alongside Head of UCP and Discipline Heads. + +As a practice leader within Made Tech, you will be expected to maintain and grow your professional network. You will be expected to contribute to thought leadership, content and events and should have a proven track record of doing so. + +You will also be expected to bring discipline-specific experience to client deliver and support project teams with their specific needs. + + +## Skills + +### Skills people must have + +We look for specific skills and experience. If you don’t have some of the experience listed below, don’t let that stop you from applying! + +This includes: +* Existing Security Clearance or eligible for Security Clearance +* Working directly with customers and users +* Worked within a design consultancy or related professional services +* Worked within the public sector +* Strong understanding of agile ways of working +* Strong understanding of user-centred design practice +* Strong understanding of design communities of practice +* Experience in growing and running design teams +* Supporting others to grow and take on more responsibility +* Evidence of self-development – we value keen learners +* Drive to deliver outcomes for users +* Desire to mentor others +* Empathy and people skills + + +### Desirable (not essential) skills + +* Working within an account or programme leadership team +* Working with sales teams to win new work +* Working with multidisciplinary digital and technology teams +* Experience in healthcare +* Working in the open - sharing little and often +* Experience in re-designing legacy services +* Maintain a deep working knowledge of design and research techniques + + +## Key measures + +* Successful relationships with our client partners +* Account growth +* Delivery of good public services for users with clients +* Case studies of how to design and deliver good public services and outcomes + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! + diff --git a/handbook/handbook-main/roles/senior_application_support_engineer.txt b/handbook/handbook-main/roles/senior_application_support_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..d9f3ad6c3b9ae50c96ed0bb7b84b4186b1c0a127 --- /dev/null +++ b/handbook/handbook-main/roles/senior_application_support_engineer.txt @@ -0,0 +1,80 @@ +# Senior Platform Support Engineer + +Delivering technical services to support, maintain and improve live services across the public sector. + +## About the role +As a Senior Platform Support Engineer at Made Tech you will work collaboratively within Managed Service teams onboarding new services without disruption, deliver enhancements, provide ongoing maintenance and support services, as well as continuously improving both digital services and service operations using DevSecOps practices and data-driven user analytics. As a senior member of the team you will have the opportunity to leverage your experience to coach and develop more junior team members, as well as drive improvement across the service line. + +Operating within a managed service environment, you will maintain a range of digital services, data services, and platform offerings. You will maintain application management procedures and documentation and manage application enhancements through to live operation. + +You will be a part of Made Tech’s client facing consultancy team, acting as a point of contact for queries from our clients and providing advice relevant to your area of expertise. You will have the opportunity to influence our clients' solutions, and help to continuously improve services used daily by members of the public. + +## Competencies & Experience +The list below describes specific competencies and behaviours that we will discuss with you during the interview process. + +## Skills and experience +### Must have +* An in depth knowledge of Azure and products such as Azure DevOps, Azure Pipelines, Azure Load Testing and Azure Database for PostgresSQL +* Familiarity with at least one of the following programming languages: .Net, React, Java, Ruby on Rails +* Can articulate the benefits of Infrastructure as Code, including a familiarity with working with Terraform +* Experience of providing 2nd, 3rd and/or 4th tier technical support using ITIL methodologies and terminology +* Hands on experience of designing and implementing application and platform monitoring and alerting solutions to identify and investigate live service issues, as well as auditing existing solutions and prioritising improvements +### Nice to have +* Experience of working with in cross functional teams, that make use of agile techniques and principles +* Managing your work in ServiceNow and/or ZenDesk, as well as configuring ITSM tolling to enable reporting and SLA tracking +* Experience of working in a consulting environment +* Experience working in teams that apply a swarm model of incident management +* A working knowledge of other cloud platforms such as AWS or GCP +* Demonstrate knowledge of SOLID principles, Object-Oriented programming and Test Driven Development (TDD) + +## Responsibilities and competencies +Don’t worry - we don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these competencies as part of your progression in the team. +### Incident and problem management +* Ensuring that all requests for support are dealt with according to a set standards and procedures, and suggesting ways to improve those processes over time +* Delivering resolutions to live incidents within SLA, prioritising service availability +* Taking the lead in problem investigation/root cause analysis and delivering resolutions that prevent recurrence and minimise technical debt +* Providing out of hours support where necessary - shifts managed via on-call rota +* Interpreting the client security standards and best practice such as NCSC guidance, then implementing process and tools that allow the team to respond to security incidents in compliance +* Providing guidance to users and 1st line support agents — including enhanced levels of support following new/updated software releases +### Service monitoring and maintenance +* Design monitoring and dashboarding solutions that are aligned to the needs of users and client strategic priorities +* Automating the monitoring of application performance including the setting up of cloud and application level monitoring tooling +* Implementing ongoing improvements to monitoring, logging and the continuous review of alerting thresholds +* Updating documentation such as knowledge base articles, playbooks and service definitions +* Implementing processes that maintain application data, backups and ensuing appropriate recovery processes are in place to meet data retention needs +* Using user monitoring, performance data and service dashboards to inform continuous improvement backlog items and prioritise technical debt removal +* A detailed knowledge of database installation, integration, configuration, maintenance, security, performance and capacity management. +* Able to leverage that knowledge to support planned changes and resolve live incidents. +* Maintaining infrastructure, ensuring compliance, upgrading live services and right-sizing with a focus on both cost and sustainability +* A detailed understanding of DNS management including records, zones, security, performance and load balancing. Able to diagnose and resolve DNS issues and develop processes that reduce manual effort required for DNS management +### Application and platform development +* Implementing application enhancements including the development of new code and sourcing existing code from open code libraries +* Implementing application enhancements to improve business performance, applying a holistic product lens to services +* Design, build and maintain CI/CD pipelines including automated testing supporting multiple environments +* Ensuring application code complies with data protection requirements, security regulations and policy standards as mandated by either the client or the team lead +* Collaborating with technical subject matter experts (SMEs), security operations and user research to ensure user-centred high quality outcomes +* Estimating time and effort required for software development, and reviewing the quality of estimating to fine tune forecasting over time +* Applying TDD, ensuring appropriate test coverage and evidencing the outcomes of testing +### Service onboarding and transition +* Taking part in proactive knowledge transfer activities with incumbent suppliers +* Code review and quality analysis including the review of complete services, including the implementation of code scanning tooling +* Reviewing and improving technical documentation such as architecture overviews, deployment process definition and incident resolution runbooks +* Onboard new services onto an IT Service Management tool, including configuring users and integrating alerting tools +### Learning and development +* Being an active member of Made Tech’s communities of practice, sharing knowledge and learning from others +* Investing in yourself and your skills by adapting to the needs of our clients and learning about emerging technologies that are relevant to the services we provide +* Taking a proactive interest in the work being done across Made Tech and supporting colleagues where possible e.g. providing inputs to case studies based on your project experience or pairing with someone in another team +* Be a mentor and coach to others across the service line, sharing expertise and taking an active role in the professional development of others + + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +## Salary and location + +We adopt a hybrid approach and anticipate that most roles will spend a mixture of time within our offices, client sites and working remotely. We have offices in London, Bristol, Manchester, and Swansea and our clients are across the UK. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. diff --git a/handbook/handbook-main/roles/senior_business_analyst.txt b/handbook/handbook-main/roles/senior_business_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..de069a46fc1008bd18872d40d03fc141ccab8972 --- /dev/null +++ b/handbook/handbook-main/roles/senior_business_analyst.txt @@ -0,0 +1,79 @@ +# Senior Business Analyst + +Senior Business Analysts help teams deliver products and services that bring value to their users through: + +- Identifying business problems and opportunities +- Conducting research to understand the public sector domain, people, organisation, processes and technology +- Explore, elicit and analyse business and user needs +- Identify areas for improvement and explore feasibility of options +- Understand any business and policy constraints that need to be considered, and assess the implications + + +# Key responsibilities + +## Scope + +A senior business analyst has a good understanding of strategic levels of analysis and typical leads on larger or more complex projects. +At this role level, you will: + +- Investigate operational requirements, problems, and opportunities, seeking effective business solutions through improvements in automated and non-automated components of new or changed processes. +- Assist in the analysis of stakeholder objectives, and the underlying issues arising from investigations into business requirements and problems, and identifies options for consideration. +- Work with stakeholders, to identify potential benefits and available options for consideration, and in defining acceptance tests. +- Contribute to selection of the business analysis methods, tools and techniques for projects; selecting appropriately from predictive (plan-driven) approaches or adaptive (iterative/agile) approaches. + +Senior Business Analysts should expect to work more autonomously and may often be the only business analyst on an assigned project. + + +## Competencies + +Senior Business Analysts display [Made Tech’s values](https://github.com/madetech/handbook/blob/main/company/about.md), relevant [DDaT capabilities](https://www.gov.uk/guidance/business-analyst--2#:~:text=Skill%20level%3A%20working-,Senior%20business%20analyst,system%20in%20a%20project%20or%20programme%20of%20work.%20(Skill%20level%3A%20practitioner),-Lead%20business%20analyst) and [SFIA (Level 4)](https://sfia-online.org/en/sfia-8/responsibilities/level-4) behaviours. + +## Skills needed for this role + +Applies the following practices as a Senior Business Analyst, within an engagement: + +- Agile working, identify and compare the best processes, evaluate outcomes, help teams manage and prioritise work. +- Business analysis, advise on identifying, analysing and communicating complex business problems, inform decision making and recommend solutions that align with goals and objectives. +- Business modelling, lead the modelling of processes, systems and data across a project or programme. +- Business process improvement, identify and lead the implementation of process and business changes to improve operations and services, assess feasibility and recommend new approaches. +- Business process testing, lead the evaluation of business process tests and usability within a project or programme. +- Methods and tools, build capability in methods and tools and ensure they are consistently adopted and used effectively. +- Requirements definition and management, advise on requirements management, define the most appropriate methods and co-ordinate prioritisation. +- Stakeholder relationship management, lead stakeholder communication, build relationships and resolve conflicts +- Systems analysis, lead the identification and analysis of IT system capabilities, and design system and user interfaces. +- Testing (business analysis), recommend the value of testing, advise on business scenarios and review testing outcomes. +- User experience analysis, advise on user experience needs, recommend analysis techniques and articulate how they affect system design. + + +## Community of Practice (CoP) + +Engages and participates within the Made Tech and client communities of practice to: + +- build an inclusive and supportive culture +- recognise when to ask for further guidance and support and identify how to improve how we work, for example, by discussing and sharing approaches, ideas and examples of practice +- initiate and lead on work within the community of practice +- mentor and coach others within the community, to support their development and practice + +## Sales + +Senior Business Analysts collaborate with Lead Business Analysts to provide feedback on whether they feel their engagements are effective, efficient and profitable. + +## Key measures + +- Delivery of good public services for users with clients, shown through relevant measures, for example, data, metrics, KPIs or the passing of service standards +- Personal performance is aligned with DDaT and SFIA grade, evidenced through peer feedback + +## Work perks and benefits +Take a look at the [Benefits & Perks](https://github.com/madetech/handbook/blob/350005eb3769ef05338461af6413e4553aee54b2/benefits/made_tech_benefits_box.md) section to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_content_designer.txt b/handbook/handbook-main/roles/senior_content_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..69594aca1e46eb4737b0544f08f8e9e8017573c2 --- /dev/null +++ b/handbook/handbook-main/roles/senior_content_designer.txt @@ -0,0 +1,70 @@ +# Senior Content Designer + +* Location: mainly remote with occasional office and client visits +* Offices: London, Bristol, Manchester, and Swansea +* Salary: Please refer to the job ad when the role is live. +* SFIA: Level 4 + +## Summary + +Made Tech wants to positively impact the future of the country by using technology to improve society. We believe being design-led can create positive outcomes in the public sector, through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +Our Senior Content Designers are strong practitioners who work with minimal support and can influence and mentor others to design and deliver public services. They do this by setting the direction, assuring the quality of design delivery within a team working a complicated and large scale service. They are vocal and visible contributors to a healthy user-centred design (UCD) community and culture at Made Tech. + + +## Key responsibilities + +### Scope + +- Responsible to the Lead Content Designer for successfully designing and delivering good public services +- Hands-on content design and design leadership for one product/team +- Acts as the content design subject matter expert on a product team, facilitating the design process and communicating design decisions to the team and stakeholders +- Considers strategic approaches to design +- Concerned about design and product practices within Made Tech +- Works with full autonomy and work doesn’t need to be reviewed +- Contributes to and may lead communities of practice, discussing and sharing suggestions, approaches and ideas - including proactively seeking feedback on own work +- May mentor and coach within the design community and line manage designers + +### Practice + +- Turn team conversations and research into user-centred content to create a shared understanding of problems to solve and ideas to test +- Make things real, by caring about content enough to ensure everyone can use public services +- Make public services simple to explain and understand, by removing complexity and keeping designs focused on creating outcomes for people and society + +### Leading teams + +- Assure the quality of content delivery within your team +- Show teams by doing, good habits for sharing and improving content + +### Community + +- Line management of content designers +- Support the hiring and onboarding of content designers +- Help define Made Tech design principles through delivering good public services +- Help establish a design studio culture at Made Tech and client offices + +## Key measures + +- Delivery of good public services for users with clients +- Case studies of how to design and deliver good public services and outcomes +- Growth and happiness of UCD community at Made Tech + +## Competencies + +- Client Focus +- Drive to Deliver +- Learning and Mentoring +- Experienced in their Profession +- Facilitation +- Thinking through Making + +## Work perks and benefits +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! + diff --git a/handbook/handbook-main/roles/senior_data_analyst.txt b/handbook/handbook-main/roles/senior_data_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..a9926854c4c5b9055301dd6e7941003085870871 --- /dev/null +++ b/handbook/handbook-main/roles/senior_data_analyst.txt @@ -0,0 +1,91 @@ +# Senior Data Analyst + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. A key component of this is developing modern data systems and platforms that drive informed decision-making for our clients. You will also work closely with clients to help shape their data strategy +As a Senior Data Analyst, you may play one or more roles according to our clients' needs. The role is very hands-on and you'll support as a senior contributor role for a project, focusing on: + +- **Data analysis and reporting**: Conducting in-depth data analysis, generating reports, and providing actionable insights for client projects. +- **Data and BI visualisation**: Producing BI dashboards using industry-standard tools - Power BI, Tableau, Quicksight etc +- **Client interaction**: Collaborating with clients to understand their needs, translating these into analytical solutions, and presenting findings in a clear, actionable manner. +- **Mentoring** junior analysts, leading data-focused projects, and setting best practices in data analysis + +You’ll need to have a drive to deliver outcomes for users. You’ll make sure that the wider context of a delivery is considered and maintain alignment between the operational and analytical aspects of the engineering solution. + +## What skills and experience are we looking for? + +### Technical Skills + +**Analysis and synthesis** + +- Application of analytical techniques: Proficiency in applying various analytical methods such as statistical analysis, data mining, and qualitative analysis. Ability to select and apply appropriate techniques based on the context and research data. +- Synthesis of research data: Experience in synthesising research data to present actionable insights and solutions. Ability to articulate the impact of their analysis on decision-making and problem-solving. +- Engagement with sceptical colleagues: Effective communication and persuasion skills to engage and gain buy-in from sceptical colleagues. Ability to foster collaboration and address concerns to ensure adherence to best practices. +- Advisory and critique skills: Capability to advise on the choice and application of analytical techniques and critique colleagues' findings to ensure high standards in data analysis. + +**Data Management** + +- Understanding of data sources and storage: Knowledge of various data sources, data organisation, and storage practices. Commitment to maintaining data integrity and accessibility. +- Advocacy for data governance: Experience in advocating for data governance standards and influencing team adherence to data quality practices. +- Continuous improvement: Ability to communicate and implement continuous improvements in data management practices through documentation, training, and regular team engagement. +- Toolset management: Proficiency in defining and supporting common toolsets for data management, ensuring efficiency and seamless integration. +- Automation of data management: Experience in automating data management activities to streamline processes and increase accuracy. (desirable) +- Compliance with data governance policies: Understanding and ensuring compliance with data governance policies, maintaining data security and ethical standards. + +**Data modelling, cleansing, and enrichment** + +- Data modelling expertise: Proficient in conceptual, logical, and physical data modelling. Ability to adhere to data modelling standards and best practices. +- Data cleansing and standardisation: Experience in resolving data quality issues and ensuring data accuracy through cleansing and standardisation techniques. +- Use of data integration tools: Skilled in using ETL tools for data integration and storage. Ensures data interoperability with other datasets. +- Collaboration with data professionals: Experience collaborating with other data professionals to improve modelling and integration standards and patterns. + +**Data Visualisation** + +- Interpretation of requirements: Ability to interpret data visualisation requirements and create meaningful, visually appealing representations tailored to the audience. +- Proficiency in visualisation tools: Experience with tools such as Tableau, Power BI, and Python libraries like Matplotlib and Seaborn. Knowledge of selecting appropriate visualisation types. +- Application of visualisation standards: Application of design principles to create clear, accurate, and accessible visualisations. Awareness of accessibility considerations. +- Mentorship in visualisation: Experience in reviewing and advising junior members to improve the quality and efficiency of data visualisations. + +**Data Quality Assurance, Validation, and Linkage** + +- Data quality assurance: Experience in implementing processes for data quality assessment and improvement, including data profiling, cleansing, and standardisation. +- Data validation and linkage: Ability to perform data validation checks and integrate data from various sources to ensure consistency and accuracy. +- Data cleansing and preparation: Proficiency in defining data cleansing processes and preparing data for analysis by handling missing values, outliers, and duplicates. +- Communication of data limitations: Skilled in articulating data constraints and limitations to stakeholders, providing context for informed decision-making. +- Peer review and quality control: Experience in conducting peer reviews to validate data outputs, ensuring high standards of accuracy and reliability. + +**Statistical Methods and Data Analysis** + +- Knowledge of statistical methodologies: Proficient in various statistical methods, such as hypothesis testing, regression analysis, clustering, and time series analysis. Ability to select appropriate techniques based on project requirements. +- Data analysis and interpretation: Experience in using statistical software or programming languages to perform data analysis and generate insights. Skilled in communicating findings to technical and non-technical stakeholders. +- Application of emerging theory: Willingness to explore and apply new statistical methodologies or practices to solve practical problems and adapt to emerging theories. + +### Business Skills + +**Communication** + +- Stakeholder communication: Experience in effectively engaging with a diverse range of stakeholders, including technical and business individuals. Ability to manage expectations and facilitate productive discussions. +- Active and reactive communication: Proficiency in handling both proactive communication (updates, insights) and reactive communication (responding to inquiries, addressing concerns) to maintain a collaborative atmosphere. +- Interpretation of stakeholder needs: Ability to understand and translate stakeholder requirements into technical solutions. Experience in bridging the gap between technical and non-technical stakeholders. +- Presentation and sharing of insights: Skilled in presenting complex data in a clear, understandable manner tailored to diverse audiences, including senior management. + +**Logical and creative thinking** + +- Problem-solving approach: Ability to apply logical and creative thinking to resolve complex problems by breaking them down and generating innovative solutions. +- Decision-making and action-taking: Skilled in making informed decisions, prioritising tasks, and taking appropriate actions to resolve issues efficiently. +- Adaptability and learning orientation: Demonstrates adaptability in strategies and a commitment to continuous learning and improvement. +- Interpretation of stakeholder needs: Ability to understand and translate stakeholder requirements into technical solutions. Experience in bridging the gap between technical and non-technical stakeholders. +- Presentation and sharing of insights: Skilled in presenting complex data in a clear, understandable manner tailored to diverse audiences, including senior management. + +## Work perks and benefits +Take a look at the Benefits & Perks section of the Made Tech Handbook to see what we can offer you. + +## Salary and location +We mainly work remotely but you may need to visit clients or visit the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_data_engineer.txt b/handbook/handbook-main/roles/senior_data_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..208d03979fcae11b77c00a448d5714b0c80eac3d --- /dev/null +++ b/handbook/handbook-main/roles/senior_data_engineer.txt @@ -0,0 +1,57 @@ +# Senior Data Engineer + +Our Senior Data Engineers enable public sector organisations to embrace a data-driven approach by providing data platforms and services that are high-quality, cost-efficient, and tailored to clients’ needs. They develop, operate, and maintain these services. They make sure they provide maximum value to data consumers, including analysts, scientists, and business stakeholders. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-driven and freed from legacy technology. A key component of this is developing modern data systems and platforms that drive informed decision-making for our clients. You will also work closely with clients to help shape their data strategy. + +As a Senior Data Engineer, you may play one or more roles according to our clients' needs. Sometimes the role is very hands-on and you'll support in a senior contributor role for a project, focusing on both delivering engineering work as well as upskilling members of the client team. At other points, you might play more of a technical architect role. + +You’ll need to have a drive to deliver outcomes for users. You’ll make sure that the wider context of a delivery is considered and maintain alignment between the operational and analytical aspects of the engineering solution. + +As a senior member of the data capability within Made Tech, you will also participate in our hiring process and continued development of the team, as well as representing us internally, and publicly via presentations. You will also line-manage members of the team up to the mid level. + +You will need to be comfortable sharing your knowledge and skills with others. We'd love to hear some examples of times you’ve mentored, coached, and contributed to the growth of team members. Maybe you’ve written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + +## What skills and experience are we looking for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +- Working directly with clients and users +- Good understanding of the possible architectures involved in modern data system design (e.g. warehouses, lakes and meshes) +- Designing and implementing efficient data transformation processes at scale, both in batch and streaming use cases +- Owning the cloud infrastructure underpinning data systems through a DevOps approach +- Agile practices such as Scrum, XP, and/or Kanban +- Showcasing and presentation skills +- Evidence of self-development – we value keen learners +- Empathy and people skills + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working at a technology consultancy +- Pair programming +- Working with data scientists to productionise advanced data deliverables, such as machine learning models +- Infrastructure-as-code (e.g. Terraform, Cloud Formation) +- Working knowledge of statistics +- Working with multidisciplinary digital and technology teams +- Working within the public sector + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) +to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_data_scientist.txt b/handbook/handbook-main/roles/senior_data_scientist.txt new file mode 100644 index 0000000000000000000000000000000000000000..aca74590dff19e33afc373b07603e4c6c7e3fdfd --- /dev/null +++ b/handbook/handbook-main/roles/senior_data_scientist.txt @@ -0,0 +1,64 @@ +# Senior Data Scientist + +Our Data Scientists enable public sector organisations to unlock the value and the potential of their data, extracting insights and helping organisations to make informed decisions. They collaborate closely with our clients in all aspects of the project - from understanding the data, to interpreting model's output and model deployment. They seek to provide reliable answers and deliver maximum value to stakeholders. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the government by using technology to improve society, for everyone. We want to empower the public sector to deliver and continuously improve digital services that are user-centric, data-supported and freed from legacy technology. A key component of this is developing modern data systems that enable informed decision-making for our clients. + +As a Data Scientist, you may play one or more roles according to our clients' needs. You could be working closely with clients to help shape their data strategy alongside our data engineers. At other times the role can be very hands-on, and you'll serve in a senior contributor role to projects, focusing on both delivering data science solutions and upskilling members of the client team. Sometimes, you might have to play the role of an advisor, suggesting to clients how data science is done and helping them set up their data science environment. At other times you will be working with the other members of data engineering teams and performing exploratory data analysis. + +As a senior member of the data capability within Made Tech, you will also participate in our hiring process and continued development of the team, as well as representing us both internally to the organisation and publicly. You will also line-manage members of the team up to the mid-level. + +You’ll need to have a drive to deliver outcomes for users. You’ll need to be comfortable sharing your knowledge and skills with others. We'd love to hear some examples of times you’ve mentored, coached, and contributed to the growth of team members. Maybe you’ve written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + +## What skills and experience are we looking for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +- Working directly with clients, users and data engineers +- Good understanding of linear algebra (vectors, matrices, tensors etc.) and statistics (probability distributions, probability, bayesian stats etc.) +- Good working knowledge of Python +- Implementing end-to-end ML pipelines +- Hand-on experience in Python data science ecosystem (e.g. numpy, scipy, pandas, scikit-learn, matplotlib etc.) +- Deep Learning frameworks (TensorFlow or PyTorch) +- Popular classification and regression techniques +- Unsupervised learning & matrix factorizations algorithms +- Feature engineering & feature extraction +- Natural Language Processing (NLP) and document processing +- Knowledge of popular DL architecture (CNNs, RNNs etc) +- Performing model selection and evaluation +- Knowledge of cloud (AWS/Azure/GCP) +- Showcasing and presentation skills +- Evidence of self-development – we're value keen learners +- Empathy and people skills + +## Desirable experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working at a consultancy +- Agile practices such as Pairing, Scrum, XP, and/or Kanban +- Working with data engineering teams to integrate data from various sources +- Working knowledge of source code repository (GitHub, BitBucket etc) +- Knowledge of SparkML +- Working with multidisciplinary digital and technology teams +- Working within the public sector + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) + to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! + diff --git a/handbook/handbook-main/roles/senior_delivery_manager.txt b/handbook/handbook-main/roles/senior_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..5d752df375cb7a6ecdf3a8a7b53dbcb365b8c9d4 --- /dev/null +++ b/handbook/handbook-main/roles/senior_delivery_manager.txt @@ -0,0 +1,124 @@ +# Senior Delivery Manager + +Our Senior Delivery Managers lead digital projects. They make sure our clients have positive experiences and achieve great outcomes. They also make sure our teams deliver to their full potential. + +## Your role at Made Tech +Senior Delivery Managers are accountable for successful project delivery. Normally working within one or two teams, you will promote effective cross-functional delivery by building motivated, collaborative delivery teams. You will use agile methodologies, with additional processes for managing dependencies, supporting risk mitigation and resolution, and managing the project scope and budget. + +You will work as part of a cross functional delivery team, which may include client stakeholders and partner agencies. You will personify servant leadership, promoting a collaborative approach to make sure the project delivers the desired outcomes for users and clients, working together to identify and manage risks and issues that arise. You will be empowered to solve problems that arise independently, but will be supported by a Lead or Principal Delivery Manager when needed. You will build effective working relationships with client stakeholders, and are the go-to person for questions about the delivery of a project. + +You will have a good understanding of agile delivery, and are able to work with a team and client stakeholders to determine the delivery methodology that will best work with the needs of the project (for example Scrum, or Kanban). You will help build trust with stakeholders and guide clients throughout the delivery process using your influence to continuously iterate and approve team processes. You will work with a Product Manager to define and deliver against a roadmap in order to monitor whether the project is on track and support conversations about priority, scope and budget. + +You understand that you will get out what you put into the organisation you work in, so you look for ways to contribute to Made Tech beyond the scope of your delivery. This could include participating in and contributing to the Delivery Community of Practice (COP), managing the performance and development of a number of Delivery Managers and supporting recruitment activities. You may also contribute to other areas of the business, for example learning and development or marketing. + +## Definition of success + +Success as a Senior Delivery Manager is predominantly measured by delivering successful outcomes to our clients, but is also assessed through contribution to Made Tech as an organisation, and effective line management where appropriate. + +### Expected outcomes +* Effective quality and risk management +* Accountable for ensuring accurate and timely adherence to all critical business processes within the delivery +* Balance client satisfaction and team happiness with Made Tech’s commercial goals +* Contribute to the Delivery Community of Practice +* Contribute to growing Made Tech’s impact +* Accelerate the career of other Delivery Managers through line management, coaching and mentoring, and knowledge sharing + +### KPIs +* Quality +* Risk +* Project Gross Profit Margin (GPM) +* Forecast accuracy +* Invoice accuracy + +## Responsibilities + +Senior Delivery Managers are responsible for delivering the above outcomes by collaborating with other members of the Delivery Management Organisation, their Account Management Team, team members, client stakeholders and internal business partners e.g. scheduling, hiring. + +### Project Level Delivery Assurance +* Accountable for ensuring delivery success, including scope, budget and quality +* Report to Heads of Delivery on a weekly basis the status of quality and risk +* Manage team resourcing to balance successful client delivery, team happiness and Made Tech commercial objectives +* Ensure compliance and accuracy of all critical business processes (time sheeting, invoicing, forecasting, delivery assurance reporting) +* Support commercial activities (Statements of Work, purchase order numbers, supplier contracts for partners, IR35 assessments for contractors, raising staffing demands) + +### Hiring and Careers +* Support hiring activities including interviewing and outreach +* Management of Delivery Managers including performance, progression and satisfaction (where appropriate) +* Ensure regular feedback (constructive and/or appreciative) is shared with all individuals working on your projects + +### Growing Made Tech’s Impact +* Ensure your clients are motivated to bring repeat business and recommend our services to others +* Identify opportunities for Made Tech to deliver value for the client beyond the current project +* Build relationships with stakeholders within your project, and engage with other experts in the organisation for example at the client Community of Practice + +### Community and Thought Leadership +* Share successes and failures with the Delivery Community to support the evolution of ways of working, techniques, and technologies across Made Tech +* Contribute to developing a thriving community of practice and shared identity + +## Competencies and behaviours +Senior Delivery Managers are expected to be operating at, or working towards, [SFIA level 4](https://sfia-online.org/en/sfia-8/responsibilities/level-4) in all five competencies. In addition to this, the below list describes specific competencies and behaviours that you’ll need in this role. + +Don’t worry - we don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these competencies on your way to promotion. + +### Articulation and role modelling of Made Tech values, purpose, and vision +* Describe each with examples +* Demonstrate role modelling + +### Commercial awareness +* Articulate project commercial fundamentals (Statements of Work, Purchase Orders, Gross Profit Margin, Forecasting, Burndown) +* Describe how they are supporting commercial activities within their delivery +* Be able to demonstrate that the team is on track to meet the deliverables defined in the SOW +* Be able to recall and describe key Made Tech case studies, including where you were not directly involved in the project + +### Time management and prioritisation +* Demonstrate prioritisation and time management + +### Performance management + +* Demonstrate fast remediation of performance issues, including highlighting issues to the relevant capability lead and requesting support where necessary* +* Demonstrate encouragement of high performers, to support them towards successful promotions +* Maintain compliance with all expectations of line management at Made Tech, with support +* Demonstrate providing regular feedback for team members + +Note: not all SDMs will be line managers, but this will not impact assessment of performance + +### Effectively manage delivery risk and quality +* Demonstrate risk management activities including identification, assessment, mitigation, assessment and reporting to key stakeholders, with support as required +* Demonstrate activities to ensure that delivery teams have appropriate practices in place to define and meet required quality levels, with support as required +* Articulate approach to managing budget and burndown within the project, being able show how this is being managed + +### Coach teams to successfully deliver projects +* Articulate the benefits and use cases of a variety of delivery approaches, methods and tools - for example Kanban, Scrum, and Waterfall. +* Demonstrate collaborating with capability experts (e.g. Lead Engineer / Lead Designer) to ensure deliveries adhere to best practices such as Security, DevOps, User Centred Design and Data Ethics +* Be able to explain the purpose of each phase of the GDS Service Manual +Demonstrate knowledge of where to find and how to use the GDS service standard +* Be able to explain the Roles and Responsibilities of all of the roles that Made Tech employs +* Be able to describe the Made Tech propositions, and articulate where to go or who to speak to learn more about these +* Demonstrate advocacy of best practice delivery with teams and clients + +### Facilitation and communication +* Demonstrate experience of running ceremonies and facilitating meetings - with post meeting feedback +* Demonstrate experience of presenting information to stakeholders using reports or presentations +* Demonstrate experience in teaching someone about agile delivery + +### Trust building with your seniors, peers, juniors and client stakeholders +* Demonstrate with feedback from seniors, peers, juniors and client stakeholders + +### Continuous improvement and feedback +* Demonstrate positive response to feedback with course correction + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_designer.txt b/handbook/handbook-main/roles/senior_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..5a6cd31535a87892fe689b4d14add3312282bf03 --- /dev/null +++ b/handbook/handbook-main/roles/senior_designer.txt @@ -0,0 +1,87 @@ +# Senior Designer + +- Location: mainly remote with occasional office and client visits +- Offices: London, Bristol, Manchester, and Swansea +- Salary: £38,250 - £72,250 with a London-weighting of £40,162 - £75,862 +- SFIA: Level 4 + +Senior Designers at Made Tech are senior specialists in their design discipline(s). In this case, we’re looking for an expert practitioner in Interaction and Service Design who is able to coach, mentor and supervise other designers within the Interaction and Service Design discipline at Made Tech. Success in this role means guiding the work of other designers within the Interaction and Service Design disciplines to deliver positive outcomes. + +## Summary + +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design-led can create positive outcomes in the public sector through critical services enabled by technology. We’ve built a community of designers and researchers to support the public sector's growing demand for a design-led approach to service delivery. + +Our Senior Designers are strong practitioners who work with minimal support and can influence and mentor others to design and deliver public services. They do this by setting the direction and assuring the quality of design delivery within a team working on complicated and large scale service. They are vocal and visible contributors to a healthy user-centred design (UCD) community and culture at Made Tech. + +Senior Interaction and Service Designers at Made Tech: + +**Are Senior practitioners** +- Able to develop new and novel approaches to highly complex design challenges, based on fundamental interaction and service design principles. +- Advocate for the Interaction and Service Design practice internally and externally. Able to coach and mentor others, and define the interaction and service design standards which others will apply. Influences the organisation, clients, partners and peers on the contribution of interaction and service design. +- Develop a wide breadth of knowledge across the industry or business. + +**Take the initiative and are fully responsible for their own outcomes** +- Work is often self-initiated. Able to define an approach from first principles, and propose alternative ways to deliver. +- Fully responsible for meeting objectives on an engagement. + +**Contributes to overall interaction and service design outcomes of engagement** +- Understand the relationship between interaction and service design, other disciplines, and wider client organisational requirements. +- Defines what ‘good’ interaction and service design looks like on an engagement, enabling and holding others to account for producing high quality outputs and deliverables +- Establish milestones and have a significant role in the assignment of tasks and/or responsibilities. Makes decisions which impact the success of assigned work, i.e. results, deadlines and budget. +- Supports client collaboration throughout all stages of work. Ensures users’ needs are met consistently through each work stage. + +**Highly accountable** +- Comfortable with owning a problem and are committed to seeing it through to resolution +- Actively look to deliver a positive outcome, even if they can’t personally do it + +**Have a growth mindset** +- Always willing to learn and develop + +**Candid-but-kind communicators** +- Give feedback often +- Understand that a balance of positive and constructive feedback is the most effective way to work +- Comfortable having difficult conversations + +## Key responsibilities + +## Scope + +- Responsible to a Lead Designer for successfully designing and delivering good public services +- Hands-on design and design leadership for one product/team +- Acts as the design subject matter expert on a product team, facilitating the design process and communicating design decisions to the team and stakeholders +- Considers strategic approaches to design +- Concerned about design and product practices within Made Tech +- Works with full autonomy and work doesn’t need to be reviewed +- Contributes to and may lead communities of practice, discussing and sharing suggestions, approaches and ideas - including proactively seeking feedback on own work +- May mentor and coach within the design community and line manage designers + +## Practice + +- Turn team conversations and research into drawings and prototypes to create a shared understanding of problems to solve and ideas to test +- Make things real by caring about content and interaction design enough to ensure everyone can use public services +- Make public services simple to explain and understand by removing complexity and keeping designs focused on creating outcomes for people and society + +## Leading teams + +- Assure the quality of design delivery across multiple teams +- Introduce good habits for sharing and improving design work into teams + +## Community + +- Line management of designers +- Support the hiring and onboarding of designers and researchers +- Help establish a design studio culture at Made Tech and client offices + +## Key measures + +- Delivery of good public services for users with clients +- Case studies of how to design and deliver good public services and outcomes +- Growth and happiness of the UCD community at Made Tech + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_product_manager.txt b/handbook/handbook-main/roles/senior_product_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..dd65074a2641359968d475f256ffab5d731ed64f --- /dev/null +++ b/handbook/handbook-main/roles/senior_product_manager.txt @@ -0,0 +1,54 @@ +# Senior Product Manager + +Reporting to one of our Lead Product Managers, this role is responsible for leading on product within a client delivery team. + +## Summary +Made Tech wants to positively impact the country's future by using technology to improve society. We believe being design and product-led can create positive outcomes in the public sector through critical services enabled by technology. We are building a community of designers, researchers and product professionals to support the public sector's growing demand for a user-centred, design and product led approach to how services are delivered. + +As a Senior Product Manager, you’ll enable public sector organisations to better design services that improve society. You will be expected to role model and lead teams with best practice in your discipline. + +You will work as part of cross-functional teams which might include other Made Tech team members, stakeholders and partner agencies. You will inspire trust in the team, guide and coach teams through the product process and use your influence to continuously iterate and improve ways of working and processes. + + +## Responsibilities + +* You will be expected to work in a self initiated manner, but with support of senior team members, and in a collaborative and inclusive manner +* Collaborate with and influence the wider Made Tech team and our clients to deliver high quality work aligned with our customers vision and needs +* Influence decision making which impacts the success of the team. This might include scoping work, prioritisation, deadlines, budgets and evaluating risk +* Work across one assignment for a client at one time +* Coach, support and people manage more junior members of the Product team. To steer and coach them towards successful delivery for our clients, enabling them and holding them accountable for producing high quality outputs and deliverables +* Maintain a broad technical knowledge of product management, and continue to develop knowledge of user-centred design and technical practice. Assist and be able to shape strategy, proposals, statements of work and roadmaps +* Contribute to Made Tech’s community of practice for Product and collaborate with other disciplines +* Assist in developing and growing the discipline in line with business and capability needs, ensuring we embed the Made Tech way of product-led and design thinking into all that we do + +## Skills people must have + +* Excellent understanding and articulation of the value of product and user-centred design +* Experience and evidence of delivering user centred products and services from ideation through to maintenance phases +* Ability to support and coach others to grow their skills, product capabilities and to take on more responsibility for client-facing projects +* Able to educate and mentor team members, colleagues and peers in the wider business on developing product and agile delivery as a core discipline +* Experienced in working directly with customers and users, and able to drive teams to deliver excellent outcomes for users +* Working within a design consultancy/senior product leadership role in the public sector, health or allied areas +* Strong empathy and relationship building skills + +At this point, we hope you're feeling excited about Made Tech and the opportunity. Even if you don't feel that you meet every single skill, we still encourage you to apply. Get in touch with our talent team if you’d like an informal chat about the role and your suitability before applying. + +## Desirable (not essential) skills + +* Working with sales teams to build client relationships, develop opportunities and win new work +* Working in the open - building the trust within teams to share little and often +* Experience in re-designing legacy services and products +* Maintaining a deep working knowledge of product,design and research techniques +* Experience in line management + +## Salary and location + +We work in a hybrid manner with on-site requirements for in-person presence when considered most beneficial for the activity (team meetings, workshops, onboarding for example). You may also need to visit clients where on-site requirements are necessary and/or beneficial. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at careers@madetech.com. We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_software_engineer.txt b/handbook/handbook-main/roles/senior_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..478425191906052df821e7db613bfc90123d6a56 --- /dev/null +++ b/handbook/handbook-main/roles/senior_software_engineer.txt @@ -0,0 +1,71 @@ +# Senior Software Engineer + +Our Senior Software Engineers create digital, data and technology outcomes that improve society. They do this by delivering and architecting software, and coaching others in public sector organisations to do the same. + +## Your role at Made Tech + +At Made Tech we want to positively impact the future of the country. We help public sector organisations deliver quality software to help citizens get more from public services. We work alongside brilliant public servants to modernise technology and accelerate digital delivery. + +As a Senior Software Engineer you will combine your technical excellence, drive to deliver and coaching skills to achieve great outcomes for our clients and their users, and establish strong engineering cultures within organisations. + +You will have the opportunity to work across a variety of technologies and will need to be comfortable doing so. Our teams have used Ruby with Rails and Sinatra, ES6 with React and Angular, C# with .NET Core, Java with Spring, Python with Django, and plenty more stacks. We don’t limit ourselves as a company to particular technologies and we expect all of our engineers to be keen on learning new skills. + +High-performing software delivery teams need to be empowered to iteratively and rapidly deliver changes all the way through to production. To do this we combine our extensive cloud automation knowledge with DevOps culture. + +We've been using AWS from the start and as Advanced Partners we’re go-to experts within the public sector. We use a range of IaaS, PaaS and FaaS depending on the needs of our users, in this case software teams, such as EC2, Lambda, ECS, Kubernetes, Heroku, CloudFoundry, Azure App Services, and more. We use VPC and PrivateLink for connecting to on-premise, legacy systems. We also use API Gateway, S3, CloudFront, SQS, SNS, SES, RDS, and many other services provided by AWS. You will have the opportunity to use and learn these technologies. We also offer AWS and other cloud training. + +We make sure we document our architecture and infrastructure as code, using technologies such as Terraform and OpenAPI. Containerisation is a big part of empowering our teams to develop, deploy and scale their applications, as is using AWS Lambda and avoiding the complexity of stateful services altogether. + +For us, DevOps is more about culture rather than roles and titles. Even though this role is for someone with strong DevOps experience, the biggest impact you will have is coaching and helping teams use the platforms you build. You won't be building infrastructure in isolation or charged with deploying other people’s work into production. You'll empower teams with the mantra, “you build it, you run it”! + +We have a team of polyglot programmers (which you might already consider yourself to be), who are versed in a mix of paradigms such as object-oriented, functional, declarative, event-based and aspect-oriented. You will need to be comfortable sharing your knowledge and skills with others. We’d love to hear some examples of where you’ve mentored, coached, and contributed to the growth of team members. Maybe you’ve written some blog posts about your discipline, or perhaps even delivered a talk or two that you’d like to share. + +## What skills and experience do we look for? + +We look for the following skills and experience. But when we’re hiring for this role, if you don’t have some of the skills and experience listed below, don’t let that stop you from applying! + +- Writing code with tests +- Delivery in an agile environment +- Working with more than one programming language +- Working with databases +- Working with APIs +- Working with a cloud platform such as AWS, GCP and/or Azure +- Debugging experience with a range of systems +- Evidence of self-development – we value keen learners +- Empathy and people skills + + +## Desirable skills and experience + +Experience in the following things isn’t essential, but it’s highly desirable! + +- Working at a technology consultancy +- Working directly with customers and users +- Working within multidisciplinary teams with product, design, and technology working within the same cycles +- Showcasing and presentation skills +- Agile practices such as Scrum, XP, and/or Kanban +- Pair programming +- Writing code with test-driven development +- Component-based design techniques such as using pattern libraries, styled-components, CSS-in-JS, BEM, and/or SUIT CSS +- Debugging infrastructure +- The React ecosystem including a test-driven approach +- Infrastructure as code technology like Terraform and Cloud Formation +- Familiarity with architectural and design patterns +- Use of architectural decision records +- Writing blog posts and giving talks + +## Work perks and benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +## Salary and location + +We mainly work remotely but you may need to visit clients or go to the office occasionally. We have offices in London, Bristol, Manchester, and Swansea. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/senior_user_researcher.txt b/handbook/handbook-main/roles/senior_user_researcher.txt new file mode 100644 index 0000000000000000000000000000000000000000..874c710b5f10ac327676c9987d742f5ad91359d4 --- /dev/null +++ b/handbook/handbook-main/roles/senior_user_researcher.txt @@ -0,0 +1,67 @@ +# Senior User Researcher + +- Location: remote/hybrid with occasional client site visits +- Offices: London, Bristol, Manchester, and Swansea +- Salary: Please refer to salary in job ad when role is live. +- SFIA: Level 4 + +## Key responsibilities + +## Scope + +- Responsible to the Lead User Researcher for informing the design and delivery of public services +- Hands-on research and research leadership for one product/team +- Acts as the research subject matter expert on a product team, helping to facilitate the design process and communicating design decisions to the team and stakeholders +- Considers strategic approaches to research +- Concerned about user research practices within Made Tech +- Works with full autonomy and work doesn’t need to be reviewed +- Contributes to and may lead communities of practice, discussing and sharing suggestions, approaches and ideas - including proactively seeking feedback on own work +- May mentor and coach within the research community and line manage researchers + +## Practice + +- Scope the focus of research, so everyone involved has a shared understanding of what success looks like +- Plan research that informs the design of public services that are helpful, usable and successful +- Put research participants at ease, so they're comfortable sharing information +- Analyse and interpret research findings so that teams can confidently confirm or challenge their understandings of problems and ideas + +## Leading teams + +- Involve whole teams in user research to build their understanding and empathy for people using and running public services +- Assure the quality of decisions across multiple teams +- Share research freely and often +- Make decisions based on research findings; model this behaviour to the rest of your team + +## Community + +- Line manage other user researchers +- Support the hiring and onboarding of designers and researchers +- Help define Made Tech design principles through delivering good public services +- Contribute to a design studio culture at Made Tech and client offices +- Represent user-centred design publicly and internally + +## Key measures + +- Delivery of good public services for users with clients +- Case studies of how to design and deliver good public services and outcomes +- Growth and happiness of the UCD community at Made Tech + +## Competencies + +- Client Focus +- Drive to deliver +- Learning and mentoring +- Experienced in their profession +- Facilitation + +## Work perks and Benefits + +Take a look at the Benefits & Perks section of the [Made Tech Handbook](https://github.com/madetech/handbook) to see what we can offer you. + +We practice salary transparency when it comes to advertising roles at Made Tech. Every role we publish will include the salary range in the job ad, please do refer to that. + +For any internal candidates, we are currently reviewing and refreshing our pay bands and will be sharing those internally first. They will then be placed back here again by the end of July 2025. + +## Applying + +When we’re hiring for this role, you can see the details and apply at www.madetech.com/careers. If you have any questions about the role please email us at [careers@madetech.com](mailto:careers@madetech.com). We’re happy to help! diff --git a/handbook/handbook-main/roles/sfia (legacy)/README.txt b/handbook/handbook-main/roles/sfia (legacy)/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..c066eef995f2e0165d5e82b0abcd20b691d02bcc --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/README.txt @@ -0,0 +1,3 @@ +# Legacy SFIA Guidance + +This home-made SFIA guidance is no longer applicable. It has been superseded by the open source SFIA responsibility descriptions: https://sfia-online.org/en/sfia-8/responsibilities \ No newline at end of file diff --git a/handbook/handbook-main/roles/sfia (legacy)/academy_software_engineer.txt b/handbook/handbook-main/roles/sfia (legacy)/academy_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..e1e71fa20abcecae56cf8656efec0a7b3c1c42f8 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/academy_software_engineer.txt @@ -0,0 +1,52 @@ +# SFIA Role Guidance: Academy Software Engineer + +[SFIA Level 1: Follow](https://sfia-online.org/en/sfia-7/responsibilities/level-1) + +[next »](associate_software_engineer.md) + +## Summary of role + +Attending Made Tech Academy to learn about software engineering in the public sector. + +## Required competency for role + +### Autonomy + +Works with other engineers above their level to be effective, seeking help rather than staying blocked and takes responsibility for requesting and addressing feedback on independent contributions. + +### Influence + +Shares opinions on approach with team and plays an active part in workshops and group activities. + +### Complexity + +Combines existing knowledge, additional research and direction from colleagues to complete tasks. + +### Knowledge + +Demonstrates ability to self-learn new knowledge, skills and behaviours. + +### Business Skills + +Has sufficient communication skills for effective dialogue with others. + +## Examples of behaviours and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Learning the basics of how technology can be delivered with a Made Tech spin +- Needs to pair with other Engineers above their level to be effective, but is likely to be mentor-mentee relationship +- Seeks feedback and guidance on contributions +- For contributions delivered independently; there is typically a lot of constructive feedback and guidance illuminates new knowledge and skills +- Influencing others around them by sharing opinions on approach +- Able to talk through thought process in pairing situations +- Involved in mob sessions +- Involved and engaged in retrospectives +- More often than not needs to seek advice to raise issues or provide feedback to others +- Applies what they have been taught in Academy by following rules, often without full consideration of the tradeoffs made +- Needs to seeks advice to understand what is possible, and needs assistance to adapt to delivery team specific needs +- Is able to reason and strategise about tiny slices of a whole problem, and require assistance to consider wider impact of work +- Is learning new knowledge, skills and behaviours +- Needs regular advice and guidance +- Is constantly re-defining internalised opinions based on new experiences and information +- Can apply known concepts in new programming languages diff --git a/handbook/handbook-main/roles/sfia (legacy)/associate_designer.txt b/handbook/handbook-main/roles/sfia (legacy)/associate_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..e127b0aebf67127d5811c8a8420e3cb9ab522d23 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/associate_designer.txt @@ -0,0 +1,91 @@ +# SFIA Role Guidance: Associate Designer + +* [SFIA Level 2](https://sfia-online.org/en/legacy-sfia/sfia-7/responsibilities/level-2) +* [Job description](../associate_designer.md) + +## Summary of role + +Associate Designers are practitioners who collaborate with others to tackle challenges faced by people and society. They work within a team to design and deliver public services. They do this by understanding problems and creating solutions that work for equally well for users and stakeholders. They are active members of a healthy User-Centred Design (UCD) community and culture at Made Tech. + +## Required competency for the role + +### Autonomy + +* Works under routine direction. +* Uses limited discretion in resolving issues or enquiries. +* Works without frequent reference to others. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Carries out clearly define tasks within a design sprint. +* Can piece together a flow of online form and seeks feedback from others after first attempt. +* Can demonstrate a prototype +* Can begin to apply GOV.UK Design System to basic forms and page layouts. + +--- + +### Influence + +* Interacts with and may influence immediate colleagues. +* May have some external contact with customers, suppliers and partners. +* May have more influence in own domain. +* Aware of need to collaborate with team and represent users/customer needs. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Assists UCD people in a team to get ready for user testing. +* Can prototype in more than one way if asked. +* Understands they need to collaborate with software engineers if they are design services that actually get built. + +--- + +### Complexity + +* Performs a range of work activities in varied environments. +* May contribute to routine issue resolution. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Sketches design ideas to a problem that’s well defined by user research. +* Leads certain activities as part of a discovery kick-off with support from more senior teammates. +* Corrects typos and other small errors in prototypes before and during testing with users. + +--- + +### Knowledge + +* Demonstrates application of essential generic knowledge typically found in industry bodies of knowledge. +* Has gained a basic domain knowledge. +* Absorbs new information when it is presented systematically and applies it effectively. + + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Applies the 'one thing per page' principle to their prototypes. +* Can spot basic accessibility issues in an existing service. +* Applies the basics of storytelling to talk about their own design career so far. + +--- + +### Business Skills + +* Has sufficient communication skills for effective dialogue with customers, suppliers and partners. +* Is able to work in a team. Is able to plan, schedule and monitor own work within short time horizons. Demonstrates a rational and organised approach to work. +* Understands and uses appropriate methods, tools and applications. +* Identifies and negotiates own development opportunities. +* Is fully aware of and complies with essential organisational security practices expected of the individual. + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Produces prototypes without pairing or instructions. +* Checks in with teammates everyday to ensure they’re not working in a silo or diverging from team goals. +* Offers to support teammates when priorities change, seeing teammate meets goals rather than just their individual ones. +* Communicates when their work is being blocked and maybe who they need to work with to change that. diff --git a/handbook/handbook-main/roles/sfia (legacy)/associate_software_engineer.txt b/handbook/handbook-main/roles/sfia (legacy)/associate_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..973c623157c073d53eafbf807f91e1d0c662b98b --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/associate_software_engineer.txt @@ -0,0 +1,51 @@ +# SFIA Role Guidance: Associate Software Engineer + +[SFIA Level 2: Assist](https://sfia-online.org/en/sfia-7/responsibilities/level-2) + +[« previous](academy_software_engineer.md) | [next »](mid_software_engineer.md) + +## Summary of role + +Assists in the delivery of digital, data and technology outcomes that improve society. They do this by autonomously developing software features and contributing ideas to workstream direction. + +## Required competency for role + +### Autonomy + +Can autonomously deliver features ensuring the quality of their work by proactively seeking and addressing feedback. + +### Influence + +Can form own opinions on how to iteratively develop a feature, validates these opinions with workstream team and contributes in workshops with customers. + +### Complexity + +Balances user needs with technical complexity to deliver all aspects of a feature including UI, API, DB and business logic components. + +### Knowledge + +Able to acquire new knowledge in order to deliver features within estimated time. + +### Business Skills + +Has sufficient communication skills for effective dialogue with customers, suppliers and partners. + +## Examples of behaviours and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- With limited experience in modern technology consulting sector +- Still learning how Made Tech delivers technology, and may need to pair on occasion to be effective +- Is able to more often than not participate equally in a pair with others +- For the majority of the time, is able to contribute independently without pairing +- Seeks feedback and guidance where appropriate; typically receives some constructive feedback and occassionally guidance highlights gaps in knowledge and skills +- Influencing immediate colleagues regularly by sharing opinions and ideas +- Challenges other Made Tech colleagues ideas tactfully when in disagreement +- Has been involved in workshops, retrospectives or other activities where ideas and opinions are shared between customers and Made Tech colleagues +- Would typically gain the ability to provide ideas, opinions and advice on specific subset of a customer's domain +- Beginning to understand tradeoffs and is learning to make adjustments to approach for the current context +- Is able to reason about subsets of a domain, building up a good working knowledge of wider technological & user needs +- Has a grounding in foundational knowledge, skills and behaviours +- Able to mentor others in some skills +- Navigates available workshops to learn skills necessary to be effective on Delivery Teams +- Has a good working knowledge of the customer domain diff --git a/handbook/handbook-main/roles/sfia (legacy)/delivery_manager.txt b/handbook/handbook-main/roles/sfia (legacy)/delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..e6f20cf4ed37ba7bf3d76cf3027b84f261ef5397 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/delivery_manager.txt @@ -0,0 +1,87 @@ +# SFIA Role Guidance: Delivery Manager + +[SFIA Level 4: Follow](https://sfia-online.org/en/sfia-7/responsibilities/level-4) + +[« previous](junior_delivery_manager.md) | [next »](senior_delivery_manager.md) + +## Required competency for role + +### Autonomy + +Understands software delivery in depth and has broad experience in delivering tech solutions, with user-focused outcomes. + +Is autonomous to a great extent - will seek guidance and direction only when a highly complex situation or problem arises (e.g. negotiations with clients were viability or profitability of the account is on the line, account inception). + +Demonstrates personal accountability for delivery success and assumes that accountability with little direction. + +Drives delivery and is the go to person for the team and customers. + +### Influence + +Influences and drives the success of the delivery - active involvement in defining ways of working and delivery approach. + +Helps the team to find a process that works for them. + +Helps to guide, upskill, mentor both team & client members. + +Ensures team is focused on providing user value and user-based outcomes and shows accountability for customer satisfaction. + +Builds strong relationships with customers and ensures customer satisfaction - proven focus on user-based outcomes when influencing ways of working and delivery outcomes. + +Able to facilitate discussions including technical and business stakeholders and help arrive to helpful conclusions. + +Able to manage stakeholders’ expectations and be flexible, regularly demonstrating proactive rathen than reactive communication. Facilitates difficult discussions within the team or with diverse senior stakeholders. + +Guides teams to focus on the outcomes rather than the process / outputs. + +Accountable for ensuring the team is always performing to a Made Tech standard, resolving, or escalating issues wherever appropriate. + +### Complexity + +Able to lead deliveries that are not well defined from the start - have led deliveries under different, often challenging circumstances. + +Has exprience dealing with complex situations and can do so in various contexts (e.g with impact to account viability, drastic changes to team shape, with impact to MT reputation, financial results and profitability). + +Has experience dealing with difficult customers and can, with support, pave the way to a successful engagement. + +Able to set the delivery cadence to a sustainable level - can make adjustments to resolve issues and ensure a high and steady delivery pace. + +Ensures value for users is always delivered at the account level and is able to remediate this by introducing techniques to surface user needs and measure the success of the delivery against those. + +Able to identify, assess & mitigate risks effectively - understands when escalation is required. + +Finds ways to help our customers beyond just shipping software, ensuring Made Tech teams always demonstrate our mission and values. + +Upskills and helps customers & team members to resolve complex, often out of the ordinary, issues. + +### Knowledge + +Has a wealth of agile & lean knowledge and has applied both fundamental & advanced principles in different scenarios with little support. + +Able to identify and compare the best processes or delivery methods to use. + +Able to recognise when something does not work and encourages a mindset of experimentation and continuous improvement. + +Has a wealth of delivery knowledge and experience; will typically have delivered at least a few tech projects with proven user-focused outcomes. + +Has good knowledge of modern software development/delivery practices, can discuss their respective benefits and principles & has applied these in multiple deliveries, helping teams become high-performing and successfully deliver outcomes. + +Able to measure and evaluate delivery outcomes. + +Remains at the forefront of both agile & delivery topics & new ideas, ensuring they gain new knowledge proactively and regularly. + +Shares this knowledge with the wider organisation. + +Shares this knowledge with the customers at every opportunity. + +### Business Skills + +Communicates fluently, orally and in writing, and can present complex information to both technical and non-technical audiences. + +Plans, schedules and monitors work to meet time and quality targets. + +Facilitates collaboration between stakeholders who share common objectives. + +Selects appropriately from applicable standards, methods, tools and applications. + +Fully understands the importance of security to own work and the operation of the organisation. Seeks specialist security knowledge or advice when required to support own work or work of immediate colleagues. diff --git a/handbook/handbook-main/roles/sfia (legacy)/delivery_support_analyst.txt b/handbook/handbook-main/roles/sfia (legacy)/delivery_support_analyst.txt new file mode 100644 index 0000000000000000000000000000000000000000..5c7cd481ff501b652ccbcc06fee685ee020ad550 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/delivery_support_analyst.txt @@ -0,0 +1,77 @@ +# Delivery Support Analyst (PMO) + +Salary: £24,975 - £32,000 +Location: Bristol, London, Manchester or Swansea with hybrid-working policy + +## Your role at Made Tech +The Delivery Support Analyst in PMO at Made Tech plays an essential role in ensuring the seamless execution and oversight of the company's digital transformation engagements. + +This role will see you managing workstream reporting, ensuring compliance with Statements of Work (SoW), and maintaining a comprehensive RAID (Risks, Assumptions, Issues, Dependencies) log across all Made Tech engagements. + +This involves capturing and managing the demand for resources within each workstream or SoW, coordinating with the Scheduling team to raise and manage resource requests, and working closely with workstream leads to ensure the appropriate allocation of resources. + +The Delivery Support Analyst will play a crucial role in maintaining the structure and efficiency of the project lifecycle. + +The Delivery Support Analyst supports the account onboarding of new team members and supports the creation of rotation plans as necessary, ensuring smooth transitions and consistent team performance within the PMO office. + +The Delivery Support Analyst also tracks budgets and capacity within each workstream or SoW, actively highlighting risks and issues to the accountable Delivery Manager, which is vital for maintaining project alignment with financial and operational goals. + +Furthermore, this role ensures accurate and timely completion of timesheets across all workstreams, which is essential for effective budget management and resource planning. + +The management of team work plans, schedules, and on-site registers also falls under the PMO's purview, allowing for the consistent and organised execution of projects. + +Beyond operational management support, the Delivery Support Analyst at Made Tech is responsible for producing timely, visual, and client-ready reports on all aspects of the engagements. + +These reports are crucial for communicating the current status, risks, and progress to various stakeholders, including the C-Suite, ensuring transparency and informed decision-making. + +The Delivery Support Analyst also supports the team with logistical tasks, such as booking travel and accommodation, facilitating key meetings and ceremonies with stakeholders, and overseeing dependencies and issue monitoring. + +These activities contribute to the overall health and success of the workstreams and SoWs, allowing the PMO office to play an integral role in maintaining project momentum and resolving challenges as they arise. + +The Delivery Support Analyst also plays an active role in presenting and reporting on engagement status at agreed frequency levels to a wide range of stakeholders across the business. + +Finally, the Delivery Support Analyst creates and maintains all key engagement documentation, or collaborates with the Delivery Manager to bring in additional expertise when needed. + +This documentation is vital for keeping a detailed and organised record of project activities, decisions, and changes. + +As an active participant in the Delivery Management community, this role not only helps to drive the successful delivery of current engagements but also contributes to the continuous improvement of project management practices within Made Tech, ensuring that the organisation remains agile, efficient, and responsive to client needs. + +## Responsibilities + +* Manage work stream reporting, SoW compliance reporting and overall RAID log for Made Tech’s engagements +* Capture and manage demand for resources within each of the Made Tech account workstreams/ SoWs. Work with Scheduling to raise/ manage resource requests and work with workstream leads to verify appropriate resource allocation +* Support onboarding new team members and create rotation plans where appropriate +* Track budget and capacity within each work stream/ SoW, highlighting risks and issues to Delivery Manager +* Ensure accurate and timely timesheet completion across all work streams/ SoWs +* Manage team work plans/ schedules and on-site register +* Provide timely and visual client-ready reporting on all of the above +* Support the team with travel and accommodation booking as required. +* Facilitate key meetings/ ceremonies with stakeholders where appropriate +* Oversee dependencies, action/ issue monitoring, and controls and help to perform health checks work streams/ SoWs +* Create and maintain all key engagement documentation, or work with the Delivery Manager to bring additional specialist knowledge onboard +* Present and report on engagement status to the agreed frequency level to a range of stakeholders across the business, up to C-Suite level. Be an active participant in the Delivery Management community within the engagement and Made Tech + +### Expected outcomes + +* Reduce the time delivery managers are spending on internal-facing activities to optimise client-facing time. +* Reduce the cost of internal-facing activities through centralisation, standardisation and automation. +* Improve quality and accuracy of products through centralisation, standardisation and automation. + +### KPIs: +* Delivery Management effort freed up. +* Quality and accuracy. + +### Definition of success: +Success as a Delivery Support Analyst is measured by smooth, efficient and high-quality implementation of delivery operational work to enable account teams to run more efficiently and focus on high-value activities for our clients. + +### Skills people must have +Don’t worry - we don’t expect you to tick all of these when you join, we will work together to define learning and development objectives that help you meet these competencies on your way to promotion. + +* Experience leading or supporting business change programs or portfolios. Programme office delivery experience within the full lifecycle of cross functional projects (software engineering, user experience, architecture, etc.) +* Experience in managing/ influencing colleagues and peers to achieve required business outcomes (timesheet compliance, policy adherence, etc.). Able to use soft power to create influence and know when to escalate to achieve required outcomes +* Experience of project scheduling, risk management, budget management, and tracking the realisation of benefits +* Clear and confident communication skills; able to partner and work with stakeholders from client organisations and across the business, including C-Suite executives +* Experience in managing the activities of a project team in a matrixed project organisation + +### Certifications: +Certified ScrumMaster or equivalent (for Agile projects) would be desirable but not essential. diff --git a/handbook/handbook-main/roles/sfia (legacy)/designer.txt b/handbook/handbook-main/roles/sfia (legacy)/designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..7d2270dc87ede5cb8d0be13283f07795e77f32f4 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/designer.txt @@ -0,0 +1,109 @@ +# SFIA Role Guidance: Designer + +* [SFIA Level 3](https://sfia-online.org/en/legacy-sfia/sfia-7/responsibilities/level-3) +* [Job description](https://github.com/madetech/handbook/blob/main/roles/sfia%20(legacy)/designer.md) + +## Summary of role + +Designers are experienced practitioners who collaborate with others to tackle challenges faced by people and society. They work within a team to design and deliver public services. They do this by influencing the direction, assuring the quality of design delivery within their team, and by leading the end-to-end design of a chosen service. They are active members of a healthy User-Centred Design (UCD) community and culture at Made Tech. + +## Required competency for the role + +### Autonomy + +* Works under general direction from Senior and Lead designers. +* Uses discretion in identifying and responding to complex issues and assignments. +* Receives specific direction, accepts guidance and has work reviewed at agreed milestones. +* Determines when issues should be escalated to a higher level. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Speaks to their line manager or another senior person when struggling in their team. +* Spots likely usability issues on a public sector website their delivery team has been tasked to replace. +* Produces designs for services using a predefined design system. +* Gives Adhoc feedback about a user interface and what to improve. +* Produces documents that clearly articulate how users can interact with a service. +* Comfortable showing in-progress design work +* Incorporates feedback from groups sessions about improving a specific way of working. + +--- + +### Influence + +* Interacts with and influences colleagues. +* Has working-level contact with customers, suppliers and partners. +* May supervise others or make decisions that impact the work assigned to individuals or phases of projects. +* Understands and collaborates on the analysis of user/customer needs and represents this in their work. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Contributes to delivery team sprint planning when asked. +* Involves teammates to take part in design activities, such as crits. +* Encourages teammates to suggest solution ideas. +* Clearly articulates a design problem. +* Helps others understand why accessibility is important. +* Shares design thinking little and often within their team. +* Advocates for other UCD roles, eg. is involved in encouraging teammates to take part in user research sessions. + +--- + +### Complexity + +* Performs a range of work, sometimes complex and non-routine, in a variety of environments. +* Applies a methodical approach to issue definition and resolution. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Can take a design through from initial research, ideas, prototyping, testing and analysing what iterations are needed. +* Applies their design process to different organisations and problem spaces. +* Can quickly see changes needed to designs when observing user research. +* Can clearly communicate the user problems the team needs to solve. + +--- + +### Knowledge + +* Has a sound generic, domain and specialist knowledge necessary to perform effectively in the organisation typically gained from recognised bodies of knowledge and organisational information. +* Demonstrates effective application of knowledge. +* Has an appreciation of the wider business context. +* Takes action to develop own knowledge. + +#### Examples behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Applies the GDS design system components to an existing software system. +* Describes how to begin to make a service more accessible. +* Aware of some research biases and how to try to avoid them. +* Structures their own work for others to give feedback. +* Awareness of the wider reasons a project is slower or not always concentrating on the user needs. +* Proactively takes time off for learning new skills or strengthening existing ones. + +--- + +### Business Skills + +* Demonstrates effective communication skills. +* Plans, schedules and monitors own work (and that of others where applicable) competently within limited deadlines and according to relevant legislation, standards and procedures. +* Contributes fully to the work of teams. Appreciates how own role relates to other roles and to the business of the employer or client. +Demonstrates an analytical and systematic approach to issue resolution. +* Takes the initiative in identifying and negotiating appropriate personal development opportunities. +* Understands how own role impacts security and demonstrates routine security practice and knowledge required for own work. + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +* Clearly explains design decisions. +* Has a basic understanding of how to build interactive HTML prototypes. +* Pairs with software engineers to develop more advanced prototypes. +* Communicates clearly who a service’s users are and the current team’s understanding of the problems their user faces. +* Pairs with the product owner to create hypotheses the team wants to test. +* Takes part in sprint planning and communicates who they need to work with to achieve team goals for that sprint. +* Produces a prototype in time for testing. Can make iterations following analysis of testing. +* Books time off for learning, be that reading around service design or attending a UX conference. +* Ensures consent for research with users is fully informed and stored safely. \ No newline at end of file diff --git a/handbook/handbook-main/roles/sfia (legacy)/junior_delivery_manager.txt b/handbook/handbook-main/roles/sfia (legacy)/junior_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..42bc27d5fdb34e436f85cfd395b0ce1c826807e5 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/junior_delivery_manager.txt @@ -0,0 +1,74 @@ +# SFIA Role Guidance: Junior Delivery Manager + +[SFIA Level 3: Follow](https://sfia-online.org/en/sfia-7/responsibilities/level-3) + +[« previous](team_assistant.md) | [next »](delivery_manager.md) + +## Required competency for role + +### Autonomy + +Understands software delivery at an entry level, and has some experience in delivering tech solutions, with user-focused outcomes. + +Can perform key role activities independently, and will often attempt to handle slightly more complex situations (e.g. negotiations with clients, improvements in ways of working in an already high-performing team) without significant help. + +Contributes to the account level and assumes accountability for a single workstream, however usually not solely accountable for the ovarall delivery success; often seeks help and shares that accountability with more senior team members in the delivery. + +Has some experience in dealing with customers / external parties but often requires support with situations that are not ordinary. + +### Influence + +Helps define the team's ways of working & resolve issues around delivery cadence. + +Strong appreciation of the importance of team dynamics, collaboration and empowering delivery teams. Understands the importance of feedback, at a team or personal level. + +Able to effectively communicate with technical and non-technical stakeholders as well as facilitate discussions within a multidisciplinary team, with potentially difficult dynamics. + +Able to advocate for the team externally and can manage differing perspectives. + +Can help teams to establish a process although will require help when having to assess and decide between frameworks, processes etc in an unpredictable, complex situation / delivery. + +Builds successful and trusting relationships with the MT customers and is able to promote MT in appropriate situations. + +### Complexity + +Can deal with low-complexity situations effectively and with little support (e.g. how to run ceremonies, backlog refinement session, internal team meetings). + +Attempts to deal with more complex situations, by presenting different alternatives and discussing the best way forward (e.g. drastic changes to team shape, team unsuccessful in Sprint cycle, with impact to MT reputation). + +Ensures value for users is always delivered at the workstream level - if not, attempts to remediate by presenting different alternatives and discussing the best way forward. + +Proven record of actively attempting to remove or minimise risks & issues with little support. Understands how the risks, issues or dependencies impact the work of a team. + +Sets the team cadence and tempo, ensuring it is sustainable. + +### Knowledge + +Proven experience in applying agile principles in practice. + +Has strong knowledge of the fundamentals of software delivery, how to support high performing teams and apply user-first principles. + +Able to provide a clear framework in which teams can deliver, with focus on openness, transparency, user-first principles, outcomes. + +Has an awareness of agile tools and is starting to use them intelligently. + +Has a good understanding of key software development principles & practices and has experience being part of teams that implement those. + +Acively seeking to build up their delivery knowledge and gain better understadning on how best to deliver tech solutions and user outcomes. + +### Business Skills + +Demonstrates effective communication skills. + + +Plans, schedules and monitors own work (and that of others where applicable) competently within limited deadlines and according to relevant legislation, standards and procedures. + + +Contributes fully to the work of teams. Appreciates how own role relates to other roles and to the business of the employer or client. +Demonstrates an analytical and systematic approach to issue resolution. + + +Takes the initiative in identifying and negotiating appropriate personal development opportunities. + + +Understands how own role impacts security and demonstrates routine security practice and knowledge required for own work. diff --git a/handbook/handbook-main/roles/sfia (legacy)/lead_content_designer.txt b/handbook/handbook-main/roles/sfia (legacy)/lead_content_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..7c26666d4b2b15d409307d09046bb8829134264f --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/lead_content_designer.txt @@ -0,0 +1,92 @@ +# SFIA role guidance Lead Content Designer +- [SFIA Level 5: Ensure, Advise](https://sfia-online.org/en/sfia-7/responsibilities/level-5) +- [Job description](https://github.com/madetech/handbook/blob/main/roles/lead_content_designer.md) + +## Summary of role + +Lead Content Designers are expert practitioners who lead and mentor others. They work with teams and clients to meet user needs and make complex processes easy to understand. They do this by setting the direction, assuring the quality of content design delivery across teams, and ensuring content aligns to strategy and objectives. They have an important role in creating a healthy user-centred design (UCD) community and culture at Made Tech. + +## Required competency for role + +### Autonomy + +Self-initates and works with little direction of where to focus energy to design and deliver good public services with their team. Takes responsibility for the team designing the right solutions for their problems. Works to define and assign design tasks to themselves and others. + +### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ +- Assess quickly what design leadership a team needs to deliver a user-centred service and fills this role without being asked to. +- Assures the quality and accessibility of content design work going into software production +- Shares good practice from own experience and other sources for how and why a team does activities like A/B testing, card sorts and interviews with users or low fidelity prototypes +- Starts community show and tells +- Develops content design guides / operating models setting out roles and responsibilities within teams and stakeholders +- Works closely with designers inputting into pattern libraries and style guides. + +--- + +### Influence +Drives team towards design excellence by influencing team, stakeholders and partners. + +### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Creates tangible, understandable vision for a service's design and direction +- Advocates key user needs with their team and client organisation must focus on to deliver a successful service. +- Shows they are a role model for less senior designers and set an example for how to be professional, supportive and effective. +- Successfully challenges major team decisions not informed by user research. +- Designs the key stages of a services that is delivered to users. +- Coaches senior content designers taking on line management for the first time and how to grow into this new responsibility +- Able to explain content design best practice and the reasons for it to senior service stakeholders to successfully influence them and ensure project decisions are based on what best meets user needs +- Works closely with Product Managers and Service Designers to ensure one approach is taken across client and service portfolios + +--- + +### Complexity +Leads content design with their team within a wider programme of work in multi-organisation stakeholder environments. Shows the minimum design to deliver value, that balances complex user needs, client goals and legacy process or systems. + +### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Can guide teams to build and create the most appropriate ways to visualise their work in context for different audiences. +- Can direct the team in the creation, testing and iteration of content patterns +- Understands complex user journeys and can direct solutions to meet different needs within these journeys. Brings insight and expertise in how user needs have changed over time to make sure these are still relevant and being met. +- Prototypes what a minimal viable service could be, balancing complex user needs, urgent client goals and legacy systems or processes +- Establishes design sprints activities and structure within a team previously not working in a agile, open or user-centred way +- Breaks down silos within their team and has UCD roles and people in other disciplines working towards the same goals +- Shares research with other delivery teams within the client organisation and shows the need for closely coordination between teams +- Working with designer to turn a new government policy into a prototypes to test with users + +--- + +### Knowledge +Develops a deep understanding of design and policy landscape in UK public sector. + +### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Can fully explain the purpose and activities of each GDS phase of service delivery to a clients unfamiliar or uncomfortable with that way of working. +- Gets teams to choose the suitable type of testing for hypothesis, communicating the strengths and weaknesses each type brings +- Works with other leaders on team set up to ensure the team can produce good user content +- Regularly seeks feedback from peers, teammates and clients. Acting on and sharing what others feel they are doing well and could improve upon. +- Seeks out new design tools being used and developed by other organisations and tries them for their own and others practice. +- Put in place new standards for how we content review design work across different client teams +Quickly assesses the suitability of a Content Designer role for someone interviewing to join Made Tech + +--- + +### Business Skills + +Demonstrates leadership. Communicates effectively, both formally and informally. + +### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Represents content design at Made Tech at public and internally company wide events. +- Brings together content designers to do a retro about challenges felt across the discipline. Works with others to begin actioning priorities +- Holds senior management to account for improving their team conditions and ways of working. +- Decides how to most effectively use their time on the team to help it achieve its outcomes. Explain to teammates and stakeholders the value of using time in a certain way. +- Facilitates workshop with indecisive stakeholders to achieve teams goals for the coming weeks. +- Work with designer, engineers and delivery manager to ensure content quality is met on MVP live services with a client. +- Advises on the achievable target for a design sprint on a live service, prioritises value for users and impact for the client organisation. +- Drafts the team shape and how often it delivers for a bid proposal with a new client to do a discovery for a public service. +- Highlights the risks their team shipping a live service with solutions not proven with any research or other evidence. + diff --git a/handbook/handbook-main/roles/sfia (legacy)/lead_designer.txt b/handbook/handbook-main/roles/sfia (legacy)/lead_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..9b694e381c5e80d9020a3074afd4e0bc37f2569b --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/lead_designer.txt @@ -0,0 +1,128 @@ +# SFIA Role Guidance: Lead Designer + +- [SFIA Level 5: Ensure, Advise](https://sfia-online.org/en/sfia-7/responsibilities/level-5) +- [Job description](../lead_designer.md) + +## Summary of role + +Lead Designers are expert practitioners who influence and mentor others. They work with teams and clients to design and deliver public services. They do this by setting the direction, assuring the quality of design delivery across teams, and by leading multiple, or highly complex, services. They have an important role in creating a healthy user-centred design (UCD) community and culture at Made Tech. + +## Required competency for the role + +### Autonomy + +Self-initiates and works with little direction of where to focus energy to design and deliver good public services with their team. Takes responsibility for the team designing the right solutions for their problems. Works to define and assign design tasks to themselves and others. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Quickly assesses what design leadership a team needs and fulfils the role without being asked to. + +- Assures the quality of design work going into software production. + +- Shares good practice from own experience and other sources for how and why a team does activities like in-depth interviews with users or low fidelity prototypes. + +- Starts community show and tells. + +--- + +### Influence + +Drives team towards design excellence by influencing team, stakeholders and partners. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Works with the client product owner to set team priorities for the coming sprint. + +- Creates tangible, understandable vision for a service's design and direction. + +- Advocates key user needs with their team and client organisation must focus on to deliver a successful service. + +- Shows they are a role model for less senior designers and set an example for how to be professional, supportive and effective. + +- Successfully challenges major team decisions not informed by user research. + +- Designs the key stages of a service that is delivered to users. + +- Coaches senior designers; establishes line management and grows the practice within the team. + +--- + +### Complexity + +Leads service design with their team within a wider programme of work in multi-organisation stakeholder environments. Shows the minimum design to deliver value, that balances complex user needs, client goals and legacy processes or systems. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Facilitates a team to visualise and agree on what its service is from end-to-end, front to the back of user interactions and internal processes. + +- Prototypes a minimal viable service, balancing complex user needs, urgent client goals and legacy systems or processes. + +- Establishes design sprints activities and structure within a team previously not working in an agile, open or user-centred way + +- Breaks down silos within their team and has UCD roles and people in other disciplines working towards the same goals. + +- Shares research with other delivery teams within the client organisation and shows the need for close coordination between teams. + +- Works with a content designer to turn a new government policy into prototypes to test with users. + +--- + +### Knowledge + +Develops a deep understanding of design and policy landscape in the UK public sector. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Can fully explain the purpose and activities of each GDS phase of service delivery to clients unfamiliar or uncomfortable with that way of working. + +- Gets teams to choose the suitable type of testing for hypothesis, communicating the strengths and weaknesses each type brings. + +- Advises other leaders on how to set up their team for effective design work. + +- Regularly seeks feedback from peers, teammates and clients. Acting on and sharing what others feel they are doing well and could improve upon. + +- Seeks out new design tools being used and developed by other organisations and tries them for their own and others practice. + +- Answers internal questions about what is ‘policy design’ and how it is and isn’t different from service delivery we’re familiar with at Made Tech. + +- Puts in place new standards for how we review design work across different client teams. + +- Quickly assesses the suitability of a Designer role for someone interviewing to join Made Tech. + +--- + +### Business Skills + +Demonstrates leadership. Communicates effectively, both formally and informally. + +#### Examples of behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Represents user-centred design at Made Tech at public and internal company-wide events. + +- Brings together designers to do a retro about challenges felt across the discipline. Works with others to begin actioning priorities. + +- Holds senior management to account for improving their team conditions and ways of working. + +- Decides how to most effectively use their time on the team to help it achieve its outcomes. Explains to teammates and stakeholders the value of using time in a certain way. + +- Facilitates workshops with indecisive stakeholders to achieve teams goals for the coming weeks. + +- Work with engineers and delivery managers to design and deliver an MVP live services with a client. + +- Advises on the achievable target for a design sprint on a live service, prioritises value for users and impacts for the client organisation. + +- Drafts the team shape and delivery rhyme bid proposal with a new client to do a discovery for public service. + +- Highlights the risks their team shipping a live service with solutions not proven with any research or other evidence. + + diff --git a/handbook/handbook-main/roles/sfia (legacy)/lead_software_engineer.txt b/handbook/handbook-main/roles/sfia (legacy)/lead_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..5817a9df5c8d898a01bd17f996e6ca9196555a92 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/lead_software_engineer.txt @@ -0,0 +1,66 @@ +# SFIA Role Guidance: Lead Software Engineer + +[SFIA Level 5: Ensure, Advise](https://sfia-online.org/en/sfia-7/responsibilities/level-5) + +[« previous](senior_software_engineer.md) | [next »](principal_technologist.md) + +## Summary of role + +Leads teams to deliver digital, data and technology outcomes that improve society. They do this by establishing and leading teams to deliver software in public sector organisations. + +## Required competency for role + +### Autonomy + +Accountable for workstream to customers, partners, account team, delivery assurance team and other stakeholders from a technical and delivery perspective. + +### Influence + +Drives workstream team towards technical excellence by influencing team, customers and partners. + +### Complexity + +Manages complex technical change of a workstream within a wider programme of work in multi-organisation stakeholder environments. + +### Knowledge + +Develops a deep understanding of digital and technology landscape in UK public sector. + +### Business Skills + +Demonstrates leadership. Communicates effectively, both formally and informally. + +## Examples of behaviours and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Represents or delegates responsibility for representing workstream to customers, partners, account team, delivery assurance team and other stakeholders from a technical and sometimes delivery perspective +- Coaches Senior Engineers within the workstream team and/or customer staff, providing continuous feedback to individuals and their line managers, and supporting line managers to find career progression opportunities +- Able to lead bootup and delivery of a product workstream where outcomes are known, and the product is complicated rather than complex +- Able to work as part of a leadership team (with delivery and product support) in a bootup and delivery of a product workstream where outcomes are unknown, and the product is complex +- Able to work as part of a workstream team (with account and business support) in a bootup of a new account +- Able to contribute within the account team in non-strategic accounts +- Able to lead, advise and support up to two workstreams and ultimately be responsible for delivery of outcomes across their workstreams +- Able to synthesise outcomes with senior stakeholders by facilitating inception and discovery work +- Proactively identifies reputational and commercial risks and takes responsibility for mitigations and corrective actions +- Ensures all technical staff in their workstream are operating at a good performance level at minimum, identifying performance issues and supporting correct action where necessary +- Ensures their workstream team is operating in line with technical and delivery principles, and working towards technical excellence. Reports to the delivery assurance and account team +- Builds relationships with senior customer stakeholders, maintains them and leverages those relationships in their work to influence, challenge and support technical practices and strategy +- Works with customers, partners, account and workstream team to ensure workstream aligned with technical practices and strategy of customer organisation +- Regularly influences and supports improvement of technical practices within a customer’s organisation at a community of practice or organisational level +- Turns technical and delivery obstacles into opportunities for improvement and betterment of practices, and can lead a team to turn these opportunities into positive organisational impacts +- Influences direction and day-to-day running of the account +- Has overall technical authority within their workstreams +- Influences organisation-wide approach to technology as part of the technology leadership team +- Able to build relationships with senior customer and partner stakeholders, both technical and otherwise +- Works with customers to define outcomes, deadlines and budgets +- Has significant influence over the scheduling of technical staff to workstreams +- Likely is the most senior day-to-day representative of Made Tech within the account +- Ensures users’ needs are met consistently through each work stage +- Influences the technology industry by engaging at public events +- Able to architect and coordinate wide scale changes across multiple applications and platforms +- Can design migration strategies in legacy environments and coordinate others to deliver +- Can navigate complex stakeholder and organisational environments +- Able to support and manage multiple workstreams, while delivering within one or more of those workstreams +- Able to coordinate and manage supplier, partner and customer staff alongside Made Tech +- Able to lead hiring interviews for Engineer 1 to Lead Engineer candidates diff --git a/handbook/handbook-main/roles/sfia (legacy)/lead_user_researcher.txt b/handbook/handbook-main/roles/sfia (legacy)/lead_user_researcher.txt new file mode 100644 index 0000000000000000000000000000000000000000..25b1ee8ef626f0f340db2ffcc741636099844e5b --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/lead_user_researcher.txt @@ -0,0 +1,98 @@ +# SFIA Role Guidance: Lead User Researcher + +- [SFIA Level 5](https://sfia-online.org/en/sfia-7/responsibilities/level-5): Ensure, Advise +- [Job description](https://github.com/madetech/handbook/blob/main/roles/lead_user_researcher.md) + +## Summary of role + +Our Lead User Researchers play a key role in scoping and managing multiple, complex user research projects in the public sector and supporting our sales time to sell new work to clients. They’re expert practitioners comfortable conducting and managing user research. They play an important role in creating an inclusive, nurturing and safe environment for our more junior user researchers to grow and develop. They are vocal and visible contributors to our user-centred design (UCD) community and culture at Made Tech. + +## Required competency for role (with example behaviours) + +### Autonomy + +Works without direction to guide their team on where to focus energy within strategy, research and design areas to deliver good public services. Takes responsibility for scoping, coordinating and supporting multiple user research projects. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Proactively requests feedback from the people they work with. Able to honestly self reflect +- Practices open and honest communication, active listening and demonstrates empathy and patience +- Take responsibility for accounts and programmes of work and embeds a no blame attitude in teams +- Able to quickly assess what our clients need and the purpose and approach of user research and UCD on projects. +- Able to connect project work to wider strategic goals +- Builds and maintains strong relationship with clients and stakeholders + +### Influence + +Clearly articulates the user research vision here at Made Tech and how it supports the business reaching its wider strategic goals. +Drives internal Made Tech teams and client teams towards research excellence by influencing individuals, stakeholders and partners. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Builds trust with our clients and quickly earns their respect +- Show teams by doing. Creates and models good behaviour and habits for sharing research, making decisions with research and making sure research has impact +- Helps to define Made Tech design principles and make sure that teams are embedding good practice when delivering public services +- Works with clients with support and inform wider strategies that our project work and user research informs +- Works with the other Leads to create and share the user research vision here at Made Tech in a way that is clear, tangible and understandable +- Establishes stronger UCD practises in client teams, leaving lasting behaviours +- Successfully challenges sceptical clients and stakeholders about the value of UCD and user research +- Coaches senior researchers taking on line management for the first time and how to grow into this new responsibility +- Shows they are role models for less senior researchers and set an example for how to be professional, supportive and effective + +### Complexity + +Shift from project planning to programme planning. +Leads multiple UCD teams on projects and wider programmes of work. +Can balance competing priorities and projects. +Holds the vision and strategy for projects and helps UCD teams navigate complex work and environments. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Supports teams to plan and scope user research activities, ensuring they align with the wider client strategy and Made Tech roadmap +- Supports teams on creating compelling research outputs that have value and impact for our clients +- Responsible for the quality of decision and work across multiple teams and programmes of work +- Able to upskill teams in UCD practises and user research +- Expert at handling challenging and difficult situations and conversations with clients across teams +- Able to explain complex project work in a clear and compelling way +- Leads the delivery of user research +- Explores and pushes the practice of user research here at Made Tech + +### Knowledge + +Expert understanding of planning and applying quantitative and qualitative methodologies on complex programmes of UCD work. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Wide range of quantitative and qualitative experience, expertise in a wide range of research methodologies +- Can fully explain the purpose and activities of each GDS phase of service delivery and the role of user researchers to clients unfamiliar or uncomfortable with that way of working. +- Takes responsibility for exploring and trialling new tools and techniques that will continue to push the growth of user research at Made Tech +- Trusted and approachable user research expert that clients and internal folk approach for support and advice +- Understands how to measure the impact and effectiveness of user research at Made Tech and the things we can do to improve as a team +- Able to plan and manage user research on complex programmes of work +- Responsible for the standards and ethical conduct of user research here at Made Tech +- Confident in carrying out user research with vulnerable and marginalised groups +- Uses insights to inform strategic direction +- Able to assess the suitability of potential candidates for user research roles at Made Tech + +### Business Skills + +Is a trusted, honest and respected leader. Communicates effectively, both formally and informally. Is confident at selling UCD work in the public sector. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Regularly represents Made Tech in the wider UCD community through writing or speaking +- Trustworthy, acts with integrity, openness and impartiality with research participants +- Able to navigate and handle conflict within teams and with clients +- Leads proposal writing around UCD activities with the sales team +- Confident at pitch presentations and selling Made Tech in front of clients +- Able to give constructive feedback to senior management to continue to improve how we develop and grow UCD at Made Tech diff --git a/handbook/handbook-main/roles/sfia (legacy)/mid_software_engineer.txt b/handbook/handbook-main/roles/sfia (legacy)/mid_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..e8720abbae071e7bc0505455f899c7b286fd5c39 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/mid_software_engineer.txt @@ -0,0 +1,63 @@ +# SFIA Role Guidance: Software Engineer + +[SFIA Level 3: Apply](https://sfia-online.org/en/sfia-7/responsibilities/level-3) + +[« previous](associate_software_engineer.md) | [next »](senior_software_engineer.md) + +## Summary of role + +Contributor to digital, data and technology outcomes that improve society. They do this by architecting and delivering features. + +## Required competency for role + +### Autonomy + +Collaboratively leads planning of work, development of features and coordinating with stakeholders though continues to seek feedback and support on complex change. + +### Influence + +Influences approaches taken by workstream team to deliver features, contributes to quality assurance of teams work and ensures features meet project outcomes and user needs. + +### Complexity + +Manages complex technical change in a single system and will seek support when managing change across multiple systems. + +### Knowledge + +Proficient in multiple languages, frameworks and technologies. + +### Business Skills + +Demonstrates effective communication skills. + +## Examples of behaviours and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Understands and is able to demonstrate Made Tech's approach to modern technology delivery +- Is participating equally when pairing +- Will autonomously pick up and deliver features that they can see a clear solution to and have delivered similarly in the past +- Will proactively pick up complex features, but will seek guidance on approach before proceeding and will seek feedback via pull requests and pairing from senior members of the team +- Will take initiative as to whether they can resolve issues themselves or need to loop in more senior member of the team +- Is building an awareness of how Made Tech is perceived by customers and partners, as well as how they and their colleagues are perceived by other colleagues – is developing a sense when something isn't right and needs escalating +- Influencing workstream at a feature level, helping to define features and approaches for delivering them +- Influencing a wider range of colleagues through sharing opinions and ideas in forums outside of their immediate deliveries +- Expected to also seek opportunities to share opinions and ideas to peers within customer and partner organisations +- Provides guidance and support to more junior members of the team in helping them identify what work to pick up +- Able to iteratively deliver features of reasonable complexity, in known contexts +- Able to architect and deliver simple features in new contexts +- Uses a range of techniques and best practices to build easy to maintain solutions +- Has developed strong debugging skills, and can remediate issues both locally and in deployed environments +- Able to work effectively in brownfield projects within days +- Proficient in multiple languages, frameworks and technologies +- Able to be proficient within many contexts due to varied and deepening knowledge of technologies +- Able to mentor, train and coach others in their areas of knowledge +- Are endorsed by colleagues as knowledgeable in a number of skills +- Working towards industry recognised training certifications +- Shares knowledge with others through blog posts and talks +- Demonstrates effective communication skills +- Plans, schedules and monitors own work (and that of others where applicable) competently within limited deadlines and according to relevant legislation, standards and procedures +- Contributes fully to the work of teams. Appreciates how own role relates to other roles and to the business of the employer or client +- Demonstrates an analytical and systematic approach to issue resolution +- Takes the initiative in identifying and negotiating appropriate personal development opportunities +- Understands how own role impacts security and demonstrates routine security practice and knowledge required for own work diff --git a/handbook/handbook-main/roles/sfia (legacy)/principal_technologist.txt b/handbook/handbook-main/roles/sfia (legacy)/principal_technologist.txt new file mode 100644 index 0000000000000000000000000000000000000000..dd7bd8944535747d5e83cb66296ba6f778caed15 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/principal_technologist.txt @@ -0,0 +1,51 @@ +# SFIA Role Guidance: Principal Technologist + +[SFIA 6: Initiate, Influence](https://sfia-online.org/en/sfia-7/responsibilities/level-6) + +[« previous](lead_software_engineer.md) + +## Summary of role + +Enables public sector organisations to better use technology in order to improve society. They do this by building and managing strategic relationships, leading accounts, finding new opportunities and advising as a senior technology leader. + +## Required competency for role + +### Autonomy + +Accountable for the technology strategy within an account, technical direction and quality of workstreams, and driving new opportunities through technical advice. + +### Influence + +Builds and maintains influential relationships with senior leadership, particularly technology leaders, of customer and partner organisations as well as wider industry. + +### Complexity + +Has a broad business understanding, a deep understanding of digital and technology and performs highly complex work activities covering technical, financial and quality aspects. + +### Knowledge + +Develops a deep understanding of digital and technology landscape in UK public sector, including customers, suppliers, partners and competitors. + +### Business Skills + +Demonstrates clear leadership. Communicates effectively at all levels to both technical and non-technical audiences. + +## Examples of behaviours and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Works with workstreams to ensure technical direction is aligned across our work and with customers organisation +- Builds and maintains relationships with senior customer and partner leadership, particularly senior technology leadership +- Responsible for Made Tech’s reputation within an account and ensuring our teams are perceived positively by customers, partners and suppliers +- Coaches and supports Lead Software Engineers to deliver their workstream outcomes successfully +- May perform role across one or more accounts +- Operates as senior hiring manager of technology staff within the region +- Works closely with regional leadership to ensure the account plan is aligned with regional growth goals +- Identifies and generates new opportunities within an account and region through networking, advice and thought leadership +- Able to lead, create and present proposals for opportunities as part of the bid process +- Defines account plan as part of an account team and leads the team to deliver against it +- Has authority over account's technology staff, though as a servant leader seeks to facilitate rather than make decisions in isolation +- Works with regional leadership to define regional hiring requirements +- Works with group technology leader (CTO) to define both regional and group outcomes for technology, and coordinates regional technologists to deliver these outcomes +- Nurtures and grows their own professional network and can use this to support and win new business +- Is known as a technology leader within their region diff --git a/handbook/handbook-main/roles/sfia (legacy)/senior_content_designer.txt b/handbook/handbook-main/roles/sfia (legacy)/senior_content_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..bae63fe05fec1213266e8893bbe60d85febc4f51 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/senior_content_designer.txt @@ -0,0 +1,97 @@ +# SFIA Role Guidance: Senior Content Designer +- [SFIA Level 4: Enable](https://sfia-online.org/en/sfia-7/responsibilities/level-4) +- [Job description](https://github.com/madetech/handbook/blob/main/roles/senior_content_designer.md) + +## Summary of role +Our Senior Content Designers are strong practitioners who work with minimal support and can influence and mentor others to meet user needs and make complex processes easy to understand. They do this by setting the direction, assuring the quality of content design delivery within a team working on a complicated and large scale service. They are vocal and visible contributors to a healthy user-centred design (UCD) community and culture at Made Tech. + +## Required competency for role +### Autonomy +- Works under general direction from Lead Content Designers and UCD Principals within a clear idea of what they are accountable for delivering. +- Exercises substantial personal responsibility and autonomy for delivering quality work on time and assisting others in their team. +- Plans own content design to meet given team goals and ways of working. + +#### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ +- Proactively requests feedback from the people they work with. Able to honestly self reflect. +- Practices open and honest communication, active listening and demonstrates empathy and patience. +- Takes ownership of content strategy and solutions. Works closely with teammates to understand user needs and create the right content design approach. +- Creates, iterates and manages user-centred content using analytics, user feedback, and user research, as well as contributing to content principles, improvements and patterns. +- Works with team to understand why key ideas are being tested. +- Documents prototype changes and versions after each round of research for transparency and trust. +- Works within their team to create an efficient design process for testing ideas little and often. Ensures content design guides and operating models are being followed +- Owns and advocates for the usability and accessibility of design work going to production. +- Works closely with engineers to ensure major usability and accessibility issues within the team's control are addressed. + +--- + +### Influence +- Mentors others in their teams about content design techniques and approaches. +- Line managing a small number of mid and junior content designers. +- Makes content design decisions that influence the success of the project and team goals. +- Collaborates regularly with teammates and service users. +- Engages to ensure that user needs are being met throughout. Participates in external activities related to content design. + +#### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ +- Works closely with the team to identify user needs, write and map user stories, design content plans, create and publish content +- Drives team towards good quality content design by influencing their whole team to work on problems in a suitable way. +- Line manages content designers new to Made Tech and the public sector. Coaches them on where to spend energy and what to compromise on, using the design guides and operating models as reference. +- Presents clearly and confidently the design decisions at the start of each sprint to the whole team. Making it clear what hypotheses the prototypes are trying to prove or disprove. +- Regularly pairs with other disciplines in their team such as user researchers. Able to see when this is needed to move work forward and show the value of working closely together like this. +- Writes key content to form part of a minimal viable service a team can ship as its first release. +- Interprets what is most valuable to users and is feasible given the current systems being used. +- Advocates for the user consistently and regularly in and outside the team. Pushing for content design changes that will have the most impact while being possible to deliver quickly. +- Breaks a service down into content that can be delivered incrementally while still delivering value for users and outcomes for the client organisation. + +--- + +### Complexity +- Leads content design within their team. +- Investigates, defines and resolves complex content problems within a service. +- Removes and adds content and language to make simple services that can be delivered quickly and improved upon with real user feedback. + +#### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ +- Designs content to meet user needs and make complex language and processes easy to understand. +- Understands and implements content design style and standards. +- Able to translate user stories and propose design approaches or services to meet user needs. Able to use quantitative and qualitative data about users to turn user focus into outcomes. Knows when to apply gov.uk style guides and patterns. +- Working with a designer to turn a new government policy into prototypes to test with users. + +--- + +### Knowledge +- Has a thorough understanding of different content design techniques and ways of working. Can either quickly apply their own content design knowledge of the public sector or have personal experience of it they can draw upon. +- Applies knowledge effectively in unfamiliar situations and actively maintains own knowledge and contributes to the development of others. +- Rapidly absorbs new information about a problem space and its users and applies it effectively. +Maintains an awareness of developing content design practices and their application and takes responsibility for driving own personal growth. + +#### Examples of behaviour and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ +- Thorough understanding of GOV.UK Proposition, Design System and style guide and why it’s needed. Keeps to these components and systems wherever possible and understand the team time needed to create a new component or review content on an existing site. +- Explains their role as Content Designer in the different GDS service design phases. Can advise a client or team how to get the best value out of their time. +- Reads around the wider context of their teams work, be that client blog posts, ministerial announcements or news about a new policy. Can communicate the policy intent behind the work and how it relates to making the language of what can be complex policies easy to understand. +- Suggests activities and tools to their team for designing a service with fewer barriers for people with disabilities and other access needs. +- Attends events relating to public sector content design. Shares learnings with the wider community of practice at Made Tech. +- Trials a new content technique from other organisations in their own team. Then, evaluates how effective the technique is and shares learning with the wider community of practice. +- Decide what is the most effective way to test an idea, be that card sorting, a paper prototype or A/B test. + +--- + +### Business Skills +- Communicates fluently, orally and in writing, and can present complex information to both design and non-design audiences. +- Plans, schedules and monitors work to meet time and quality expectations. +- Facilitates collaboration between stakeholders who share common objectives. +- Selects appropriately from applicable design standards, methods, tools and applications. + +#### Examples of behaviours and responsibilities +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ +- Blogs clearly about ideas that have tested well and badly. Communicate what worked (and didn't) and why. +- Manages own time to get designs or content changes ready for testing with users. Is able to fit in other responsibilities like line management without it affecting their team's ability to learn and deliver value. +- Facilitates a workshop with their team and stakeholders to show how the different steps of a service might fit together. Is able to hold and move on conversations. +- Can demonstrate user needs focus underpinning decisions on Information Architecture, patterns, layout, language and design to stakeholders who may have had other preferences. +- Supports the development of content design at Made Tech. +- Represents Made Tech in the wider UCD community through writing or speaking. +- Trustworthy, acts with integrity, openness and impartiality. +- Able to navigate and handle conflict within teams and with stakeholders. +- Support the sales team in proposal writing. diff --git a/handbook/handbook-main/roles/sfia (legacy)/senior_delivery_manager.txt b/handbook/handbook-main/roles/sfia (legacy)/senior_delivery_manager.txt new file mode 100644 index 0000000000000000000000000000000000000000..33f12432a3db05bebd35cf277a4c008d78d06c03 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/senior_delivery_manager.txt @@ -0,0 +1,103 @@ +# SFIA Role Guidance: Senior Delivery Manager + +[SFIA Level 5: Follow](https://sfia-online.org/en/sfia-7/responsibilities/level-5) + +[« previous](delivery_manager.md) + +## Required competency for role + +### Autonomy + +Understands software delivery in depth and has extensive experience in delivering tech solutions, with user-focused outcomes. + +Is fully autonomous and requires very little, broad direction. + +Is ultimately accountable for delivery success and has proven this accountability in multiple deliveries, with little support. + +Defines and drives the e2e delivery (from inception to close out). + +Builds strong customer relationships & is considered the ultimate POC for escalating issues. + +Seeks feedback & initiates discussions on complex problems with Senior delivery / tech people. + +### Influence + +Influences and drives the success of the delivery; plays a key role in the ways the team works and delivers value to Made Tech's customers. + +Builds strong relationships with customers and ensures customer satisfaction; Able to mediate and mend relationships, communicating with stakeholders at all levels. + +Proven record of managing stakeholders’ expectations and facilitating discussions with high risk and complexity (e.g under constrained timescales, with impact to account viability, MT reputation, financial results and profitability). + +Accountable for all decisions made within the delivery (non-tech) and ultimately drives delivery success - proven record this has delivered user-focused outcomes for MT customers. + +Although not accountable for tech decisions, is aware of the key tech decisions being made and challenges tech colleagues where appropriate. + +Leads customers to a successful e2e delivery and has proven experience in leading a delivery from inception to close out; helps to guide, upskill, mentor both team & client members. + +Coaches MT Delivery managers and helps with their upskilling. + +Proven record of advising teams across MT on modern software delivery principles. + +### Complexity + +Able to lead any kind of delivery and proven record of operating over multiple workstreams, delivering user value and user-focused outcomes. + +Successfully deals with highly complex situations and delivery issues, with broad guidance (e.g under constrained timescales, with impact to account viability, MT reputation, financial results and profitability). + +Deals with difficult customers / stakeholders, and have proven they can do so successfully in different occasions / contexts. + +Can break through inital resistance to change and successfully introduce new ways of working and delivery improvements. + +Ensures value for users is always delivered at the account level and is able to remediate this by introducing techniques to surface user needs and measure the success of the delivery against those. + +Finds ways to help our customers, beyond the traditional DM responsibilities ensuring our customers understand and see that the MT mission spans from delivering software to helping organisations and delivery teams build capabilities, grow and improve. + +Upskills and helps customers & team members to resolve complex, often out of the ordinary, issues. + +Advises junior & mid-level DMs in how to best deal with complexity. + +### Knowledge + +Has extensive agile & lean knowledge and has applied advanced principles in different scenarios; Is a recognised expert that advocates these approaches, continuously reflecting and challenging the status quo. + +Has extensive delivery knowledge and experience; will typically have delivered numerous tech projects and proven record of leading, supporting, advising on how to best run a delivery e2e. + +Remains at the forefront of both agile & delivery topics & new ideas, ensuring they gain new knowledge proactively and regularly. + +Has great knowledge of modern software development/delivery practices & has applied these in multiple deliveries, helping teams become high-performing and successfully deliver outcomes - is able to help guide teams on improvements and best practices. + +Proven record of advising teams across MT on modern software delivery principles. + +Coaches juniors & mid DMs into best practices of software delivery. + +Has participated in numerous bids, proving a deep understanding of what success looks like in the bid process and how best to contribute to a successful bid. + +Shares this knowledge with the wider organisation. + +Shares this knowledge with the customers at every opportunity. + +### Business Skills + +Demonstrates leadership. + +Communicates effectively, both formally and informally. + +Facilitates collaboration between stakeholders who have diverse objectives. + +Analyses, designs, plans, executes and evaluates work to time, cost and quality targets. + +Analyses requirements and advises on scope and options for continuous operational improvement. + +Takes all requirements into account when making proposals. + +Demonstrates creativity, innovation and ethical thinking in applying solutions for the benefit of the customer/stakeholder. + +Advises on the available standards, methods, tools and applications relevant to own specialism and can make appropriate choices from alternatives. + +Maintains an awareness of developments in the industry. Takes initiative to keep skills up to date. Mentors colleagues. + +Assesses and evaluates risk. + +Proactively ensures security is appropriately addressed within their area by self and others. + +Engages or works with security specialists as necessary. Contributes to the security culture of the organisation. diff --git a/handbook/handbook-main/roles/sfia (legacy)/senior_designer.txt b/handbook/handbook-main/roles/sfia (legacy)/senior_designer.txt new file mode 100644 index 0000000000000000000000000000000000000000..83cf565b3393e1f8272347ff08da38bdf4db5437 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/senior_designer.txt @@ -0,0 +1,136 @@ +# SFIA Role Guidance: Senior Designer + +- [SFIA Level 4: Enable](https://sfia-online.org/en/sfia-7/responsibilities/level-4) +- [Job description](../senior_designer.md) + +## Summary of role + +Our Senior Designers are strong practitioners who work with minimal support and can influence and mentor others to design and deliver public services. They do this by setting the direction, assuring the quality of design delivery within a team working on a complicated and large scale service. They are vocal and visible contributors to a healthy user-centred design (UCD) community and culture at Made Tech. + +## Required competency for the role + +### Autonomy + +* Works under general direction from Lead Designers and UCD Principals within a clear idea of what they are accountable for delivering. +* Exercises substantial personal responsibility and autonomy for delivering quality work on time and assisting others in their team. +* Plans own design to meet given team goals and ways of working." + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Takes ownership for user research happening regularly. Works to involve teammates in planning, conducting and analysing user research sessions. + +- Takes accountability for creating and regularly updating team prototypes. + +- Works with team to understand why key ideas are being tested. + +- Documents prototypes changes and versions after each round of research for transparency and trust. + +- Works within their team to create an efficient design process for testing ideas little and often. + +- Owns and advocates for the usability and accessibility of design work going to production. + +- Works closely with engineers to ensure major usability and accessibility issues within the team's control are addressed. + +--- + +### Influence + +* Drives team towards good quality design by influencing their whole team to work on the useful problems in a suitable way. +* Mentors non-designers in their teams about design techniques and approaches. Line managing a small number of mid and junior designers. +* Participates in external activities related to design. +* Makes design decisions that influence the success of the project and team goals. +* Collaborates regularly with teammates and service users. +* Engages to ensure that user needs are being met throughout. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Line managers designer new to Made Tech and public sector. Coaches them where to spend energy and what stuff to compromise on. + +- Presents clearly and confidently the design decisions at the start of each sprint to the whole team. Making it clear what hypotheses the prototypes are trying to prove or disprove. + +- Regularly pairs with other disciplines in their team such as software engineers. Able to see when this is needed to move work forward and show the value of working closely together like this. + +- Prototypes key features to form part of a minimal viable service a team can ship as its first release. + +- Interprets what is most valuable to users and feasible given the current systems being users. + +- Advocates for the user consistently and regularly in and outside the team. Pushing for design changes that will have the most important while actually possible to deliver quickly. + +- Breaks a service down into features that can be delivered incrementally while still delivering value for users and outcomes for the client organisation. + +--- + +### Complexity + +Leads service design within their team. Investigates, defines and resolves complex design problems within a service. Remove and add features to make simple services that can be delivered quickly and improved upon with real user feedback. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Translates a paper form into prototype flow of pages, breaking down information into logical steps and tasks. + +- Audits existing design of a service. Identifies opportunities for consolidation and removal of design features. Where to apply gov.uk design patterns and components. + +- Working with a content designer to turn a new government policy into prototypes to test with users + +- Prototypes three different ways to potentially solve the same problem for a user task + +- Visualises a complex user journey of an existing service to improve team discussion + +--- + +### Knowledge + +* Has a thorough understanding of different design techniques and ways of working. Can either quickly apply their own design knowledge to the public sector or have personal experience to draw upon. +* Gained a thorough knowledge of the domain of a client organisation. +* Applies knowledge effectively in unfamiliar situations and actively maintains own knowledge and contributes to the development of others. +* Rapidly absorbs new information about a problem space and its users and applies it effectively. +* Maintains an awareness of developing design practices and their application and takes responsibility for driving own personal growth. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Thorough understanding of GOV.UK Design System and why it’s needed. Keeps to design components wherever possible and understand the team time needed to create a new component. + +- Explain their role as a designer in the different GDS service design stages. Can advise a client or team how to get the best value out of their time. + +- Reads around the wider context of their teams work, be that client blog posts, ministerial announcements or news about a new policy. Can communicate the policy intent behind the work and how it relates to what a design needs to achieve. + +- Suggests activities and tools to their team for designing a service with fewer berries for people with disabilities and other access needs. + +- Attends events relating to public sector design or user research. Share learnings with the wider community of practice at Made Tech about what ideas from the idea might copying and trialling. + +- Trials a new design technique from another organisation in their own team. Evaluate how effective the tool is and shares learning with the wider community of practice. + +- Decides what is the most effective way to test an idea, be that a paper prototype or A/B test. + +--- + +### Business Skills + +- Communicates fluently, orally and in writing, and can present complex information to both design and non-design audiences. + +- Plans, schedules and monitors work to meet time and quality expectations. + +- Facilitates collaboration between stakeholders who share common objectives. + +- Selects appropriately from applicable design standards, methods, tools and applications. + + +#### Examples of behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Blogs clearly about ideas that have been tested. Communicates what work (and didn't) and why. + +- Manages own time to get prototype work ready for testing with users. Is able to fit in other responsibilities like line management without it affecting their team's ability to learn and deliver value. + +- Facilitates a workshop with their team and some stakeholders to show how the different steps of a service might fit together. Is able to hold and move on conversations and visualise team thinking in artefacts like user journeys. + +- Advise on prototype techniques that make the most sense for a team’s ideas and hypotheses to test. diff --git a/handbook/handbook-main/roles/sfia (legacy)/senior_software_engineer.txt b/handbook/handbook-main/roles/sfia (legacy)/senior_software_engineer.txt new file mode 100644 index 0000000000000000000000000000000000000000..3a27537841acc9c221124a235aaaf01b7d13a018 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/senior_software_engineer.txt @@ -0,0 +1,66 @@ +# SFIA Role Guidance: Senior Software Engineer + +[SFIA Level 4: Enable](https://sfia-online.org/en/sfia-7/responsibilities/level-4) + +[« previous](mid_software_engineer.md) | [next »](lead_software_engineer.md) + +## Summary of role + +Senior contributor to digital, data and technology outcomes that improve society. They do this by delivering and architecting software, and coaching others to do so in public sector organisations. + +## Required competency for role + +### Autonomy + +Collaboratively leads workstream team to deliver complex change and supports development of others to do the same. + +### Influence + +Facilitates the design of architecture, technical decision making and agreeing ways of working. + +### Complexity + +Manages complex technical change across multiple systems and legacy technology. + +### Knowledge + +Expert across multiple languages, frameworks and technologies. + +### Business Skills + +Communicates fluently, orally and in writing, and can present complex information to both technical and non-technical audiences. + +## Examples of behaviours and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Ships complex features collaboratively and independently as appropriate and is recognised as a key player of the team +- Pairs with and coaches junior members of the team and/or customer staff, supporting line managers to find career progression opportunities within the workstream +- Able to lead a bootup and delivery of a product workstream where outcomes are known, and the product is complicated rather than complex, with support and coaching from a Lead +- Continues to seek consensus with approaches, and feedback on work as it is iteratively delivered +- Confidently facilitates retrospectives and other team ceremonies regularly, and delivers Showcases +- Has strong awareness of how Made Tech is perceived by customers and partners, as well as how colleagues and themselves are perceived by other colleagues. Will provide direct performance data and feedback in order to rectify the situation +- Plays an active part in evolving Made Tech's approach to modern technology delivery +- Identifies performance issues within the workstream team and works with individuals and line managers supporting corrective action where necessary +- Facilitates the design of architecture with customers, partners and workstream team through workshops and other collaborative formats +- Shapes backlog collaboratively, providing technical leadership within backlog planning and refinement sessions, as well as in three amigos +- Influences ways of working and helps to facilitate alignment between customers, partners and workstream team +- Influences Made Tech account leads in terms of how the account is organised and run. +- May have (or shares with customer) authority over approach to delivering workstream, though as a servant leader seeks to facilitate rather than make decisions in isolation +- Likely leads or is a major contributor to meetups, communities of practice and working groups +- Engages outside immediate worksteam as a trusted advisor to customers and partners +- Engages to ensure that user needs are being met throughout +- Able to architect and deliver complex features +- Able to work across multiple applications to deliver system-wide features and changes to architecture +- Able to navigate large customer organisations +- Can deliver legacy migrations +- Able to maintain a calm and collected approach to fixing issues in chaotic environments +- Has deep knowledge of Made Tech both commercially and technically +- Able to lead hiring interviews for Engineer 1 to Senior Engineer candidates +- Are endorsed by colleagues as expert in a number of skills +- Seen by customer as an expert in their domain +- Able to apply technical knowledge within complex environments +- Has passed industry recognised training certifications at a professional level +- Actively mentoring, training and coaching colleagues in areas of expertise +- Can rapidly learn new technology +- Spearheads introduction of new concepts into Made Tech diff --git a/handbook/handbook-main/roles/sfia (legacy)/senior_user_researcher.txt b/handbook/handbook-main/roles/sfia (legacy)/senior_user_researcher.txt new file mode 100644 index 0000000000000000000000000000000000000000..ecbf2110c5ee84a1b0199812595eed62733a4d48 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/senior_user_researcher.txt @@ -0,0 +1,93 @@ +# SFIA Role Guidance: Senior User Researcher + +- [SFIA Level 4](https://sfia-online.org/en/sfia-7/responsibilities/level-4): Enable +- [Job description](../senior_user_researcher.md) + +## Summary of role + +Our Senior User Researchers play a key role in leading project teams and setting direction for project work. They’re expert practitioners, confident leading the planning and running of user research on complicated and large scale public sector projects. They are vocal and visible contributors to our user-centred design (UCD) community and culture at Made Tech. + +## Required competency for role (with example behaviours) + +### Autonomy + +Self-initiates and works with little direction of where to focus energy to research, design and deliver good public services with their team. Takes responsibility for the team focusing their research in the right areas, using the most appropriate methodologies and expertise in guiding teams to producing the most impactful research outputs. Works with to define and assign research tasks to themselves and others. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Proactively requests feedback from the people they work with. Able to honestly self reflect +- Practices open and honest communication, active listening and demonstrates empathy and patience +- Take responsibility for work and decisions and embeds a no blame attitude in teams +- Assess quickly what design leadership a team needs to deliver a user-centred service and fills this role without being asked to. +- Assures the quality of research work going into software production +- Shares good practice from own experience and other sources for how and why a team does activities like in-depth interviews with users or low fidelity prototypes +- Shows work at community show and tells + +### Influence + +Drives team towards research excellence by influencing team, stakeholders and partners. + +Able to support teams making decisions based on balancing research evidence against organisational needs and constraints +Identifies key stakeholders, tailoring communication to their needs. Ability to influence stakeholders and teams to practice user centred design in their organisation + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Able to hold and inform the strategic vision of our clients through user research +- Works with the client to set team priorities for work +- Able to create and share a clear, tangible and understandable vision for the role and direction of user research +- Is an advocate for users and able to focus teams on the key needs +- Shows they are role model for less senior researchers and set an example for how to be professional, supportive and effective +- Successfully challenges decisions not informed by user research +- Coaches less senior researchers taking on line management for the first time and how to grow into this new responsibility + +### Complexity + +Leads user research with their team within a wider programme of work in multi-organisation stakeholder environments. Able to balance complex user and organisational needs and use research to inform design, strategy and processes. + +#### Examples of behaviour and responsibilities + +- Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. +- Confident managing complex stakeholder groups +- Demonstrates understanding and empathy for stakeholders +- Produces research outputs that are suitable for the type of project, type of stakeholders and audience ensuring it has impact and leads to decision making +- Able to plan and lead on complex programmes of research +- Establishes research activities and structure within a team previously not working in a agile, open or user-centred way +- Breaks down silos within their team and has UCD roles and people in other disciplines working towards the same goals. +- Shares research with other delivery teams within the client organisation and shows the need for close coordination between teams + +### Knowledge + +Deep understanding of user research quantitative and qualitative methodologies and is competent at understanding how and when to apply different approaches. +Wide range of quantitative and qualitative experience, highly competent with a range of methodologies + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Understands how and when to apply different methodologies across the design cycle +- Able to create appropriate, clear and compelling findings. Experienced in how to deliver them to reflect the needs of individual projects and clients and ensure strong outcomes +- Experience working with other user centred design disciplines and a deep understanding of how user research works cohesively with these disciplines +- Competent at the leading the planning of research approaches +- Understanding of how to include and consider and involve traditionally marginalised and oppressed groups to deliver accessible services that work for all users +- Deep understanding of conducting ethical and inclusive research and confident leading and upskilling teams +- Can help teams understand the diversity of users of government services. Knows how to include all kinds of users in appropriate research activities. Can advocate for inclusive practices and help teams design + +### Business Skills + +Demonstrates leadership. Communicates effectively, both formally and informally + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Supports the development of user research at Made Tech +- Represents Made Tech in the wider UCD community through writing or speaking +- Trustworthy, acts with integrity, openness and impartiality +- Able to navigate and handle conflict within teams and with stakeholders +- Can help colleagues understand how digital technology is changing user behaviour, and the challenges and opportunities for government services. +- Has knowledge of the technologies used to build and operate digital services. Can collaborate closely with colleagues in different digital disciplines +- Supports the sales team in proposal writing diff --git a/handbook/handbook-main/roles/sfia (legacy)/team_assistant.txt b/handbook/handbook-main/roles/sfia (legacy)/team_assistant.txt new file mode 100644 index 0000000000000000000000000000000000000000..6e16b1ef2120249e65e5dc17d1f81f89f45ef50e --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/team_assistant.txt @@ -0,0 +1,66 @@ +# SFIA Role Guidance: Team Assistant + +[SFIA Level 2: Follow](https://sfia-online.org/en/sfia-7/responsibilities/level-2) + +[next »](junior_delivery_manager.md) + +## Required competency for role + +### Autonomy + +With limited experience in modern software delivery. Still learning how Made Tech delivers solutions & works with its customers. + +Able to perform all functional aspects of the role autonomously such as a budget management, reporting, schedulingm and SOW development. + +Seeks guidance and help about the best way to perform key role activities such as facilitating team ceremonies, team and client meetings, and hangling challenging situations. + +Seeks and receives constructive feedback for entry level activities, aiming to regine and build strong basic knowledge in software delivery and supporting teams. + +Seeks for advice on how to resolve delivery issues and how best to engage with customers and external parties. + +### Influence + +Has an awareness of the importance of team dynamics, collaboration and empowering delivery teams. Understands the importance of feedback, at a team or personal level. + +Understands the importance of early feedback and has actioned on this numerous times within teams. Challenges other Made Tech colleagues ideas tactfully when in disagreement. + +Has been involved in and in some cases has even become responsible for running workshops, retrospectives or other activities where ideas and opinions are shared between customers and Made Tech colleagues. + +Shows clear signs of awareness and appreciation of the important of high team morale - understands how to act upon situations where this needs to be improved. + +Proven record of forming successful relationships with customers at all levels. + +### Complexity + +With little or no experience in dealing with complexity within the tech world - requires assistance to adapt to team delivery & team specific needs - asks for help when presented with team-related issues that are unusual / challenging. + +Deals with complexity at the team & team morale level, but usually not at the delivery level. + +Will often need to seek advice to understand what is possible in a given situation. + +Understands how the risks, issues or dependencies can impact the team and its success and is able to identify most of them without support (this refers to internal risks & issues and does not apply to the wider delivery). + +Able to identify and assess risks, issues or dependencies with medium or high complexity and expected be proactive about ensuring these are captured and discussed further / get escalated. + +### Knowledge + +Has or is in the process of developing knowledge around the key delivery & agile principles. + +Seeks advice if needed to apply these principles in practice as they are expected to have very limited experience to delivery. + +Has an awareness of Agile tools and is starting to use them intelligently. + +Has an awareness of key software development principles. + +Has an awareness of the functional side of the DM role ie managing budgets, reporting, EOS facilitation and experienece into owning these. + +### Business Skills + +Has sufficient communication skills for effective dialogue with customers, suppliers and partners. + +Is able to work in a team. Is able to plan, schedule and monitor own work within short time horizons. Demonstrates a rational and organised approach to work. + +Understands and uses appropriate methods, tools and applications. +Identifies and negotiates own development opportunities. + +Is fully aware of and complies with essential organisational security practices expected of the individual. diff --git a/handbook/handbook-main/roles/sfia (legacy)/ucd_principal.txt b/handbook/handbook-main/roles/sfia (legacy)/ucd_principal.txt new file mode 100644 index 0000000000000000000000000000000000000000..cf3239d5d88dd76de11f64cac909e03506460e99 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/ucd_principal.txt @@ -0,0 +1,151 @@ +# SFIA Role Guidance: UCD Principal + +- [SFIA Level 6](https://sfia-online.org/en/legacy-sfia/sfia-7/responsibilities/level-6) +- [Job description](https://github.com/madetech/handbook/blob/main/roles/sfia%20(legacy)/ucd_principal.md) + +## Summary of role + +Our User-Centred Design (UCD) Principals enable public sector organisations to better design services in order to improve society. They do this by building and managing strategic relationships, leading accounts, finding new opportunities, creating space for teams to do good work and advising as a senior design leader. + +They might have built their leadership skills as a designer, user researcher, content designer or design manager. + +## Required competency for the role + +### Autonomy + +Has ultimate authority and is responsible for the productivity and quality of design and user research on selected client accounts, consisting of multiple teams. Establishes organisational objectives with client and account team. Assigns broad responsibilities and direction to UCD Leads and Seniors within teams. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Make changes within a team when the quality of work is not of a high standard + +- Acknowledges with the client when design work is not progressing and makes a plan for how to quickly improve the speed of delivery + +- Takes responsibility for addressing any issues that are blocking their teams from delivering a good service. + +- Sets the unifying design vision for their different teams to work towards + +- Works with client to define the direction for a team as it's being assembled + +- Assigns line managers to new people informed by people learning objectives. + +- Works within an account team to plan, grow, and improve the outcomes teams are delivering and ways of working + +- Accountable for the growth and promotion of people they direct and indirectly line manage. + +- Meeting targets for team growth across multiple offices. + +- Owning the bidding of new work with a big emphasis on user-centred design. + +--- + +### Influence + +* Drives team towards design excellence by influencing teams, stakeholders and partners. +* Influences policy and strategy formation through building relationships and communicating vision. +* Initiates influential relationships with most senior client stakeholders and peers within an account team. +* Persuades peers and stakeholders to focus on the right user needs, outcomes and team working conditions to design a good service. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Convinces a client to create a new delivery team focussed on a strategically important problem or opportunity. + +- Brings user researchers into an existing client account, which previously didn’t have any UCD roles. + +- Brings senior operations, technical and policy leaders into the design process, creating buy-in for the next stage of delivery. + +- Advises Chief Design Officer at a government department on recruitment strategy for growing their UCD community + +- Regularly sources and hires people for senior UCD roles. + +- Regularly speaks and shares ideas in and outside Made Tech about how to run communities of practice. + +- Successfully supports someone they line manage to get promoted to a Lead or Principal + +- Sets the creative direction for a bid for new work and takes the lead for a bid team + +--- + +### Complexity + +* Clearly communicate the wider organisational context teams will have to deliver in. +* Identifies and communicates the fundamental problem policies, teams and services that exist to try to solve. S +* hows a deep understanding of their UCD discipline and how it applies to a specific problem space. +* Assesses the design maturity of client organisations and applies a wide range of design and/or management principles suitable for getting good services delivered. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Is aware and can explain the client motivations for creating a team in the first place, be those political commitments, legacy tech or operational costs. + +- Can explain to teammates and stakeholders how user-centred design will help de-risk a specific project and how it relates to the specific problem area. Be that farming or social housing. + +- Leads the development of experimental new services that require emergent technology or user behaviour change. + +- Leads strategic discovery phase with the government department to start work on key policy areas, such as planning reforms + +- Presents strategic findings at the executive level to a client organisation. Follows up individually with different senior stakeholders. + +- Quickly takes policy documents and early conversations to make an MVP prototype. + +- Leads the accelerated delivery of new service response to a quick-growing need, such as a pandemic. + +- Coaches less senior UCD people to navigate complex and difficult work + +--- + +### Knowledge + +Develops a deep understanding of design in the UK public sector. + +#### Examples of behaviour and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Make training videos for Made Tech people new to UCD or design in government, to show how discovery and alpha phases can work. + +- Coaches client team to get ready for a GDS service assessment, drawing on their own experiences going through the process. + +- Run accessibility talks for client teams who are unsure who to approach designing for people with access needs. + +- Speaks at a public panel discussion about Made Tech’s approach to improving the citizen experience of local government. + +- Runs introduction to UCD in government as part of Onboarding week at Made Tech + +--- + +### Business Skills + +* Demonstrates clear leadership. Communicates effectively at all levels to both design and non-design audiences. +* Understands and communicates industry developments, and the role and impact of design in the employing organisation. Absorbs complex information. +* Promotes diversity, inclusion and the need for services, teams and working practices to provide equal access and equal opportunity to people with diverse abilities. +* Takes the initiative to keep both their own and colleagues' skills up to date. +* Manages and mitigates risks across client programmes of work and across Made Tech. + +## Examples of behaviours and responsibilities + +_Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only._ + +- Speaks at a public panel discussion about Made Tech’s approach to improving the citizen experience of local government. + +- Speak to the Head of User Research at a government department about how Made Tech integrates UCD roles with operations in the run-up to a bid. + +- Sets the vision for user-centred design at Made Tech and how that fits into the sector’s transformation of public services. + +- Proactively gets someone levelling someone’s role who’s performing at a higher level of maturity than we hired them for. + +- Blogs about how APIs and thoughtful service design can lay the foundations for quicker, more accurate carbon taxes on vehicles. Frames ideas around the recent and increasing introduction of ultra-low emission zones in UK cities. + +- Works closely with stakeholders blocking team delivery due to concerns and unfamiliarity with the agile way of working. Listens to both sides of the sticking points between the team and the stakeholder. + +- Works with others to rotate UCD people from teams to improve delivery outcomes and provide better learning opportunities for people to progress. + +- Organises away day for their community-of-practice, to facilitate group learning, bonding and get feedback on the vision for the team. + +- Creates and runs an Academy session on the fundamentals of user research. + diff --git a/handbook/handbook-main/roles/sfia (legacy)/user_researcher.txt b/handbook/handbook-main/roles/sfia (legacy)/user_researcher.txt new file mode 100644 index 0000000000000000000000000000000000000000..5e3008265b672264e05ce4e474e37327261b6a16 --- /dev/null +++ b/handbook/handbook-main/roles/sfia (legacy)/user_researcher.txt @@ -0,0 +1,91 @@ +# SFIA Role Guidance: User Researcher + +- [SFIA Level 3](https://sfia-online.org/en/legacy-sfia/sfia-7/responsibilities/level-3) +- [Job description](https://github.com/madetech/handbook/blob/main/roles/sfia%20(legacy)/user_researcher.md) + +### Summary of role + +Our User Researchers work within service teams. They support the planning of user research activities and carry them out . They’re confident practitioners, able to support our seniors and leads to plan and run user research as part of a team on public sector projects. They are contributors to our user-centred design (UCD) community and culture at Made Tech. + +### Required competency for role (with example behaviours) + +### Autonomy + +Works with guidance from Senior User researcher on the focus of work. Can plan own user research activities to design and deliver good public services with their team. Contributes to selecting the most appropriate methodologies for producing the most impactful research outputs. Supports the adoption of agreed approaches. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Able to give and receive feedback from the people they work with. Able to honestly self reflect +- Practices open and honest communication, active listening and demonstrates empathy and patience +- Take responsibility for their own work and decisions and participates in / supports a no blame attitude in teams +- Shares good practice from own experience and looks to continually develop skills and knowledge of conducting activities like in-depth interviews with users or low fidelity prototypes +- Contributes to community show and tells + +### Influence + +Contributes to team success in research excellence. +Able to explain research results and influence team, stakeholders and partners. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Able to understand, analyse and share research results to contribute to teams making decisions based on balancing research evidence against organisational needs and constraints +- Can explain and involve stakeholders and teams in user centred design activities +- Understands the strategic vision of our clients that needs to be informed through user research +- Can manage their time effectively to prioritise and plan activities +- Is an advocate for users. Able to take direction from Senior User Researcher on the key needs +- Highlights decisions not informed by user research + +### Complexity + +Conducts user research in their team within a project that may be part of a wider programme of work in multi-organisation stakeholder environments. Conducts research to inform design, strategy and processes. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Conducts research activities with stakeholder groups +- Demonstrates understanding and empathy for stakeholders +- Produces research outputs that are suitable for the type of project, type of stakeholders and audience ensuring it has impact and leads to decision making +- Conducts research activities that enables working in an agile, open or user-centred way +- Shares results with all team members within their team to ensure people in other disciplines working towards the same goals +- Has the ability to work in a fast-paced, evolving environment and use iterative methods and a flexible approach to enable rapid delivery +- Shares research with other delivery teams within the client organisation and shows the need for close coordination between teams + +### Knowledge + +Good understanding of user research quantitative and qualitative methodologies and is able to assess and explore how and when to apply different approaches. +Has a range of quantitative and qualitative experience, and is competent with a range of methodologies. + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Understands how and when to apply different methodologies across the design cycle +- Able to create appropriate, clear and compelling findings +- Experience in how to deliver findings to reflect the needs of projects and clients to ensure strong outcomes +- Experience working with other user-centred design disciplines and a growing understanding of how user research works cohesively with these disciplines +- Understands how to apply basic techniques for analysis of research data and synthesis of findings. Knows how to involve their team in analysis and synthesis. Can present clear findings that colleagues can understand and use +- Understanding of how to include and consider and involve traditionally marginalised and oppressed groups +- Knowledge of how to conduct ethical and inclusive research with a desire to develop and grow understanding + +### Business Skills + +- Demonstrates effective communication skills +- Plans, schedules and monitors own work (and that of others where applicable) competently within limited deadlines and according to relevant legislation, standards and procedures +- Contributes fully to the work of teams. Appreciates how own role relates to other roles and to the business of the employer or client. Demonstrates an analytical and systematic approach to issue resolution +- Takes the initiative in identifying and negotiating appropriate personal development opportunities +- Understands how own role impacts security and demonstrates routine security practice and knowledge required for own work + +#### Examples of behaviour and responsibilities + +Below are examples of behaviours and responsibilities a person in this role might be expected to demonstrate. The list is provided for illustrative purposes only. + +- Understands how and when to apply different methodologies across the design cycle +- Demonstrates willingness and an ability to support leadership. Communicates well, both formally and informally and is proactively working to develop communication skills +- Supports the development of user research at Made Tech +- Represents Made Tech in the wider UCD community through writing or speaking +- Trustworthy, acts with integrity, openness and impartiality when conducting and sharing user research diff --git a/handbook/handbook-main/team-norms/README.txt b/handbook/handbook-main/team-norms/README.txt new file mode 100644 index 0000000000000000000000000000000000000000..530c20d7a093cb66ccedfd0d6d560e802f46cb0d --- /dev/null +++ b/handbook/handbook-main/team-norms/README.txt @@ -0,0 +1,26 @@ +# Team Norms + +We have a number of team norms that have evolved (and continue to evolve!) as practices that we've found effective in building and scaling agile teams. + +## [Delivery Standards](delivery_standards.md) + +Our accepted practices for structuring deliveries. + +## [Delivery Healthcheck](delivery_healthcheck.md) + +Our expected reporting standards for delivery teams. + +## [Principles](principles.md) + +Our principles describing how we deliver in teams and work with clients. + +## [Development Practices](development_practices.md) + +Our accepted development standards. + +## [Retrospectives and Comradrospectives](retrospectives.md) + +Our methods of running team-wide and company-wide retrospectives. + +## [Timesheets](../guides/process/scheduling/how_to_timesheet.md) +Guidance on how to fill in timesheets. diff --git a/handbook/handbook-main/team-norms/delivery_healthcheck.txt b/handbook/handbook-main/team-norms/delivery_healthcheck.txt new file mode 100644 index 0000000000000000000000000000000000000000..12a7c4cb346f4710ac389f6abf42570b622bc576 --- /dev/null +++ b/handbook/handbook-main/team-norms/delivery_healthcheck.txt @@ -0,0 +1,20 @@ +# Delivery Healthcheck + +We ask teams to provide Delivery Healthchecks to the wider business to encourage the implementation of our Delivery Standards. + +It is the responsibility of the lead on each delivery team to provide an update on the health of their delivery in each week's TGIF. + +A Delivery Healthcheck should answer: + +## Current iteration + - When was your current iteration started? + - What is your current iteration goal? + - When is your next showcase? + - Are you on track to meet customer expectations? + +## Next iteration + - What is the goal for your next iteration? + +## Retrospective + - When was your last retrospective? + - What were your last retrospective action points? diff --git a/handbook/handbook-main/team-norms/delivery_standards.txt b/handbook/handbook-main/team-norms/delivery_standards.txt new file mode 100644 index 0000000000000000000000000000000000000000..c021531ace45a14d646dfcaaaaa940b3359fce8a --- /dev/null +++ b/handbook/handbook-main/team-norms/delivery_standards.txt @@ -0,0 +1,62 @@ +# Delivery Standards + +We realise a few things around deliveries: + +- Every customer has different needs, and so adapting to the most applicable way of working rather than forcing an entirely cookie-cutter approach is beneficial + +- Teams on the ground are usually best placed to make decisions about the best way to structure their work + +- Evolving the way we approach our deliveries is desirable as we mature our agile practices and learn from past successes + +That said, there are a number of delivery norms that we expect teams to adopt by default. Where teams wish to deviate from these norms, we expect them to do so consciously, and with documented and justified reasoning. + +## 1. Hold a standup every morning + +Every team is expected to hold a standup involving Engineers, Delivery Managers, and wherever possible customer teams. Standups should focus around the Trello board for transparency and to visualise bottlenecks. Standups must use the yesterday/today/blockers format, and care should be taken to avoid standups turning in to customer status reports. + +## 2. Hold a retrospective at least every 2 weeks + +Every team is expected to hold frequent retrospectives to help improve the team's effectiveness. + +## 3. Hold a showcase at least once per week + +Every team is expected to have their next showcase scheduled, and to be clear on what is planned to be showcased. Teams must perform practice runs of their showcases. Teams must always showcase from pre-production or production environments. A showcase must conclude with a plan for the next iteration. + +## 4. Practice Continuous Delivery + +Every team is expected to practice Continuous Delivery from the first iteration. Deployments must be automated to pre-production and production environments. Automated tests must be run as part of an automated build cycle. + +## 5. Productionise Application + +Every team is expected to deliver a production-ready application from the first iteration. The team must provide centralised application and infrastructure logging, application exception tracking, application performance monitoring, and automated dependency and security upgrades. + +## 6. Use Pull Requests + +Every team is expected to make use of the Pull Request workflow, and work in appropriately short-lived branches. Teams should not allow Pull Requests to span multiple days work. Pull Requests should be reviewed by at least one other person before merging to main. + +## 7. Deliver Done features + +Every team is expected deliver to the definition of done. Teams must not consider a feature done until the following criteria are met: + + * Cross-browser tested + * Visually checked against designs + * Refactored and readable + * Optimised, response time is acceptable + * Has an appropriate level of test coverage + * Can be deployed to production and is ready for users + +## 8. Maintain up-to-date roadmap and epic boards + +Every team is expected to keep their roadmap and epic boards current. + +## 9. Bring forward uncertainty + +Every team is expected to bring forward uncertainty. Where an iteration contains more risky features, teams must work on these first. Where possible teams should make use of spikes ahead of iterations starting in order to mitigate or remove uncertainty. + +## 10. Communicate regularly with customers and each other + +Every team is expected to be in contact with their customer at least once per day. Individuals in teams should communicate when they're unclear on any aspect of the delivery. Teams must not defer communication until standup. Teams must have a conversation with their customer as soon as any iteration goals become at risk. A customer must not be negatively surprised by progress at a showcase. Teams should send a weekly summary email to their customer stakeholders and for inclusion in the Made Tech TGIF email. + +## 11. Maintain quality + +Every team is expected to maintain a high level of quality, both at a code and application level. Teams must fully test their features as part of a deployment to a pre-production environment. Teams and customers should share an understanding of the desirable behaviour of all features in the current iteration. Teams must apply good scouting practices to improve the quality of every codebase they work on. diff --git a/handbook/handbook-main/team-norms/development_practices.txt b/handbook/handbook-main/team-norms/development_practices.txt new file mode 100644 index 0000000000000000000000000000000000000000..02e18f27146731cccbd52b41fef2422cbb65355a --- /dev/null +++ b/handbook/handbook-main/team-norms/development_practices.txt @@ -0,0 +1,40 @@ +# Development Practices + +When a new engineer joins the team, we'll often find they need some guidance on our preferred practices. + +Below we've included a list of practices that we encourage engineers to adopt so they can get up to speed as quickly as possible: + +## Understand our Delivery Standards + +Regularly validate your delivery against our [Delivery Standards](delivery_standards.md). + +## Commit little and often + +Engineers should commit frequently (5, 10, 15+ times per day) using short-lived branches that are merged back in to main via PR the same day. Commit messages should be well [structured and descriptive](https://github.com/erlang/otp/wiki/writing-good-commit-messages). + +## Bring the pain forward + +Tackle the hardest and most uncertain things in an iteration first. Use [spikes](https://en.wikipedia.org/wiki/Spike_(software_development)) where appropriate. + +## Attend your standup + +Your team should be having a standup every day. Prepare yourself ahead of the standup to talk about: what you achieved yesterday, what you're planning to achieve today, and things that are currently or likely to block your progress. You should be specific at standup, preferring "styling of cart line items and flash notification for mobile and desktop breakpoints" over "working on the cart". + +## Be loudly blocked + +If you're blocked on making further progress, loudly and immediately raise this with your team and continue to do so until you have assistance in becoming unblocked. Do not spend more than an hour trying to solve a problem before asking someone else for help. + +## Communicate effectively + +Be sure to communicate effectively. Asking too many questions is much preferred to not asking enough: + + - Talk to your team frequently + - Request clarifications if you're unsure + - Don't be scared to speak to the customer + - Involve any other specialists that might be available to you + +## Document the decision making process using ADRs + +ADR's are a formal way of documenting the decision-making process. (ADR stands for Architecture Decision Record) + +For a full write up see [Michael Nygard's blog post on ADRs](http://thinkrelevance.com/blog/2011/11/15/documenting-architecture-decisions). diff --git a/handbook/handbook-main/team-norms/principles.txt b/handbook/handbook-main/team-norms/principles.txt new file mode 100644 index 0000000000000000000000000000000000000000..41b92d85ce8efc2e34187c603f7af7cbde3682c0 --- /dev/null +++ b/handbook/handbook-main/team-norms/principles.txt @@ -0,0 +1,39 @@ +# Principles + +How we work with clients and build teams that deliver. + +## 1. Create impact for all +We create services that balance user needs, policy goals and what's possible now. Public services exist to create an impact on people's lives. Good services deliver positive outcomes for society that are fair and equitable for all. Be it cleaner air, safer roads, more jobs or better use of taxes - we understand that everything we do has an impact, no matter how large or small. + +## 2. Build successful teams +Success comes from our people. To build the right team, we strive to truly represent the communities we serve. We bring people together with a mixture of skills and experience. And we give everyone the opportunity to explore. We trust one another, respect hands-on skills, and always assume best intentions. + +## 3. Everyone can learn +We’re passionate about learning. We strive to leave our clients, partners and suppliers with the skills, enthusiasm and credibility to keep delivering. Learning works both ways - we understand that others can teach us as much as we can teach them. + +## 4. Make real solutions +We measure value in our work by delivering real things that impact our clients, citizens and society. By inviting feedback and seeking the shortest path to deliver real value, we see the change our work creates in people’s lives. + +## 5. Do less to achieve more +By working in agile teams, designing fewer features and using words everyone understands, we make a meaningful impact sooner, and create strong foundations to build on. + +## 6. Deliver little and often +By delivering features step by step we can get the small stuff out first, giving real value to the people who need it - quickly. We invite feedback early and to learn, iterate and reduce risk. + +## 7. Earn trust +Openness is at the core of everything we do. We use open ways of working on our projects, in our business and with one another. Sharing our successes and failures builds trust, gives us room to grow and holds us accountable. This lets others reuse and give feedback on our work so we all learn and improve. + +## 8. Be brave, be curious +We have the courage to challenge the status quo and the curiosity to innovate. By exploring new ways of doing things and taking lessons we've learnt, we can build services the public sector needs. We recognise there's always a different way to solve a problem, often supported by proven practices and technologies. + +## 9. Believe in compromise +There's no such thing as perfect and we acknowledge that tradeoffs can often be part of our work. When making challenging decisions, we focus on quality and work within our limits. We recognise when to shift deadlines and make smart business decisions - always with a humble approach. + +## 10. Nurture long-term relationships +As trusted advisors we always aim to go above and beyond. We collaborate with our clients, working with them to design and build the future of their services. We support them to define and solve their challenges, building long-term partnerships. + +## 11. Work ourselves out of a job +Real change means helping our clients deliver services independently and long term. We nurture long term partnerships so we can support the next challenge rather than locking ourselves in to the last one. + +## 12. Leave things better than we found them +Our work involves trying to meet the often-competing needs of our people, clients and users while building solutions that really work. This means knowing that, sometimes, we must build trust now to create a bigger impact later on. diff --git a/handbook/handbook-main/team-norms/retrospectives.txt b/handbook/handbook-main/team-norms/retrospectives.txt new file mode 100644 index 0000000000000000000000000000000000000000..f48df4b03e224bfd4c34d59160a5805f1328dd42 --- /dev/null +++ b/handbook/handbook-main/team-norms/retrospectives.txt @@ -0,0 +1,140 @@ +# Retrospectives + + +## The Prime Directive + +The purpose of the Prime Directive is to assure that a retrospective has the right culture to make it a positive and result oriented event. It makes a retrospective become an effective team gathering to learn and find solutions to improve the way of working. + +The prime directive should be read before a retrospective begins. + +"Regardless of what we discover, we understand and truly believe that everyone did the best job they could, given what they knew at the time, their skills and abilities, the resources available, and the situation at hand." + +--Norm Kerth, Project Retrospectives: A Handbook for Team Review + +(source: [Retrospective Wiki](http://retrospectivewiki.org/index.php?title=The_Prime_Directive)) + + +## Retrospectives + +There are two elements to retrospectives: + +* Retrospective (smaller groups performing retrospectives) +* Comradrospective (whole company retrospective format) + +### Schedule + +Retrospectives should occur at least once every two weeks and should normally take 30-60 minutes but can be flexible depending on team size; for instance Academy Retrospectives have a 90 minute timebox. +Comradrospectives are scheduled every 2 weeks on Friday for 60 minutes. + +### Purpose + +The purpose of retrospectives is to: + +* Examine outcomes from previous retrospective, and understand what went well, and what didn’t. +* Create action points or decide on problems that the team will tackle +* Provide a conduit to allow continuous improvement to be facilitated safely within teams. + + +The purpose of the comradrospective is to: + +* Examine previous action points, what went well and what didn’t. +* Avoid “localised optimisations” i.e. the action points of one smaller group, hurting the whole. +* Set one or two action points, or problems, for the whole company to focus on. + +#### Action points + +Remember that action points are only potential solutions to a problem. In order to aid examining your own achievements, being able to measure the impact of your action points by some form of measurable yard-stick can be quite helpful. Establishing a definition of awesome is one accepted solution to this, or some sort of hard metric can also help. + +#### Tackling problems + +Sometimes it is not immediately obvious how to solve a problem that the team is collectively facing. In these situations it may be wise to have the team attempt to resolve a particularly pressing pain point during normal working time. + +Similar to action points, it’s important that the team is able to measure and sense check whether it has made progress towards some goal. + +Make sure the team has awareness on what the outcome of potential solutions would look like. + +### Format + +Teams are expected to self-organise into groups that make sense to perform retrospectives with. + +Team members should only attend one retrospective, and then the comradrospective. + +#### Safety Checks + +Sharing views can be difficult at times; it's important we recognise this by holding safety checks. + +Safety checks should be run before both retrospectives and comradrospectives, our numbering system is outlined below. + +5 - I’ll talk about anything + +4 - I’ll talk about almost anything; a few things might be hard + +3 - I’ll talk about some things, but others will be hard to say + +2 - I’m not going to say much, I’ll let others bring up issues + +1 - I’ll smile, claim everything is great and agree with authority figures + +0 - I'm not comfortable talking/I don't want to do this/I want to leave + +The facilitator should collect the team's safety numbers anonymously, this can be done using either the same pen and paper or digitally, and work out if safety is high or low. If it is low the facilitator should hold an exercise to raise safety and work out what might be causing low safety. + +It follows the basic flow: + + * Facilitator asks everyone to put themselves in the shoes of someone who might not feel safe and to note down what those causes might be + * Based on the submitted post-it notes, add a separate column where people can think of reasons that might cause these issues + * Based on the potential causes, add another column asking for people to submit potential solutions + * Read these all out and discuss with the team + * Run the safety check again + +If the safety level has increased after this point, then you can run the retrospective. + +#### Getting the most out of Retrospectives + +Six Thinking Hats is a good discipline for everybody to get the most out of your retrospective experience. + +Ensuring that everyone in the retrospective only focusses on one hat at a time, can keep the discussions aligned towards a common direction. + +A common order to move through the hats is: + +* **Managing Blue** – what is the subject? what are we thinking about? what is the goal? Can look at the big picture. + +* **Information White** – considering purely what information is available, what are the facts? + +* **Emotions Red** – intuitive or instinctive gut reactions or statements of emotional feeling (but not any justification) + +* **Discernment Black** – logic applied to identifying reasons to be cautious and conservative. Practical, realistic. + +* **Optimistic response Yellow** – logic applied to identifying benefits, seeking harmony. Sees the brighter, sunny side of situations. + +* **Creativity Green** – statements of provocation and investigation, seeing where a thought goes. Thinks creatively, out of the box. + +Source: [Edward de Bono - Six Thinking Hats](https://en.wikipedia.org/wiki/Six_Thinking_Hats) + +### Timing + +* The first hour is booked for smaller group retrospectives +* The second hour is booked for the comradrospective + +### Expectations + +Teams are expected to self-manage which includes time boxing their retrospectives. + +If you wish to perform your retrospective at a different time, or, more or less frequently. You are free to do so, so long as you have sought both agreement and input from your group. + +Any improvements, changes to the comradrospective, should be discussed at the comradrospective with everyone it will affect involved. + +#### Facilitators + +Teams are expected to elect a facilitator for their individual retrospectives. + +The facilitation role should be seen as a skill that can be improved, and facilitators should treat it as such. + +The comradrospective facilitator should rotate so that everyone performs it. + +### Notes + +The format is expected to be evolutionary, this document serves as it’s living documentation. + +* Some further reading is available on the [Retrospectives Wiki](https://retrospectivewiki.org/index.php?title=Agile_Retrospective_Resource_Wiki) +* Some common [retrospective ailments & cures](https://retrospectivewiki.org/index.php?title=Common_ailments_%26_cures)