Please login or join to subscribe to this thread
I'm guessing that the question is prompted by the Organizational keynote? I must admit that using output and outcome in the way that Josh describes is a bit foreign to me but that is a different discussion.
For me the difference is tangibility. The output is tangible artifacts such as the traffic signs in the video. The outcome is the result and might not be tangible but measurable.
Outcome is strategic
Output is tactical
Is this really new, or simply more recognized? Is it restricted to only Agile?
I agree with Andrew. I'm not sure it's an "Agile" thing.
I think it's more of a leadership approach.
I have worked with leaders that are very outcome and output focused.
I think if you are responsible for development and direction setting a strategy, then you have to know your charted course and desired business outcome. Personally, once I have established that, I tend to focus my energy on the inputs.
Is the design of a product or service (to be delivered in operations) an output or an outcome?
In these cases, there is alignment with the strategy of the organization and / or company.
I would like to better understand the use of strategy and tactics applied to these concepts.
A simple example of this is documents produced during the life of a project. It is tempting to look at requirements or design documents and believe that we are delivering value, but real value is when we deliver scope to a customer and they can achieve their business needs with it.
Process & artifact-intensive delivery approaches emphasize outputs whereas lean and agile methods focus on outcomes such as business value realization, early risk reduction, improved quality and increased team and team member engagement.
In your opinion this concept is applicable to projects with an adaptive (agile) development approach, is that it?
Another perspective of analysis. I can take a predictive approach and deliver the product (service) to the end customer.
In this case can I talk about outcome instead of output?
Most of our outcomes follow the output after an amount of time. (For example, the percentage of clients using the application requires an amount of time to measure this outcome.)
While we have traceability between the two, it is too far in the future to allow managing teams by outcome.
Please login or join to reply