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 [...]
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.
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.
How do you ensure that one person doesn’t derail your entire project? Most of us have been there before. Maybe it’s a co-worker who doesn’t work well with the team. Maybe it’s your boss, who has to oversee every single decision even though he’s an overtasked bottleneck. Either problem poses a critical risk to your project: Delays, mistakes and rework because one person isn’t part of a streamlined effort. Learn how the situation can be improved, realizing positive gains in this habitually entrenched process.
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 [...]
Is ALM at odds with Agile? Application Lifecycle Management is often perceived as a traditional waterfall technique, but not always. Collabnet clearly believes there’s a convergence between ALM and at least Scrum, a process that is well-known as an “agile-oriented” technique for improving project efficiency and visibility. According to Bill Portelli, CEO of Collabnet, we [...]
Management tools probably don’t bring to mind excitement and visions of “getting things done” the agile way. Nevertheless, it’s an important aspect of running any project — whether agile or not — and there are some tools, believe it or not, that are easy to use, hugely helpful in managing a project and sometimes even [...]
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.
An operational, successful team is more than a set of interchangeable, anonymized skill sets. Would you buy a car that had never been tested in a safety lab? Of course not, and yet the software industry, particularly the commercial industry (as compared to Military, for example) has been ploughing along without whole teams for decades–a trend that seems to be getting more and more negative attention.
Looking for a fast-paced, easy to digest introduction to Scrum? Check out Hyrax International LLC’s Scrum Workshop or contact me directly to discuss an on-site Rational Scrum workshop. Recently updated for 2010, this workshop will get your whole team up to speed and using Scrum in record time.