// archives

agile software development

This tag is associated with 5 posts

Scrum versus Kanban

Pawel Brodzinski makes a very succinct and key observation regarding the differences of Scrum and Kanban (and also links to a handful of opposing views by Ken Schwaber, David Anderson and Mike Cohn). If you want to figure out how Scrum and Kanban differ, this is a great starting point — be sure to check [...]

Common oversights in choosing methodology

Changing the way a business operates is a daunting task. It involves assessing and understanding the strengths and weaknesses of the current organization, identifying solutions to the weaknesses without compromising the strengths and, ultimately, changing the way people work. Above all, people tend to be resistant to change — and this is the most common issue that arises when adopting a new methodology.

Why Agile isn’t enough (and why it doesn’t work)

Agile methods are powerful tools when used properly — but as with all tools, they can be misused. The critics of agile methods are many and vocal, calling Agile a poorly thought-out “shortcut” that fails to get the job done. And with 90% of projects failing to meet objectives, the criticism is valid. So is Agile just hype or is there something to it? And if there is, why are project success ratios so abysmal? Here’s the scoop on why Agile doesn’t work and what to do about it.

Scrum is not an agile methodology

People have lost sight of the fact that Scrum is not a methodology. I see comments such as “Scrum is killing agile” and it drives home, with emphasis, that there’s a huge disconnect between understanding what an agile methodology is and what Scrum is (and I know I’m beating a dead horse, but it’s important [...]

Making Scrum work: Common failings in adopting Scrum

Scrum can be remarkably beneficial in many kinds of software projects. But, as with any process, methodology or management technique, when used inappropriately it can cause more problems that it solves. In this article I’ll discuss some of the common misconceptions and “lessons learned” as related to Scrum.

Twitter

Connect

Add to Technorati Favorites


View Zacharias Beckman's profile on LinkedIn
Follow zbeckman on Twitter

Open Calais
Creative Commons License