Beyond "Outcomes Over Outputs"
Without the underlying coherent story — spanning multiple time horizons — the OKRs are just a process hoop, and without "closing the loop" there is no learning:
Source: hackernoon.com
Without the underlying coherent story — spanning multiple time horizons — the OKRs are just a process hoop, and without "closing the loop" there is no learning:
Source: hackernoon.com
When you take this humble approach — instead of "installing" a bunch of artifacts, tools, roles, and rituals AKA doing Agile — I think you’re embracing the true spirit of Agile.
Source: hackernoon.com
Because at the end of the day, your job is not to write code. Your job is to create business value.
Source: hackernoon.com
By decoupling accommodation and the physical location, we decentralize housing and empower the individual to instantly switch to alternative locations.
Source: hackernoon.com
If you have a proper "content security policy" your users are safe
Source: hackernoon.com
I don’t live to work anymore, I work to live.
Source: hackernoon.com
Forget about Agile and Scrum on the team level. Start with the org. Visualize the work as it is really happening ... with all the gnarly dependencies. Have 150 person stand ups if that is the true size of the team.
Source: hackernoon.com
Your users don’t care if your design is unique or not. They just want it to work for them
Source: hackernoon.com
Links relevant to my work and interests: IT, agile, startups, Internet, web development, databases, programming, design patterns, work motivation... (Popular topics)