Managing Risks with ROAM

In this week’s episode, Ricardo introduces the concept of ROAM Risk (Resolved, Owned, Accepted, Mitigated / Minimized). The process of traversing (ROAMing) risks is a quick way to categorize and act on the relevant risks. This process is widely adopted in agile models such as SAFe (Scaled Agile Framework), mainly during the planning of increments or PI Planning.

Stop Worrying About Things You Cannot Control

In this episode, Ricardo reflects on our desire for control and how the lack of control can create all sorts of psychological threats which could culminate in poor results for the project, for the organization and for you. Ricardo also talks about mechanisms of acceptance, reaction, adaptation and learning that you should put in place to be effective and deliver positive results in an environment where you do not have control.

Understanding Scope Statement, Statement of Work and Requirements

In this episode, Ricardo explains the fundamental difference between the scope you define for the project, the procurement documents you may use to source products and services, and the requirements you identify to set the boundaries of the work you need to do. It is essential to highlight that Ricardo does not restrict these documents to waterfall project management.

Bowtie Method to Evaluate Risks

This week, Ricardo talks about the evaluation of risks using the Bowtie method. The method has its roots in the oil and gas industry, but it is used today in several areas to visualize the event, the threats that could trigger the risk and its consequences. After evaluating the threats and consequences, the team should work together to identify barriers that they can implement to avoid or mitigate the threat or impact.

How to Manage Coupled Dependencies in Projects

This week, Ricardo talks about a type of relationship that is becoming increasingly popular: coupled dependencies. This kind of relationship increases the delivery speed. However, if not appropriately managed, this coupled dependency can increase the risks and the chances of rework. This is due to the set of assumptions teams needed to create these coupled dependencies.

Search in Podcasts
Section Statistics
Total Episodes
Published in 2020
views (total)
Book recommendations

Read Ricardo's reviews of some of the best technical books published.

View recommendations Powered by logo