Why Agile test planning makes software quality superior than in Waterfall

When comparing the frequency and granularity of test planning and execution in products developed under Waterfall and Agile methods, we observed that in Agile: we have more tests, in the story level and we have a progressive increment of test coverage all over the product and higher frequency running those tests.
Continue reading “Why Agile test planning makes software quality superior than in Waterfall”

The importance of the regular alignment between different Organization levels

(Somewhere in the EU Sky) Normally when an Agile Transformation starts, it starts by the bottom of the structure. It’s easy to get Scrum up and running in small Agile Teams.
When Agile Transformation enters in a scale process, the challenge starts. It is mandatory regular alignment across the different portfolio levels to make sure that the Transformation occurs.
Continue reading “The importance of the regular alignment between different Organization levels”

Why is so hard to educate a waterfall project manager to take a role in a Scrum Team?

(Cabanas Beach, Portugal) A lot was written already in this blog about why we have more advantages adopting Agile methods. The truth is, once an organization decides for an Agile Transformation, adopting Agile methods and, particularly Scrum practice, to train and educate resources can be a terrifying challenge. Even with training, the roles will change. The background experience required for a Scrum Master or Product Owner role, for instance, is very different from what normally it comes with an experienced resource acting as project manager in waterfall methods since many years.
Continue reading “Why is so hard to educate a waterfall project manager to take a role in a Scrum Team?”