Community Blog

Scrum is a straightforward framework to develop complex software products in a complex environment but hard to practice.

Continuing to grow your skills is vital in a field where technologies, frameworks, and skills change so rapidly. So what do you do? How do you get other developers in your team excited about their craft?

Hello awesome people. How was your week? In today's vlog I would like to talk about one of the most important aspects of Scrum, that is the Definition of "Done".

Often we work harder in Scrum teams, but not necessarily smarter. Therefore the way we work has to change. Five tips for more effective agile work.

Should the PO really balance the level of technical debt? I just had this conversation yesterday at Sweden's "big" agile conference, Agila Sverige.

The other day, I picked up my son from soccer and he had a huge smile on his face. I asked him how it was and he answered with an even bigger smile “Awesome!”.

Some people just happen to learn more from short movie clips. And they can be a great way to bring some humor in. Also available as a Youtube Playlist.

Warning - this post is not about Scrum. It is about Technical Debt in my home!!! Please do not judge me!!

Software developers are mostly guys, happy to work by themselves at night in dark rooms. And they turn coffee, cola and pizza into code. Right?

DevOps es un área de mi interés desde hace varios años. En Diciembre de 2014, en la CAS de Barcelona, di una charla en Inglés sobre la experiencia haciendo que DevOps fuera uno de los pilares de la agilidad en la DVLA -Una suerte de DGT británica-.

One of the most important things we can do to help individuals and teams improve is coach them to embrace the agile mindset. The Manifesto for Agile Software Development provides values and principles to help guide teams in navigating the complexities of product delivery.

Hello great people of the world. Welcome back to Professional Software Delivery with Scrum (PSD) blog series with yours truly. This time we're going talk about how to use Scrum And DevOps. I am interested to discuss this topic because it's quite common I get a question from someone in the agile community, "Should I use Scrum or DevOps?".

I would like to discuss Scrum and XP because I often get a question "When should I use Scrum or XP?" from people in the community.

In my last post about Professional software teams creating working software David Corban made a good point. How do you determine what "Free from fault or defect" means?

Many organisations wrestle with the seeming incompatibility between agile and release management and they struggle with release planning and predictable delivery.

There is a frustrating misunderstanding of reality when one thinks that the Product Owner can reject a single story at the Sprint Review.

Many teams are struggling with delivering modern software because they are not building with Test First Principals.

One of the most common critiques about Scrum that I've heard from smart software engineers are "Scrum does not care about technical practices, Scrum is for wimps". I've also heard managers down the hallway say that "Scrum is for wreckless developers because its main concern is only about fast delivery".

There are a number of things that you have to think about when selecting a modern source control system. Some of that is purely about code, but modern source control systems are about way more than code.

The PSD training teaches the whole Scrum Team on how to do real Scrum. They work in Sprints, create Done software and use the appropriate tools and practices for it. It is a unique experience on how really good Scrum feels like.

As the saying goes, it’s not about the destination, it’s about the journey. The same could be said about DevOps and its implementation in an organization. Yes, the result is magic since it aims to deliver daily business value, but the journey is even more interesting. This journey is full of organizational, technological, but especially human discoveries.

Comme dit le dicton ce n'est pas la destination, mais la route qui compte. On pourrait dire la même chose pour DevOps et de son implantation dans une organisation.

Pour avoir un aperçu de la perception et compréhension des personnes de quelque chose, il suffit de regarder les réseaux sociaux.

To get an insight into people's perception and understanding of something, just look at the social networks.

Recently discussing design and programming with an external programmer, he explained me his approach of defensive programming. But before going in detail of his explanations, Wikipedia help us to define the defensive programming: