Management

Methodology

Metrics

Quality

Requirements

Home » Archive by Category

Articles in Methodology

The Old School Manifesto
Monday, 10 Nov, 2008 – 22:08 | 2 Comments
The Old School Manifesto

As we saw in the last essay, the 80:20 rule seemingly appears in many circumstances. When I was attending college and working as a programmer during the 80’s, there were some commonly accepted tenets that guided our software development processes and behaviors.

What Methodology Do You Follow?
Thursday, 6 Nov, 2008 – 19:20 | 3 Comments

I’m curious to know what software process methodology the readers of my material practice. If you would, please take the poll and share your experiences with a comment. In the comment if you can answer the following questions, it would be greatly appreciated.

Upfront Analysis Saves Time
Monday, 1 Sep, 2008 – 8:00 | One Comment

Work smarter, not harder is common wisdom for solving difficult problems. Analysis is the process of applying our knowledge intelligently to solve difficult problems. Upfront analysis saves time. It’s about working smarter, not harder.

Agile Content is the Goal
Tuesday, 1 Jul, 2008 – 5:13 | No Comment
Agile Content is the Goal

It’s suggested that the web has changed everything. Whatever requirements there were for delivering desktop applications, the requirements for delivering web applications has changed. For the web, the thinking goes; delivery of new features to customers is paramount to remain competitive. Maybe it’s true, but what’s the evidence? My own experience with popular web sites does not support this conclusion.

Does Agile Solve the Right Problem?
Sunday, 22 Jun, 2008 – 22:32 | 3 Comments
Does Agile Solve the Right Problem?

David Starr argues that Agile doesn’t work because business operations aren’t Agile, and his remedy is to have Agile business practices that embrace change: “Embrace continuous integration of the enterprise.” Customers don’t want continuous change; they want a great product the first time they purchase it, so they can spend more time serving their customers and invest more money on other important needs. While your product delivery is most important to you and your company, it’s likely not the most important need for your customer. Agile simply solves the wrong problem.

Agile Isn’t a Process
Friday, 15 Feb, 2008 – 0:01 | 17 Comments
Agile Isn’t a Process

 
I’m reminded of an interview I had with a young company for a Software Director role.  They were at point where they were ready to begin rapidly acquiring new customers.  When a new customer signed, …

Refactoring Isn’t A Design Methodology
Monday, 28 Jan, 2008 – 0:01 | 10 Comments
Refactoring Isn’t A Design Methodology

 
One of the difficulties I have with the Agile software methodologies and its proponents is that they go to far.  They are often susceptible to hyperbole while hawking their methodology like used car salesmen.   Their …

Commit To Excellence
Monday, 24 Sep, 2007 – 0:01 | One Comment
Commit To Excellence

When I was a high school student I was an avid competitor in the sport of wrestling. It’s an extremely demanding and punishing sport: requiring extreme stamina, strength, skill, agility, and mental toughness. You have to have a strong mind to compete successfully in wrestling. When you’re in the 3rd period of a match, you’re exhausted, and your opponent continues aggressively to push the action, only the tough-minded continue to fight and pull out a win.

The Software Process Wars
Friday, 14 Sep, 2007 – 10:18 | No Comment
The Software Process Wars

The Agile software development practices are in their infancy stage as evidenced by the number of variants that are being promoted in popular print and usage today:  Scrum and XP being two popular variants.  Clearly …

Why Software Process Adoption Fails
Thursday, 6 Sep, 2007 – 22:48 | 2 Comments
Why Software Process Adoption Fails

Have you ever wondered why software process has yet to flourish in the software industry?  Why, after many decades of industry growth, there is no consensus on a process methodology or even best practices?  Why …