斯基尔鲸鱼

2023年4月20日

欧洲商业杂志2023年4月20日,4与空间技术领导人终于可以解决生产力拼图,海维尔·卡佛说,(如图)的联合创始人和首席执行官斯基尔鲸鱼技术领导人在所有部门的任务是将合适的技术功能表在正确的时间。但是他们在2023年面临着无数的挑战。动荡的经济领先的削减预算,开发人员的劳动力烧坏了多年来前所未有的创新在大流行期间,和执行团队似乎总是期待更多的生产力。很多人将会问自己同样的问题:如何提高生产力时不能雇佣更多的人吗?评估团队的起点是回答这个问题的关键的第一步。但是生产力从来都不是一件容易的事情来衡量时,软件工程。复杂,经常无形的工作,不能准确地捕获使用纯粹的数值指标,如行代码生成、修复的bug数量或审查需要多久。这并没有阻止一些企业尝试。一个著名的科技巨头,例如,提供了1000美元的奖金为每一个bug固定在两周前他们把新版本的旗舰产品。反常激励鼓励人们离开bug在新代码中他们写道,而不是立即修复它们。 They could then report the bug, fix it later and claim their reward. But a new framework from Nicole Forsgren and Microsoft Research offers a more holistic approach to productivity. SPACE is organised around five pillars: satisfaction and wellbeing, performance, activity, communication and collaboration, and efficiency and flow. Forsgren has said the Covid-19 pandemic and shift to hybrid work expedited the need for the industry to better understand developer productivity and wellbeing, and that “doing so in an efficient and fair way is critical”. Making SPACE for a new approach There’s a lot of flexibility written into the framework and how it’s applied by tech leaders will depend on the context of each organisation. But leaders might start by exploring satisfaction – how fulfilled do developers feel about their work, team, tools, and the culture within which they work? How healthy and happy are they, and how much stress do they feel under? Performance relates to outcome rather than output – so rather than count the number of releases, a CTO or other tech leader might ask whether a release was made on time and if the goals of the release were met. Activity metrics will depend on the design of an organisation’s engineering system along the development life cycle, but leaders should look to use measures around quality (such as reliability and absence of bugs), alongside impact (e.g. customer satisfaction and cost reduction). Communication and collaboration considers how people and teams work together, and how able individuals feel to bring their whole selves to work. Metrics such as the discoverability of documentation and expertise, the quality of reviews, and the time spent onboarding new members of the team are all helpful. And finally, efficiency and flow questions how able a team feels to get complex tasks done with minimal distractions or interruptions. GitHub has found that developers who average just one meeting per day have a 99% chance of doing high quality work. That drops to 14% for three meetings per day. Upgrading performance with targeted learning SPACE will give tech leaders a system to measure developer productivity, but it will also highlight what needs to change for productivity to improve. That may be environmental or cultural factors, new tools and processes, or investing in targeted, high-quality learning to boost the skill level within a team. That not only helps with making developers feel more satisfied and empowered to make a difference, but it will also create more skilled teams, able to produce better software faster, impacting overall business performance. Measuring and optimising the productivity of engineering teams isn’t an exact science. There isn’t one metric that will summarise every facet, or a magic wand that will improve everything overnight. It’s an iterative process that will take time, pose challenging questions, and require investment in the right places. But organisations that are going to perform need people who are good at their jobs. And – at least in the short term – tech leaders are going to need to focus on the people they already have to meet those ambitions. Hywel Carver is the co-founder and CEO of Skiller Whale, a live coaching platform for engineering teams that targets individual skill gaps to achieve a team-level strategic outcome. Find out more about SPACE and live coaching with Skiller Whale’s latest whitepaper .