best practices
Why heroes are bad
Most project leaders have been there before: The hero saves the day, yet again. Everyone is grateful because, obviously, if not for the hero the project would have crashed and burned. It seems so lucky that the team can benefit from this all-star who pulls the project out of the fire time and again. So, what exactly would we do without him (or her)?
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.
So you think you’re following Scrum?
I have a prediction. If you take the Nokia “Scrum Test” you are going to score somewhere less than 7. That means you aren’t doing Scrum, you’re doing “ScrumButt:”
A ScrumButt is a sort of like Scrum implementation… but some changes that were too painful have been left out… Companies in this category tend to only [...]
The Weekly Review as an OmniFocus Project
Automation can be a wonderful thing when used right. With information overload at an all-time high (see Is Google Making Us Stupid) it’s a challenge to reap the benefits while avoiding the pitfalls. Systems such as OmniFocus and other GTD-oriented solutions can be hugely successful when adopted — and consistently used. Fraser Speirs has documented [...]
Why projects fail 101
90% of projects do not meet time/cost/quality targets. Only 9% of large, 16% of medium and 28% of small company projects were completed on time, within budget and delivered measurable business and stakeholder benefits. [Standish Group Chaos Report, 1995] There are many reasons for such failures. As per a KPMG survey of 252 organizations, technology [...]
The case against releasing early
In Releasing Early Is Not Always Good? Heresy! author Jason Cohen discusses the reasoning behind “release early” and the argument against. He points out the pitfalls of the rapid-development-early-release paradigm, and introduces a few practical ideas to avoid them. While I don’t agree with all his points (and would add many of my own), it’s [...]
Memory aids
Good management needs good memory. That means being able to remember everything, no matter when you think of it: While I was at the beach getting ready for some ocean kayaking, it occurred to me that I hadn’t spoken with Chris about some new widget development concepts. I tap the screen on my phone, and [...]
Recommended reading
Looking to learn the fundamentals of Scrum? First and foremost I’ll recommend a short hands-on course, but if you can’t swing that try “Agile Software Development with SCRUM (Series in Agile Software Development)” (Ken Schwaber, Mike Beedle) and “Agile Project Management with Scrum (Microsoft Professional)” (Ken Schwaber), two definitive works on the subject.
White-board to wall-space ratio
Patrick Wilson Welsh has a great little rant on this really incomprehensible trend. I think the root of the problem is that too many companies still think of software development as an industrial, assembly line process and too few have really embraced the idea that it’s a creative effort.
Whole teams
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.
Connect
