DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Newsletter
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • The SDLC After AI
  • You Don’t Need To Be a Manager To Lead: Why Leadership Matters for Software Engineers
  • Building an AI Visibility Checker With Cloudflare Workers (Without a Backend)
  • Stop Using the ATM-Didn’t-Kill-Jobs Story to Reassure Developers About AI

Trending

  • Microsoft Fabric Throttling: Diagnose Before You Scale
  • Post-Quantum TLS for Cloud APIs and Microservices
  • Why Your Test Automation Is Always Behind the Code And the Architecture That Fixes It
  • Searching Kafka Without an Index: Lessons From Building Message Search for Kafdrop

Draft This article hasn't been published, so readers can't see it.

In moderation This article is waiting for review, so readers can't see it yet.

Deleted This article has been deleted, so readers can't see it.

Improving Visibility Without Being Annoying

Anders Wallgren, the VP of Technology Strategy at CloudBees, discusses increasing visibility in the software development process.

By 
Dan Lines
·
Jul. 16, 21 · Interview
Post on X (opens in a new tab) Share on LinkedIn (opens in a new tab)
6.5K Views

Join the DZone community Save articles, join the discussion, and download Refcards and Trend Reports with a free account.

Join for free Already a member? Log in

It’s safe to say that everyone wants more visibility into their software delivery process.

When project management and git systems don’t talk to each other, we have only small islands of visibility and no way to connect them. Anders Wallgren, the VP of Technology Strategy at CloudBees, joins the Dev Interrupted Podcast to help us connect these islands, and discuss the outcome-based metrics we should all be using to make the software development process more visible.

Episode Highlights include:

  • How to increase development visibility without micromanaging
  • Which team-based metrics are best for pipeline visibility
  • Why it’s important to look at your software at the feature level
  • What the future holds for software delivery pipeline visibility

Join the Dev Interrupted Server

With over 1200 members, the Dev Interrupted Discord Community is the best place for Engineering Leaders to engage in daily conversation. No sales people allowed. Join the community >>

Visibility (geometry) Software development

Published at DZone with permission of Dan Lines. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • The SDLC After AI
  • You Don’t Need To Be a Manager To Lead: Why Leadership Matters for Software Engineers
  • Building an AI Visibility Checker With Cloudflare Workers (Without a Backend)
  • Stop Using the ATM-Didn’t-Kill-Jobs Story to Reassure Developers About AI

Partner Resources

×

Comments

Loading comments

The comments didn't load

Please try again in a moment.

Likes

Loading

The next likes didn't load. Please try again.

The likes didn't load

Please try again in a moment.

See who liked this

Log in or join DZone for free to see who liked this article.

Log in Join for free
  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook