Expansion Pack Improvements

[KysukeX]

After reviewing the content of this expansion (I really appreciate the effort put into this document), I've identified a few areas where further refinement could enhance clarity and reinforce core agile principles.
My suggestions aim to strengthen the guidance and prevent potential misunderstandings.

• "Stakeholder (including but not limited to user/customer)",
  While seemingly inclusive, it inadvertently risks diluting the essential focus on customer-centricity. In my experience, this broad framing can sometimes be misinterpreted as an invitation to prioritize other interests over direct customer feedback, leading to a "Highest Paid Person's Opinion" (HiPPO) effect.
  While it's crucial to value all stakeholders and weigh their contributions appropriately, the customer/user remains paramount in product development. Proposed alternative phrasing: "Stakeholders (Customers/Users and anyone with a vested interest)."
  This phrasing explicitly positions customers and users at the forefront while still acknowledging the importance of other vested interests, thereby maintaining a healthy balance without diminishing the customer's voice.

• "Definition of Output Done & Definition of Outcome Done",
  Introduces conceptual overlap and conflicting terminology, especially given the widespread adoption of "Definition of Done" (DoD).
  An outcome is, by its very nature, an event that has already occurred or is actively happening, making the concept of an "Outcome Done" somewhat redundant.
  Furthermore, emphasizing "Output Done" might inadvertently reinforce a "feature factory" mindset, where the focus remains on delivering features rather than achieving valuable results.
  I believe that a dedicated section on "Output vs. Outcome" explaining the fundamental difference between Output (what we produce) and Outcome (the value or impact achieved) would clarify the distinction.
  This educational component is vital for guiding teams towards value delivery rather than mere production.
  Retain DoD : Continue using the established "Definition of Done" to describe the criteria for a completed work or output.
  Reduce DoOD to DoO : A dedicated "Definition of Outcome" section would be highly beneficial. This would focus on defining what successful outcomes look like, emphasizing the desired impact and value.

• Rethinking "Avoiding Demotivation"
  The suggestion that leadership's duty includes "Avoiding demotivation" can be misleading.
  True motivation in a professional context, especially within agile environments, is inherently intrinsic.
  Focusing on "avoiding demotivation" risks implying that motivation is something to be managed externally.
  Based on principles championed by researchers like Daniel Pink (Drive!), intrinsic motivators such as Purpose, Mastery, and Autonomy are fundamental for a healthy and productive work environment.
  I recommend a section dedicated to Fostering Intrinsic Motivation. This would guide leadership on creating an environment that naturally cultivates engagement and high performance by focusing intrinsic values. This shift in perspective would align more closely with modern agile leadership principles and empower individuals to be self-driven.

I hope these comments provide valuable insights for refining the expansion pack and further empowering agile practitioners.

Best Regards,
Lamine Haouam

[rjocham]

@KysukeX thanks for your time providing the feedback.

I like your idea of a specific section of 'Output vs Outcome' in the context of 'Output Done' and 'Outcome Done' could be helpful.
I could argue that how Leadership is described is about intrinsic motivation. Might be clearer though.

[rjocham]

@KysukeX would you be willing to provide feedback directly on the PDF? That is how we collected feedback from our early reviewers. That way we see the location of your suggestion and your suggestion. Provided much better context. Right now, I believe there good valid ideas but I am probably making too many assumptions.

[KysukeX]

Sure I would be happy to do that ^^

[rjocham]

Thanks!

[KysukeX]

scrum-guide-expansion-pack_lamine_edit.en.pdf
Here you can find the updated document with my suggestions as comments, happy reading ^^

[rjocham]

Thanks for you work, this is great. We will look at it. Give is a couple of days please.

[ViralGoodAgile]

Thank you for bringing this up, @KysukeX

[rjocham]

We would like to have a chat with you. We are thinking about having a Zoom call. Nothing beats having a live in person conversation.
Let us know if this would be ok for you. Then we can find a suitable time slot.

[rjocham]

@KysukeX here is a Doodle poll. https://doodle.com/group-poll/participate/b6K1zznd
Would be great if one of those time slots works for you.
BTW anyone is invited to join ;)

[rjocham]

Topic: SGEP Exchange #13 #44
Time: Jun 24, 2025 18:00 Zurich
Join Zoom Meeting
https://us06web.zoom.us/j/81667154533?pwd=rsAwNP9MNyGZzYhu6cOZ8fmgtOKqb6.1

Meeting ID: 816 6715 4533
Passcode: 494685