Menu

Week one inside an inherited engineering department: what I actually look at
πŸ“°

Week one inside an inherited engineering department: what I actually look at

DEV Community: careerΒ·yaniv zalevasΒ·9 days ago
#JD164yek
#devtocareer#devto#dev#answer#stopped
Reading 0:00
15s threshold

The situation repeats itself: I walk into a company as its fractional CTO, the engineering org is a few dozen developers, and nobody β€” not the CEO, not the VP R&D, not the team leads β€” can answer "what is everyone working on?" without opening four different trackers.

The first week decides whether you're credible or just another consultant. Here's what I actually do with those seven days.

What I stopped doing

I stopped asking for status reports. I stopped asking for slide decks. Both are already out of date by the time they reach you, and both are written by the people you're supposed to be checking on.

Nobody in an 80-developer department is lying to you. Everyone is just reading a different tracker, and none of them match.

What I look at instead, in order

1. Where the work actually lives. Every company has an official tracker and several real ones. I've walked into places running Jira, Azure DevOps, and a GitHub Issues graveyard in parallel β€” active projects split across all three.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.