Author Archive

The second Roseto Salon: Getting Individual Recognition in a Teamwork Environment

October 13th, 2011 No Comments

The second Roseto Salon will be held on Tuesday, October 18, 2011, from 6:30 to 8:00 PM, in the Lobby Conference Room of Cisco Bldg. 24, 510 McCarthy Boulevard, Milpitas, California 95035.
The topic is “Getting Individual Recognition in a Teamwork Environment.”

read more...

Risk-taking and the “Freedom to Fail”

January 5th, 2011 1 Comment

“Take calculated risks–that is quite different from being rash.” General George S. Patton Especially in high-tech, progress is made only by taking risks. Taking a risk implies the possibility of partial or complete failure. So how can we decide what risks to take, and how can we encourage the identification of those risks and the willingness to go forward with them, i.e., institute a culture of risk-taking? One of the most important factors in encouraging risk-taking is the “freedom to

read more...

Agile Methods and Process/Quality Standards

June 15th, 2010 No Comments

In a nutshell, agile methods give the development team a great deal of freedom as to what activities to carry out; if they choose activities, including documentation and review/approval, that conform to the standard, then they can claim conformance and obtain any certification that may be available.

read more...

Baseball and BP

June 13th, 2010 No Comments

Newsweek editor-in-chief Jon Meacham asks: why can’t the Gulf of Mexico oil spill be handled more like the missed-call (non) perfect game in Detroit? The umpire admitted he blew the call, the pitcher who had his perfect game taken away shook the ump’s hand, the fans cheered, eyes grew damp. Good sportsmanship, apologies, “be honest, admit mistakes, and keep moving.” My reaction was: why wasn’t the non-perfect game handled more like the oil spill? Why didn’t the pitcher sue the

read more...

AGILE DEVELOPMENT METHODS AND SOFTWARE QUALITY

May 13th, 2010 4 Comments

“Quality is more than the absence of bugs” In recent years, a strong trend has emerged toward the use of “Agile Methods” for development of software and of software-intensive systems. While many forms of Agile exist, they tend to be characterized by values such as “communication, simplicity, feedback, courage, respect” (Extreme Programming [“XP”], Ref.1) and “Interactions and individuals over processes and tools; Working code over comprehensive documentation; Customer collaboration over contract negotiation; and Responding to change over following a plan”

read more...