In this week's episode, Ricardo talks about the form of development approach you will choose, according to the type of project. He comments that one of the Performance Domains of the new PMBOK® is the Development Approach and Lifecycle. And he explains that for some projects, it is better to choose the predictive approach, while for others, the adaptive approach is more suitable. Listen to the Podcast to learn more.
In this week's episode, Ricardo discusses the proper level of control we need to have on a project, preventing the rise of chaos or the construction of an empire out of papers and reports. Hear more on the podcast.
In this week's episode, Ricardo talks about three aspects, features or characteristics of agile that we all should learn and apply. Listen to the podcast to know them.
In this week's episode, Ricardo explains the fundamental differences between 3 roles in the project environment: the product owner and Scrum Master, widely used when applying Scrum and the Project Manager. All of them have critical roles in supporting their projects to deliver the results. However, each of them comes with a different set of accountabilities and responsibilities. Listen to the podcast to know more.
This week, Ricardo presents the last episode about the engineering culture created by Spotify to manage and deliver projects. The Spotify model aims to shape a culture of self-organized, autonomous teams, where independence and alignment combined with a strong focus on people and motivation aim to bring agility at scale with fast decoupled releases and an incredible sense of mutual trust.
This week, Ricardo presents part 2 of 3 about the engineering culture created by Spotify to manage and deliver projects. The Spotify model aims to shape a culture of self-organized, autonomous teams, where independence and alignment combined with a strong focus on people and motivation aim to bring agility at scale with fast decoupled releases and an incredible sense of mutual trust.
This week, Ricardo kicks off a series of 3 episodes about the engineering culture created by Spotify to manage and deliver projects. The Spotify model aims to shape a culture of self-organized, autonomous teams, where independence and alignment combined with a strong focus on people and motivation aim to bring agility at scale with fast decoupled releases and an incredible sense of mutual trust.
In this episode, Ricardo comments on a recent LinkedIn post comparing “Project Management Thinking” with “Scrum Master Thinking”. The post clearly presents one side as a controller, authoritarian, centralizer, etc. and the other as a team player and an enabler. On a rare reply to posts, Ricardo mentioned that this is not the right comparison. This is a comparison between competent and incompetent professionals.
Firms need to develop an appetite for innovation, leverage knowledge about customers, and adopt agile ways of working.
Even though the literature on business transformation is enormous, managerial and organisational appetite for change tends to be limited. Leaders of organisations that are remotely successful are not inclined to change things. Transforming the business is not the same as implementing incremental change or improvements in processes, operations and products. We argue that transformation refers to an organisation achieving a sustainable quantum-leap improvement in performance while transforming the mindsets of employees and thus the culture of the organisation.
In this episode, Ricardo discusses the organizational and individual behaviour that shapes the concept of agility: rapid decision making, flat structure, decision close to the execution, adaptation to change. He also discusses the Agile methods or approaches that intends to help organizations embed the concept of agility inside their organizations. However, the problem goes above and beyond a technique.
In this episode, Ricardo talks about the nightmare of trying to get things done and while managing a lot of works in progress that consume money and effort and do not deliver any value to the organization or project.
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.
Ricardo starts 2018 sharing some tips on how to prepare yourself for the year that is coming. He approaches the need to stay tuned with the technology advancements, as also the attitude and behavior related to the decision making, the amplification of your knowledge base, and finally, the management of our fears when facing the unknown.
