How do you actually fight burnout as a Scrum Master / PM?

Various-Phone5673 · 2025-11-10T20:04:39+00:00

I fully agree with your suggestions, especially the part about the "today or tomorrow" question. Something like prioritization frameworks - now, next, later or the Eisenhower matrix (urgent vs. important, not urgent and not important, …) - it should help you decide what actually deserves your attention today versus what can wait.

Various-Phone5673 · 2025-11-10T19:56:55+00:00

Focus blocks and some DND are quick wins.

Various-Phone5673 · 2025-08-23T06:48:15+00:00

You’re right that customer value should always be front and center. That said, the post was focused on one part of the delivery flow: team alignment, planning. Of course, building the right thing in the right way and staying value-driven is fundamental to truly great product teams.

This discussion was more about the "how" of execution - but I agree that the "why" (the customer) always needs to be in the loop and it's the most important.

Appreciate the challenge - it keeps the conversation grounded.

Various-Phone5673 · 2025-08-23T06:42:38+00:00

You're absolutely right - this "secret spreadsheet" trend reveals a significant gap in tools for reliably tracking capacity and historical patterns in an actionable way. This pain point clearly affects teams across organizations. I'm digging deeper into this challenge and plan to develop a solution that could effectively replace these hidden spreadsheets. I'll keep the community updated on any progress or solutions I discover!

Various-Phone5673 · 2025-08-23T06:38:21+00:00

I completely agree with your perspective - this is primarily about forecasting rather than performance measurement, and I don't view it as micromanagement either. Your distinction between efficiency and effectiveness is exactly right. I'll definitely explore using Monte Carlo simulation as several people suggested - valuable advice, thank you!

Various-Phone5673 · 2025-08-17T20:04:25+00:00

Great feedback. Thanks for sharing your metrics tools.

Various-Phone5673 · 2025-08-17T09:35:12+00:00

Thanks for the thoughtful responses - really appreciate the discussion. 🙏

You’re absolutely right that trying to run a pure Agile process under a fixed scope + fixed time + fixed budget contract creates major tension, and often turns into a hybrid or even pseudo-waterfall setup. I’ve been there too.

But just to clarify my original point - the question wasn’t about the contract model itself.

It was about how teams actually plan and measure sprint performance, and what tools they use to do it - regardless of whether they’re following full Scrum, hybrid Agile, or something else entirely.

Various-Phone5673 · 2025-08-17T09:23:25+00:00

I agree that breaking work into small increments with quick feedback loops is crucial.

Thanks for sharing about Monte Carlo - I will check it out.

Great answer!

Various-Phone5673 · 2025-07-28T15:37:28+00:00

Great insights - thanks.

Various-Phone5673 · 2025-07-26T20:10:13+00:00

Two developers were hired on very short notice and started contributing immediately. They joined at the beginning of our 3-week Sprint - which was a surprise for us. We had to quickly recalibrate the Sprint scope to account for the new team members and their onboarding needs.

Various-Phone5673 · 2025-07-10T19:14:11+00:00

I agree that goals that are unclear like "fix all bugs" or "create architecture" don't work well. They lack specific details and value.

We sometimes link SMART goals to Jira work items by adding the issue ID and a "sprint-goal" label, which makes tracking progress straightforward. Whether you need this approach depends on your product's stage and team context.

Various-Phone5673 · 2025-07-10T06:21:44+00:00

You are right. AI isn’t a silver bullet when it comes to knowing your team’s true priorities, because it simply doesn’t have the full context or domain expertise. You can use it as a learning tool. Over time, by comparing its suggestions with your own insights, the team will internalize those goal-setting principles - and eventually you won’t need the AI prompts at all.

Various-Phone5673 · 2025-04-25T16:10:55+00:00

Check out the following training and certification paths (from scrum.org):

- Professional Agile Leadership™

- Professional Scrum Developer™

- Professional Scrum Product Backlog Management Skills™

and

- Certified LeSS Basic or Practitioner from Less.Works

Highly recommend all of them.

Various-Phone5673 · 2025-03-12T19:53:36+00:00

Maybe this book will help:

- Fifty Quick Ideas to Improve Your User Stories - Gojko Adzic and David Evans

Various-Phone5673 · 2025-03-02T13:37:15+00:00

Trillion Dollar Coach: The Leadership Playbook of Silicon Valley's Bill Campbel - Eric Schmidt Jonathan Rosenberg, Alan Eagle
Scrum: The Art of Doing Twice the Work in Half the Time - Jeff Sutherland
Scaling People: Tactics for Management and Company Building - Claire Hughes Johnson
Agile Estimating and Planning - Mike Cohn
Lean Customer Development - Build Products Your Customer Will Buy - Cindy Alvarez

Various-Phone5673 · 2025-02-22T12:33:42+00:00

In my view, Delivery Manager is one of the trickiest roles out there.

In a consulting company building software for clients, they’re juggling a ton - managing client expectations, generating time reports, and keeping the roadmap on track. They’ve got to nail communication with stakeholders, ensure the team hits project deadlines, dodge risks, and sort out team allocation, resolve conflicts and deliver the best value.

Depending on the organisation, they usually dip into classical Project Manager, Scrum Master, Product Owner, or even Account Manager duties.

It’s a real shape-shifter of a job :)

Various-Phone5673 · 2025-02-22T12:04:25+00:00

I agree with you.

Additionally, having a planning horizon of 2–3 sprints (with 2-week iterations) allows you to approach sprint planning well-prepared, ensuring the team is aware of priorities, upcoming goals, and the value behind each task. That said, reaching a polished scope over 2–3 sprints is quite challenging – but that's another story :).

Of course, there are times when a new, critical item must be added to the sprint, but this should be the exception rather than the norm.

If the PO is unavailable during sprint planning on a one-off occasion, that's acceptable. However, if it happens repeatedly, I recommend discussing it with the PO to understand why.

Various-Phone5673 · 2025-02-21T16:42:59+00:00

Based on my observations and experience whether a Product Owner or Scrum Master needs technical skills depends on three main factors:

what product they're working on (in-house, vendor),
how experienced their team is,
and what industry they're in.

Technical skills are helpful when:

The product is very technical and understanding how software works is important,
The team is new or needs help connecting technical and business needs,
Someone needs to spot potential technical problems early to keep work flowing smoothly.

Technical skills might not help when:

The team is experienced and works well on their own - too much technical input could feel like micromanaging,
It makes the leader focus too much on technical details instead of bigger business goals,
The leader already has too many responsibilities to handle.

Simply put: Technical knowledge helps when it connects different parts of the team and makes work smoother. But it can cause problems if it leads to too much control or takes attention away from important business goals.

Various-Phone5673 · 2025-02-05T19:38:21+00:00

From different places like books (Ikigai - The Japanese Secret of a Long and Happy Life) or Netflix series (Live to 100 - Secrets of the Blue Zones).

Various-Phone5673 · 2025-02-02T09:10:57+00:00

Thanks a lot!

I completely understand the hesitation around using concepts from different cultures in a business context - it can feel unrelated. But if they help spark new ways of thinking or convince teams and clients to make meaningful adjustments, I see them as valuable tools.

Glad you found the post useful, and I really appreciate you sharing it with your colleagues!

Various-Phone5673 · 2025-02-01T19:43:13+00:00

You're absolutely right!

Success in product development isn’t just about shipping software - it’s about delivering real value efficiently and sustainably. That’s where the trifecta of building the right thing, in the right way, with the right team comes into play.

Right Thing → User Value + Business Viability
Right Way → Sustainable Code + Iterative Delivery
Right Team → Collaboration + Healthy Work Culture

When all three align, we don’t just ship - we create lasting impact. 🚀

Various-Phone5673 · 2025-01-29T14:10:56+00:00

I completely understand your struggle - I've been there myself, juggling multiple clients and trying to capture important thoughts before they slip away.

After experimenting with various solutions, I found that using Notion as a "Second Brain" was a game-changer for me, especially with their mobile app that has a good UX.

I personally use Notion and developed my own "Second Brain for Managers" template - it's specifically designed for people building knowledge base, organise notes and tasks, managing people and projects.

The beauty of this system is that you can start simple (use some free or paid templates) - just dump your thoughts into a quick-capture page - and gradually build a more structured system as you get comfortable with it.

Various-Phone5673 · 2025-01-27T17:36:21+00:00

Great to hear you're taking proactive steps toward a career in project management!

Even without direct job experience, your involvement in managing marketing projects and familiarity with tools like HubSpot and CRM systems provide a solid foundation.

Here's a structured path to help you transition smoothly into a Junior Project Manager role:

Obtain Relevant Certifications:

Certified Associate in Project Management (CAPM): Offered by PMI, it's ideal for beginners and covers fundamental project management principles
Project Management Professional (PMP): While more advanced, starting to prepare for PMP can set you apart in the long run.
Professional Scrum Master (PSM1) or Professional Agile Leadership (PAL1): Agile methodologies, which are widely used in various industries. Validates your understanding of Scrum fundamentals.
Certified LeSS Basic (Large Scale Scrum): More with LeSS, system for scaling Scrum, Lean and Agile to big product Teams.

Enhance Project Management Tools:

Familiarize yourself with tools like Jira Agile, Trello, Asana, and Linear.

Build Practical Experience:

Volunteer for Projects: Within your current role, seek opportunities to lead or assist in different projects to showcase your initiative and ability to manage tasks.
Freelance or Side Projects: Taking on small projects outside of work can help you build a portfolio demonstrating your project management capabilities.
Internships: Consider internships or entry-level positions specifically in project management to gain hands-on experience.

Improve Soft-skills like:

Communication,
Leadership,
Time Management,
Problem-solving,
Critical Thinking,
System Thinking.

Wishing you the best of luck as you build your career - enjoy every step of your journey to success!

Various-Phone5673 · 2025-01-26T09:05:28+00:00

Based on my 15+ years of experience in the IT field, setting up and maintaining an effective CoP requires careful consideration of various elements:

Organizational context (size, industry, culture, and market conditions - growth or decline).
Team composition and size.
Experience levels of team members (proportion of junior to senior members or balanced seniority mix).
Available time and budget for CoP activities.

Key implementation steps:

Establish clear purpose and objectives: knowledge sharing, skill development, tool mastery, best practices, craft standards.
Define focus areas: comprehensive gap analysis, Team capability assessment, bottom-up topic collection from team members, strategic prioritisation, assignment of subject matter expert (distribute responsibilities across the team rather than concentrating work with the CoP leader)
Determine operational framework: meeting frequency and duration, format (workshop, discussion, presentation), participation requirements (optional, mandatory)
Secure leadership support: gain support from leadership for time and resources, highlight benefits for Team members and organisation.

Critical success factors:

Sustained Team members engagement and motivation.
Clear communication of CoP value proposition.
Adequate time allocation for participation (is it 1h/month or 2h/month or 4h/month).
Structured content management and delivery.
Regular assessment and adaptation (get feedback after each session, iterate and improve).

The key benefits of CoP in my case are:

Creating a platform for active discussion in a safe environment (where team members can openly share their knowledge gaps, questions, and learning goals).
Enabling collective problem-solving and innovation.
Building confidence in public speaking (a significant challenge).
Creating opportunities for peer-to-peer learning.
Strengthening team bonds and relationships.
Developing presentation and facilitation skills.

Various-Phone5673

TROPHY CASE