Agile

In this week's episode, Ricardo talks about customizing methods and approaches in project management. He explains that we insist on finding a solution that solves all the problems in the project, but in reality, there is no "One size fits all." No methodology or approach is universally perfect for all scenarios, and the nature of the project and the very definition presuppose something unique.

In this week's episode, Ricardo talks about cadence in the project. He explains that cadence dictates the rhythm of project deliveries and gives some examples of cadence, such as the frequency of the heartbeat and the rhythm of a military parade.

In this week's episode, Ricardo explains the difference between agility and agile methods. He says that if the project uses an agile method, it may not necessarily have agility. And on the other hand, a project that uses the predictive model may have agility. Ricardo comments that, regardless of the method used, it is first necessary to have a critical sense of urgency, agility and adaptability in the organization.

In this week's episode, Ricardo talks about the risks that can be associated with technology projects. He explains that the approach to managing technology projects, where releases are delivered faster and more frequently, can allow aspects that are not thoroughly thought out and validated to produce security flaws, risks, and even use and encouragement of unexpected behavior when used.

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.

Listen to podcasts on Agile features, the difference between Business Agility and Agile, small project management, and 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.