Excellent advice found on 43 folders: Before you sweat the logistics of focus: first, care. Care intensely. We spend a great deal of time working on “engaging the team” or engaging ourselves when what we really need to do is find the willpower to focus on the foremost problem at hand. As Merlin points out, [...]
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.
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 [...]
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.
Recently I tried out a variant on methodology that I’ll dub Rational Scrum. I’ve been trying to put together a few thoughts about the overall process for months, and finally found some time for it.
Just as people have specializations, so do processes. Applying one process to all situations is just as wrong as calling your [...]
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.
The price of software problems is very high: As much as 50% of development and 100% of all maintenance costs can be attributed to software defects. Often, this price becomes apparent late in the software life cycle—quite often after the software has reached its operational phase (after the software ships)—as previously undetected defects are discovered [...]