Sign In

Sven Peters

Developer Advocate at Atlassian 🧢 - Ex-MongoDB 🍃

Sven Peters is a Lead Developer Advocate focusing on helping teams worldwide improve their effectiveness and finding fulfillment in their work.

With a background in Telecommunications Engineering, Sven has gained extensive experience in DevRel strategy, public speaking, keynote production, event content strategy, social media, content marketing, software development, team development, and organizational development.

Formerly involved with notable organizations such as Atlassian, Manfred, MongoDB, K15t, and others, Sven has held positions ranging from DevOps Advocate to VP of Marketing, showcasing his diverse skill set and leadership abilities.

Highlights

Aug 29 · linkedin

Do your project reports suffer from the watermelon effect? 🍉 I've seen this happen in many companies. At the end of the month, it's time to update the project status for the department review meeting. The project leader gathers updates on milestones, previews what’s next, and then updates a slide in the shared PowerPoint deck. Finally, the status is marked: Green ✅.

But here's the thing—rarely do people step up and say, "We’re off track." Even when that’s the reality, they often stay silent. Why? Well, there are a few reasons:

😬 There’s pressure to stay on schedule, so teams hope to fix things next month before anyone notices. They might fear the consequences of calling out a “red status.” 📊 Sometimes, project leaders just don’t know the real status. Without solid metrics, they might assume things are on track. ⏳ There's no time for deep reporting. Project leaders are busy keeping stakeholders happy, leaving little time to dive into the data and figure out the true status. 🚩 And sometimes, the signs are just ignored. It’s tough to admit that the team isn’t on track or that early assumptions were off.

The problem is that this often leads to a nasty surprise when the project turns red right before it’s supposed to ship, and suddenly, the deadline slips by six months. This is bad news for everyone involved—team members, leadership, and customers alike. 😱

This is the watermelon effect: The project looks green on the outside, but if you slice it open, it’s red on the inside. 🍉 You need an open, honest, and blameless culture to avoid this. Here are a few tips to help:

🔍 Don’t just read the project status in meetings—ask deeper questions to really understand what’s going on beneath the surface. 📈 Set up better metrics and more frequent milestones so your status updates are based on real data, not just a gut feeling. 🚀 Report more often. It’s easier to say you’re “At risk” for a couple of weeks and then get back on track. It’s less dramatic than turning red for a whole quarter and helps you get help earlier. 🎉 Celebrate honesty when things aren’t going as planned. Highlighting slipping deadlines can actually help other projects, so yours isn’t seen as the exception.

It’s a bit wild to expect a six-month project involving multiple departments and dozens of people to hit the exact deadline and outcome as planned. Plans are just that—plans. They change when they hit reality. So, admit it early and avoid the watermelon effect. 🍉🚫

Aug 20 · linkedin

How many days does your company need to put a ☑ checkbox into production?

Gene Kim asked that great question at the Enterprise Tech Summit in Las Vegas. It's an excellent test of agility and nimbleness.

Most enterprise organizations will easily hit the one-year mark when running this thought experiment. Even though their teams are agile, have a DevOps mindset, and have the right tooling, the coordination it takes will prevent the business from doing things fast.

How long would your organization need?

Sven Peters
Add to my network

Location

Kiel, Schleswig-Holstein, Germany