Scoring and Evaluating Software Methods, Practices, and Results

[article]

 

133

Pair programming

 

 

 

2.83

 

134

Clean-room development

 

 

2.50

 

135

Formal design languages

 

 

2.50

 

136

ISO Quality standards

 

 

2.00

 

 

 

 

 

 

 

 

 

 

Neutral Practices

 

 

 

 

 

137

Function point analysis (backfiring)

 

1.83

 

138

Use Case points

 

 

 

1.67

 

139

Normal customer support

 

 

1.50

 

140

Partial governance (low risk projects)

 

1.00

 

141

Object-oriented metrics

 

 

0.33

 

142

Manual testing

 

 

 

0.17

 

143

Outsourcing (development < CMM 3)

 

0.17

 

144

Story points

 

 

 

0.17

 

145

Low-level languages (current)

 

 

0.00

 

146

Outsourcing (maintenance < CMM 3)

 

0.00

 

147

Waterfall development

 

 

-0.33

 

148

Manual change control

 

 

-0.50

 

149

Manual test library control

 

 

-0.50

 

150

Reusability (average quality materials)

 

-0.67

 

151

Capability Maturity Model (CMMI Level 1)

-1.50

 

152

Informal progress tracking

 

 

-1.50

 

153

Outsourcing (offshore < CMM 3)

 

-1.67

 

 

 

 

 

 

 

 

 

 

Unsafe Practices

 

 

 

 

 

154

Inadequate test library control

 

 

-2.00

 

155

Generalists instead of specialists

 

-2.50

 

156

Manual cost estimating methods

 

-2.50

 

157

Inadequate measurement of productivity

-2.67

 

158

Cost per defect metrics

 

 

-2.83

 

159

Inadequate customer support

 

 

-2.83

 

160

Friction between stakeholders and team

 

-3.50

 

161

Informal requirements gathering

 

-3.67

 

162

Lines of code metrics (logical LOC)

 

-4.00

 

163

Inadequate governance

 

 

-4.17

 

164

Lines of code metrics (physical LOC)

 

-4.50

 

165

Partial productivity measures (coding)

 

-4.50

 

166

Inadequate sizing

 

 

 

-4.67

 

167

High-level languages (obsolete)

 

 

-5.00

 

168

Inadequate communications among team

-5.33

 

169

Inadequate change control

 

 

-5.42

 

170

Inadequate value analysis

 

 

-5.50

 

 

 

 

 

 

 

 

 

 

Worst Practices

 

 

 

 

 

171

Friction/antagonism among team members

-6.00

 

172

Inadequate cost estimating methods

 

-6.04

 

173

Inadequate risk analysis

 

 

-6.17

 

174

Low-level languages (obsolete)

 

 

-6.25

 

175

Government mandates (short lead times)

-6.33

 

176

Inadequate testing

 

 

 

-6.38

 

177

Friction/antagonism among management

-6.50

 

178

Inadequate communications with stakeholders

-6.50

 

179

Inadequate measurement of quality

 

-6.50

 

180

Inadequate problem reports

 

 

-6.67

 

181

Error-prone modules in applications

 

-6.83

 

182

Friction/antagonism among stakeholders

 

-6.83

 

183

Failure to estimate requirements changes

-6.85

 

184

Inadequate defect tracking methods

 

-7.17

 

185

Rejection of estimates for business reasons

-7.33

 

186

Layoffs/loss of key personnel

 

 

-7.33

 

187

Inadequate inspections

 

 

-7.42

 

188

Inadequate security controls

 

 

-7.48

 

189

Excessive schedule pressure

 

 

-7.50

 

190

Inadequate progress tracking

 

 

-7.50

 

191

Litigation (non-compete violation)

 

-7.50

 

192

Inadequate cost tracking

 

 

-7.75

 

193

Litigation (breach of contract)

 

 

-8.00

 

194

Defect potentials > 6.00 per function point

-9.00

 

195

Reusability (high defect volumes)

 

-9.17

 

196

Defect removal efficiency < 85%

 

-9.18

 

197

Litigation (poor quality/damages)

 

-9.50

 

198

Litigation (security flaw damages)

 

-9.50

 

199

Litigation (patent violation)

 

 

-10.00

 

200

Litigation (intellectual property theft)

 

-10.00

 

It should

About the author

TechWell Contributor's picture TechWell Contributor

The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email editors@techwell.com.

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!

Upcoming Events

Sep 22
Sep 24
Oct 12
Nov 09