Wednesday, 19 February 2014

"Forced Agile" - What's your reason to resist it?

Interesting article about the 'crisis' between the implementation of what I call "forced agile", and the resistance many professionals experience.

In many organizations, Agile kind of creeps in starting with that one team that experiments it and gets so excited with the result that it naturally spreads it gradually to the entire organization.
However, in some organizations, Agile is imposed from above as a management strategy and everyone has to change the way they work, even if it doesn't really see whichever benefits Agile Methodologies bring along. That creates resistance.

Is it okay to resist to Agile, or should you check your real motivations to this resistance?

Fact: Agile changes the way we work.
Fact: Resistance to change is the typical human reaction.
These two factors combined often create tension in a new imposed environment, as happens in an Agile forced one.
That's why the subject of culture change is such a strong topic when addressing the changes in an organization into an Agile mindset.

Despite the implementation of strategies to help mitigate this, it's important for each of us to check our real motivation to these resistance.

The author of the below article addresses some interesting topics on this matter. It's worth to read it.
Here's the link:

And have fun, as always! :)

Tuesday, 18 February 2014

Spike and Stabilize, by Liz Keogh

"By doing TDD – writing our tests first, or before we’ve got feedback on what it is we’d like to achieve – we are creating a premature commitment. The principles of Real Options say, “Never commit early unless you know why”. If you’re working with uncertainty, and if you can avoid adding investment before getting feedback – for anypractice – then you will actually go quicker and be able to respond to discovery faster. You will be more agile."

This is how Liz Keogh sums her approach on software development beyond TDD.
In her article, Liz defends that we don't always have to do TDD before-hand, 'cause sometimes we just aren't sure of where we're heading to. Therefore, she suggests developers to Spike and Stabilize first, that is, "trying one or several things quickly to get feedback, then stabilizing the end result after we’ve managed to eliminate some of the uncertainty around what we’re doing."

Now, note that she does not defend this approach instead of TDD. On the contrary she suggests you should master TDD before you make this move in the way you work.

It's really worth to take a look!

Here you are:

Have fun! :)

Friday, 7 February 2014

How to choose the best approach on software development methodologies?

Nice article on finding the balance between innovative development approaches - because of the principles behind them - AND the right choice for our reality.

It's worth to take a look!

Here it is: The Best Approach to Software Development


The relation between Agile and Ownership in Agile Environments

Nice article about Trust and Ownership in an Agile environment!

Focuses on WHY we do thing instead of just following RULES, and also how different control levels of leadership, according to the author, affect the team outcomes.

Here it is: Trust and Ownership – a Perfect Couple in an agile world!!!


Wednesday, 5 February 2014

Learning / reviewing Scrum Ceremonies with funny and easy videos

The Scrum Training Series provide animated videos about Scrum Ceremonies, that can be learned in a fun way.
The videos go through the basics of the ceremonies, and add additional information about the principles behind the ceremonies. It also includes quizzes to check your understanding of these principles.

Check them out in here:

And have fun! :)