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.

Fix your boss (or, reduce risk to quality using a matrix approach)

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.

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 [...]

Should Training be an Integral Part of a Project Budget to Increase Project Profitability?

Organizations that are “training challenged” must learn to do things differently. This includes delegating authority along with responsibility, being inspirational to employees, building trust and improving communication — all of which are direct benefits of a comprehensive process that incorporates training. Take a look at part two of Should Training be an Integral Part of [...]

What do you mean, SQA isn’t testing?

Software Quality Assurance (SQA) and Structured Software Testing (SST) are completely different fields. Every single book on the topic (textbooks, course materials, you name it) make this clear. In fact, most emphasize how important it is that these fields be completely separate. Consider:

Quality Assurance is responsible for auditing and ensuring all aspects of work meet [...]

Articulating the value of training

Training budgets are one of the first to go in a down economy. I first pointed this out in Finding Strategic Learning Funds, but there’s ample evidence to be gathered. When the money isn’t there, organizations start casting about for any program they deem expendable. But the unfortunate truth is that training is the best [...]

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.

Formal inspections: An introduction

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 [...]