Agile 2014 Interview with Ken Rubin on Agile Risk Management

From the The Reluctant Agilist Blog
by
Adam Weisbart | Agile | Agile 2013 | agile 2014 | agile 2015 | Agile 2017 | Agile 2018 | Agile Alliance | agile coaching | Agile Metrics | Agile Practice | agile transformation | Agile Transition | agile2014 | agile2015 | agile42 | Agilistocrats | Alistair Cockburn | autism | Bas Vodde | BigVIsible | Bob Tarne | book review | Brian Bozzuto | business agility | carson pierce | Center for Non-Violent Communication | Certification | Certified Scrum Master | Certified Scrum Product Owner | Chet Hendrickson | Chris Li | Coaching | commitment | Communication | conteneo | Craig Larman | cross functional teams | CSM | CSPO | DAD | Daniel Gullo | Dave Prior | David Anderson | David Bernstein | David Bland | David J Anderson | Dhaval Panchal | diana larsen | Digital Agency | Digital PM | digitalpm | Disciplined Agile | Disciplined Agile Delivery | Distributed Teams | Don Kim | dpm | dpm2013 | drunken pm radio | drunkenpm | drunkenpm radio | eduscrum | emotional intelligence | empathy | Enterprise Agile | Essential Scrum | esther derby | Excella | Gangplank | Gil Broza | Howard Sublett | Individuals and Interactions | Jean Tabaka | Jeff Sutherland | Jesse Fewell | Jessie Shternshus | jim benson | johanna rothman | john miller | Jukka Lindstrom | Jutta Eckstein | kanban | Kanban Pad | kanbanfor1 | Ken Rubin | Kenny Rubin | Kim Brainard | lacey | Language | Large Scale Scrum | Larry Maccherone | LeadingAgile | lean | Lean Kanban North America | LeanKit | LESS | lkna | luke hohmann | lyssa adkins | Maria Matarelli | Mark Kilby | Marshall Rosenberg | Michael Sahota | Mike Vizdos | Modern Management Methods | modus cooperandi | Natalie Warnert | Nic Sementa | Non-violent communication | North American Global Scrum Gathering | NVC | Olaf Lewitz | ├średev | ├średev 2013 | organizational agility | Organizational Change | overcommitment | Patrice Colancecco Embry | Paul Hammond | personal kanban | personal productivity | personal project management | Peter Saddington | PMBOK | PMI | PMP | podcast | portfolio management | Product Development | Product Owner | Product Ownership | productivity | project management | Project Management Institute | Rally | reluctant agilist | Renata Lerch | retrospective | Richard Cheng | Roman Pichler | Ron Jeffries | SAFE | Safety | Sallyann Freudenberg | scaling agile | Scaling Scrum | Scott Ambler | Scrum | Scrum Alliance | Scrum Gathering | Scrum Master | ScrumMaster | self organizing teams | SGPHX | SGPHX 2015 | Shane Hastie | social engineering | SolutionsIQ | SoundNotes | sprint planning | Team | teams | Temenos | The Improv Effect | Things | Tom Perry | troy magennis | User Stories | value | Vivek Angiras | waste | Waterfall | What We Say Matters | why limit wip | women in agile | Woody Zuill | show all posts

About this Blog

RSS

Recent Posts

What to do when your team won't to talk In Retrospectives w/ Adam Weisbart

Using Improv to Improve Your Listening Skills w/ Jessie Shternshus

Melissa Watts - Tips for ScrumMasters

Chris Bailey - Hyperfocus and Optimizing Your Productivity

Scott Ambler on PMI's Acquisition of Disciplined Agile



I had the chance to visit with Essential Scrum author Ken Rubin at Agile 2014. One of Ken’s primary focuses right now is Agile Risk Management. His presentation “Agile is Risk Management” addresses the fact that if it is applied well, agile will inherently help reduce the risk you would normally see on projects. His approach involves a lightweight way of addressing risk that let’s you reduce your exposure without having to cope with a lot of the heavy machinery that traditional risk management typically involves.

Posted on: July 30, 2014 02:01 PM | Permalink

Comments (3)

Please login or join to subscribe to this item
Anonymous
Risk management should not be something you do once at the beginning of a project. It should be part of the regular operating rhythm of any project. Whether you take a very structured approach to assessment, with quantitative analysis and a separately managed risk budget, or a qualitative approach with risk management costs baked in to the project budget, risk management is only beneficial if it is part of execution, as well as planning. Ken's comment that we do our risk assessment at the beginning of the project, when we know the least about the risks, reflects poor practice. Our risk assessment, like our requirements gathering, should be an ongoing process that improves the resilience (anti-fragility, if you prefer) of the endeavor over the course of the project.

Thanks for sharing!

Please Login/Register to leave a comment.

ADVERTISEMENTS

"He may look like an idiot and talk like an idiot, but don't let that fool you. He really is an idiot."

- Groucho Marx

ADVERTISEMENT

Sponsors