How do you know if your team is high performing? In this post, Andreas describes a series of indicators that you can use to see if a team that you manage, or are part of, are ‘high performing’, the reasons we encourage particular team behaviours, and what we can do to move a team towards becoming ‘high performing’.
Made Tech Team Interviews: Charlene Hunter, Lead Engineer
This month we had our first interview in our Made Tech team interview series with our Lead Engineer Charlene Hunter to better understand her role and to feature the great work she has been doing.
Why data-driven organisations: The problem
Why we should care about data-driven organisations? We will look at the specific problem that drives our inquiry into this area and forms the basis of the direction in how this large topic can be broken down.
Launching the Made Tech Talks webinar series
We are excited to announce the launch of our new webinar series, Made Tech Talks. During this series, we aim to provide helpful, accessible information to empower digital leaders to improve software delivery in the public sector.
Don’t estimate without evidence
In software, estimating is controversial. In this post, we’ll look at how to measure the quality of your estimates, and what to do when it doesn’t stack up.
Stop buying specialists and start delivering outcomes
Rich discusses the problems that can arise when companies hire specialists and how to refocus a team to start delivering outcomes. Multidisciplinary teams allow you to focus on what outcomes you’re delivering and enable the team to share the responsibility of all aspects of delivery.
Modernising legacy applications in the public sector – new book launch!
I’m really pleased to announce the launch of our latest book, Modernising legacy applications in the public sector. We have written the book to share our experience of successful legacy application transformations with technology leaders working across the UK public sector.
Documentation should meet outcomes too
How do we go beyond seeing documentation as a burden and ensure that it is maintainable, reliable and valuable? Documentation is necessary to explain how something complicated works and defines a critical process to ensure a successful software release.
Defining outcomes as a product team
How defining outcomes can help a product team collaboratively discover, identify, collate and rank what they should do and enable them to perform effectively and happily to ensure outputs are tied to those outcomes.
Prioritising your application transformation
After you have mapped your application ecosystem as best as you can, you should begin work on prioritising which applications to modernise first.
