Monday, April 12, 2010
Importance of quality, time and features
In an ideal world quality, time and features should be given equal weight in the software development lifecycle.
The ranking for most firms it seems is:
1) quality
2) time
3) features.
Quality should always be given precedence. If things need to go, due to scheduling, etc..., you need to throw out features first, then time and always try to maintain quality standards.
Makes sense and we practice that here too.
Subscribe to:
Post Comments (Atom)
Exploring ELK (Elastic) Stack for hack-a-thon
At my current gig, our group finally got to do hack-a-thon week and I joined a team project that tied together a few of the technologies I...
-
When I first started using WebEx 3 years ago for my current job I accidentally set the WebEx One-click meeting topic to my colleagues' n...
-
I was having the toughest time trying to sync a new folder tree in my depot. I was getting this error: //depot/Some-path/some-sub-path/....
-
If you're doing security/cryptographic testing with Java - especially with JMeter - you might encounter errors in your testing where you...
No comments:
Post a Comment