and<\/em> prescription.<\/strong><\/h3>\n\n\n\nOriginal Meaning:<\/strong> Thoughtfulness means considering context, and taking action only after one has attempted to understand the situation. Prescription means following predefined steps, as in a framework, unchanged and not tailored to the situation, without necessarily understanding or being thoughtful about those steps or what they are for<\/em>.<\/p>\n\n\n\nOur Thoughts<\/strong><\/p>\n\n\n\nThe very first value and I am already confused. From the outset, while the part about thoughtfulness is relatively clear, it still leaves ample room for misguided action. What raises concerns is the phrase “taking action only after one has attempted to understand the situation<\/em>“. An attempt is not a conclusive action; we can attempt many things in our minds, fail, and move on without further consideration. The value of thoughtfulness seems diminished if we merely “attempt” to understand the situation. What if we don’t? Should we blindly take action without clarity on our direction, purpose, and approach?<\/p>\n\n\n\nIn situations that are costly from various perspectives\u2014financially and in terms of timing for the right opportunity\u2014this approach may lead to more uncertain and unverified actions where we “attempted but didn’t reach” a clear understanding of the situation.<\/p>\n\n\n\n
The prescription<\/em> aspect of this statement is equally confusing and doesn’t align with agile principles. It appears that we are expected to “follow predefined steps, …unchanged and not tailored to the situation, without …being thoughtful about those steps.” How is this prescription agile? How is it adaptable? Did the authors mean that we should be “aware” of the prescription without thoughtfulness? Do they still recommend prescription? Or did they intend to convey that there should be no prescription if there is no thoughtfulness? The last interpretation makes the most sense, but why is the prescription still a part of this particular value then? <\/p>\n\n\n\nHow would we phrase it<\/strong><\/p>\n\n\n\nThoughtfulness\u00a0and<\/em>\u00a0flexibility.<\/h4>\n\n\n\nThoughtfulness means considering context, and taking action only after clearly understanding<\/em> the situation. Flexibility means following an agreed-upon framework that serves the particular team<\/em> and product, clearly understanding and being thoughtful about specific steps or what they are for. Revisit the framework to adjust and tailor<\/em> it to enhance the process. <\/p>\n\n\n\n2. Outcomes and<\/em> outputs.<\/strong><\/h3>\n\n\n\nOriginal Meaning:<\/strong> Outcomes mean the direct and indirect end results that occur after one has taken action. Outputs refer to what is directly produced by an action: for example, working software is the output of a programming task. Outcomes require outputs, and both<\/strong> matter; but outcomes are what matter most.<\/em><\/p>\n\n\n\nOur Thoughts<\/strong> and<\/strong> How would we phrase<\/strong> it<\/strong><\/p>\n\n\n\nIt seems like there is some confusion in this statement as well. In our best understanding, the outputs are the result of the specific action, and the outcomes are shaped by the interplay of outputs and external factors. They represent the broader and longer-term impact of actions. So, this would be our explanation of the value: <\/p>\n\n\n\n
Outcomes\u00a0over<\/em>\u00a0outputs<\/h4>\n\n\n\nThe outputs are the immediate results of the specific actions, and the outcomes are shaped by the interplay of outputs and external factors, capturing the holistic consequences of those results over time. Outcomes require outputs, and both matter, but outcomes are what matter most.<\/em><\/p>\n\n\n\nSide note: why is this statement needed, isn’t it self explanatory that the outcome is always more important? <\/p>\n\n\n\n
3. Individuals and<\/em> teams.<\/strong><\/h3>\n\n\n\nOriginal Meaning:<\/strong> Individuals and their differences are important, and should never be forgotten: people are not the team that they belong to. Teams are important, and team spirit is important, and making agreements and compromises for the benefit of one\u2019s team is important. But team interests and individual interests should be in balance: one is not more important than the other in an absolute sense.<\/em><\/p>\n\n\n\nOur Thoughts<\/strong><\/p>\n\n\n\nI like that. It’s a valid and crucial statement, and I’m glad it’s part of Agile 2 in this form. I’m not sure I would change anything about it, except maybe add some guidance on how to implement its principles… <\/p>\n\n\n\n
No need to rephrase.<\/p>\n\n\n\n