Kanban depends on ongoing improvement by the team, not only of the kanban board they originally design, but also of their guidelines and guardrails (e.g. WIP limits). Starting at about minute 2, this 7+’ video offers further explanation supported by some interesting anecdotes.
Category: Adapting in Turbulence
Manage risk systemically, at the level of project team and organization. Leverage threats, issues, and opportunities for the benefit of all stakeholders. Support organizational change initiatives as needed.
“Product Goals in Scrum”
10.5′ explanation, oriented specifically to Scrum development approaches and the Scrum construct of “product goal”. However, this talk helps understand how, in agile generally, some very, very high-level model of the product – our “product vision” construct – is useful in engaging stakeholders, informing team formation, and representing potential project outputs in a persuasive way. […]
“Business Model Canvas Explained”
Brief (2′) overview of the canvas by Strategyzer, its inventors. Clear visuals, high production values.
“Knowledge Management – The SECI Model”
Great 3′ intro to this key construct for many of today’s projects, especially those where the knowledge needed to build the product does not already exist.
“What is CATWOE?”
Useful introduction to the construct of “root definition” of any “human activity system”, including any project or potential project. CATWOE is the acronym of human activity system (HAS) elements: Customer, Actor, Transformation, Worldview, Owner, Environment. Explained more from a business rather than a systems perspective. A bit “talky” but a helpful into in about 5.5′.
“Soft Systems Methodology in 10 Minutes (nearly)!”
Useful visuals and talk
“Satir Change Model”
Brief introduction (<4′) to the six stages of this model.
“The Story of Codesign”
Animated narrative (<4″) demonstrating principles and key constructs of co-design
“The Cynefin Framework”
The Cynefin Framework is a sense-making device for understanding the sort(s) of environment you and your team/organization may need to make decisions and take action in. Here is a great 8′ video on it by its creator, Dave Snowden.
“How to Get Your JIRA Product Backlog Right”
Nice 27′ video on conceptualizing and managing product backlog. Uses JIRA as an example software platform for managing it “right” and, for conceptualizing it “rIght”, the acronym DEEP – Detailed appropriately, Estimated, Emergent, Prioritized.