Posts in process Category

Jeff Patton says that agile development is more of a culture than a process. It is quite refreshing to read constructive a constructive discussion on the topic, though it did put pressure on me to really understand what culture meant, and it can have several meanings. I think agile can be agile because it asks you to follow a set of principles without being restrictive about how we do that. [Continue]

The proponents of the agile methodologies wanted to change the way software development was done. I think that changes have happened, but unfortunately most of them are superficial ones, leading to failures and more notoreity for the underlying philosophy. Scott Nelson explains how some aspects of agile methodologies can be wrongly used. [Continue]

Martin Fowler talks about avoiding common Scrum pitfalls. A refreshing read. But Martin is able to point out the root cause of most of the faulty adoptions in a single sentence: When you just try to do the practices, and don’t adopt the philosophy, it’s not going to work terribly well. [Continue]

Kent Beck says that XP is in the danger of getting stagnated because of a combination of limited adoption and no opposition. It has become like the standards, which everyone accepts in principle, but no on adopts in practice. I like XP, it was like a breath of fresh air after working through various waterfall models and burning the hands. [Continue]