Food for Agile Thought #263: Engineering Sanity, Skill Mapping, Technical Debt Survey, Outcomes vs. Outputs
Food for Agile Thought #263: Engineering Sanity, Skill Mapping, Technical Debt Survey, Outcomes vs. Outputs

Food for Agile Thought #263: Engineering Sanity, Skill Mapping, Technical Debt Survey, Outcomes vs. Outputs


TL; DR: Engineering Sanity, Skill Mapping — Food for Agile Thought #263

Welcome to the 263rd edition of the Food for Agile Thought newsletter, shared with 27,516 peers. This week, we delve into how UX can support engineering sanity; we study a recent survey among CIOs on technical debt, and we learn about options of remote engineers if they want to be noticed.

We then enjoy an audio guide to product discovery; we take it beyond the usual ‘output vs. outcome’ discussion, and we learn how to ask better questions when we need to decide what to measure on our quest to create value for customers.

Lastly, we are grateful for a downloadable template that supports skill mapping to identify educational needs.

Did you miss last week’s Food for Agile Thought’s issue #262?

?? Do you want to get this article in your inbox? You can sign up here and join 27k other subscribers.


?? The Tip of the Week: Engineering Sanity


(via InfoQ): Dev & UX: How Integrating UX Improves Engineering’s Efficiency and Sanity

Debbie Levitt advocates that UX is engineering’s time, money, and sanity saver.

Source: InfoQ: Dev & UX: How Integrating UX Improves Engineering’s Efficiency and Sanity


No alt text provided for this image

?? ?? Join the Hands-on Agile #28: If You Use Scrum, Don’t Miss this One!


Agile & Scrum


(via McKinsey & Company): Tech debt: Reclaiming tech equity

McKinsey provides data from a recent survey with CIOs on technical debt, 60 percent of whom believe it has risen over the past three years.

Source: McKinsey & Company: Tech debt: Reclaiming tech equity


(via Triplebyte): Getting noticed as a remote engineer — and why it matters

Joseph Pacheco shares suggestions on how to not recede into the background. It is a good inspiration for Scrum Masters on how to support their Development Team members.

Source: Triplebyte: Getting noticed as a remote engineer — and why it matters


Rachel Krause (via Nielsen Norman Group): Skill Mapping: A Digital Template for Remote Teams

Rachel Krause provides a template for skill mapping. Okay, it is focused on UX designers but can easily be adapted to support your Scrum Teams’ members.

Source: Nielsen Norman Group: Skill Mapping: A Digital Template for Remote Teams

Author: Rachel Krause


?? ?? Join the Virtual Agile Camp Berlin 2020, Oct 22–24, 2020 — € 25

Join the virtual Agile Camp Berlin 2020 and experience three energizing days with 250-plus agile peers focusing on community, sharing, and learning.

We will practice games and exercises; we will share tips & tricks, lessons learned, and war stories from the agile trenches — all self-organized in a virtual Barcamp format from October 22–24, 2020.

No alt text provided for this image

Learn moreVirtual Agile Camp Berlin 2020, Oct 22–24, 2020.


No alt text provided for this image

If you prefer a notification by email, please sign-up for my weekly newsletter and join 27,516 peers.


Product & Lean


?? Roman Pichler: A Brief Guide to Product Discovery

Roman Pichler offers an overview of product discovery, explaining its purpose and why it matters. Enjoy the audio version, too.

Source: ?? A Brief Guide to Product Discovery

Author: Roman Pichler


Jens-Fabian Goetzmann (via The Startup): Why “Outcomes Over Outputs” Is Flawed Advice

Jens-Fabian Goetzmann believes that merely considering output and outcome is insufficient to address the challenge.

Source: The Startup: Why “Outcomes Over Outputs” Is Flawed Advice

Author: Jens-Fabian Goetzmann


John Cutler (via Amplitude): Asking Better Questions

John Cutler delves into the art of questioning so that your team can make better decisions about what to measure.

Source: Amplitude: Asking Better Questions

Author: John Cutler


?? Product Roadmap First Principles

The end of 2020 is nearing, and it’s product roadmap building time again — at least for those companies that are still dedicated to the old command-and-control model. In the next few weeks, executives and (key) stakeholders will come together and define new functionality that they believe will meet business demands in 2021.

While investing in product roadmaps can yield a reasonable return by creating a shared understanding between the “the business” and product teams, I also believe that product roadmaps need to be living artifacts requiring continuous attention by everyone involved. To make that process as worthwhile as possible, adhering to the following seven product roadmap first principles has proven beneficial in my experience.

No alt text provided for this image

Learn moreProduct Roadmap First Principles.


??? Last Week’s Food for Agile Thought Edition

Read moreFood for Agile Thought #262: Product Management Dysfunctions, Play SHIP IT, Change Agency, Walking in Other People’s Shoes


?? Join 2,450-plus Agile Peers on Youtube

Now available on the Age-of-Product Youtube channel:


? Do Not Miss Out: Join the 8,300-plus Strong ‘Hands-on Agile’ Slack Community

I invite you to join the “Hands-on Agile” Slack Community and enjoy the benefits of a fast-growing, vibrant community of agile practitioners from around the world.

If you like to join all you have to do now is provide your credentials via this Google form, and I will sign you up. By the way, it’s free.


?? Do You Want to Read more like this?

Well, then:

Food for Agile Thought #263: Engineering Sanity, Skill Mapping, Technical Debt Survey, Outcomes vs. Outputs was first published on Age-of-Product.com.

要查看或添加评论,请登录

社区洞察

其他会员也浏览了